Domains and Warmup for Podcast Invite Campaigns

Most teams treat domain warmup as a deliverability chore. We run outbound for 50 plus B2B companies and have sent over 8 million invitations this year, and on an invite campaign warmup is a scheduling item, because the day you buy the domains is what sets the day your first guest sits down to record. Below, the mailbox math behind a 10,000 invite month, the warmup curve that has to finish before invite 1, why reply-heavy invite campaigns hold reputation better than pitch campaigns do, and the 4 numbers that tell you a domain is going bad before the bookings stop.

What Does a Podcast Invite Campaign Need for Domains and Warmup?

None of those numbers are unique to podcast invites. What is unique is the deadline attached to them. A pitch campaign can slip a week and nobody notices. An invite campaign is booking a calendar for a human being who has cleared time to host, so the infrastructure has a fixed date on the other end of it, and every day of warmup you did not plan for is a day the show sits empty.

That reframes the whole setup. You are not asking what infrastructure produces the best inbox placement. You are asking what infrastructure produces acceptable placement by a specific Tuesday. Those two questions have different answers, and the second one is the one that gets asked too late.

Sending Domain

A domain registered for outbound email only, usually a close variant of the company's real domain, redirecting to the real site. It carries the mailboxes that send invitations. If its reputation goes bad, it gets retired without touching the company's primary domain.

Warmup

A staged ramp of low-volume mail between a new mailbox and a network of real inboxes, with opens and replies, so mailbox providers see a normal sending history before real volume starts. It runs 21 to 28 days on a new mailbox and then continues in the background for the life of the campaign.

Why Is Warmup a Launch Date Problem, Not a Deliverability Problem?

Work the calendar backwards and the point makes itself.

Say a client wants their first recorded conversation in the first half of November. The recording has to be booked, so an invitation has to land in October. The invitation cannot go out until warmup is finished, which is 3 to 4 weeks. Warmup cannot start until DNS has propagated and the mailboxes exist, which is another few days. And domains should be registered a couple of weeks before any of that, because a domain that was bought yesterday and is sending today looks exactly like what a spammer does.

Add it up and the domain purchase sits 5 to 6 weeks ahead of the first invitation. Nobody feels that gap while they are picking a show name and arguing about cover art. They feel it the week they are ready to send and the mailboxes are 9 days old.

The list work is the part that can run alongside warmup, and it should. Verification, enrichment, and segmentation do not touch the sending reputation, so there is no reason to do them in sequence. Warmup is the only step on that table that cannot be compressed by working harder, which is exactly why it belongs at the front of the plan instead of the middle. We commit to a client's first recording landing within 14 days of the first invitation going out, and the only way that commitment is keepable is if the infrastructure was started 6 weeks before it.

How Many Domains and Inboxes Do 10,000 Invites a Month Need?

The domain count is arithmetic, not preference. Take the monthly invite target, divide by what one mailbox can carry, and you have your mailbox count. Divide that by mailboxes per domain and you have your domain count.

Here is the math we run on every build:

1. 20 cold sends per mailbox per day. That is the ceiling we hold, and we hold it whether the mailbox has been running for 3 weeks or 3 years. The temptation to push to 50 shows up every time somebody wants volume faster. It is the single fastest way to burn a domain that was fine yesterday. The reasoning is in how many cold emails you can actually send per day.
2. 22 sending days a month. Weekdays only, minus holidays. So one mailbox carries roughly 440 invitations a month.
3. 10,000 invites divided by 440 is 23 mailboxes. Round up for the mailbox you will inevitably have to pull out of rotation.
4. 3 mailboxes per domain. More than that concentrates too much volume behind a single reputation. Fewer than that multiplies your DNS surface for no benefit. 23 mailboxes lands at 8 domains.
5. Build in a spare domain. A ninth domain sitting warm and unused is cheap insurance. When one goes sideways in month 4, you swap instead of waiting 4 weeks for a replacement to warm.

That last one is the item most builds skip and most builds later regret. The full decision tree for domain count by volume is in multi domain sending, 5 domains versus 50, and the architecture rules sit in how to set up email domains for outbound. The short version: the number of domains is a function of volume, and anybody quoting you a domain count before asking your monthly send target is guessing.

What Has to Land Before Warmup Day 1?

Warmup on a misconfigured domain teaches the mailbox providers something you do not want them to learn. Get the records right first, then start the ramp.

• SPF, DKIM, and DMARC, all 3, all aligned. Not 2 of 3. Google's sender guidelines and Yahoo's sender best practices both treat authentication as table stakes, and Outlook's high volume sender requirements put the same 3 records behind enforcement. The record-by-record walkthrough is in what SPF, DKIM and DMARC actually do and the DNS records explained.
• A redirect on every sending domain. The lookalike domain should resolve to the real website, not a parked page. A recipient who checks is a good sign, and a dead page turns a good sign into a bad one. More on the pattern in what a secondary domain is for.
• A real signature and a real profile photo on every mailbox. Cheap, and it changes how the message reads to a human before it changes anything for a filter.
• One-click unsubscribe wired up. Required for bulk senders and, more usefully, the pressure valve that keeps an annoyed recipient from reaching for the spam button instead.
• A verified list waiting. Bounces on the first real batch undo weeks of warmup in an afternoon. This is what verification is protecting, and it matters more on day 22 than at any other point in the campaign.

What Does the Warmup Curve Look Like Week by Week?

The curve itself is not controversial. Start small, climb slowly, and let the tool handle the opens and replies. What varies is patience.

1. Week 1, 5 to 10 a day. The mailbox has no history at all. This week exists to prove it is a real account behaving like one.
2. Week 2, 10 to 20 a day. Reply activity climbs. Placement should be sitting in the primary inbox across providers by the end of this week.
3. Week 3, 20 to 30 a day. The mailbox now looks like a person with an active thread history rather than a fresh install.
4. Week 4, 30 to 40 a day. Hold here. This is the week most people skip, and the difference between a mailbox that survives month 6 and one that does not usually got decided in it.
5. Day 22 onward, mix in real sends. Start real invitations at 5 to 10 a day per mailbox and step up to 20 over the following week. Do not go from warmup straight to full volume on a Monday morning.

The mistake worth naming: a warmup tool showing green at day 10 is reporting on its own network, not on how Gmail feels about you. Practitioner guides like MailReach's warmup walkthrough and Instantly's deliverability guide land in the same 3 to 4 week band for a reason. Our full day by day version is how to warm up a new email domain, with the concept explained plainly in email warmup explained.

Why Do Invite Replies Protect the Domain?

This is the part that makes invite infrastructure genuinely different from pitch infrastructure, and it is the reason we moved the whole business onto invitations.

Mailbox providers weight engagement. Replies, forwards, stars, and a message getting dragged out of promotions all read as wanted mail. Deletions without opening and spam complaints read the other way. Warmup exists to fake the first category until you have earned it for real.

An invitation earns it faster than a pitch does. Asking somebody to be a guest on a show gets answered, including by the people saying no, because declining an invitation feels like manners and ignoring a sales email does not. Across our book that lands reply rates around 4.6 percent against the 3.43 percent market median, and every one of those replies is a positive engagement signal hitting the same reputation the warmup tool was simulating a month earlier.

There is a second-order effect worth knowing. A pitch campaign's reputation decays as the list gets colder, because the message never gets better and the recipients never get warmer. An invite campaign's reputation tends to hold, because the traffic includes real conversations with real people who answered on purpose. The infrastructure is doing the same job in both cases. Only one of them is being fed. The mechanics behind that gap are in invite versus pitch and why executives say yes to podcast invites.

Does Warmup Ever Stop Once the Campaign Is Live?

No, and treating it as a phase that ends is how good infrastructure quietly degrades in month 5.

Background warmup should keep running at roughly 20 to 30 percent of daily volume for the life of the campaign. An invite campaign is not a 6 week sprint. It runs for as long as the show does, which means the mailboxes go through holidays, list rebuilds, a pause while a client changes their target market, and the odd week where sending stops for a reason nobody wrote down. A mailbox with background warmup running comes back from those gaps. A mailbox that went dark for 3 weeks comes back looking new again.

The same logic applies to rotation. Mailboxes should share volume evenly rather than one domain carrying the campaign while the rest idle. Idle domains do not stay warm on their own, and the day you need to swap one in is the day you find out. Background warmup and even rotation are the 2 habits that separate infrastructure that lasts a year from infrastructure that needs rebuilding every quarter, which is the expensive version of this problem covered in how to recover a burned domain.

Which 4 Numbers Tell You a Domain Is Going Bad?

Reply rate is a lagging indicator. By the time it drops, the placement problem is weeks old. Watch these instead, weekly, per domain rather than per campaign:

1. Inbox placement from a seed test. The only direct read on where mail is landing. Under 60 percent primary placement, that domain comes out of rotation. Method in inbox placement tests.
2. Spam complaint rate. Google asks bulk senders to stay under 0.3 percent and to aim below 0.1 percent. Treat 0.1 percent as the ceiling. Google Postmaster Tools is where you read it for Gmail traffic.
3. Bounce rate per domain. A domain-level spike while the others hold steady is an infrastructure signal, not a list signal. A spike across all of them is the list.
4. Blacklist status. Weekly checks catch a listing while it is still 1 domain instead of 4. Details in blacklist monitoring and the wider dashboard in deliverability monitoring.

Run a deliverability test on the primary sending domain every week and log the result. The number itself matters less than the trend, and the trend is invisible unless somebody is writing it down. When placement slips, the fix is volume and rotation, not copy. Rewriting an invitation while the domain underneath it is degrading burns a rewrite and teaches you nothing, which is the argument in why your cold email is landing in spam and how to stay out of the spam folder.

The Practitioner Take on Invite Infrastructure

Every campaign we have watched fail on infrastructure failed for one of 2 reasons, and neither of them was a hard technical problem. Either the domains were bought too late and warmup got cut to 10 days to make a date somebody had already promised a client, or the daily volume got pushed past 20 because the target felt slow at week 3. Both are decisions made under time pressure by somebody who understood the risk and took it anyway.

So the useful discipline is not technical. It is putting the domain purchase on the calendar before the show name, the cover art, or the first list pull. Those things can be finished in a day. Warmup cannot, and no amount of budget shortens it.

The direction of travel makes the gap wider, not narrower. Google, Yahoo, and Microsoft have all tightened bulk sender enforcement in the last 2 years, and none of them are loosening it. Authentication, complaint rates, and engagement history are becoming the whole game. That is bad news for anybody sending generic mail at volume and quietly good news for invite campaigns, because an invitation generates exactly the engagement the new rules reward. Build the infrastructure 6 weeks early, hold the volume ceiling, keep warmup running in the background forever, and check placement weekly. The copy can be fixed in an afternoon. The domain cannot.