The domains, the mailboxes, the sequences and the replies — run in one place, per client. Every message that reaches a real person left because a human read it and approved it.
14-day trial. No card required.
Timing is decent — we're specifying for two builds in Q1. Can you send dimensions and lead time? Copying our PM.
A live walkthrough — it runs itself, and the sidebar is clickable. Example data, not a real client account.
This is the whole job, in the order it happens. The machine does the reading and the writing. Step three is the handover, and it is not a setting you can switch off.
Every mailbox feeds one inbox. Replies are matched back to the lead and the sequence that produced them, so a thread arrives with its history attached rather than as a loose email.
The reply is classified — interested, a question, an objection, a referral, out of office, unsubscribe — and a response is drafted in the client's voice, from what the account actually knows about them.
The draft sits in a queue until a person acts on it. Approve and it goes. Edit and your version goes. Do nothing and nothing happens — silence is not consent, and no timer decides for you.
The approved reply goes out from the mailbox that started the conversation, in the same thread. Interested replies become opportunities you can work; everything else is filed, not deleted.
Most outbound tools are judged on how much they will do without you. This one is built around two things it refuses to do.
No campaign launches, no lead is pushed and no reply is sent without a person clicking it. The scheduled jobs that run in the background are read-only syncs. The single one permitted to write can only ever pause something.
That is a structural guarantee rather than a promise: the send path is not reachable from anything that runs on a timer.
How it is held: a test fails the build if a scheduled job ever gains a send path.
An unknown figure renders as a dash and says so. Nothing is defaulted to nought, averaged into existence, or filled in to make a dashboard look complete.
It matters most where it is least visible: a fabricated 100% inbox rate on a mailbox nobody has tested is how an estate gets burned quietly, over weeks, while the screen stays green.
How it shows up: a reply means one person who actually wrote back. Auto-responders are counted as auto-responders.
What needs a person, before anything else. The fourth tile has no number because no test was run — so it shows none.
| Mailbox | State | Inbox rate |
|---|---|---|
| dana@northwind-precast.com | Ready | 98% |
| sales@northwind-precast.com | Ready | 97% |
| ops@northwind-build.com | Warming | — |
| quotes@nw-precast.co | DNS incomplete | — |
Per mailbox, not per account. Two of these four have never been tested, and the screen says exactly that.
Cold email fails at the infrastructure long before it fails at the copy. All of it lives in one place, per client.
| Domains & mailboxes | Buy domains, provision mailboxes, and watch the records that decide whether mail lands.MX · SPF · DKIM · DMARC, per mailbox |
|---|---|
| Warm-up | Warm-up state tracked per mailbox, so a mailbox enters rotation when it is ready rather than when the calendar says so.Ready · warming · held back |
| Deliverability | Reputation and inbox placement per mailbox, so a problem shows up as a number before it shows up as silence.Untested reads as a dash, never a zero |
| Campaigns & sequences | Multi-step sequences with variants. Performance is compared weekly and a losing variant is paused for you to look at.Paused for review, never rewritten |
| Prospecting | Build a list by role, seniority, company size, industry and location, with verified addresses.The cost of a search is shown before you run it |
| Signals | Reach people when something changed — a new role, a funding round, a hiring push, a tender.Timing beats volume, and it is cheaper |
| One inbox | Every mailbox in one thread view, with the conversation in place.Reading a reply is not three clicks from deciding on it |
| Pipeline | Interested replies become opportunities with the thread attached, and out-of-office is handled as a delay rather than a dead end.Referrals are caught and offered as contacts |
| Separate by client | Each client's data lives in its own database — not a column with a client id in it.One client's data has nowhere to leak to |
Classification, the approval queue, out-of-office, referrals, opportunities.
02DNS, warm-up, reputation, placement and send health, per mailbox.
03Variants, windows, limits, and numbers that count people.
04Free search, paid reveal, and leads when something changed.
A fourteen-day trial with no card, then Starter, Growth or Agency. The plan limits are published; the monthly prices are not yet, and the pricing page says so rather than guessing.
It drafts; you decide. Each draft is written from what the workspace knows about the client and the thread, and carries a confidence tag. You approve, edit, schedule or skip. Nothing goes out otherwise.
No. It is not a setting. The build has a test that fails if any scheduled job can reach a send path.
Bring your own or provision them from inside the workspace at a quoted price. Either way each mailbox is checked for MX, SPF, DKIM and DMARC and warmed before it sends.
The return date is extracted and the lead is parked until then. They are never counted as a person replying. Anyone named as covering is offered to you as a contact, and nothing is sent to them until you approve.
Each workspace is a separate database. The security page lists how that and the other guarantees are held.
The trial is free for fourteen days with no card. Plan limits are published on the pricing page; monthly prices are not yet set, and a plan is agreed in writing before anything is charged.
If you already run outbound for clients, this is the control plane for it. If someone runs it for you, this is where you watch it happen.