- Query discovery defaults to Google Places API.
- Existing output and file imports keep prior runs usable.
- Legacy Maps scraping is explicitly gated instead of silently used.
- API budget checks can abort before a run burns required quota.
System Deep Dive
Snapshot: May 2026
Lesswork Leads, lead intelligence with reportable proof.
Lesswork Leads is the prospecting side of the Break Room ecosystem: it finds local businesses, audits their websites, scores the evidence, drafts outreach from the findings, and leaves behind generated reports that make the opportunity visible before anyone sends a pitch.
Proof Surfaces
The page now shows the product, the reports, and the architecture.
These artifacts come from the local Lesswork source and generated February 25, 2026 report output. Contact details in the package summary are redacted; every image opens full-size through the proof viewer.
Current Pipeline
Load leads, enrich sites, audit evidence, then score the opportunity.
The implementation is practical and local-first: Places or file input, SQLite state, website enrichment, heuristic and Lighthouse audit paths, AI drafting options, and dry-run-safe output.
- Site checks cover HTTPS, responsive signals, calls to action, contact forms, modern-design indicators, and load time.
- Lighthouse adds performance, accessibility, best-practices, SEO, and average score rows.
- Form details are extracted so outreach can tell whether contact-form delivery is possible.
- Only audited leads continue into email delivery paths.
- Already-contacted, suppressed, duplicate, and low-confidence leads are filtered before sending.
- Business-level dedupe keys reduce repeated outreach to the same prospect.
Reports
Generated PDFs turn a scrape into a visible decision packet.
- The 6-page run report shows lead count, email coverage, hot/warm/cool/cold distribution, average score, and average performance.
- Coverage rows include PSI, SEO, Tech Stack, TLS, Content, DNS, RDAP, Moz, Apollo, Social, Market, Reviews, Privacy, Bot Ready, and Risk Flags.
- SEO and tech-stack rows expose specific fixes like multiple H1s, missing hreflang, analytics, booking widgets, ecommerce, server software, and ad pixels.
- The 16-page package artifact proves Lesswork can assemble market summaries and per-lead detail into a client-readable deliverable.
- The public screenshot is deliberately redacted so the site shows capability without publishing raw prospect contact data.
- The PDF metadata identifies the current report generator as Chromium/Skia output, so the page avoids old PDF-engine claims.
AI And Outreach
Qualification and drafting are connected to the audit brief.
- Local Ollama/mem-agent qualification asks whether the lead is real, needs help, and has red flags.
- Responses are parsed into structured qualification, reason, and observations.
- Parse failures default safely so one model error does not stop the pipeline.
- Claude CLI or Ollama drafting receives the audit brief and qualification observations.
- Form-only messages can be drafted for prospects without usable email paths.
- Template fallback keeps previews and review output available if AI drafting fails.
- Resend delivery stays behind dry-run/no-send preview behavior unless explicitly armed.
- Suppression, bounce/complaint guardrails, and domain delivery checks run before sending.
- Contact-form outreach uses Playwright, CAPTCHA skip logic, rate limits, circuit breakers, and screenshot artifacts.
Data Boundary
Current truth: SQLite now, Postgres planned.
The public page should not pretend the future migration already shipped. The current implementation is SQLite-backed; Postgres is documented as the next multi-client step.
- Lead state, contacts, suppressions, campaigns, form outreach attempts, and API usage currently live in the local lead database path.
- The current verified quality signal is 321 passing tests across 28 Vitest files.
- The source surface audited here contains 94 TypeScript files under `src`.
- The Postgres migration doc is marked planned and frames the need for client isolation, concurrency, remote access, and stronger transactions.
- That plan stays valuable, but it is treated as roadmap evidence rather than a shipped production claim.
- The page is now written so future upgrades can replace this boundary cleanly when the migration lands.
Stack
Chosen for source-to-report lead operations.
- TypeScript
- Hono
- SQLite
- Vitest
- Playwright
- Lighthouse
- Google Places
- Resend
- Claude CLI
- Ollama
- Chromium PDFs
- Vercel
Need lead intelligence that brings its own evidence?
That takes sourcing, audit proof, AI review, report generation, and guarded outreach working as one system.