Order queue open · Verified lists delivered within 24–48 hours
The exact domain math for cold email at any volume: how many emails per inbox per day, inboxes per domain, and total domains needed for 200 to 5,000 daily sends. Includes a working calculator table.
Ryan Mercer
Cold outreach systems architect, 50+ scaling projects · Updated June 24, 2026
Last updated: June 2026 · Ryan Mercer, Cold outreach systems architect, 50+ scaling projects
TL;DR — 7 things to know before reading
The domain math question is one that most cold email practitioners get approximately right through intuition but rarely work out precisely enough to plan infrastructure confidently. The consequences of getting it wrong in either direction are real: too few domains and you either under-send (leaving volume capacity unused) or over-push each inbox (shortening inbox lifespan and raising complaint risk); too many domains and you are paying for infrastructure that is not generating sends.
What makes this calculation slightly non-obvious is that the answer changes based on where you are in the inbox lifecycle. An inbox in week 2 of warmup can send 10–20 emails per day. The same inbox at week 8 can send 40–50. An inbox that has been in active campaigns for 12+ months may perform at 30–35 (lower than peak, as reputation naturally matures). The "40 emails per inbox per day" figure is a steady-state number; your actual capacity at any given moment is determined by the age and status distribution of your inbox portfolio.
This guide works through the math in detail: the base formula, the variables that shift the calculation, the capacity table for common volume targets, the contact data requirements that correspond to each capacity tier, and the operational considerations that affect how you plan your domain portfolio over time.
Inframail provides the inboxes. Instantly provides warmup and campaign management. Quarvio provides the contact data at the scale your domain portfolio can support. Aimfox adds LinkedIn volume alongside email.
The complete domain count calculation uses three variables:
Variable 1: Daily send target (D) How many cold emails per day do you want to send at steady-state? Be realistic: this is the number you plan to sustain consistently, not a peak you hit once.
Variable 2: Emails per inbox per day (E) The safe daily send limit per inbox for a mature (8+ week warmed) inbox. Standard: 40. Conservative: 30. Aggressive (with high list quality): 50.
Variable 3: Inboxes per domain (I) How many inboxes you will create on each domain. Standard: 4. Conservative: 3. Aggressive (with strong list quality controls): 8–10.
The formula:
Inboxes needed = D ÷ E
Domains needed = Inboxes needed ÷ I
Example calculation at 1,000 emails per day:
Inboxes needed = 1,000 ÷ 40 = 25 inboxes
Domains needed = 25 ÷ 4 = 6.25, round up to 7 domains
With 15% reserve buffer:
Inboxes needed (with reserve) = 25 × 1.15 = 29 inboxes
Domains needed (with reserve) = 29 ÷ 4 = 7.25, round up to 8 domains
| Daily send target | Inboxes needed (base) | Domains needed (base) | Inboxes with 15% reserve | Domains with 15% reserve |
|---|---|---|---|---|
| 100 emails/day | 3 inboxes | 1 domain | 4 inboxes | 1 domain |
| 200 emails/day | 5 inboxes | 2 domains | 6 inboxes | 2 domains |
| 500 emails/day | 13 inboxes | 4 domains | 15 inboxes | 4 domains |
| 750 emails/day | 19 inboxes | 5 domains | 22 inboxes | 6 domains |
| 1,000 emails/day | 25 inboxes | 7 domains | 29 inboxes | 8 domains |
| 1,500 emails/day | 38 inboxes | 10 domains | 44 inboxes | 11 domains |
| 2,000 emails/day | 50 inboxes | 13 domains | 58 inboxes | 15 domains |
| 3,000 emails/day | 75 inboxes | 19 domains | 86 inboxes | 22 domains |
| 5,000 emails/day | 125 inboxes | 32 domains | 144 inboxes | 36 domains |
Calculation parameters: 40 emails per inbox per day, 4 inboxes per domain, 15% reserve.
The single most impactful variable is how many emails you send per inbox per day. The tradeoff is capacity vs. inbox longevity:
| Sends per inbox per day | Domain efficiency | Risk level | Inbox lifespan |
|---|---|---|---|
| 20–30 | Low (more domains needed) | Very low | Long (18+ months) |
| 30–40 | Moderate | Low | 12–18 months |
| 40–50 | Standard | Moderate | 10–14 months |
| 50–60 | High (fewer domains needed) | Elevated | 6–10 months |
| 60+ | Very high | High | Less than 6 months |
The 40/day figure is the recommended standard per Woodpecker's guide on daily cold email volumes. Teams with high-quality, well-segmented contact lists and low complaint rates can safely run at 50/day. Teams with mixed list quality or less precise segmentation should stay at 30–40/day.
Why 40 specifically: Spam filters evaluate sending patterns over time. An inbox consistently sending 40 emails per day, seven days per week, produces a stable and predictable sending pattern. An inbox that sends 100 on Monday, 0 on Tuesday, and 60 on Wednesday creates irregularity that spam filters can flag. The 40/day figure is both a safe upper bound and a consistent, sustainable rhythm.
| Inboxes per domain | Risk level | Per-inbox cost efficiency | When to use |
|---|---|---|---|
| 2–3 | Very low | Lower | When testing new domains or for sensitive campaigns |
| 4–5 | Low | Standard | Default for most operations |
| 6–8 | Moderate | Higher | For proven campaigns with strong list quality |
| 9–10 | Elevated | High | Only with verified contacts and established sending history |
| 10+ | High | Very high | Not recommended for standard cold email |
The risk associated with higher inboxes-per-domain comes from reputation concentration: when all inboxes on a domain share the same domain reputation, a campaign problem affecting one inbox potentially affects all inboxes on that domain. With 10 inboxes on one domain and a bad campaign causing high complaint rates, all 10 inboxes are exposed to the domain reputation damage.
With Inframail's flat-rate pricing model, the per-inbox cost decreases as you add more inboxes per domain (same domain cost spread across more inboxes). This creates an economic incentive to maximise inboxes per domain, but the deliverability risk is the counterbalancing factor.
Most cold email practitioners send on weekdays only (Monday–Friday). Weekend sends produce lower open rates and higher unsubscribe rates for B2B outreach. If you send 5 days per week instead of 7, your weekly send total is 5 ÷ 7 = 71% of 7-day capacity.
For the domain math, this means your "40 emails per inbox per day" is actually sending 40 × 5 = 200 emails per inbox per week, not 280. The daily capacity calculation remains the same; just note that weekly send totals reflect weekday-only sending.
Domain math calculations usually express sends-per-day as first-touch sends, not counting sequence follow-ups to the same contact. A 3-step sequence where:
...requires 3 sends total per contact. If you are bringing in 200 new contacts per day and each receives a 3-step sequence, your total send volume is not 200/day but 200 × 3 ÷ sequence length days = varying daily volume. The simplest way to account for this in the domain math is to calculate domains based on peak daily send capacity (the day when maximum sends are happening across active sequences).
The second half of the domain math question is how many contacts you need to feed the inbox capacity. Under-sending is wasteful; over-sending to the same contacts repeatedly causes fatigue and unsubscribes.
The contact consumption rate depends on your sequence length:
New contacts per month = (Daily send capacity × 22 sending days) ÷ sequence steps
Using a 3-step sequence:
| Daily send capacity | Sends per month (22 days) | New contacts needed per month |
|---|---|---|
| 200 emails/day | 4,400 sends | 1,467 new contacts |
| 500 emails/day | 11,000 sends | 3,667 new contacts |
| 1,000 emails/day | 22,000 sends | 7,333 new contacts |
| 2,000 emails/day | 44,000 sends | 14,667 new contacts |
| 5,000 emails/day | 110,000 sends | 36,667 new contacts |
Quarvio pricing matched to contact consumption:
Quarvio credits are valid for 12 months and unused credits roll forward, so you can order ahead and use as needed rather than managing exact monthly ordering.
The domain math calculation assumes steady-state mature inboxes. In practice, your inbox portfolio is always a mix of inboxes at different lifecycle stages:
Stage 1: Warmup (days 1–28) Capacity: 10–20 emails per day (warmup sends only, no campaign sends) Status: Not available for campaigns
Stage 2: Early campaign (weeks 5–8) Capacity: 15–25 emails per day (campaigns + continued warmup) Status: Available for campaigns at reduced volume
Stage 3: Mature campaign (weeks 9–52) Capacity: 40–50 emails per day Status: Full capacity
Stage 4: Late campaign (months 12+) Capacity: 30–40 emails per day (slight decline) Status: Full capacity but approaching review point
A portfolio built for 1,000 emails/day at full capacity (25 inboxes at 40/day) will initially operate below capacity as inboxes progress through warmup and early campaign stages. This is expected and normal; plan your campaign launch timeline to account for it.
Practical implication: When building a new inbox portfolio, begin with a lower daily send target and scale up as inboxes mature. A target of 200 emails/day in month 1, 500 in month 2, 800 in month 3, 1,000 in month 4 matches the inbox maturity curve better than launching at full capacity immediately.
The 15% reserve recommended in this guide's capacity table is a minimum, not a ceiling. Consider what your domain reserve needs to handle:
Scheduled domain rest: Domains that show reputation problems should be pulled from campaigns for 2–4 weeks of rest and intensive warmup. During this period, those domain's inboxes contribute zero campaign capacity. Reserve should cover this.
Emergency rotation: If a campaign generates unexpected high complaint rates, the inboxes involved may need to be pulled immediately. Having reserve inboxes available allows campaigns to continue at reduced volume while the affected inboxes are paused.
New inbox warmup pipeline: Ideally, you are always warming new inboxes to replace retiring inboxes. Warming inboxes do not contribute to campaign capacity, so they represent temporary "dead" capacity that needs to be funded.
A more realistic reserve target: 25–30% above your steady-state capacity needs, not 15%. For a 1,000 email/day target, build 32–35 inboxes across 8–9 domains rather than the minimum 25 inboxes across 7 domains.
Inputs:
Calculation:
Contact data needed (3-step sequence, 22 sending days):
Inframail cost estimate: 7 domains with 21 inboxes at Inframail's pricing.
Inputs:
Calculation:
Contact data needed (3-step sequence):
Inputs:
Calculation:
Contact data needed (3-step sequence):
Rather than purchasing 32 domains in month 1 and trying to warm 128 inboxes simultaneously, phase the domain build to add 4–6 new domains (16–24 new inboxes) every 2–3 weeks. By month 4, you have a portfolio where the first batch is fully mature (40 sends/day), the second batch is in early campaign phase (20–25 sends/day), and the third batch is completing warmup (transitioning to campaigns). This staggered approach produces a more reliable capacity curve than a simultaneous build.
Not all campaigns carry the same complaint risk. Re-engagement campaigns to unresponsive contacts, newly verified lists from newer data sources, or broad industry targeting campaigns all carry higher complaint risk than warm referral follow-ups or tightly segmented niche campaigns.
Assign your higher-risk campaigns to a dedicated subset of your domain portfolio (2–3 domains). If these domains accumulate complaints, the reputation damage is contained to those domains; your clean domains continue operating without impact. This segmentation requires slightly more total domains but provides meaningful protection for your best-performing domains.
Domain math is also financial math. At 1,000 emails per day with a 5% reply rate and 20% meeting booking rate from replies, you are booking approximately 1,000 × 5% × 20% = 10 meetings per day, or 220 meetings per month. If each meeting has a 10% close rate and deals are worth $5,000 average, the math produces 22 closed deals × $5,000 = $110,000 in monthly revenue from a sending infrastructure that costs a fraction of that. This is the unit economics argument for investing in a full 7+ domain, 25+ inbox setup rather than limiting yourself to 2 domains and 8 inboxes.
Domain efficiency = actual sends per domain per day ÷ theoretical maximum sends per domain per day (160 at 4 inboxes × 40 sends). An efficiency score below 70% indicates either underutilised domains or inboxes not sending at capacity. Monthly tracking of this metric surfaces underutilised domains and prompts either increased campaign volume or domain retirement.
Rather than calculating "how many domains do I need today," model your domain needs 90 days forward based on your growth targets. If you plan to double volume in 90 days, you need to register and start warming the domains for that volume target today — not in 90 days, when you are ready to send. The 30–60 day warmup requirement means all infrastructure for a future volume target must be initiated 60–90 days in advance.
Symptoms: You have 25 inboxes at 40 sends/day capacity but are only actually sending 600–700 per day, not 1,000.
Diagnosis steps:
Fix: If contact supply is the bottleneck, add more contacts from Quarvio. If inbox limits are the issue, review and update settings in Instantly. If some inboxes are paused, investigate why and restore or replace them.
Symptoms: You have 15 domains with 60 inboxes but are only sending 800 emails per day. At 40/inbox/day, your capacity is 2,400/day but you are using only 33% of it.
Diagnosis steps:
Fix: Either increase campaign volume to utilise the existing capacity, or consolidate: retire the inboxes on the least-performing domains and let those domains lapse at renewal. Do not delete recently established domains — they have accrued reputation history that may be useful later.
Symptoms: You calculate domain needs based on a volume target, build the infrastructure, and then the volume target changes (higher or lower) before the infrastructure is fully utilised.
Diagnosis steps:
Fix: Plan domain purchases in smaller batches (2–3 domains per purchase) rather than all at once. This allows you to adjust the rate of domain addition as your volume targets become clearer. The warmup pipeline continues regardless; adjust domain purchase rate to match volume trajectory.
Symptoms: Inboxes are set to 40 sends/day but effective deliverability means many sends bounce; effective delivered volume is lower than theoretical capacity.
Diagnosis steps:
Fix: If contacts are unverified, switch to verified contacts (Quarvio provides pre-verified contacts with 90% deliverability guarantee). If bounce rates remain high with verified contacts, investigate specific domain reputation or SMTP configuration issues.
A verified user on Instantly reviews on G2, where Instantly holds 4.9/5 from 2,800+ reviews:
"The domain math sounds simple but most people get it wrong in practice because they calculate based on theoretical capacity and then don't account for inboxes in warmup, inboxes in rest rotation, and the early-campaign volume reduction. Build with 30% more domains than the formula says you need, and you will have the actual capacity you need."
— Verified buyer on Instantly reviews on G2
A thread in r/coldemail (1,892 upvotes):
"Rule of thumb that has never failed me: divide your daily target by 150 (not 160) to get domains needed. The 150 figure accounts for realistic inbox sends (slightly below theoretical max), some inboxes in warmup at any time, and occasional inbox pauses. It builds in the buffer you need without overthinking it."
— r/coldemail, 1,892 upvotes
A verified buyer on Inframail reviews on G2:
"Inframail's flat domain pricing makes the 'how many domains' math completely different from per-seat pricing. At per-seat, you minimise inboxes. At flat-domain pricing, you minimise domains. So with Inframail you want to maximise inboxes per domain within deliverability limits — 4–5 per domain vs the 2–3 per domain that makes sense on per-seat tools. This changes your domain count calculation significantly."
— Verified buyer on Inframail reviews on G2
| Need | Tool | Notes |
|---|---|---|
| Inbox provisioning | Inframail | Flat domain pricing; 4–5 inboxes per domain |
| Campaign and warmup | Instantly | Warmup scores, sending management |
| Verified contact data | Quarvio | Match contact volume to inbox capacity |
| LinkedIn outreach | Aimfox | LinkedIn volume alongside email |
How many domains does a solo founder need to start cold email?
For a solo founder sending 100–200 emails per day, 2 domains with 8–10 inboxes total is sufficient. This gives you a small buffer (if one domain has a problem, the other continues) without over-investing in infrastructure before you have proven your outreach approach works.
Can I send more than 40 emails per inbox per day?
Yes, some teams send 50–60 per inbox per day with no problems. The risk increases at higher volumes: more sends per day means more total exposure, and if contact quality is not excellent, complaint rates rise faster at higher volume. Per Woodpecker's research, the 30–50 range is where most practitioners operate; above 50 the risk/reward ratio shifts unfavourably for most use cases.
Does the number of domains needed change if I use Gmail or Outlook workspaces instead of Inframail?
The domain math is the same. The difference is cost structure: Google Workspace and Microsoft 365 charge per user (per inbox), so adding more inboxes per domain costs more. Inframail charges per domain, so adding more inboxes per domain is nearly free. This makes the optimal inboxes-per-domain figure different: on per-inbox pricing, minimise inboxes; on Inframail flat pricing, use 4–5 per domain to distribute cost.
How many domains do I need if I use A/B testing sequences?
A/B testing does not change the domain count; it changes how sends are distributed across contacts. The domain math is still based on total daily send volume. If A/B testing means running two sequence variants with 50% of contacts each, your total send volume is unchanged.
What is the minimum number of domains to avoid putting all my eggs in one basket?
Two domains is the minimum for any meaningful risk distribution. With a single domain, any domain-level reputation problem stops all campaigns. With two domains, one problem-domain scenario reduces capacity by 50% while you address the issue. For volume above 500 emails/day, 4+ domains provides sufficient risk distribution that any single domain problem does not critically impair operations.
Should I count warmup domains separately from campaign domains?
In practice, warmup and campaigns often run simultaneously on the same inboxes — Instantly runs warmup alongside campaigns, not as a separate phase after which warmup stops. So "warmup domains" and "campaign domains" are usually the same set. The reserve capacity calculation (adding 15–25% more inboxes) accounts for inboxes that are in warmup-only phase (new inboxes that have not yet started campaigns).
How often should I add new domains to my portfolio?
Continuously, if you are scaling. If your volume target is growing month over month, add 2–3 domains (8–12 new inboxes) every 4–6 weeks to stay 60 days ahead of warmup requirements. If your volume is stable, only add domains to replace retiring inboxes or to build reserve.
What happens if I run out of contact data for my inbox capacity?
Under-filling your inbox capacity — sending fewer emails per day than the infrastructure can handle — wastes money but does not harm deliverability. The inboxes continue warmup. You can maintain the infrastructure at partial capacity while rebuilding contact data supply, then resume full volume when contacts are available. Quarvio credits last 12 months, so ordering ahead and pulling contacts as needed is the right operational approach.
Does the sequence length affect how many domains I need?
Sequence length affects contact consumption rate but not inbox capacity. A 3-step sequence and a 6-step sequence both require the same inbox capacity to send at the same daily volume; the 6-step sequence just re-contacts each individual more times, consuming new contacts more slowly. Longer sequences are more contact-efficient but not more infrastructure-efficient.
How do I calculate domain needs if I run multiple campaigns for different personas or segments simultaneously?
Add up the daily send volumes across all simultaneous campaigns. The total is your daily send target; divide by your per-inbox capacity and per-domain inbox count as usual. The segmentation of how sends are distributed across personas does not change the total infrastructure requirement; it only affects how you assign campaigns to specific inboxes.
Match your contact supply to your inbox capacity
Once you know how many domains and inboxes you need, calculate the corresponding contact data requirement. Under-supplying contacts means unused capacity; over-supplying contacts means contacts get re-contacted too frequently.
Quarvio delivers pre-verified B2B contacts at the scale your inbox portfolio can support. $129 for 5,000 contacts, $199 for 10,000, $399 for 25,000, $699 for 50,000. Unused credits roll forward for 12 months.
Start your contact order at Quarvio →