Shipped in code Live
- Honest open classification. Every recorded open is classed as a real read, an Apple Mail prefetch, a bot scan, or the sender's own re-read, and only real reads count.
Mechanism: a registered send id, a pixel and click endpoint, and a class field. Reports (
/api/stats,/api/events) count onlyclass=real; the sender's own opens are suppressed by a server-set window. - Pipeline in the thread. Pipelines, deal boxes, stages, and free-text notes, attached to the Gmail thread rather than a separate dashboard.
Mechanism:
/api/pipelines,/api/boxes,/api/noteson a Cloudflare Worker + D1. - Reply queue by engagement. Threads ordered by how engaged the recipient is right now.
- The self-canceling reminder. A follow-up reminder that clears itself the moment the contact replies.
Mechanism:
/api/reminderswith an active/fired/canceled lifecycle. - One built-in report. Stage-conversion funnel, reply rate, and cold-thread count, computed from the pipeline. Not a report builder.
Mechanism:
/api/report. - Mail merge with unsubscribe. Personalized batches, a one-click unsubscribe honored on all future sends, and a suppression list.
Mechanism: RFC 8058 one-click unsubscribe,
/api/suppressions. - Server-enforced tiers. Tracked-per-month and pipeline caps enforced in the backend, not just the UI.
- Fast mobile web view. A self-contained page with no external requests.
- Warmth engine + commitment field. Contacts carry a computed warm / cooling / cold read from last-touch, a going-cold filter, and a per-contact next-step commitment (what you promised, by when).
Mechanism:
/api/contacts?cooling=1; warmth computed at read time so it is always current. Verified byworker/test/contacts.test.sh(19/19). - Data hygiene enforced in code. A colliding email is never auto-merged; every change is audited and can be undone.
Mechanism:
/api/contactsreturns 409needs_confirmationon a collision, anaudit_logrecords every before/after, and/api/contacts/undoreverts (undo of a create archives, never hard-deletes). - Landed-signal API (reply + meeting). One authenticated call records that a message landed and makes a reply the primary signal: it warms the contact, bumps the deal's reply date so the report moves, and cancels the follow-up reminder on its own.
Mechanism:
POST /api/signal{type:reply|meeting}. A reply/meeting cannot be degraded by Apple MPP or Gmail proxying, unlike an open. Verified byworker/test/signal.test.sh(17/17). The Gmail poller that CALLS this is the one remaining leg (below).
Building now Building
- The Gmail poller for the landed signal. The landed-signal API is live (above); what remains is the Gmail history poller and calendar watcher that call it automatically, so replies and bookings are detected without you lifting a finger. Needs Google OAuth. Pixel opens stay a disclosed, off-by-default secondary hint.
- Automatic warmth from the live mail signal. The warmth engine and commitment field are live (above); wiring reply and calendar detection so each contact's last-touch populates itself from the mail already flowing is what remains.
- Sanctioned Google Workspace add-on. The in-thread sidebar on Google's supported add-on framework, alongside the existing server rail, rather than the DOM-injection approach the most-installed competitor still uses.
- MCP server + this llms.txt, ungated at the entry tier. So an AI agent can read who is cooling and what was committed. No surveyed personal-CRM peer ships one; this is a category first.
- Free view-only deal link. A live, no-login read on a single deal.
Data hygiene guarantee Live
Contacts are never merged without asking, and this is enforced in code. A write whose email collides with an existing contact returns a confirmation prompt instead of overwriting; every change keeps a full undo and an audit trail. This is the explicit answer to a documented competitor failure: silent, undisableable contact merges that lose data. Verified by worker/test/contacts.test.sh.
How it compares
| Capability | Cachet Inbox | Streak | Cloze | Superhuman | Attio |
|---|---|---|---|---|---|
| Warmth layer | yes | no | yes | no | no |
| Pipeline | yes | yes | no | rents HubSpot | yes |
| Both in one product | yes | no | no | no | no |
| Reply/calendar-first signal | building | pixel | pixel | pixel | no |
| Never auto-merges contacts | yes | yes | forced merge | yes | no dedupe |
| MCP + llms.txt | building, entry tier | free | top tier | Business only | yes |
From the July 2026 competitor atlas of vendor pages and public reviews. Where a rival is stronger, this table says so.
Limits, plainly
- The mailbox is never synced or stored. The panel reads data for the open thread only; sends go through Gmail's own API signed in as the user and never route through our servers.
- Pixel opens are unreliable and we say so. Apple Mail preloads pixels and Gmail proxies and caches them, so most opens are structurally unreliable in 2026 and are consent-gated in the EU. We do not present them as certainty.
- Gmail-native today. Outlook is not supported. We would rather ship it well than claim it early.
- Private preview. Single user, nothing public, pricing proposed and nothing charges yet.