Email software market size in England: a worked scenario, not a measured figure

Define which software the estimate covers

Set the market boundary before any counting. Here, email marketing software means a paid, recurring subscription to a platform that builds and sends campaigns, manages contact lists and consent records, automates sequences and reports on sends. Examples of the category are Mailchimp and Brevo.

The scenario leaves out agency fees, one-off implementation work, transactional-email services built into other products and free tiers. Those can be sized separately, but mixing them in would stop the annual contract value from describing one comparable offer.

Fix the denominator before filtering

Use an England business population only as a starting denominator, then define whether each record represents an enterprise or a local unit. The gate sequence matters because a broad count does not establish recurring email work, usable contacts, permission, purchasing authority or practical reach.

The Department for Business and Trade business population estimates put private sector businesses in England at 4,996,000 at the beginning of 2025, with a 95% confidence interval of plus or minus 117,000. Its head-office basis includes registered and estimated unregistered businesses, while government and not-for-profit bodies sit outside the principal measure.

ONS publishes enterprise and local-unit counts from an Inter-Departmental Business Register snapshot. The series uses a different unit and date, so state the selected England denominator rather than blending the two. A provider catalogue cannot reveal confirmed customers; the England market guide separates population context from demand.

Once the denominator is fixed, narrow it in a stated order: recurring email work, data and permission readiness, buying authority, then the ability to serve. Record the reason each account fails. Without that audit trail, a small final count can look precise even when its classification cannot be checked.

Retain the source date, location, population definition and removal reason at every gate, including where direct marketing permission remains unresolved. The data protection record can help specify supporting evidence, while buying signals can distinguish a live purchasing process from interest without a decision.

Convert checks into a scenario

Be clear about what is measured and what is assumed. The starting population of 4,996,000 is an official figure. Every pass rate, the 50% reachable capacity and the GBP 6,000 contract value in the calculation below are planning assumptions chosen to show the arithmetic; none is a measured England rate. Replace each with your own sampled rate before relying on the result.

Treat the output as conditional potential value for a defined period, not measured nationwide revenue. Calculate pass proportions from checks within the segment being assessed, apply them in sequence, then multiply surviving accounts by the stated annual software contract value.

Suppose 40 of 100 sampled accounts have a named email owner and a recurring campaign in the previous 12 months. The sample rate would then be 40%, the operating-fit figure used in the calculation below. Keep the sample tied to its segment and gate; this example is not an England-wide rate and should not be presented as one.

The government's UK Business Data Survey can help shape a question about data readiness, but it cannot supply this gate's pass proportion. It covered multiple data types and did not ask specifically about marketing email, so its findings do not show how many businesses meet the defined condition.

Keep sample selection, review date and reviewer beside every rate so another analyst can repeat the account rules. Buyer persona research can guide which organisations to examine, but it does not replace checking retained records against the gates. Attach each rate to the segment and test that produced it.

Before using the example contract value, specify package, currency, date and tax treatment. The pricing worksheet supports a comparable software basis. Report implementation and service receipts separately, because this scenario concerns recurring software value rather than a mixture of subscription and one-off work.

Check that every input refers to the same territory and counting unit. Do not swap enterprises for sites, carry a UK survey proportion into an England estimate without explanation, or classify every organisation using digital data as a qualified prospect. Assign a source, date, owner and sensitivity span to each assumption.

A sensitivity span helps only when its endpoints describe the same offer and population.

Call the result a planning range for the stated period, not realised market revenue, and state whether VAT is excluded. If another analyst cannot match the totals using the same rules and retained records, withhold the calculation from a launch or investment decision.

Apply the forecast evidence test before calling the result a forecast: the stated inputs may support an illustrative scenario without establishing a forecast. This keeps the arithmetic within its evidence boundary, even when the multiplication is exact and the account rules are reproducible.