All tools
DELIVERABILITY OPERATIONS / DATED RUNBOOK / LOCAL MODEL

Ramp with feedback,
not a magic curve.

Build a receiver-aware sending schedule, document readiness, and turn live complaints, bounces, and deferrals into an explicit proceed, hold, or pause decision.

Dated schedule Receiver mix Health gates
WARMUP RUNBOOK BUILDER
NEW DEDICATED IP / MEASURED MODEL

57 send days to reach 25,000/day

Target first appears Fri, November 6, 2026; the runbook ends after 7 send days at target.

Calendar span63 days

63 active send days

Target dateNov 6, 2026

57 send days

Warmup sends236,204

Through first target day

Full runbook386,204

Includes 7 target days

VOLUME CURVE

Bars represent planned volume, not a mailbox-provider capacity promise.

Sep 11, 2026First target: Nov 6, 2026Nov 12, 2026
LIVE HEALTH GATE
Eligible for operator review

The entered metrics remain below this planner’s conservative guardrails. Confirm per-provider reputation and SMTP evidence before approving the next volume step.

Gmail’s published target is below 0.1% user-reported spam and never 0.3% or higher. Bounce and deferral thresholds here are conservative planning guardrails, not universal provider standards.
PRE-SEND READINESS
0 / 6 confirmed

A schedule does not compensate for missing authentication, consent, unsubscribe, or monitoring controls.

DATED SENDING MANIFEST
DayDateStatusTotalGmailMicrosoftYahoo/AOLOtherCumulative
1Sep 11, 2026Ramp5025137550
2Sep 12, 2026Ramp50251375100
3Sep 13, 2026Ramp63321696163
4Sep 14, 2026Ramp63321696226
5Sep 15, 2026Ramp793920128305
6Sep 16, 2026Ramp793920128384
7Sep 17, 2026Ramp9949251510483
8Sep 18, 2026Ramp9949251510582
9Sep 19, 2026Ramp12462311912706
10Sep 20, 2026Ramp12462311912830
11Sep 21, 2026Ramp15578392315985
12Sep 22, 2026Ramp155783923151,140
13Sep 23, 2026Ramp194974929191,334
14Sep 24, 2026Ramp194974929191,528
15Sep 25, 2026Ramp2431226136241,771
16Sep 26, 2026Ramp2431226136242,014
17Sep 27, 2026Ramp3041527646302,318
18Sep 28, 2026Ramp3041527646302,622
19Sep 29, 2026Ramp3801909557383,002
20Sep 30, 2026Ramp3801909557383,382
21Oct 1, 2026Ramp47523811971473,857
22Oct 2, 2026Ramp47523811971474,332
23Oct 3, 2026Ramp59429714989594,926
24Oct 4, 2026Ramp59429714989595,520
25Oct 5, 2026Ramp743372186111746,263
26Oct 6, 2026Ramp743372186111747,006
27Oct 7, 2026Ramp929465232139937,935
28Oct 8, 2026Ramp929465232139938,864
29Oct 9, 2026Ramp1,16258129117411610,026
30Oct 10, 2026Ramp1,16258129117411611,188
31Oct 11, 2026Ramp1,45372736321814512,641
32Oct 12, 2026Ramp1,45372736321814514,094
33Oct 13, 2026Ramp1,81790845427318215,911
34Oct 14, 2026Ramp1,81790845427318217,728
35Oct 15, 2026Ramp2,2721,13656834122720,000
36Oct 16, 2026Ramp2,2721,13656834122722,272
37Oct 17, 2026Ramp2,8401,42071042628425,112
38Oct 18, 2026Ramp2,8401,42071042628427,952
39Oct 19, 2026Ramp3,5501,77588853235531,502
40Oct 20, 2026Ramp3,5501,77588853235535,052
41Oct 21, 2026Ramp4,4382,2191,10966644439,490
42Oct 22, 2026Ramp4,4382,2191,10966644443,928
43Oct 23, 2026Ramp5,5482,7741,38783255549,476
44Oct 24, 2026Ramp5,5482,7741,38783255555,024
45Oct 25, 2026Ramp6,9353,4681,7341,04069361,959
46Oct 26, 2026Ramp6,9353,4681,7341,04069368,894
47Oct 27, 2026Ramp8,6694,3352,1671,30086777,563
48Oct 28, 2026Ramp8,6694,3352,1671,30086786,232
49Oct 29, 2026Ramp10,8375,4182,7091,6261,08497,069
50Oct 30, 2026Ramp10,8375,4182,7091,6261,084107,906
51Oct 31, 2026Ramp13,5476,7733,3872,0321,355121,453
52Nov 1, 2026Ramp13,5476,7733,3872,0321,355135,000
53Nov 2, 2026Ramp16,9348,4674,2342,5401,693151,934
54Nov 3, 2026Ramp16,9348,4674,2342,5401,693168,868
55Nov 4, 2026Ramp21,16810,5845,2923,1752,117190,036
56Nov 5, 2026Ramp21,16810,5845,2923,1752,117211,204
57Nov 6, 2026Target25,00012,5006,2503,7502,500236,204
58Nov 7, 2026Stabilize25,00012,5006,2503,7502,500261,204
59Nov 8, 2026Stabilize25,00012,5006,2503,7502,500286,204
60Nov 9, 2026Stabilize25,00012,5006,2503,7502,500311,204
61Nov 10, 2026Stabilize25,00012,5006,2503,7502,500336,204
62Nov 11, 2026Stabilize25,00012,5006,2503,7502,500361,204
63Nov 12, 2026Stabilize25,00012,5006,2503,7502,500386,204

A schedule is a hypothesis with stop conditions.

Warmup is a controlled increase in wanted, authenticated email while receivers learn the behavior of a changed IP or domain. The curve is only an initial operating plan. SMTP responses, complaints, bounces, authentication, and provider reputation data decide whether the next increase is justified.

SEND

Use the most relevant, permissioned audience available.

OBSERVE

Separate results by receiving provider and traffic stream.

ADAPT

Proceed, hold, reduce, or pause before the next step.

New IP, new domain, and migration are different changes.

A dedicated IP needs its own sending history. A new domain can be unfamiliar even on provider-managed shared infrastructure. A migration can preserve domain reputation while changing IPs, DKIM keys, return paths, headers, and cadence. Record exactly what changed and segment that traffic instead of treating every scenario as “brand new.”

New dedicated IP

No established IP history; provider-specific capacity matters.

New sending domain

Domain identity is new; shared-IP capacity may already be managed.

ESP migration

Preserve cadence and segment the infrastructure change.

Restart after inactivity

Treat prior history as stale and rebuild predictable traffic.

Ten thousand messages is not one reputation event.

Capacity and feedback emerge independently at Gmail, Microsoft, Yahoo, corporate gateways, and other destinations. A list that is 70% Gmail warms very differently from one that is 10% Gmail. The manifest makes the assumed split explicit so operators can compare planned and actual volumes per receiver.

Hold before a weak signal becomes a pattern.

Google tells senders to increase slowly, send at a consistent rate, begin with engaged recipients, monitor SMTP responses and Postmaster Tools, and reduce volume when bounces or deferrals rise. Its current guidance says to keep user-reported spam below 0.1% and avoid ever reaching 0.3%. Open rate is not a receiver-side control signal: Google says it does not track opens and cannot verify third-party open-rate accuracy.

PROCEED

All readiness controls pass and provider-level signals remain stable.

HOLD

Keep or reduce current volume while investigating a deteriorating signal.

PAUSE

Stop the affected stream when complaints or delivery failures cross a serious guardrail.

Move the audience in observable cohorts.

Preserve the old path long enough to shift traffic deliberately. Start with recent, consented recipients, compare receiver-level outcomes, and avoid changing provider, From identity, content architecture, cadence, and audience policy all at once. If the new path is deferred, route only according to a documented rollback plan; uncontrolled retries can turn throttling into a volume spike.

Email warmup FAQ.

Is this an automatic warmup service?+

No. It creates a planning runbook and exports. It does not send mail, manufacture engagement, open messages, or interact with recipient accounts.

How long should warmup take?+

There is no universal duration. AWS says dedicated-IP reputation can take roughly two to six weeks depending on provider, while its standard automatic warmup increases over 45 days. Actual receiver feedback should control your pace.

Should I warm a shared IP?+

Your email service provider generally manages shared-IP capacity. You may still need to ramp a new domain, new traffic stream, migration, or major volume change. Confirm the provider’s responsibilities.

Should warmup mail go to seed accounts?+

Seed testing can reveal rendering or directional placement, but it does not substitute for wanted production mail and real recipient behavior. Never use coordinated opens or replies to manufacture reputation.

Can I warm with cold outreach?+

That creates an avoidable consent and complaint risk. Warmup should begin with the most clearly permissioned and currently relevant recipients available.

RUN THE PLAN WITH REAL SIGNALS

Keep audience, sending, and deliverability evidence together.

Build consent-aware segments, send campaigns and transactional mail, and inspect results from one operational workspace.

Start for free