Plan the ramp
How it works
Set the shape
Start low, pick a growth rule and a target. Linear ramps are easier to reason about; percentage ramps accelerate late.
Read the week totals
Fleet volume per week is what the receivers see from the domain. That is the number to sanity-check against the domain's age.
Reserve warmup traffic
A share of early sends should be warmup-tool mail that gets opened and replied to. It builds engagement history before real prospects see you.
Hold on any signal
Bounces above 3% or a complaint during the ramp means freeze for three days, then resume one step lower.
Why the ramp matters more than the tool
Warmup services get the credit, but the thing receivers actually score is the shape of your volume curve. A new domain that goes from zero to 200 a day in a week looks like a snowshoe operation regardless of how many warmup replies it collected. One that climbs steadily over three weeks with real engagement looks like a business that just started emailing. The calculator is here to make that curve deliberate instead of accidental.
Defaults and where they come from
The defaults — five a day rising by three, target thirty, weekends off — are what holds up across the Google Workspace fleets I run without tripping the first-fortnight scrutiny Google applies to new accounts. Microsoft 365 is less predictable; it throttles by recipient domain reputation as well as sender, so I run the same shape one notch lower and accept an extra week. Self-hosted SMTP on a fresh IP needs a slower curve again, because the IP has no history at all.
The target of thirty per inbox is not a technical limit. Workspace will let a new account send far more. It is the ceiling at which cold email from an inbox still looks like a person, and where a single bad list does not take the domain down with it. Plenty of operators run fifty; almost none who run a hundred still have the domain a year later.
Reading the schedule
The per inbox column is what each mailbox sends that day. Fleet multiplies that by your inbox count, and cumulative is the running total. The first week is marked as warmup-only because real prospects should not be in the mix yet; the day the ramp hits target is marked so you can put it on a calendar.
The warmup-tool share is a guideline for how much of the early volume should be simulated conversation. Thirty percent in week one, tapering to a small floor that never quite reaches zero, is the pattern that keeps engagement metrics from collapsing the moment real campaigns start.
What to do when it breaks
A ramp is a plan, not a contract. If bounces climb past three percent, the list is the problem and the ramp should pause until it is cleaned. If a spam complaint lands, drop back one step and hold for three days. If Google starts returning 4.7.28 rate-limit responses, you went too fast — halve the daily target and rebuild from there. The calculator can be re-run from any point by treating today's volume as the new start.
Frequently asked questions
How long does email warmup take?
Two to three weeks for a new inbox on an established domain; three to four weeks for a new domain. A month is not excessive if the domain will carry volume for years.
Can I skip warmup if the domain is old?
An old domain that has never sent still has no sending reputation. Age helps a little with the initial trust score, but the ramp is about establishing send history, so run it anyway — you can start slightly higher.
Should warmup continue after the ramp?
A small share, yes. Keeping five to ten percent of volume as warmup traffic maintains engagement history and softens the impact of a bad campaign. Turning it off entirely on day 22 is a common cause of week-five drops.
Is a percentage ramp better than a linear one?
Neither is better; they have different shapes. Percentage ramps start very slowly and accelerate, which suits large fleets that can afford a long quiet start. Linear ramps are more predictable for small fleets and easier to explain to a client.
Does sending on weekends hurt?
Not directly, but B2B recipients engage less on weekends and engagement is what you are trying to build. Weekdays only is the default for that reason. Consumer lists are different.
What if some inboxes are older than others?
Run the calculator per cohort. Mixing a fresh cohort into an established fleet's daily total is fine as long as the fresh inboxes individually follow the ramp.
Last reviewed
What to run next
The checks that most often follow this one.
More in this category
Guides that go deeper
When the tools tell you something is wrong
The diagnostics here are free and always will be. When the fix is bigger than a DNS record, this is the work I do.
Deliverability rescue
Mail landing in spam, replies gone quiet, or a domain suddenly blocked. I find the actual cause rather than guessing, and fix it.
- Authentication and alignment failures
- Blocklist delistings and reputation repair
- Gateway and filter-level blocks
- A written report on what broke and why
Email & sending infrastructure
Sending domains, inboxes, authentication and warmup, built to survive volume instead of burning down in a month.
- Domain and inbox fleets at any scale
- SPF, DKIM, DMARC and tracking domains
- Google Workspace and Microsoft 365 inboxes
- Handover documentation you actually own
Domain, DNS & migration
Changing registrar, mail provider or host without a day of downtime or a week of mail silently failing.
- Registrar and nameserver moves
- Workspace and Microsoft 365 migrations
- MX, SSL and subdomain cutover
- Staged rollout with rollback at every step
Monitoring & retainer
Infrastructure drifts. Records get edited, certificates expire, domains get listed. Ongoing eyes on the fleet.
- Scheduled checks across every domain
- Alerts before your clients notice
- Monthly reporting
- Priority response when something breaks
Start with a call
Bring a domain and the symptom. I will tell you what is actually wrong and whether you need me at all — plenty of people leave that call able to fix it themselves.
Thirty minutes, no pitch
We will run the checks together on your actual domains, and you will leave knowing what is broken, what it takes to fix, and what it should cost. If that is a job you can do in-house, I will say so.