IP Warm-Up Schedule Calculator

A cold sending IP has no reputation, and mailbox providers do not read that as neutral — they read it as unproven. IP Warm-Up Schedule Calculator turns your target volume into a concrete day-by-day ramp: how many messages to send on each date, which engagement segment to send them to, how to split the volume across a pool of IPs, and when to hold steady instead of climbing.

The model uses a decaying multiplier rather than flat doubling, because a jump from 100 to 200 is nothing and a jump from 200,000 to 400,000 is a red flag. Early days climb fast, later days flatten, and the schedule stops the moment it reaches your target rather than overshooting. Weekday-only sending, multiple IPs, and three risk postures are all supported, and the planner tells you honestly when your list is too small to supply the ramp you have asked for.

Alongside the schedule you get the deliverability context that actually determines whether a warm-up succeeds: engagement-first segmentation, provider-specific behaviour for Gmail, Microsoft, Yahoo and Apple, the pre-flight authentication checklist, and the metric thresholds that mean stop climbing today. Export the whole plan as CSV and work through it.

• Day-by-day schedule: Every sending day with its date, volume, per-IP volume, cumulative total, engagement segment, and a note explaining the phase.
• Decaying growth model: Multipliers taper as absolute volume rises, so the curve is aggressive where it is safe and cautious where it is not.
• Three risk postures: Conservative, standard and aggressive ramps, with the trade-off in days stated plainly rather than hidden in a preset.
• Multi-IP splitting: Enter your pool size and every row shows the per-IP figure, with a warning about the reputation cost of spreading history thin.
• Weekday-only mode: Skip weekends without breaking the curve, for senders whose audience only engages on business days.
• Engagement-first segmentation: Each phase specifies which recency window to send to — 30-day openers first, dormant contacts last or never.
• List sufficiency check: Warns when the schedule needs more engaged recipients than your list plausibly contains.
• Visual ramp chart: See the shape of the curve at a glance, including the plateau where you hold at target.
• Provider intelligence: How Gmail, Microsoft, Yahoo and Apple each treat a new sender, and what each one throttles on.
• Guardrails and pre-flight checklist: Complaint, bounce and deferral thresholds that mean pause, plus the authentication setup to complete before day one.
• CSV export: Download the full schedule for your project tracker or ESP planning sheet.

1. Enter your target daily volume. This is the steady-state number you need to reach — the whole schedule is derived from it.
2. Enter your engaged list size. Use the count of contacts who have opened or clicked in the last 90 days, not your total subscriber count. This is what the sufficiency check tests against.
3. Pick a start date and sending days. Choose weekday-only if that matches how your audience behaves.
4. Choose your risk posture. Conservative if you are recovering reputation or cannot afford a block; aggressive only if you have clean data and headroom to pause.
5. Set your IP count. The per-IP column updates so you know what each address is actually carrying.
6. Read the schedule and the warnings. Follow the segment column as strictly as the volume column — sending the right number to the wrong people is how warm-ups fail.
7. Export the CSV and monitor daily. Track complaints, bounces and deferrals against the guardrail thresholds, and hold at the current volume whenever a metric goes the wrong way.

Example 1 — SaaS newsletter reaching 50,000 a day. Target 50,000, engaged list 180,000, one IP, standard posture, weekdays only. The schedule opens at a few hundred to 30-day openers, climbs through the first fortnight, and reaches target in roughly four working weeks with a plateau at the end to consolidate. Because days are weekday-only, the calendar span is longer than the sending-day count.

Example 2 — E-commerce migration to a dedicated pool. Target 300,000 a day across four IPs. Each IP carries 75,000 at steady state, and the per-IP column makes clear that each one only accumulates a quarter of the sending history — so the pool takes longer to establish than a single IP hitting the same total would.

Example 3 — Reputation recovery after a blocklisting. Conservative posture on a fresh IP with a deliberately small engaged segment. Volumes climb slowly and the plan holds at each level longer, because the cost of a second incident is far higher than the cost of two extra weeks.

Example 4 — A list that cannot support the ask. Target 100,000 a day with an engaged list of 40,000. The planner flags it immediately: the schedule would need to mail the same people repeatedly to hit the numbers, which drives complaints rather than reputation. The fix is list growth or a lower target, not a cleverer ramp.

• Replace guesswork with a dated plan: A concrete schedule you can put in a project tracker beats a vague intention to increase gradually.
• Avoid the blocking event that costs weeks: One filtering incident undoes more progress than the entire extra time a cautious ramp would have taken.
• Build reputation from the right signals: Engagement-first segmentation means early volume comes from the people most likely to open and least likely to complain.
• Know your realistic go-live date: The sending-day count and calendar span let you commit to a date rather than hoping.
• Understand what a bigger IP pool actually costs: Per-IP figures make the reputation dilution of a wide pool visible before you buy the addresses.
• Catch trouble the day it starts: Explicit complaint, bounce and deferral thresholds tell you when to hold instead of pushing on.
• Free, private and portable: No account, nothing uploaded, and a CSV you own at the end of it.