Email Revenue Forecast: A Copy-and-Adapt Template Pack

An email revenue forecast is a defensible estimate of the revenue your email programme will produce over a period, built from four inputs: reachable list size, send plan (campaigns plus automations per month), expected conversion rate, and average order or contract value. This article gives you five copy-and-adapt templates — a spreadsheet model, an assumptions log, a one-page memo, a monthly re-forecast check-in, and the internal email that circulates it — plus the subject lines and preview text to pair with them.

What an email revenue forecast is actually for

A forecast does two jobs. First, it sizes the return on email investment so you can defend a budget line next to paid channels. Second, it sets a target the team can be held to and, more usefully, diagnose when it misses.

The distinction that matters: a forecast is a range with named assumptions, not a promise. If you present a single number, you have made a promise you cannot keep, because at least one of your four inputs will move.

The model is only as good as its historical inputs, so step one is pulling real numbers rather than guessing. You need delivery, bounces, complaints, clicks and approximate opens, per campaign and overall — the figures Mailerflow's analytics report per campaign and across your account, which is where the conversion and click-rate inputs come from. If you are still building the business case around those numbers, the ROI calculator template covers the budget-conversation side.

If you are still deciding where to send from, see the Best Email Marketing Platforms compared side by side, with prices checked daily on each provider's own pricing page.

When to use these email revenue forecast templates

Three situations justify the full pack:

• Annual or quarterly budget planning. Email competes with paid channels for the same pot. Use Template 1 (model) plus Template 3 (memo). The memo is what gets read; the model is what gets questioned.
• A proposal to add headcount, tooling or list-growth spend. Use Template 2 (assumptions log) plus Template 3. Reviewers will attack the assumptions, not the arithmetic, so lead with them.
• A mid-quarter re-forecast. After a deliverability problem, a list change or a pricing change, use Template 4 (check-in) and update Template 2 rather than rebuilding the model.

When not to use them: a brand-new list with no send history, or any period following a major change — new sending domain, new offer, new market — where historical conversion no longer applies. In those cases forecast a range, label it explicitly as a hypothesis, and commit to validating it in the first 30 days.

The templates (copy and adapt)

All numbers below are invented for fictional companies. They illustrate how the arithmetic flows; they are not benchmarks.

Template 1: The forecast model (spreadsheet layout)

Paste this header row into a spreadsheet:

Worked illustrative example for a fictional B2C brand with a 40,000-contact list:

Two inputs people forget. First, deliverable rate: bounces and complaints reduce the audience before a single click happens, so forecast on reachable contacts after suppression, not on the raw list. Second, effective reach: not every contact receives every send. Segment overlap and engagement-based exclusions mean your 6 emails per contact is really 6 emails for the engaged core and fewer for everyone else.

Build the low and high cases as a simple multiplier on conversion rate — 0.7x and 1.3x is enough — rather than maintaining three full models. If your conversion rate is genuinely uncertain, widen to 0.5x and 1.5x and say so.

Template 2: The assumptions log

This table matters more than the model. It is what lets you defend the number in a meeting and update it honestly.

Rule: any assumption marked low confidence gets a range in the memo, not a point value. The blended conversion rate above is a good example — if campaigns and automations convert differently, split the row.

Template 3: The one-page memo to leadership

Structure it exactly like this:

HEADLINE
Email revenue forecast: $X–$Y for [period], midpoint $Z.

WHAT DRIVES IT
- Reach: [n] reachable contacts, growing at [rate] per month
- Send plan: [n] campaigns + [n] automations per month
- Conversion: [rate] click-to-conversion at $[AOV] average order value

WHAT WE NEED
- [Budget / headcount / tooling], by [date]

WHAT COULD BREAK IT
- [Risk 1] — early signal to watch: [metric]
- [Risk 2] — early signal to watch: [metric]

HOW WE WILL KNOW
- Day 30: [checkpoint]
- Day 60: [checkpoint]
- Day 90: [checkpoint]

Filled illustrative version for a fictional B2B SaaS company:

HEADLINE
Email revenue forecast: $180k–$260k pipeline-sourced for H1, midpoint $215k.

WHAT DRIVES IT
- Reach: 22,000 reachable contacts, +400/month net of unsubscribes
- Send plan: 4 campaigns + 3 nurture automations per month
- Conversion: 1.8% click-to-opportunity at $9,400 average contract value

WHAT WE NEED
- One lifecycle marketer (0.5 FTE) and $1,200/quarter in list-growth spend, by February

WHAT COULD BREAK IT
- Deliverability: complaint rate above 0.1% — watch weekly reputation
- Offer change: pricing page rewrite in March — watch demo-request rate

HOW WE WILL KNOW
- Day 30: click rate within 15% of forecast
- Day 60: opportunity rate per 1,000 clicks holding
- Day 90: re-forecast with two months of actuals

Lead with the range and the assumptions. A memo that opens with the best-case number invites the reader to hold you to it.

Template 4: The monthly re-forecast check-in

FORECAST VS ACTUAL — [month]
Forecast: $X | Actual: $Y | Variance: Z%

VARIANCE BY INPUT
- Reach: forecast [n] / actual [n]
- Deliverability: forecast [%] / actual [%]
- Click rate: forecast [%] / actual [%]
- Conversion rate: forecast [%] / actual [%]
- AOV: forecast $[n] / actual $[n]

BIGGEST MOVER: [input], [direction], [magnitude]
ACTION TAKEN: [what changed]
REVISED FORECAST: $X–$Y

Variance by input beats variance by total, because it tells you whether to fix the list, the content or the offer. A revenue miss caused by a click-rate drop is a content problem; the same miss caused by a deliverability drop is a list-hygiene problem. Per-campaign analytics make this a 15-minute job rather than a half-day one.

Template 5: The subject line and preview text for the forecast review email

This is the internal email that circulates the forecast, not a marketing send. Keep it plain.

Body template:

Hi [name],

Attached is the [period] email revenue forecast: $X–$Y, midpoint $Z.

The three drivers are [reach], [send plan] and [conversion]. The assumptions
and their sources are in the second tab, so you can see which ones are firm
and which are still estimates.

The ask: [budget / headcount / decision] by [date].

Happy to walk through the model — it takes ten minutes.

[Name]

Adapt by audience. For a board, lead with the range and the ask. For the working team, lead with the variance and the action, and drop the pleasantries.

How to personalize these templates to your business

Four adaptations do most of the work.

B2C vs B2B. B2C forecasts use average order value and a short conversion window. B2B needs pipeline value and a longer window — a click in March may convert in June, so either extend the attribution window or forecast on opportunity creation rather than closed revenue, and say which you chose.

Transactional vs marketing revenue. Decide whether transactional emails count, then stay consistent across periods. Switching definitions between quarters is the fastest way to lose credibility.

Automation vs campaign split. Automations often convert differently from one-off campaigns. If your data supports it, forecast them as two lines. If you segment by engaged versus unengaged contacts, note that unengaged contacts drag both deliverability and conversion down, so a forecast built on a blended rate will overstate revenue. Mailerflow's dynamic segments on engagement and website behaviour let you model the engaged core separately if you want that precision.

Seasonality. If you have last year's monthly data, use it as a shape multiplier rather than forecasting flat. A flat forecast across a November peak and a January trough is arithmetically correct and practically useless.

Subject lines and preview text to pair with the templates

Grouped by situation, for the internal forecast email and its follow-ups:

Each works because it names the number or the cause in the subject line rather than saying "forecast update". If you want a faster way to draft the internal review email itself, Mailerflow's AI email builder takes a one-sentence description and returns a complete responsive design plus subject lines and preview text — useful for the formatting, though the numbers still come from your model. The feature overview shows what else is available for the reporting side.

Mistakes to avoid

• Forecasting on total list size. Fix: use reachable contacts after bounces, complaints and hard suppressions.
• Assuming 100% deliverability. Fix: apply your own recent deliverable rate, and if you do not know it, find it before forecasting.
• One blended conversion rate. Fix: split campaigns and automations if their rates differ by more than a few tenths of a percent.
• Ignoring conversion lag. Fix: for considered purchases, either extend the window or forecast on the earlier event.
• Treating the forecast as a target. Fix: keep the forecast and the target as separate numbers, and report against both.
• Forgetting list decay. Fix: subtract expected unsubscribes and complaints from future reach each month.
• Building the model once. Fix: update the assumptions log monthly, even when nothing changed — the date column is the point.
• Presenting a single number. Fix: always ship a range with the assumptions attached.

FAQ

How many months of data do I need before forecasting?

Ninety days is a reasonable minimum, because it covers at least one full campaign cycle and usually one seasonal shift. With less, forecast a range and mark the conversion assumptions as low confidence.

Should I include transactional email revenue?

Include it only if you can attribute revenue to those sends, and then keep the definition identical every period. Many teams exclude it and forecast marketing email only, which is simpler to defend.

How do I forecast with no historical data?

Do not forecast a number. Forecast a range from your send plan and a stated conversion assumption, label it a hypothesis, and commit to replacing it with actuals after 30 days.

What conversion rate should I use if I have never tracked it?

Derive it from your own analytics rather than borrowing an industry figure. If you have no tracking at all, instrument clicks and conversions first — a forecast built on an invented rate is worse than no forecast.

How often should I re-forecast?

Monthly for the input-level check-in, and immediately after any structural change: a sending-domain move, a pricing change, or a deliverability incident.

How do I forecast automations separately from campaigns?

Give them their own rows in the model with their own click and conversion rates, then sum. Automations tend to run continuously, so model them on a monthly active-contact basis rather than a per-send basis.

Track deliveries, clicks and conversions per campaign and run A/B tests in Mailerflow — start free and you will have the historical inputs for your first forecast within a month.