A whole-life cost framework for email software

An email software budget for email marketing software should cover the whole operating life, not just the subscription. Start with the messages and populations the organisation intends to support, then price the supplier, implementation, internal work, assurance, operation, failure and exit needed for that scope.

The model assumes an organisation operating from England. All monetary inputs should be recorded in pounds sterling unless the approving finance owner specifies another currency. No example amount appears because a defensible figure depends on a dated quote, internal labour evidence and the organisation's tax position.

What to take away

Use a cost record that can be challenged

Every line needs: currency, VAT treatment, unit, quantity, period, product and edition where relevant, source date, inclusions, exclusions, evidence owner, confidence and next update. Mark it fixed or variable, one-off or recurring, cash or non-cash economic cost.

The arithmetic is simple:

line cost = quantity x unit price x number of periods

whole-life cash cost = sum of cash lines across implementation, operation, renewal and exit

whole-life economic cost = cash cost + loaded internal labour + other opportunity costs

These are blank structures, not estimates. A loaded labour rate must identify salary or contractor source, employer costs included, productive hours used as denominator, role, geography and date. A finance reviewer should approve the accounting and tax treatment.

Keep two reconciliations: the cash view follows invoices and payment dates, exposing affordability and VAT timing. The economic view adds internal effort and opportunity cost, so a low invoice cannot disguise a labour-heavy option. Never mix those totals without labelling the basis.

If depreciation, capitalisation or foreign-exchange accounting matters, send the actual facts to the organisation's accountant rather than inventing a general treatment.

Build the model from work, not vendor categories

Subscription and usage

Record the exact edition, contacts or profiles counted, send allowance, storage, users, domains, automation limits, support and add-ons. Show how duplicates, unsubscribed records, archived contacts and seasonal peaks affect billable quantity. Put overage, upgrade and downgrade rules on separate lines.

Never copy a headline price without its term, currency, tax status and eligibility. If two suppliers count contacts differently, keep the native calculations and create a common buyer scenario rather than dividing incomparable prices.

Implementation and migration

Include discovery, data mapping, cleansing, permission and suppression migration, templates, integrations, testing, training, project control and remediation. Old and new services may overlap during cutover. Failed imports and a second migration attempt are scenario risks, not hidden contingencies.

The government's Technology Code of Practice is mandatory only in its stated public-sector context, but its lifecycle themes are useful here: accessibility, security, privacy, integration, purchasing strategy and adaptability all consume resources.

Authentication and domains

Allow for DNS ownership, SPF, DKIM and DMARC configuration, monitoring and incident work. NCSC email-security guidance supports staged controls. These costs reduce some identity risks; they do not buy legal permission or guaranteed delivery.

Content and accessible testing

Budget copy, design, review, plain text, dynamic variants, localisation where needed, client testing and testing with relevant assistive technologies. Remediation and retesting belong in the base workflow. An accessibility scan is not a legal certificate or a complete user test.

Privacy, PECR and claims

Cost the data map, lawful-basis and PECR analysis, notices, tracking assessment, suppression controls, claim substantiation, records and qualified review. The ICO's direct-marketing planning guidance assigns these decisions to the organisation. Software configuration cannot remove them.

If messages or linked pages use pixels or other storage and access technologies, price a separate technical inventory and legal assessment. The ICO publishes guidance on storage and access technologies. Its application depends on the actual technology and purpose, so a generic tracking toggle is not enough evidence for the budget sign-off.

Security, incidents and recovery

Include access administration, logging, assurance review, vulnerability work, backup, exercises, incident response and recovery. NCSC SaaS guidance makes customer configuration and recovery responsibilities visible. Treat prevention and rehearsal as planned costs rather than assuming the supplier absorbs them.

Operation and complaints

Count campaign preparation, approvals, list-quality investigation, suppression reconciliation, complaints, support, reporting, data-rights work and supplier management. Separate operator time from analyst and specialist time. Apply actual measured hours after launch and reforecast when the operating pattern changes.

Renewal and exit

Include notice management, contract review, price-change assessment, export, validation, deletion evidence, transition support, dual running and decommissioning. ICO processor-contract guidance covers return or deletion and audit among other terms. It is under review after the Data (Use and Access) Act, so use the current text and qualified legal advice.

Reconcile cost to a defined capacity

Create a capacity sheet beside the budget. Show the maximum approved contacts, sends, users, retention and live workflows for each period. Link every variable line to one of those quantities. When a plan bundles capacity, record both the purchased allowance and expected use, but do not call unused capacity a saving.

Reconcile supplier invoices during the first operating period. Compare invoiced units with system logs and the approved definition. Investigate duplicates, restored records, automated retries, test sends and status changes that might affect the count. Record whether a variance is a timing difference, data-quality fault, scope change or supplier interpretation, because each category requires a different remedy.

Keep assurance costs attached to the control they support. Accessibility testing belongs to the content being tested; transfer review belongs to the mapped access route; contract advice belongs to the offered terms. One generic review line cannot cover later changes it never examined.

Show VAT rather than burying it

GOV.UK states the standard VAT rate is 20% for most goods and services, but does not prove a specific invoice's rate, place-of-supply treatment or recoverability. Store supplier net amount, VAT charged, gross cash payment, expected recovery if any, timing and authority separately. VAT-registered organisations may face cash timing, partial exemption or evidence issues; obtain current UK tax review.

Add uncertainty without fake precision

Create low, central and high scenarios from stated input changes: contact volume, sends, integrations, remediation hours, support incidents, exchange rate, renewal uplift and exit effort. Do not assign probabilities without evidence.

Use sensitivity analysis to identify the value at which an uncertain input changes the decision. Where available, compare assumptions with the organisation's historical forecast error.

Put uncertainty beside the affected line, not one opaque percentage added to the total. A quote can have high price confidence but low quantity confidence, while migration hours may be uncertain because source fields have not been inspected. Explain the reason and evidence that could narrow the range.

Contingency should cover identified residual risk under an approved rule, not provide a spare pot for unexamined scope.

Keep benefit claims outside the cost ledger

Attributed orders are not automatically caused by email. Gross turnover is not contribution. A decision model should state:

incremental contribution = causally supported incremental revenue x contribution margin

ROI = (incremental contribution - whole-life economic cost) / whole-life economic cost

The Magenta Book distinguishes monitoring outcomes from methods that can support causal attribution. Government evaluation guidance is not proof that a campaign caused revenue.

Put control around the budget

Assign each cost family an owner, approved ceiling, warning tolerance and evidence date. Trigger reforecast when scope, contact counting, send volume, exchange rate, tax treatment, supplier terms, accessibility defects, security findings or migration effort changes materially.

Create an approval calendar rather than relying on one purchase decision, and include quote expiry, implementation gates, data-migration sign-off, launch readiness and invoice review. Add forecast refresh, contract notice and exit-test dates.

At each point, name expected evidence and person who can approve, reject or require remediation. A renewal review that begins after the notice deadline gives little commercial control.

The ledger should keep actuals level with the forecast, and preserve variance cause and corrective action. Preserve invoice line, billing unit, usage extract and internal hours. A finance owner can then tell timing from permanent price changes, genuine scope increases from duplicated records, and expected implementation effort from defect repair.

Use these observations to update remaining periods. Do not overwrite the original approved case, because the comparison provides evidence for the next procurement and exposes recurring estimation errors.

Pause commitment when a mandatory legal, privacy, accessibility, security or contract gate fails, regardless of apparent ROI. Recovery means resolving the defect, updating cost and risk, rerunning affected tests and obtaining fresh approval. Schedule reviews before quote expiry, contract notice dates and renewal, with enough time to test an exit.

The final approval pack should contain the versioned workbook, assumptions, source documents, scenario results, open issues and named finance, tax, privacy, cyber, accessibility and commercial decisions. A number without those records is not a budget that can be governed.

Before you act

Common questions

Why should the budget cover the whole operating life rather than just the subscription?

The article says an email software budget should cover the whole operating life, not just the subscription. It advises starting with the messages and populations the organisation intends to support. Then price the supplier, implementation, internal work, assurance, operation, failure and exit needed for that scope.

How should internal labour be treated in the model?

The economic view adds loaded internal labour and other opportunity costs to the cash cost. A loaded labour rate must identify salary or contractor source, employer costs included, productive hours used as denominator, role, geography and date. A finance reviewer should approve the accounting and tax treatment.

What should happen if two suppliers count contacts differently?

The article says never copy a headline price without its term, currency, tax status and eligibility. If two suppliers count contacts differently, keep the native calculations and create a common buyer scenario rather than dividing incomparable prices.