Bridge: outreach that does not burn the mailbox
A sales workspace to find and enrich leads, then reach them across email and LinkedIn from one inbox, with AI drafting follow-ups.
- Role
- Full-stack engineer
- Timeline
- Jan 2025 to now
- Status
- In development
- Stack
- Django, Celery, Postgres, Redis, Next.js, TanStack
- Problem
- Sales teams juggle separate tools for lead data, email and LinkedIn, and burn mailboxes by sending too fast.
- What I did
- Built the campaign engine with per-mailbox pacing, the threaded inbox, and the Next.js client with its spreadsheet-style enrichment workspace.
- Result
- One workspace from enrichment to paced, multichannel outreach, in active development.
The system
Outbound sales teams run sequences across several channels and mailboxes. Send too fast and a mailbox gets flagged; thread replies wrong and a prospect gets a follow-up after they already answered.
Built the campaign engine, email threading and AI agents on a shared Django backend, and wrote the Next.js client, including a full rewrite, almost entirely myself.
- client LOC
- 86k
- Django apps
- 16
- frontend commits
- 370+
How a campaign step goes out. Hover or tap a node to see its job.
Pacing per mailbox
Campaigns are multi-step sequences with waits, conditions and A/B variants, and each prospect moves through its own state machine. Before a step sends, the pacing service checks that mailbox's daily cap and minimum gap, counting manual replies from the same mailbox too. A full mailbox defers the prospect to the next slot instead of failing the whole campaign.
Threads that match how email works
The unified inbox parses Message-ID, References and In-Reply-To headers, walks to the thread root, normalizes subjects and collapses each conversation to its latest message. Inbound senders are matched to CRM contacts so a reply stops the sequence for that prospect.
A spreadsheet in the browser
The client rewrite centers on an enrichment workspace that behaves like a spreadsheet: a virtualized grid with a formula bar, keyboard navigation, find, clipboard and selection, tested with more than a hundred test files. Auth tokens stay in cookies behind a backend-for-frontend, never in JavaScript.
Decisions worth defending
Defer, do not fail
A capped mailbox is a scheduling problem, not an error. Campaigns keep moving and nothing burns.
Decision log for the agents feature
Each choice records the options, the decision and its reversal cost, which kept a large refactor reviewable.