BUILD Sending foundation build

Sending foundation build. Domains, IPs and warmup, done properly.

Domains registered away from your corporate mail and aged 30 days with nothing sent from them, authentication configured and validated, dedicated IPs sized to your volume, and warmup run until measured placement says volume can rise. The aging clock starts on day one, so the data and the sequences are prepared while it runs. Four to six weeks, and you keep all of it.

Talk to a deliverability expert Read our Standard

What it covers

30-day aging, no exceptions
SPF, DKIM, DMARC, TLS
IPs sized to volume
Warmup to measured placement

What it is

The four to six weeks before anyone sends anything.

The short answer

A sending foundation build is the infrastructure work that has to happen before a cold program launches: domains registered and then aged for 30 days with nothing sent from them, authentication configured, dedicated IPs allocated, and warmup run until measured placement says volume can rise. Done properly it takes four to six weeks, because the aging period runs alongside the data and copy work rather than after it. Skipped, it is the most common reason a program fails in month one.

What gets built

Four things, in order.

Domains

Registered, separated from your corporate domain so outbound cannot damage mail you cannot afford to lose, and then left alone for 30 days with nothing sent from them, starting on day one so the clock runs while everything else is being prepared. A domain registered yesterday carries no weight however carefully you send from it, and this is the requirement clients push back on hardest and the one we will not move on.

Authentication

SPF, DKIM, DMARC and TLS configured and validated from the outside. Misaligned records are one of the most common findings in an audit and one of the least visible from your own inbox.

Dedicated IPs

Allocated and sized to your target volume, because providers throttle per IP. Rotation groups set up so cold discovery and engaged follow-up do not share a reputation.

Warmup to placement

Provider-aware warmup with reply patterns and timing variance, with each volume increase earned against measured placement rather than a calendar.

You keep all of it. The domains are registered to you and the configuration is yours. This is not a rental that stops working if you leave.

If we can't establish a deliverable baseline, the setup fee is refunded. We control the domains, the authentication, the IPs and the warmup, so this is a promise we can actually make. We will not promise you replies, because your offer and your market decide those.

Who it is for

Three situations where this is the right first purchase.

Starting

Launching cold outbound for the first time

You have the list and the offer and no infrastructure. Building it properly costs six weeks once. Building it badly costs a domain and then six weeks anyway.

Rebuilding

Coming back from a burnt domain

After a reputation repair, the replacement infrastructure has to be built rather than borrowed. Reusing anything from the damaged pool is how the second attempt fails the same way.

Scaling

Outgrowing mailboxes

A sequencer at a few hundred a day does not become a million a month by adding inboxes. At that point the answer is dedicated IPs, and they need building before they need using.

Questions

Sending foundation build, answered.

What is a sending foundation build?

The infrastructure work that happens before a cold email program launches: sending domains registered and aged, SPF, DKIM, DMARC and TLS configured, dedicated IPs allocated and grouped for rotation, and warmup run until measured inbox placement says volume can safely rise. It normally takes four to six weeks, which is set by the 30 days sending domains spend aging with nothing sent from them.

Why does it take four to six weeks?

Because the constraint is at the receiving end. Sending domains age for 30 days with nothing sent from them, and that is what sets the length. It is not dead time: the data is sourced and verified, authentication and IPs are configured, and the sequences are written while the clock runs. Google and Microsoft decide the pace, not us, and there is no version of this that can be bought faster. A client who will not wait out the aging period is the client whose program fails in month one, which is why we treat it as a condition rather than a recommendation.

Do I own the domains and IPs?

The domains are registered to you and the configuration is yours. This is deliberately not a rental that stops working if you stop being a customer, because a foundation you cannot keep is not a foundation.

Can I use my existing domain?

Usually not your main corporate one, and we will push back if you ask. Cold outbound and the mail your business depends on should not share a reputation, because a bad month on the first takes the second with it. Separate sending domains are standard practice for good reasons.

What happens after the build?

Either you run it yourself on the platform, or we do. Managed outbound is the same infrastructure with our team operating the campaigns, and ongoing management is the lighter version where you run the sending and we watch the reputation.

What does it cost?

It is scoped rather than listed, because a two-domain build for 100,000 a month and a twenty-IP build for ten million are not the same project. Tell us the volume, the data and the timeline and we will quote it. Any audit fee you have already paid is credited in full against a build started within 60 days.

Get started

Tell us what you need to send.

Volume, data type and when you need to be live. We will scope the build and tell you honestly whether your date is achievable.

A realistic date, even when it is later than you hoped
Domains and configuration you own and keep
The option to run it yourself afterwards, or hand it to us

Prefer to talk? 1-800-604-5058

Six weeks once, or six weeks after a failure.

Those are genuinely the two options, and only one of them starts with a working domain. Tell us your volume and we will scope the build.

Talk to a deliverability expert Read our Standard