Outreach infrastructure
Most tools compete on volume, and the domains stop landing in inboxes a few weeks later — silently, with no error to tell you. AutoEmail keeps volume low per mailbox, ramps new accounts over weeks, and spaces every send at an irregular interval.
OAuth only · no passwords stored · revoke in one click
The pipeline
A message only becomes sendable after it passes review. That ordering is structural, not a instruction — so a bad draft cannot reach a prospect because something decided to skip a step.
Pulls their actual pages and cites a source URL for every claim. No source, no claim.
Personalisation comes from something genuinely on their site, not from a merge field.
Invented statistics, fake familiarity, guarantees, false urgency, unresolved placeholders.
Picks a mailbox with capacity, then holds until that account’s next interval comes round.
The difference
Deliverability is not only a DNS problem. Mail that gets deleted unread teaches the provider to filter you — so the copy is infrastructure too.
Hi Sam,
Great catching up last week! I saw Ghost just raised a $40M Series B — congrats!
We helped Acme increase revenue 340% in 60 days and can guarantee the same for you.
Only 2 slots left this month.
Hi Sam,
I noticed on your about page that Ghost is owned by a non-profit foundation — and that you offer a 14-day trial with no card.
We build MCP integrations for publishing platforms, so external AI agents can work with them directly.
Worth a short chat?
Every highlighted phrase on the right traces to a page that was actually fetched. Anything that cannot be traced does not ship — which is why the left-hand version never reaches an inbox.
Your console
Warmup stage, today’s volume against the effective cap, health, and the next available slot — so you can see a problem before a provider does.
Warmup
Sending 50 on day one from a fresh account is the fastest way to get filtered. Every account ramps, and the cap is enforced in the send path — it isn’t a setting anyone can raise past policy.
Safeguards
Each of these is a hard check in the send path. None can be overridden by whatever is asking to send.
Unsubscribes, bounces and do-not-contact are checked when a message is queued and again immediately before it sends. State changes in between, and that gap is where systems email people who already opted out.
Every send carries an idempotency key. A crash, retry or restart mid-send cannot produce a second email. When delivery is genuinely uncertain it stops and asks rather than guessing.
Bounce rates above 3%, or repeated send errors, pull a mailbox out of rotation automatically instead of letting it keep damaging its own reputation.
Gaps are randomised between 3 and 14 minutes, inside business hours in the recipient’s timezone. Mail every seven minutes exactly is a machine signature.
When state is ambiguous the system stops. A missed email costs nothing; a duplicate, or one to someone who opted out, costs the prospect and the domain.
We ask to send and read — never to delete or control a mailbox. Refresh tokens are encrypted at rest and never exposed through the API.
Security
Before you start
SPF, DKIM and DMARC must be set on any domain you send from. Since 2024 Google and Yahoo require it of bulk senders — without it, even well-written mail lands in spam, and no amount of pacing helps.
Rules differ by market: permitted with opt-out in the US and UK, narrower in the EU, and requiring prior consent in Canada. Know which markets your list covers.