Cold outreach CRM · coming soon
Every follow‑up, in the chain it started in.
Keep Your Chain sends your outreach, writes each follow-up as a reply to the last one, and stops the moment someone answers — even when the answer comes from a person you never wrote to.
Plans will start at $29 / month · built for founders who send their own email
Dana
Why the chain matters
A follow-up that starts a new thread is a stranger. A reply is a conversation.
It reads as one note, not four.
Your prospect opens a single conversation with the whole context quoted underneath. They never have to remember who you are, because the first email is right there.
Filters see a reply, not a blast.
Mailbox providers score a message carrying In-Reply-To and References differently from a fresh send. It is the difference between "someone I've heard from" and "someone new."
Every reply finds its way home.
Because each message carries the chain, a reply from a colleague, an assistant, or a forwarded inbox still matches the right prospect — and stops the sequence.
The product
Five screens. Everything hard is underneath.
Simple on the surface: an inbox, a pipeline, a sequence editor, a prospect list, and a domain health board. The sending, threading, reply matching and deliverability work happens where you never have to look at it.
One inbox for every sending domain
All replies, across every domain and both of you, threaded and classified. Reply inline and Keep Your Chain sends from the right address with the right headers, so the chain never breaks. Engaged replies arrive with a drafted answer written from your own product guide — you are the send button.
A pipeline that knows what already happened
Every company and every product track with its state: sequenced, engaged, installed, deferred, referred, bounced, suppressed. Filter by competitor detected, bulk-approve prospects, and see reply rate per sequence without exporting anything.
Sequences that can only reply
Write four short steps. Set the delays. Preview any step rendered against a real prospect. The editor will not let a step after the first go out as a new message — reply in chain is the default, and it is locked.
- Per-step reply rate, so you learn which line works
- One template per product × competitor detected
- Zero links in steps one and two, one in step three, by design
Prospects that come with a reason to write
Built-in scrapers read public storefronts and app-store reviews, detect which competitor a store already runs, find the person, and verify the address before it ever enters a sequence. Approve, skip, or suppress — the first line of the email is already true.
A postmaster for each domain
DMARC pass rate, Google reputation, spam rate, blocklists, bounces and reply rate — per sending domain, refreshed daily. Ramp is a schedule the monitor enforces, and a domain that drifts is throttled before you would have noticed.
The reply reaches your phone. So does the draft.
Only a human reply that scored as engaged or referred pushes. Out-of-office, bounces and "no thanks" are logged, never pushed. Tap the alert, the thread opens with a draft in the reply box, and the primary action is Send.
Invariants
Things it will not do.
Most outreach tools have settings. Keep Your Chain has rules. These are enforced in code, not in a checkbox someone can uncheck at 11pm.
- Rule 01Never a new thread
A step after the first cannot send without a parent Message-ID. Subject stays
Re:the original, verbatim; References carries the full chain. - Rule 02Never sends after a reply
Any human reply in the chain — from any address — ends the sequence. So does an install of your app, an opt-out, or a bounce.
- Rule 03Never a tracking pixel
No open tracking, no link rewriting. Measure replies and installs, the two numbers that were ever real.
- Rule 04Never from your real domain
Cold mail goes out from lookalike domains that redirect to the real one. Your product's domain keeps its reputation for the mail that matters.
- Rule 05Never two strangers from one shop
One company holds one active track at a time. Product A from one domain and product B from another in the same fortnight reads as a spam operation. Tracks queue.
- Rule 06Never past the ramp
Daily caps per sender and per domain, enforced by the health monitor, advancing only while every signal stays green.
If you sell software
They installed without replying? That is the system working.
Your app posts a signed install event. Keep Your Chain matches the shop, ends the cold track, and hands the relationship to your welcome flow on your real domain. No follow-up three arrives for a customer who signed up after follow-up two.
Mon — step 1 lands.
Thu — step 2 lands. They install that afternoon and start onboarding.
Sat — step 3 lands: "wanted to make sure this didn't get buried." They are already a paying customer. First impression: you don't know who your customers are.
Mon — step 1 lands.
Thu — step 2 lands. They install that afternoon.
Thu, 4:02 PM — install event matches the shop. Track ends. Welcome flow starts from your product domain. Pipeline shows installed. Nobody had to tell you.
From the blog
Reading on outreach and the chain
Why your cold email follow-up should be a reply, not a new email
The case for sending every follow-up in the same email chain: what the recipient sees, what the filter sees, and the three headers that make it work.
A cold email that landed in my primary inbox three times: a header-by-header teardown
What one well-run sequence got right — and the two things it got wrong.
Stop sending when they reply — including when someone else replies
Forwards, out-of-office, referrals, installs, and the reply-detection cases most sequencers miss.