Why We Built Our Own Outreach Pipeline (Not Another SaaS Inbox)
We stopped stacking outreach SaaS on top of Gmail. Here's the pipeline we actually run — dedup, warmup, reply routing — with screenshots from prod.
We already ship production AI — WhatsApp on vessels 1,000+ messages a week, Academy intern workflows, SEO agents on the same FastAPI router. Outbound was the awkward cousin: Hunter for emails, something like Instantly for sends, replies in a Gmail tab nobody checked on weekends. It worked until it didn't. A prospect replied on Thursday. I found it Monday, buried under newsletters. Same person existed in two lists with slightly different titles — we almost emailed them twice. "AI personalization" was {first_name} plus a sentence scraped from LinkedIn About. Not great. So we built outreach into the stack we already run. Not because cold email is magic — because coordination and deliverability kept losing to tools that don't talk to each other. !Outreach Agent dashboard with deliverability, DNS health, and funnel counts/images/blog/outreach-pipeline/outreach-admin-dashboard.png The admin panel real prod, not Figma The GIF below is the actual dashboard we use — outreach funnel, sent prospects, unified email inbox. No mock data. !Animated walkthrough: outreach dashboard, sent prospects, and email inbox/images/blog/outreach-pipeline/outreach-pipeline-walkthrough.gif What was breaking Replies vanishing. Sends go from arsalan@mail.appopoleis.com. Replies should update CRM state. They didn't — they sat in Gmail until someone remembered to look. Duplicate rows. Two discovery runs, same email, different company spellings. Without a hard dedup gate, you send twice and look spammy. Deliverability as a one-time DNS task. SPF/DKIM/DMARC green on day one means nothing if you blast 40 emails on a fresh domain at 2am UTC. Warmup has to be code, not a spreadsheet reminder. Empty inbox bodies. Resend's webhook gives you metadata. HTML-only replies showed up in admin with blank bodies — useless when you're trying to decide if someone is warm. What we built | Piece | What it does | Why it exists | |-------|----------------|---------------| | Discovery | Finds ops-heavy companies via DDG
Appopoleis Team