Case study / 03
Lead Room
Local-First Outreach Workspace
- Role
- Product design and full-stack development
- Year
- 2026 / Ongoing
- Stack
- JavaScript / Node.js / Express / SQLite / n8n / Google Places API
The overview
Lead Room is a private, local-first workspace that turns business searches into a persistent outreach queue. Express and SQLite preserve CRM state while n8n handles enrichment. Two callers reserve different leads, record outcomes, schedule follow-ups, and use editable Arabic and English templates. This case study uses synthetic data.
01 / The challenge
Repeated business searches created duplicate work, refreshed enrichment data risked overwriting human-maintained notes and statuses, and two callers could unknowingly receive the same lead. Research, outreach drafts, assignments, call outcomes, and follow-ups also lived across separate tools.
02 / The response
I made Express and SQLite the durable source of truth and narrowed n8n to stateless discovery and enrichment. Transactional upserts refresh external information while preserving CRM history, and an atomic reservation flow assigns each caller a different eligible lead. Editable Arabic and English templates replaced unpredictable generated copy, keeping the workflow fast, local, and understandable.
What shipped
- 01Atomic two-caller reservations prevent duplicate lead assignments
- 02State-preserving deduplication refreshes enrichment without erasing notes, statuses, assignments, or follow-ups
- 03Editable Arabic and English outreach templates with WhatsApp links and optional email delivery
- 04Versioned SQLite migrations, WAL mode, indexes, backups, and transactional campaign ingestion
- 05Defensive rendering, safe-link validation, CSV formula neutralization, and idempotency-aware email claims
- 06103 passing deterministic database, server, rendering, and website-classification tests
- 07Responsive operational views for campaigns, lead inbox, call sessions, follow-ups, and funnel insights
Next case study
Architecture Publishing