Never break your email outreach chain again.
Email a list of prospects, follow up automatically inside the same conversation, and stop the moment anyone writes back — even a colleague they forwarded it to.
Coming soon · plans will start at $29 / month
Dana, saw Fairing on your checkout. Solid tool, but you're paying per order for a two-question survey…
One more on the Claude piece — it sets the whole survey up from one prompt. Want it?
Yes — send the prompt. We've been meaning to look at this.
Three sends. One chain. Then Dana says yes.
Scroll through it: follow-ups arrive as replies, a human answers, the sequence stops itself, and your phone gets the draft.
The real inbox, one scroll long. Step 3 never sent, because step 3 wasn't needed.
Follow-ups that can only be replies
Your follow-up shows up under the first email, not as a new one. Your prospect sees one conversation — not three strangers.
Under the hood: no parent Message-ID, no send. Subject stays Re: the original; References carries the whole chain.
Any human reply ends it. So does an install.
A colleague replying from a different address. An out-of-office with a return date. "Talk to Raj instead." A signup in your app with no email at all. Each one is understood, and each one stops or reschedules the chain.
We watch whether your email actually arrives
Every sending domain gets checked daily. If a problem starts, we slow that domain down before it becomes one — and no new domain sends a cold email until its DNS passes and its ramp has started.
Under the hood: authentication pass rate, blocklists, bounces, reply rate, and an enforced ramp.
What happens to one prospect, link by link.
One example, start to finish. Halcyon Skin is a made-up store; Fairing is a real survey app that Luv Survey competes with.
Halcyon Skin runs Fairing
The storefront scan reads the public site, detects the app, captures the shop's platform ID; a contact-finder you connect names Dana, and her address is verified before she ever enters a sequence.
A note, not a newsletter
Prose. One named competitor. One specific gap. A two-second ask. Zero links. Sent inside the store's business hours from a warmed lookalike domain, never from your real one.
Same chain, four days later
The follow-up is a reply. Dana opens one conversation with the first note quoted underneath. Filters see a reply between two parties, not a fresh campaign.
Someone answers. Anyone.
Dana replies — or forwards it and Raj replies from an address you never targeted. The reply carries your Message-IDs in its headers, so it matches Halcyon Skin regardless of who sent it. The sequence stops. Sibling tracks at the company pause.
They signed up without replying
Your app posts a signed install event. Halcyon Skin matches. Cold track ends, welcome flow starts from your real domain. Step 3 never arrives for someone who's already a customer.
Five screens. Nothing to configure daily.
Click any screen to zoom. You read replies, approve prospects, and edit four short emails. Sending, threading, reply matching and domain health run without you.
One inbox, every domain, both of you
Replies threaded and classified. Reply inline from the address the chain started on. Engaged replies arrive with a draft written from your own product guide — you are the send button.
Company × product, one state
Sequenced, engaged, installed, deferred, referred, bounced, suppressed. One company holds one active track at a time.
Four steps, previewed on a real row
Per-step reply rate. One template per product × competitor detected. Reply-in-chain is greyed out and on, forever.
The first line is already true
Store, detected competitor, country, person, verification. Approve, skip, or suppress.
One colour per domain
Healthy, throttled, or paused — with every signal that decided it.
new threads. Every follow-up is a reply. The editor can't do otherwise.
tracking pixels. We never secretly track opens or rewrite your links — it's the fastest way to land in spam. Your read is per-step reply rate.
inbox. Every sending domain, every seat, one place. No IMAP to configure, no mailbox to buy — replies land as events.
Things it will never do.
Most outreach tools have checkboxes. These are enforced in code, and nobody can uncheck them at 11pm.
- 01Start a new thread
Every follow-up is a reply. The only first email it ever starts is to a person you were referred to — and you approve that one.
- 02Send after a reply
Any human reply in the chain, from any address, ends the sequence. So does an install, an opt-out, or a bounce.
- 03Track opens or rewrite links
The pixel is the biggest avoidable hit to inbox placement. You measure replies and installs instead.
- 04Send from your main domain
Cold email goes out from a second domain you own —
getacme.comnext toacme.com, pointing at the same site — so your invoices and customer email never share its reputation. Everyone doing this well does it this way. - 05Pitch the same company twice at once
One company, one active conversation. If you sell two products, the second waits its turn.
- 06Blow past the ramp
Per-sender and per-domain caps that only advance while every health signal stays green.
They installed without replying? Good.
Your app posts one signed event. The cold track ends and your welcome flow takes over from your real domain.
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're already paying you. 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 starts. Pipeline shows installed. Nobody had to tell you.
Example account · illustrative numbers
Plans will start at $29 a month.
We're running it on our own outreach first. Leave your address and you get first access when plans open, with founding pricing held for your first year. One email when we open, nothing else — and if we follow up, it'll be a reply to that first email. Obviously.
- Reply-in-chain sequences, threading invariant locked
- Stop on reply from any address in the chain
- Stop on install or signup from your own app
- One inbox across every sending domain and seat
- Domain health monitor with enforced ramp and auto-throttle
- Prospect discovery with competitor-app detection
- Phone alerts with a drafted reply for engaged threads
Reading on the chain.
Cold email compliance checklist: CAN-SPAM, GDPR and CASL in plain English
What the law actually requires of a B2B cold email, with the checklist we hold our own product to.
Keep Your Chain vs. Instantly, Smartlead and Lemlist: what's actually different
A fair comparison. The volume tools win on scale; we're built for a founder selling their own product.
How many cold emails can you send per day? The honest math for 2026
Per mailbox, per domain, per person: the numbers that keep you in the inbox, and how to get to 180 a day safely.