Cold Email Cost Per Mailbox at Scale

"What does a mailbox cost?" is the wrong question, and it is the one almost every outbound team asks first. A mailbox is not a line item. It is a bundle of a licence, a slice of a domain, a slice of a platform, a warmup period during which it earns nothing, and a recurring share of somebody's time. Price only the licence and you will under-budget by a wide margin. Price all five and the number stops being a shopping decision and starts being a unit economics decision.

This matters most at the point where teams scale. The per-mailbox economics of a 10-mailbox setup and a 500-mailbox setup are genuinely different, and not in the direction most people assume. Some costs fall sharply with volume. One large cost does not fall at all. And a set of costs that were invisible at 10 mailboxes become the dominant term at 200.

This guide builds the model from the ground up: the five real cost drivers, why the per-mailbox curve flattens instead of collapsing, an illustrative cost structure at 10, 50, 200 and 500 mailboxes, the hidden costs that break budgets, and finally the metric that should replace cost per mailbox entirely once you are past the experimentation stage — cost per booked meeting. If you want the getting-started version of this — how to stand up a lean setup on a small budget — read our guide to cost-effective cold email infrastructure setup first. This article picks up where that one ends.

The Five Things You Are Actually Paying For

Every fully loaded mailbox cost decomposes into five components. Understanding which of them scale with volume and which do not is the whole game.

1. Mailbox licences (per-seat, strictly linear)

Every mailbox you send from needs a real, licensed identity at a real provider. This is the one component with essentially no economies of scale — the hundredth mailbox licence costs what the first one did. Volume agreements exist at genuine enterprise scale, but for the range most outbound teams operate in, treat licence cost as a pure multiple of mailbox count. It is usually the single largest line item, and it is the one you cannot engineer away.

2. Domains (shared across mailboxes, so sub-linear)

Domains are cheap individually and are amortised across the mailboxes that sit on them. At two to three mailboxes per domain — the ratio most cold email operations settle on — a domain registration spread over a year and across three mailboxes becomes a small per-mailbox figure. The interesting decision is not price but ratio: pushing more mailboxes onto each domain lowers cost per mailbox and raises blast radius when a domain is flagged. Our breakdown of how many mailboxes you need for cold email covers the safe ratios in detail.

3. Infrastructure platform (tiered, so falls with scale)

The platform that provisions domains, configures DNS, creates mailboxes and keeps them healthy is typically sold in tiers with an included mailbox allowance plus an add-on rate beyond it. Because the base fee is spread across a larger allowance at each tier, the platform component of your per-mailbox cost falls as you move up. This is the clearest source of genuine scale economics in the stack, and it is worth modelling explicitly rather than assuming a flat rate.

4. Warmup, monitoring and reputation (mostly linear, partly fixed)

Warmup is a per-mailbox activity, so its direct cost tends to track mailbox count. Reputation monitoring is closer to per-domain, which makes it sub-linear. The expensive part of this category is not the tooling fee at all — it is the opportunity cost of capacity that is billed but not yet sending, which we treat separately below because it is routinely the largest omission in cold email budgets.

5. Operations and engineering time (fixed-ish, then step-function)

Someone buys the domains, sets the DNS, creates the mailboxes, fills in profiles and signatures, connects everything to the sending platform, watches the health dashboards and replaces what burns. At 10 mailboxes this is a weekend. At 200 it is a recurring part of a role. At 500 it is a role. Priced at any realistic internal hourly rate, this line frequently rivals licence spend — and it is the one almost nobody puts in the spreadsheet.

"Teams that under-budget cold email rarely got the licence price wrong. They forgot that infrastructure has an hourly rate attached to it."

Why Per-Mailbox Cost Flattens Instead of Collapsing

It is tempting to assume that if you buy ten times as many mailboxes, the per-unit cost drops by something like ten times. It does not, and understanding why prevents both over-optimistic budgets and pointless negotiations.

Split the cost into two buckets. The variable bucket — mailbox licences and per-mailbox warmup — is close to perfectly linear. The shared bucket — domains, platform base fees, monitoring and the fixed portion of operations time — is amortised across whatever mailbox count you run. Total cost per mailbox is therefore the variable rate plus the shared pool divided by mailbox count.

The consequence is a curve that drops steeply early and then flattens hard. Going from 10 to 50 mailboxes spreads the shared pool across five times as many units, which is a large per-unit improvement. Going from 200 to 500 spreads it across 2.5 times as many units, but by then the shared pool is already a small fraction of the total — so the improvement is marginal. Past a certain point, your per-mailbox cost asymptotically approaches the licence rate, and no amount of further scaling will push it below that floor.

There is a second-order effect that pushes in the opposite direction, and it is why some large operations see per-mailbox cost rise: at high mailbox counts the ops burden stops being fixed and becomes a step function. Somewhere between 100 and 300 mailboxes, most teams cross the threshold where health monitoring, replacement and reconfiguration no longer fit into slack time and start requiring dedicated headcount. If your model treats ops as a constant, it will be wrong exactly at the scale where the decision matters most.

Cost Structure at 10, 50, 200 and 500 Mailboxes

The table below is a structural illustration, not a price list. The figures are placeholders chosen to show how the shape of the cost changes with scale; your own licence rates, domain registrar, platform tier and internal hourly rate will move every number. Use it as a template to fill in, not as a benchmark to quote.

Read the last row, not the individual cells. The story of the table is that per-mailbox cost falls most between 10 and 50, still improves meaningfully to 200, and barely moves from 200 to 500 — while the ops row moves in the opposite direction the entire time. The interesting scale question is not "how cheap can a mailbox get" but "at what point does the ops line overtake the savings?"

The Hidden Costs That Break Budgets

These are the components that almost never appear in a first-pass budget and almost always appear in the actual invoice.

• Idle warmup capacity. Mailboxes bill from day one and cannot carry full volume for two to four weeks. With ongoing replacement, a slice of your fleet is permanently in this state — paid for, producing nothing.
• Replacement churn. Mailboxes get burned and domains get retired. Every replacement re-incurs the setup cost, the warmup window and the ops time, so churn multiplies your effective per-mailbox cost by more than the sticker price suggests.
• Domain burn. A flagged domain does not just cost a new registration — it costs every mailbox sitting on it, all of which must be rebuilt and re-warmed simultaneously. This is the direct financial argument for keeping mailboxes-per-domain low.
• Rework from misconfiguration. A wrong SPF include or an unpublished DKIM key can silently degrade an entire cohort. The cost is not the fix; it is the weeks of sends that underperformed before anyone noticed.
• Deliverability drag. The largest hidden cost of all. Every email sent from a mailbox with poor placement is fully paid for and partially wasted. Deliverability is a multiplier on your entire spend, which is why it belongs in a cost model rather than only in a quality discussion.
• Reconciliation and admin overhead. At scale, tracking which mailbox belongs to which domain, client or campaign — and which are actually being billed — becomes real work. Orphaned, paid-for mailboxes are extremely common in operations above 100 seats.
• Switching costs. Whatever you build, you may need to move it. Factor in that migrating providers has its own cost and risk profile, covered in our guide to migrating cold email infrastructure without losing deliverability.

A useful discipline: add a churn and idle-capacity factor to your model as an explicit multiplier on the licence line rather than pretending every mailbox you pay for is a mailbox that sends. Teams that do this are rarely surprised by their invoice; teams that do not, always are.

The Metric That Should Replace Cost Per Mailbox

Cost per mailbox is an input metric. It tells you what you spend, not what you get. Once your infrastructure is past the experimental stage, the only number worth optimising is cost per booked meeting — because that is the unit your pipeline is actually made of.

Look at where inbox placement sits in that chain. It multiplies everything downstream. Halve your placement rate and you halve your meetings from an identical spend — which means you have doubled your cost per meeting without changing a single price. This is the reason a cheaper mailbox is frequently the more expensive mailbox.

Work through the comparison directionally. Take two setups with the same mailbox count and the same sending volume. Setup A costs less per mailbox but lands at moderate inbox placement. Setup B costs more per mailbox but lands at high placement. Because placement multiplies through replies and meetings, Setup B produces materially more meetings from the same volume — and its higher per-mailbox price is spread over more of them. The setup that looked cheaper on the input metric is more expensive on the output metric, and the output metric is the one your revenue model uses.

Two practical implications. First, never compare infrastructure options on per-mailbox price alone — a price comparison without a placement assumption is not a comparison. Second, spending that improves placement is usually the highest-return spend in the stack, because it acts on the multiplier rather than on a single term. Our guide to calculating and optimising cold email ROI walks the same chain through to closed revenue.

"Cost per mailbox is what you pay. Cost per meeting is what you buy. Only one of them belongs in a scaling decision."

How to Model Your Own Numbers Before You Scale

Build this once and re-run it every time someone proposes adding capacity. It takes under an hour and it prevents the most expensive category of outbound mistake: scaling volume on top of economics that do not work.

1. List every recurring line. Licences, domains, platform, monitoring, outreach tool, data and verification. Anything billed monthly or annually goes in.
2. Put a price on ops time. Estimate hours per month spent on provisioning, health checks and replacement, and multiply by a realistic internal rate. If this feels uncomfortable to write down, that is the signal it is large.
3. Apply a churn and idle factor. Estimate the share of your fleet that is warming or out of service at any moment, and inflate the licence line accordingly. This converts "mailboxes paid for" into "mailboxes sending".
4. Split fixed from variable. Separate the shared pool from the per-mailbox rate so you can re-run the model at any mailbox count without rebuilding it.
5. Model three counts, not one. Compute cost per mailbox at your current count, at roughly double, and at roughly five times. The shape of the curve tells you where the efficient scale actually is.
6. Convert to cost per meeting. Layer in your real placement, reply and meeting-conversion rates. This is the output that should drive the decision.
7. Re-check the ops step. Ask explicitly at what mailbox count your current operating model breaks and requires headcount. Model the step, because it will not appear gradually.

Pair the model with clear scaling triggers so you add capacity for the right reasons. Our guide to when to add more mailboxes covers the demand-side signals that should precede any of this spend, and mailbox provisioning at scale covers the operational patterns that keep the ops line from exploding.

Where InboxOne Sits in the Model

InboxOne is the platform component of the model above — the layer that provisions domains and mailboxes, configures authentication and keeps the fleet healthy. Its published plans are tiered specifically so that the platform share of your per-mailbox cost falls as you scale:

• Starter, $39/month, 10 Google mailboxes included. The stage where you are proving that sequences and targeting work before spending on volume.
• Scale, $99/month, 30 mailboxes included. Roughly three times the allowance for roughly 2.5 times the fee — the tiering doing exactly what tiering is supposed to do.
• Max, $299/month, 100 mailboxes included. The point where the platform base fee has been amortised down to a small share of fully loaded per-mailbox cost.
• Extra mailbox quota at $3.50, $3.25 or $3.00 per mailbox per month depending on tier, added or removed at any time, so you can scale in small increments instead of jumping a tier before you need to.
• InboxOne Protect at $2 per domain per month for continuous DNS and blacklist monitoring — priced per domain rather than per mailbox, which is why the monitoring line is sub-linear in the model.

The larger effect, though, is on the operations line rather than the subscription line. Automated DNS configuration, bulk provisioning and continuous health monitoring are what stop the ops step-function from arriving at 200 mailboxes. Converting variable human hours into a fixed subscription is not a marginal saving at scale — on most models it is the difference between per-mailbox cost flattening and per-mailbox cost turning back upward.

See the full breakdown on the InboxOne pricing page, including quarterly and annual billing options that lower the platform component further.

Key Takeaways

• A mailbox is five costs, not one: licence, domain share, platform share, warmup and reputation, and operations time.
• Per-mailbox cost flattens rather than collapsing. Shared costs amortise; the per-seat licence does not, and it becomes the floor.
• Ops time is the line that can reverse the curve. Somewhere past 100–300 mailboxes it becomes a step-function unless it is automated.
• Idle warmup capacity and replacement churn are the two most commonly omitted costs. Model them as an explicit multiplier on the licence line.
• Deliverability is a cost multiplier, not a quality metric. Poor placement inflates cost per meeting without changing a single price.
• Optimise cost per booked meeting, not cost per mailbox. A price comparison with no placement assumption is not a comparison.
• Build the model at three mailbox counts — current, double, five times — before committing to any scaling plan.

Frequently Asked Questions