Product 03 · The email operating system
Warp
Every email personal.
Every one remembered.
Knowing when to stop matters more than knowing when to send.
The category
Bulk or personal.
Every tool makes you choose.
Marketing platforms broadcast to a list that opted in. CRMs log an email as an activity against a deal that doesn't exist yet. Cold-email platforms will send at volume — from their infrastructure, from their domains, on their terms.
For a luxury home furnishing brand selling to design professionals, the sender's identity is the credibility. Routing the relationship through a third party's servers to gain volume is not a trade worth making — which leaves every team in the same place: sending one at a time, from a real name, and accepting the ceiling that comes with it.
That ceiling is the trap, and it compounds. Because sending is manual, volume stays low. Because volume is low, nobody builds a system. And the natural workaround — one generic message you can paste faster — makes the writing worse exactly as it makes the volume higher.
Warp removes the choice. Thousands of individually written emails, from your own name and your own servers, with a system that remembers every one of them. The sending was never the hard part. The memory was.
Screen 01
Eighteen hundred conversations
that used to just stop.
The highest-revenue screen in the product — and the one that replaced pure memory.
| Person | Studio | Last sent | Overdue | Next | |
|---|---|---|---|---|---|
HCHarriet Colefax
h.colefax@… |
Colefax & Vane Studio | P1 · 22 Jun 2026 | 39 days overdue | P2 | Send P2 → |
DMDiarmuid Moran
d.moran@… |
Moran Interiors | P1 · 22 Jun 2026 | 39 days overdue | P2 | Send P2 → |
TATheodora Alexiou
t.alexiou@… |
Alexiou Architects | P2 · 04 Jul 2026 | 27 days overdue | P3 | Send P3 → |
ELElke Lindqvist
elke@… |
Nordiska Rum | P1 · 11 Jul 2026 | 20 days overdue | P2 | Send P2 → |
JWJames Whitcombe
james@… |
Whitcombe Design | P3 · 19 Jul 2026 | 12 days overdue | P4 | Send P4 → |
RBRosa Bellandi
r.bellandi@… |
Studio Bellandi | P2 · 26 Jul 2026 | Due today | P3 | Send P3 → |
- What this is
- How overdue each follow-up is. The oldest here has been waiting thirty-nine days.
- Why it exists
- The buying cycle runs about six months. The first email almost never closes anything — the follow-up is where the business is, and it is the part that requires memory, which is precisely the part humans reliably drop.
- Business outcome
- 1,860 live conversations that would previously have ended after a single email. At this order value, that queue is the single most valuable object in the system.
- What this is
- The next phase, already written, one click from sending — P2, P3, P4, per person.
- Why it exists
- A queue that tells you somebody is overdue but leaves you to write the email has moved the work rather than removed it. Five phases, each with its own copy and its own delay, set once and then left alone.
- Business outcome
- A prospect can go quiet in March and be followed up correctly in September, by whoever happens to open the screen.
- What this is
- “Send all P2” — an entire overdue phase, in one action.
- Why it exists
- Sends stagger automatically to protect deliverability, and anyone who has replied or bounced has already been removed before the batch runs. The bulk action is safe precisely because the exclusions happen upstream of it.
- Business outcome
- A month of neglected follow-up clears in a morning, without a single email landing somewhere it shouldn't.
- What this is
- “Anyone who has replied has already dropped out of this queue.”
- Why it exists
- The worst email in outbound is the automated follow-up that arrives after a human has already answered. It tells the prospect, unmistakably, that nobody was reading. The sequence is re-evaluated before every send, not when it was scheduled.
- Business outcome
- This is the behaviour that makes automated outreach safe to turn on at all. Where the sender's credibility is the pitch, it is the difference between using automation and not being able to.
Screen 02
Bulk that doesn't
read like bulk.
The trade-off between personal and scalable was never real. It was a tooling assumption.
I came across {company}'s work on {project} — {personalization}.
Everything we make is commissioned to order, and we work with studios across {city}. If it's useful, I can send the new collection with sizes and lead times.
Best,
Ayaan
I came across Colefax & Vane's work on the Chelsea townhouse…
- What this is
- Real variables in the body — first name, company, city, and the specific project you actually noticed.
- Why it exists
- Nobody can hand-write two thousand emails, and everybody knows it. The industry's answer is to make the email generic. The better answer was to make the sending automatic and leave the writing specific.
- Business outcome
- Personalisation and volume stopped competing. That was the entire trap, and it was never a law of nature — just the shape of the available tools.
- What this is
- 1,840 recipients — with bounced and already-replied addresses removed before you got here.
- Why it exists
- Exclusions belong upstream of the send button, not in the operator's memory. A dead address left on a list gets mailed four more times across the sequence and takes your sending reputation with it.
- Business outcome
- A 1.8% bounce rate across 38,600 sends, in a market where cold outreach routinely runs five to ten times that.
- What this is
- A live preview of recipient 1 of 1,840, with the variables already resolved.
- Why it exists
- Friction belongs at the moment of consequence. You should be able to read the actual sentence a real designer will receive before two thousand of them go out under your name.
- Business outcome
- Broken merges — the empty greeting, the wrong studio in the second paragraph — get caught before they become two thousand small embarrassments.
- What this is
- One button. 1,840 individually composed emails, staggered on the way out.
- Why it exists
- They send through the company's own mail servers, from real named people, with proper signature blocks and correct conversation threading — so the follow-up arrives in the same thread instead of announcing itself as a machine.
- Business outcome
- Automated outreach indistinguishable from a person writing to you — because it is a person writing to you, at scale.
Screen 03
This is the memory.
The answer to the question the old way of working could never answer: have we contacted this studio, and when?
| Batch | Phase | Sent | Outcome | Total | |
|---|---|---|---|---|---|
| Autumn collection — London studios
06 Aug 2026 at 03:32 |
Initial outreach | 1,840 sent | 22 bounced & removed | 1,862 leads | View leads Send P2 → |
| A note on your recent project
05 Aug 2026 at 07:28 |
Initial outreach | 960 sent | 14 bounced & removed | 974 leads | View leads Send P2 → |
| Collection preview — second note
05 Aug 2026 at 06:43 |
Follow-up 2 | 1,240 sent | 96 replied | 1,240 leads | View leads |
| Lookbook — Nordics
29 Jul 2026 at 09:13 |
Follow-up 4 | 480 sent | 41 replied | 480 leads | No more phases |
- What this is
- Bounces detected, classified and removed from the list in the same motion — 22 out of 1,862 on the largest batch.
- Why it exists
- Replies, out-of-office auto-replies and bounces look similar and mean completely different things. A real reply stops the sequence. An auto-reply deliberately doesn't — they're away, not answering. A bounce removes the address entirely.
- Business outcome
- Deliverability treated as a business metric rather than an engineering detail. 1.8% across 38,600 sends, which is what keeps the good emails arriving at all.
- What this is
- Every batch keeps its own next action — send the next phase, or nothing at all if the sequence has finished.
- Why it exists
- The record and the machinery are the same object: what happened, and what happens next, in one row. Replies are already excluded from whatever goes out next.
- Business outcome
- Duplicate outreach — the one mistake a relationship sale cannot absorb — became structurally impossible rather than a matter of memory.
- What this is
- 1,284 batches and 38,600 sends, permanently searchable and grouped by campaign.
- Why it exists
- “Have we contacted this studio?” used to be unanswerable, which meant it was answered by guessing. Now it's a search rather than an archaeology project.
- Business outcome
- A colleague can pick up any account cold, because the history is in the system rather than in somebody's head.
What changed
Same team. Same hour.
One of these mornings produced eleven emails. The other produced eighteen hundred, each addressed to a specific person about a specific thing.
Before · one at a time
11
emails by lunchtime
Identical body text, pasted. No database, no follow-up, no record anybody else could see. “How many did we send this month?” — genuinely nobody knew.
After · Warp, one click
1,840
emails by 09:05
Every recipient gets their own name, studio, city and project. Every send recorded. Every follow-up scheduled — and cancelled the moment they reply.
Personalisation and volume were never a trade-off. They were a tooling problem.
| Before | After | |
|---|---|---|
| Lead database | None | 12,400 people, researched once |
| Emails sent, recorded | Unknown — no record existed | 38,600, every one logged |
| Follow-up mechanism | None | 1,860 queued and dated |
| Personalisation | One generic template | Per person, per market |
| Sends per action | 1 | Up to 1,840 |
| Bounce rate | Unmeasured, never cleaned | 1.8%, cleaned on detection |
| Reply handling | Manual, often missed | Detected, classified, sequence auto-cancelled |
| “Have we contacted them?” | Unanswerable | One search |
Where the money actually is: the follow-up queue.
1,860 conversations that, under the old way of working, would have ended after a single email. In a six-month buying cycle at this order value, the follow-up isn't a nice-to-have — it is where essentially all of the revenue lives. That queue did not exist before.
Try it
Watch a six-month sequence
cancel itself at week three.
Everybody understands mail merge. Almost nobody has seen the behaviour that makes automated outreach safe.
The sequence that stops itself
Five phases across six months. She replies on day 26. Then flip the switch and watch what most tools do.
“Yes — send the collection.”
The demo doesn't claim the product is sophisticated. It demonstrates that it is considerate — which, in a premium relationship sale, is the same thing as saying it is correct.
Architecture, for the people who ask
A self-contained application sending through the company's own mail servers, with a reply-reading connection back into the mailbox to detect replies, bounces and auto-replies. Sequences are scheduled server-side and re-evaluated before every send — not when they were queued. Contacts sync to the company CRM. Multi-user from the start: each salesperson has their own login, their own leads, their own sending identity and their own limits. Admins can see across; nobody sees sideways.
The decisive engineering choice is the least glamorous one: it sends from the company's own infrastructure rather than a third party's. That is a harder build and a much better product, because in this market the sender's credibility is the entire proposition. It is also what makes correct conversation threading possible, so a follow-up lands inside the original thread rather than as a disconnected new message.
Deliverability is treated as a first-class constraint rather than a side effect: staggered sending, per-identity limits, automatic removal of dead addresses on detection, and high-bounce-region rules applied before a batch is allowed to run.
After the sale
Atlas
Know it's late before it's late.