Step 00 — The call
Thirty minutes, and there is genuinely no pitch in it. You bring a domain and a symptom; we run the checks together on your actual infrastructure while we talk. By the end you know what is wrong and roughly what fixing it involves.
A decent share of these calls end with the person able to fix it themselves, and I will tell you when that is the case rather than quoting you for it. That is not generosity — it is that the work I want is the work that actually needs doing.
Step 01 — Scope the stack
Everything is worked backwards from one number: how many emails you need to land per day. That determines inbox count, which determines domain count, which determines the registrar and DNS layout, which determines the warmup timeline. Get the number wrong and every downstream decision is wrong with it.
Also settled here: ESP mix, naming families for the domains, whether existing infrastructure is salvageable, and the timeline. You get a written scope with what it costs before anything is built. There is no situation where the bill is a surprise.
Step 02 — Domains and DNS
Domains registered in naming families that read as a real company, spread so one listing cannot take out the fleet, each redirecting to your actual site. Zones created in bulk, then SPF, DKIM, DMARC, MX and a custom tracking domain configured on every one.
Then verified — an actual message sent and its headers read. A record that exists and a record that works are different things, and the gap between them is where most fleets acquire their first invisible fault.
Step 03 — Provision the mailboxes
Workspace or Microsoft 365 tenants configured, mailboxes bulk-created to a consistent spec, signatures and profiles completed, sending limits set, and OAuth or app passwords connected to Instantly or Smartlead. Mailboxes arrive ready to warm rather than merely existing.
Step 04 — Warm and launch
Structured warmup with reputation watched as it builds. This is the stage nobody wants to wait through and the stage that decides whether the fleet lasts. Plan on two to four weeks between mailboxes existing and being safe for real volume.
You get told when each pool is ready and what daily ceiling it can hold. Sending past that ceiling is the single most common way a well-built fleet gets burned in its first month.
Step 05 — Handover or hold
Either I document the whole thing and hand it to you — every domain, record, mailbox and credential, in your accounts — or it moves onto monitoring and I keep watching it. Both are fine. What is not fine is a fleet that nobody is checking, because infrastructure drifts and it drifts silently.
What it costs
I do not publish prices, and I want to be straight about why rather than hide behind “it depends”. A small setup for a solo founder and a large fleet with ongoing management are not the same product at two price points. Quoting a number without knowing your volume would mean either overcharging you or discovering halfway through that the scope was wrong.
What I will commit to: you get a written scope with a price before any work starts, the price does not move unless the scope does, and you are told during the first call if the honest answer is that you do not need to hire anyone.
What I need from you
Your daily target
How many emails you need landing per day. Everything else is derived from this.
Raw message headers
Two or three from emails that landed badly. The single most useful thing you can send.
Access, not ownership
Registrar, DNS and sending tool access. Everything stays in your name throughout.
Your timeline
When you need to be sending. Warmup is the constraint, so this shapes the plan.
Questions people ask before hiring
Do you work with agencies or only direct?
Both. A good share of the work is white-label for agencies running client fleets, where I am the infrastructure layer and you keep the client relationship. That works well and I am happy to stay invisible.
What if I already have infrastructure?
Then we start with an audit rather than a build. Sometimes it is repairable, sometimes half the domains are burned and rebuilding is cheaper than repairing. You get told which, with the reasoning.
How quickly can you start?
Usually within a few days for a scoped build. The honest constraint is never my availability, it is warmup — the calendar is set by how long reputation takes to build, not by when I can begin.
Do you sign NDAs?
Yes, routinely. Most agency work runs under one.
What happens if it does not work?
Deliverability has no guarantees and anyone offering one is selling something. What I commit to is diagnosis you can verify yourself — every check I run is one of the free tools on this site, so nothing is a black box you have to take on faith.
What this applies to
Start with the call
It is free, it is thirty minutes, and there is no pitch in it.
Bring a domain and a symptom
We run the checks together on your actual infrastructure. You leave knowing what is broken, what it takes to fix, and what it should cost — including if that cost is nothing.