Rarity Index logo Rarity Index case study
Start a Project
Back to systems

Case Study 03

Snapshot: May 2026

Break Room, from website ownership to client delivery.

Break Room is a small-business website practice with an actual operating surface behind it: a public Next.js portfolio site, transparent pricing, audit-backed positioning, Resend-backed contact handling, Stripe and Calendly conversion paths, AI-readable site metadata, and cloneable client templates. The point is not just to sell websites. It is to prove the site problem, set a clean scope, and deliver the replacement.

  • 321tests recorded green
  • 11dashboard pages
  • 100Lighthouse promise
  • $2.5kstarting price
Break Room public site proof showing the website ownership offer, pricing, audit request, and booking path

Working Surfaces

The page now shows Break Room itself, not a borrowed proof image.

These artifacts separate the public brand, the private operator guardrails, the client delivery lane, and the system map. The old run-form and lead-table screenshots are out; every remaining proof image opens as a sharp full-size SVG.

Break Room public site proof showing the ownership offer, audit request, pricing, and booking path
Public site frame The customer-facing surface centers ownership, pricing, audit proof, booking, and a direct contact path instead of hiding the offer behind a sales deck.
Break Room private operator guardrails showing dry run review, suppression sync, sender health, budget limits, and human approval
Operator guardrails The private command surface is represented without exposing old run screens: dry-run review, suppression sync, sender health, budget limits, and human approval stay explicit.
Break Room delivery lane showing consult, scope, build, launch, and handoff steps for client websites
Client delivery lane The Moss and Maple template proves the replacement website lane is already scaffolded: scope, build, launch, handoff, and support are repeatable.
Break Room system map showing public offer, site audit proof, responsible contact controls, checkout, AI assist, and client delivery
System map Public site, audit proof, contact controls, checkout, AI assist, and client delivery stay visible as one service system without publishing private operator tables.

Operating Model

Break Room is strongest when the sales motion and delivery motion stay connected.

The public site makes the offer inspectable. The private operator surface keeps contact work controlled. The delivery lane turns an approved scope into a finished client project.

Site audit engine
  • Public discovery and site checks start with observable website problems, not a generic pitch.
  • Lighthouse and heuristic audit modes turn slow pages, weak SEO, and broken UX into concrete proof.
  • Qualification, deduplication, and confidence checks happen before any message drafting.
  • Dry-run mode previews operator actions before any send path is allowed.
Contact control
  • Claude CLI or Ollama can draft email and form messages from a structured site brief.
  • Resend handles email delivery while SQLite records contacts, sequences, outcomes, and API usage.
  • Follow-ups run on day 3 and day 7, then auto-stop on reply, bounce, complaint, or unsubscribe.
  • Form outreach captures filled/submitted artifacts and skips CAPTCHA paths.
Client delivery
  • The public site explains the offer, pricing, audit promise, process, and contact path.
  • Starter delivery is documented at $2,500 for a 5-page site, contact form, basic SEO, and support.
  • The Moss and Maple template proves the replacement website lane is already scaffolded.
  • Portfolio-site webhooks and suppression sync support the outbound engine rather than sitting apart from it.

Guardrails

Outbound work moves only after budget, compliance, and sender-health checks.

Compliance and sender safety
  • Legacy scrape mode requires an explicit environment gate; `--source places` is the default path.
  • Every send checks suppression state before outreach and syncs local suppression with the cloud store.
  • List-Unsubscribe and one-click unsubscribe headers are part of the documented email path.
  • Deliverability guards pause sending above bounce and complaint thresholds.
Dashboard scope
  • Execution pages cover run review, contacts, follow-ups, templates, deliverability, and form-worker state.
  • Templates, Deliverability, Jobs Queue, Suppression List, and How It Works cover review and settings.
  • The command center runs through a Hono API, vanilla dashboard, SQLite, Resend, Lighthouse, and Playwright.
  • The outreach guide records 321 tests passing with TypeScript clean for the current engine snapshot.

Stack

One stack for public conversion, one stack for local execution.

  • Next.js
  • Tailwind
  • Vercel
  • Stripe
  • Calendly
  • Resend
  • Upstash Redis
  • Hono
  • SQLite
  • Playwright
  • Lighthouse
  • Google Places
  • Claude CLI
  • Ollama

Need a website practice that connects audit, conversion, and delivery?

That is a systems problem: proof, scope, contact handling, conversion, and client production have to share one operating model.

Email Rarity Index