Deliverability as a Business Lever

Every deliverability number has a money number behind it. This article shows how to turn inbox placement into revenue, what deliverability problems cost, and how to explain both to your boss, your finance team and your engineers. Use it to win time and budget for the work the rest of this manual describes.

Deliverability is a business number

Inbox placement is the share of your emails that land in the inbox, rather than in spam or nowhere. If it drops from 95% to 85%, about one in ten of the people you used to reach no longer sees your email. That’s not just a technical problem. It’s a smaller audience for every email you send.

How placement turns into revenue

For a business that sells through email, revenue follows a chain:

revenue = emails sent × inbox rate × open rate × click rate × purchase rate × average order value

Each rate is a share of the step before it: the share of sent emails that reach the inbox, the share of those that get opened, the share of opens that get a click, and the share of clicks that become a sale. Average order value is what each sale is worth. Because each step multiplies the next, a drop at the inbox shrinks everything after it.

Treat open rates with care. Apple Mail Privacy Protection opens emails automatically for many Apple Mail users, so open rates look higher than they are. Clicks and sales are more reliable.

Example: a 10-point drop in inbox placement

	Before	After
Emails sent a month	500,000	500,000
Inbox placement	95%	85%
Emails in the inbox	475,000	425,000
Opened (22% of inbox)	104,500	93,500
Clicked (3.5% of opens)	3,658	3,273
Bought (2.2% of clicks)	about 80	about 72
Average order value	$85	$85
Revenue a month	about $6,840	about $6,120
Lost a month		about $720
Lost a year		about $8,640

Only the inbox rate changed. That’s 50,000 fewer emails in the inbox, about 10.5% fewer, so revenue also falls about 10.5%. A business making $500,000 a year from email would lose about $52,600 a year from the same drop.

Problems feed themselves

The example assumes the drop stays put. In reality, deliverability problems tend to grow:

Less mail in the inbox means fewer opens and clicks. Providers see that engagement (how people interact with your mail) has dropped, so they send more of it to spam. The loop continues until you fix the cause. A “small” problem left alone for three to six months can do far more damage than it first seemed.

What deliverability problems cost

Direct costs

Staff time. A typical incident takes 4–8 hours to find the cause, 2–4 hours to fix, and 2–4 weeks of watching while things recover. A new IP address or domain adds warm-up time. At $100–200 an hour for a senior engineer, that’s $600–2,400 for one incident, before the weeks of monitoring.

Paying for email nobody sees. Many ESPs (email service providers, the companies that send your mail for you) charge by emails sent or contacts stored. Mail that bounces or lands in spam still counts. With a 10% bounce rate on 500,000 emails, you pay for 50,000 messages that never arrive.

Tools. Inbox placement tests, blocklist monitoring and email validation cost extra each month, more as you grow.

Hidden costs

• Unhappy customers. When receipts, password resets or shipping updates land in spam, customers contact support, wonder whether their order went through, or give up on signing in.
• Missed sales. Every email in spam is a sale not made or a customer not kept. You can’t see these costs, but they’re often the largest.
• Brand damage. People who find you in their spam folder start to connect your brand with spam.

Making the case for investment

Speak each person’s language

Fill in your own numbers:

• CEO or finance lead: “Email earns us $X a month. A 10-point drop in inbox placement would cost about $Y a year. Spending $Z on monitoring and good practice protects that income.”
• Head of marketing: “Raising inbox placement from 85% to 95% reaches about 12% more people. On 500,000 emails a month, that’s 50,000 more inboxes, like adding subscribers without paying to find them.”
• Head of engineering: “Each incident takes the team X hours to find and fix. Stronger authentication and monitoring prevent them.”
• Product team: “When password-reset emails land in spam, X% of people drop out of the reset flow.” Measure your own drop-off before you say this.

Compare the cost with what it protects

What you spend: a dedicated IP address if your volume justifies one, inbox placement monitoring, email validation, blocklist monitoring, and 20–40 hours of engineering time to set it up. Prices vary a lot by provider and volume, so add up your own yearly total.

What you get back: revenue you don’t lose to incidents, more revenue when placement improves, less time spent on emergencies, and fewer support tickets.

Then compare. In the example above, a business earning $500,000 a year from email loses about $52,600 from a 10-point drop. A $10,000 yearly budget that prevents one such drop pays for itself about five times over.

Numbers to report

For leadership

Turn each technical number into the business question it answers:

Technical number	What it tells the business	Target
Inbox placement rate	How many people we actually reach	Above 95%
Bounce rate	How healthy our list is	Below 1%
Spam complaint rate	How happy subscribers are	Below 0.1%, never above 0.3%
Gmail spam rate (Postmaster Tools)	How Gmail users react to us	Below 0.1% and steady
Revenue per email sent	How efficient the channel is	Steady or growing
Revenue from email	How much email adds	Share of total revenue

Gmail and Yahoo require bulk senders (5,000 or more messages a day to their users) to keep spam complaints under 0.3%. Aim well below that.

Monthly report

1. Inbox placement: a 30-day chart, per provider.
2. Revenue impact: revenue kept or lost, estimated from placement.
3. Authentication: how many emails pass SPF, DKIM and DMARC. Aim for close to 100%. Forwarded mail causes a few failures you can’t prevent.
4. List health: bounce rate, list growth, and how many subscribers are active.
5. Incidents: what went wrong, why, and how you fixed it.
6. Coming risks: for example, a growing group of inactive subscribers or a planned jump in volume.

Quarterly review

Add year-over-year trends, a comparison with competitors if you have the data, plans for growing volume, a review of tool budgets, and whether your team has the skills it needs.

Who owns deliverability

Deliverability sits between marketing, engineering and operations. Without a clear owner, it falls through the cracks.

Owner	When it works
Marketing	A small team where marketers send all the email
Engineering	A technical team runs the sending systems
A dedicated deliverability role	Mid-size and large senders with real email revenue
A shared responsibility chart	Large companies with several sending teams

A RACI chart splits the work. For each task it names who does it (Responsible), who answers for the result (Accountable), who gives input (Consulted), and who is kept up to date (Informed):

Task	Responsible	Accountable	Consulted	Informed
Authentication setup	Engineering	Engineering	Marketing	Leadership
List hygiene	Marketing	Marketing	Engineering	Leadership
Volume management	Marketing	Marketing	Engineering	—
Monitoring and alerts	Engineering	Engineering	Marketing	Leadership
Incident response	Engineering	Marketing (business impact)	Both	Leadership
Vendor management	Marketing	Marketing	Engineering	Finance
Reporting	Marketing	Marketing	Engineering	Leadership

Working across teams

Before a big send

• Is the list validated, so you expect under 1% bounces?
• Do SPF, DKIM and DMARC pass? Send a test to the test inbox to see.
• Is the volume less than twice your last send?
• Have you checked the links in the email against blocklists?
• Is monitoring switched on?

When something goes wrong

1. Spot it: an alert fires, or someone notices.
2. Size it: how bad is it, and which kinds of mail are affected?
3. Tell people: the affected teams and leadership.
4. Limit the damage: quick steps to stop it getting worse.
5. Find the cause: what happened, and why.
6. Fix it: confirm you have fully recovered.
7. Learn from it: change what’s needed so it doesn’t happen again.

Review changes first

Check these for their effect on deliverability before you make them: DNS changes, a move to a new ESP, new sending domains or IPs, big volume changes, new ways of collecting subscribers, and redesigned templates.

What to do next

• Work out how much revenue email brings in, using the chain above with your own numbers.
• Estimate what a 10-point drop in inbox placement would cost you.
• Decide who owns deliverability, and write down who does what.
• Start a monthly report covering placement, authentication, list health and incidents.
• Agree on a pre-send check and an incident process that every team follows.