How Unified Email API gets built

One endpoint. Every inbox.

Adoptability 67/100 · technical · developer tools

The build path at a glance

Implementation plan (5 weeks to first paid pilot)

The dossier maps a 5-week sequence from zero to first paying pilots. Headlines:

Week 1: ICP-specific landing + pricing + first integration
Week 2: Auth + first cohort onboarding flow
Week 3: Reporting + admin shell + outreach launch
Week 4: First 50 outbound conversations, 5 paid pilots
Week 5+: Iterate on the workflow that paid pilots actually used

Suggested tech stack (Wes-stack aware)

The recommended stack is buildable solo or with a small team:

Hosting: cPanel + Caddy + Postgres or SQLite
Backend: Node 22 or PHP 8.1
LLM layer: Claude API via prompt-cached batches
Email + auth: Stripe + magic links
Frontend: server-rendered HTML + lightweight Alpine.js for state

MVP scope (what's in, what's not)

The dossier names the single workflow this product MUST solve in v1, plus what to explicitly leave out (mobile app, partner API, second workflow). Discipline that lets you ship in 30-60 days instead of 6 months.

First 7 build tasks (ranked)

The full ranked task list - what to build day 1, week 1, week 2 - is in the dossier. Each task names the specific deliverable and exits criteria.

30/60/90 launch plan

Day 30: what good looks like. Day 60: pivot signal vs persistence signal. Day 90: kill criteria vs scale criteria. Full text in the dossier.

What we'd implement for you

If you'd rather we run the launch, the operator-partnership scope for this product (timeline, cost band, exit terms) is in the dossier's final section.

This page shows the structure of what's in the dossier. The specifics - which ICP, which week, which task - cost $5. We don't fake live customer outcomes; the math is Fermi, not promises.