Strategy9 min read

Deliverability as a board-level metric

The board does not want to hear about SPF. They want to know whether a high-leverage revenue channel is healthy. Here is how to earn deliverability a permanent line in the quarterly pack.

Most board packs do not mention email deliverability. They mention email — usually as a subscriber count, an attributed revenue line, and occasionally a campaign highlight — but not placement. This is an oversight at any company where email contributes more than a few percent of revenue, because placement is a leading indicator of that revenue and the only way to see it coming is to have it on the page.

This article is about how to get deliverability onto the board agenda and keep it there. It is not about what deliverability is; the board does not need that. It is about what a single board-ready line on deliverability looks like, and the discipline required to sustain it.

Directors ask two questions about any metric

Is it moving meaningfully, and is it within our control? If you cannot answer both, the metric does not belong on the slide. Deliverability passes both tests — but only if you have been measuring it.

What a board cares about, and what it does not

A board of directors is roughly three layers of abstraction above an email practitioner. They care about:

  • Whether channels driving revenue are healthy and trending favourably.
  • Whether operational risk is being managed.
  • Whether the team can articulate the health of the business in numbers they can interrogate.

They explicitly do not care about tool names, configuration files, or whether DMARC is in quarantine or reject. That entire surface is noise from their perspective.

The one line on the slide

Deliverability deserves one line in the quarterly channel health table. That line should look something like this:

Channel        Revenue    Trend    Health
──────────────────────────────────────────
Email          $4.2M      +6% QoQ   85% inbox placement (on target)
Paid search    $6.1M      +2% QoQ   CAC within tolerance
Organic        $2.3M      -3% QoQ   Ranking drop flagged

That is it. Health column carries the deliverability number. The board now has visibility without sitting through a deliverability briefing. If the number drops, there is a conversation. If it holds, there is not. Both outcomes are correct.

Getting placement onto the slide

The hard part is not the slide design. It is building the pipeline that produces a defensible placement number every quarter. Three prerequisites:

  1. Continuous measurement. A one-off test does not produce a quarterly trend. You need a seeding infrastructure that measures placement on every major send, or at minimum weekly.
  2. A blended number and per-provider detail. The board sees the blended number; the head of marketing sees per-provider so they can diagnose drops.
  3. A target band. Without a target, the number is uninterpretable. "85%" is neither good nor bad until you say the target is 85–90%.

Setting the target band

Industry norms for transactional and warm opt-in mail:

  • Best-in-class: 95%+ blended.
  • Healthy: 85–95%.
  • Underperforming: 75–85%.
  • Incident: below 75%.

Cold outreach programmes run at lower placement baselines and should have separate targets — typically 60–80% blended, because cold mail attracts more spam-filter friction.

What to do when the number drops

The value of having placement on the board slide is that it creates a forcing function. When the number drops 5pp quarter over quarter, the board wants an answer. The answer template:

  1. Root cause: one sentence. "Outlook placement dropped due to a content change in the October campaign."
  2. Impact: one sentence in revenue terms. "Estimated $180k in lost attributed revenue in Q3."
  3. Remediation: one sentence on action. "Reverted content change and added pre-send placement check; November placement recovered to 87%."
  4. Prevention: one sentence on systemic fix. "Adding automated placement test to the pre-send checklist for all campaigns over 100k recipients."

Four sentences. The board moves on. Without this discipline, the drop either does not get reported or gets buried in a fifteen-slide marketing update — both failures.

Board-level narratives that work

Narrative 1: The insurance narrative

"Email drives X% of our revenue. Placement monitoring costs Y/year and prevents the class of incident where revenue drops for weeks before anyone notices. The ROI is insurance-like: small premium, large bounded downside reduction." This works with boards that prioritise risk management.

Narrative 2: The channel health narrative

"We measure every revenue channel's health. Email's health metric is inbox placement. We added it this quarter to close a gap in our channel-health dashboard." This works with boards that like governance and consistency.

Narrative 3: The leading indicator narrative

"Inbox placement is a leading indicator of email revenue, visible 2–6 weeks before the revenue number itself moves. Including it on the pack gives us early warning of channel deterioration." This works with growth-focused boards.

Build the input layer first

You cannot present placement on a board slide until you measure it continuously. Inbox Check gives you free per-provider placement tests and a paid API for continuous measurement that feeds directly into BI tools. Measure first, then narrate.

Common pitfalls in the board presentation

Pitfall 1: Over-explaining

If your deliverability line requires more than one sentence of explanation, it is not board-ready. Distil harder.

Pitfall 2: Inconsistent definition quarter to quarter

If the placement number is calculated differently in Q2 than Q3, the trend is meaningless. Lock the methodology — same seed list, same providers, same aggregation — and report changes to methodology as footnotes.

Pitfall 3: No target

A number without a target is a data point. A number with a target is a decision aid. Set targets in collaboration with the CMO before the first board appearance.

Pitfall 4: Reporting only the blended number

The blended number is for the board. Per-provider detail is for the pre-read or the appendix. Having only one of the two means either the board cannot interpret the number or the team cannot diagnose drops.

What the first board appearance looks like

If deliverability has never been on the pack before, the first quarter you introduce it, allocate one extra line to the introduction:

New this quarter: inbox placement rate
Why: leading indicator of email revenue; 15% of company revenue
Target: 85–90% blended across Gmail, Outlook, Yahoo, Apple
This quarter: 87%
Next quarter: tracking weekly with alerting below 80%

Six lines. Introduces the metric, sets the target, reports the value, commits to an ops cadence. You have earned the line permanently.

FAQ

Does the board actually want this level of operational detail?

They want the health signal, not the operational detail. Placement is a health signal with operational detail tucked behind it. The surface-level line is all they need.

What if our board meeting is brand-focused rather than performance-focused?

Reframe placement as brand exposure: "We are reaching X% of our subscribers in their primary inbox this quarter." This lands with brand-centric boards while carrying the same diagnostic value.

How often should the metric definition change?

Annually at most. Methodology stability matters more than methodological perfection. A defensible number used consistently beats a theoretically better number that changes every quarter.

What should we do if placement is below target when we first report it?

Report it anyway, with the remediation plan. Directors respect honest diagnostics more than selective disclosure. The credibility carried into future quarters is worth the first-quarter discomfort.
Related reading

Check your deliverability across 20+ providers

Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and more. Real inbox screenshots, SPF/DKIM/DMARC, spam engine verdicts. Free, no signup.

Run Free Test →

Unlimited tests · 20+ seed mailboxes · Live results · No account required