Cold email platform with warmup and a unified inbox
Inbox warmup, one inbox for every sending account, campaign sequences and six deliverability tools — without five separate subscriptions.
Built for: PixelGrowth · Updated 2026-09-01
Who it's for
Agencies and outbound teams running cold email across many sending accounts.
The problem
Agencies running cold email were stitching together four SaaS subscriptions: one for sending, one for warmup, one for list hygiene, one for copy. Every handoff between them lost data and nobody could attribute a reply back to a subject line.
What it does
- 01Inbox warmup on owned mailboxes, with a reputation trend and a 30-day volume ramp.
- 02A unified inbox: replies from every sending account in one view, answered from the account they landed on.
- 03Campaign sequences bound to sending accounts, with live open, reply and bounce counts.
- 04Six deliverability tools: List Cleaner, Copy Writer, Subject Tester, Send Planner, Audit Report and Spintax.
- 05Analytics comparing campaigns and warmup activity.
- 06Custom open-tracking domain and seed inboxes for placement testing.
Building something in this shape? Book a 30-min scope call →
The product
Mailbox addresses and my own account email are blurred — some of those sending identities belong to clients, and a warmup dashboard is exactly the thing you don't publish addresses from. Everything else is the live app.
Walkthroughs
How it's built
Role: Sole engineer — platform architecture, Supabase schema, tool suite, warmup system, deliverability logic.
What's in the codebase
The build
- 01Built a 23-route platform covering accounts, campaigns, contacts, pipeline, inbox, unibox, warmup, analytics, workflows, and API docs.
- 02Shipped six first-party tools as their own routes rather than buried features: List Cleaner, Copy Writer, Subject Tester, Send Planner, Audit Report, and Spintax.
- 03Built the warmup system to run against real mailboxes on a dedicated domain, so reputation is built on the same infrastructure that later sends.
- 04Unibox consolidates replies across every connected sending account into one thread view, so a reply is answered from the account it landed on.
- 05Workflow engine with a shared catalog module — the single most-imported file in the graph — so new automation steps register in one place.
Engineering decisions
Every tool has its own URL. That means an agency can hand a VA a link to the List Cleaner without giving them the campaign dashboard, and it means each tool is independently linkable from the docs.
components/workflows/lib/catalog.ts is the most-imported file in the codebase. Every workflow step type is declared there once. Adding a step is one entry, not a change across the builder, the runner, and the display layer.
Warmup mailboxes live on a domain the platform controls. Renting warmup from a third party means your sending reputation is built on someone else's IP pool and disappears when you churn.
Want your own cold email platform?
Bring the problem, not a spec. 30-minute call — I'll tell you what it actually takes to build, what I'd cut, and what it costs. No decks, no discovery phase invoice.