Choosing email software from the workflow up, with the buying gates kept apart

Choose email software only after defining the messages, populations and operating decisions it must support. A polished editor is irrelevant if the team cannot reproduce an eligible audience, propagate an objection, restrict an export or leave with usable records.

The buying context is an organisation operating from England. UK privacy and electronic-marketing rules still require a fact-specific assessment. Global supplier pages are cited only for the scope stated by their publishers. Research closed on 5 September 2026, so every plan, term and control needs reconfirmation before a 2027 purchase. No product was used or independently tested.

What to take away

Write the workflow before the requirements list

Begin with one message stream. Name its purpose, recipients, address source, final classification, owner, approval route, sending identity, data inputs, exclusions, tracking choice, evidence and stop rule. Keep genuine research, requested information, service content and direct marketing in separate rows. The ICO's electronic-marketing overview explains why promotional content can change the treatment of a purported research or service message.

Trace five populations independently:

Turn the trace into acceptance tests. For example: import synthetic contacts with different permission histories; object through each available route; confirm the suppression state reaches every connected audience; remove an operator; interrupt an integration; export the evidence needed to reconstruct the decision. A feature label is only a candidate capability until that exact edition passes the buyer's controlled test.

Add volumes and timings, not as market benchmarks. Record the buyer's maximum expected stored contacts, approved sends per period, peak import and operator count. Note the acceptable recovery window and audit-retention need.

Test just beyond each intended boundary in a safe environment to reveal queues, automatic upgrades, blocked exports or support dependencies before they affect real recipients. Figures come from the buyer's operating forecast and risk limit, not a supplier's generic customer profile.

Keep the buying gates independent

These gates do not compensate for each other. A projected saving cannot justify an unresolved transfer, and a security certificate does not establish electronic-marketing permission.

Build a plan-specific evidence pack

Per proposed capability, record product, exact plan or edition, page or contract section. Note publication or access date, region, evidence owner and expiry date.

Separate included functionality from paid add-ons, beta services, usage limits and supplier discretion. Capture the order form offered to the English buyer because a global marketing page may not settle currency, taxes, contracting entity, renewal or support.

Read claims as supplier statements. A vendor's security page can describe its control environment; it does not verify the buyer's configuration. A help article can show that an export command exists; it does not prove that all required fields, history, relationships and suppressions survive migration.

The ICO's controller and processor contract guidance covers factual role allocation, Article 28 terms, sub-processors, assistance, audit and end-of-contract handling. It is marked under review following the Data (Use and Access) Act, so procurement needs the current text and qualified legal review.

A bounded desk shortlist

Two editions were retained for evidence-gathering examples, not ranked as the best tools. Mailchimp Standard and Brevo Standard both had current first-party plan descriptions, campaign or automation documentation, data-processing material and contact-export instructions accessible on the research date. Inclusion does not indicate suitability, UK availability, security, accessibility or value.

Mailchimp's plan guide attributes expanded automation, segmentation and multiple user roles to Standard. Its contact-export page lists included and omitted fields. The DPA addresses sub-processing, transfers, security, return and deletion.

Mailchimp says servers are in the United States on its security page. Its accessibility help describes content features and practices, but the email accessibility page is not a conformance report for the purchased service or a buyer-created email.

Brevo's current plan description attributes automation, testing and reporting to Standard at stated sending tiers. The campaign workflow documents recipients, exclusions and test sending, and its export instructions show selectable contact and subscription fields. Brevo points customers to its terms for the data-processing agreement. Its alt-text documentation demonstrates an editor control, not end-to-end accessibility; see the image-editing help.

For both candidates, the public pages did not establish every field required here, including complete product accessibility conformance for the relevant edition and the outcome of a UK transfer assessment. Those are open items, not reasons to assume equivalence.

Compare one evidence matrix, not sales narratives

Use identical rows for each candidate:

Mark each cell verified, supplier-stated, buyer-tested, contractually committed, unknown or failed. Do not convert unknown to zero in a weighted score. A missing fact can be a mandatory stop, whereas a low-priority feature gap may be an accepted limitation.

Test with synthetic fixtures first

Create records that cannot identify real people. Include individual and corporate subscriber examples, multiple address sources, an objection, a changed email, a duplicate, missing data and an accessibility preference. The aim is to test state transitions and evidence, not to send marketing.

Apply least privilege. Separate template creation, audience approval, sending, export, integration administration and billing. Revoke a test operator and inspect logs. The NCSC's secure SaaS guidance stresses that customers retain responsibilities for configuration, access and recovery even when the supplier operates the service.

Configure SPF, DKIM and DMARC in a controlled sequence and monitor results. NCSC email security guidance explains their anti-spoofing roles. An authentication pass neither authorises a marketing message nor guarantees inbox placement.

Rehearse failure and exit before launch

Simulate an incorrect import, a failed suppression sync, an unavailable integration, a compromised account and a late supplier response. Name who pauses sending, isolates access, assesses affected people, contacts the supplier and authorises recovery. Do not resume because a dashboard returns to green; repeat the broken control and its dependencies.

Export contacts, permission evidence, suppression status, templates, campaign configuration and audit history. Import the agreed portable fields into a safe test destination, then compare counts, meanings and relationships. The exercise exposes gaps that a successful download can hide.

Make the purchase conditional

The decision record should state the preferred edition, viable alternative, unresolved facts, required contract changes, implementation owner, test window, maximum exposure, stop conditions and next review. Require named UK privacy, PECR, accessibility, cyber, procurement and commercial specialists to clear their own gates.

Before signature, refresh every supplier page and obtain the applicable order form, terms, DPA, sub-processor list and assurance pack. If the team cannot reproduce permission, enforce suppression, test accessible use, constrain access or leave with its evidence, the tool is not ready for that workflow regardless of its feature count.

Before you act

Common questions

Why should the buying gates stay separate?

The article states the gates do not compensate for each other. A projected saving cannot justify an unresolved transfer, and a security certificate does not establish electronic-marketing permission. Each gate needs its own minimum evidence and its own reason to stop, so a strong result in one area cannot mask a failure elsewhere.

What should an evidence pack record for each capability?

For every proposed capability, record the product and exact plan or edition. Also record the page or contract section, the publication or access date, the region, the evidence owner and the expiry date. Separate included functionality from paid add-ons, beta services, usage limits and supplier discretion.

Why were Mailchimp and Brevo retained?

They were retained for evidence-gathering examples, not ranked as the best tools. Both had current first-party plan descriptions, campaign or automation documentation, data-processing material and contact-export instructions accessible on the research date. Inclusion does not indicate suitability, UK availability, security, accessibility or value.