Foundations
Part of How to assess England's marketing automation market with no official revenue figures
A go or no-go record for a marketing automation platform pilot
A marketing automation market entry checklist for a platform pilot: workflow, data path, supplier contract, unit costs and the go or no-go record to sign.
Use this marketing automation market entry checklist before building a broad platform or funding a national launch. The pass condition is a narrow workflow with a defined buyer, lawful data path, credible delivery model and reversible pilot. A large England business count is not a substitute for any of those things. The checklist ends in a go or no-go record for piloting one marketing automation platform, such as HubSpot, Klaviyo or Dotdigital, on that one workflow.
What to take away
- A narrow workflow with a defined buyer and lawful data path is the pass condition for launch.
- A large England business count does not replace a credible delivery model or reversible pilot.
- Map every data field through the journey and separate subscriber types under PECR rules.
- Model consistent units and verify every commercial claim with dated evidence and assumptions.
- The final go or no-go record needs an owner and evidence link for every tick.
Buyer definition and discovery evidence
Market and problem evidence
- Name one event and one action
- Choose the statistical unit
- Exclude non-buyers explicitly
- Collect real discovery evidence
- Name one event and one action.Write the trigger, data needed, decision rule, customer-facing action, exception and human owner. Name the workflow type and platform, such as abandoned-cart email in Shopify or lead scoring in HubSpot. Reject descriptions such as "automate engagement" that cannot be observed.
- Choose the statistical unit.If an England count informs the case, state whether it covers enterprises, local units, registered firms or estimated unregistered activity. The ONS business-data methodology explains why an enterprise and a site are not interchangeable.
- Ground the England figure.ONS Business population estimates for the UK and regions: 2024 records about 4.9 million private sector enterprises in England, a count of enterprises not local units.
- Exclude non-buyers explicitly.Remove organisations without the relevant channel, recurring volume, usable data, staff ownership or realistic purchasing route.
- Collect real discovery evidence.Record recruitment, questions, dates, non-responses and dissent. Do not publish invented personas or attribute an internal assumption to "the market".
Data and communications
- Map every field through the journey.For each identifier and attribute, record its source, purpose, owner, permitted use, update path and deletion or suppression behaviour, and the UK GDPR lawful basis for using it.
- Confirm the organisation's ICO registration.Organisations processing personal data generally have to pay the ICO data protection fee unless exempt; check the register entry before personal data enters the platform. GOV.UK's page on paying the data protection fee says the annual fee depends on size and turnover and is £52 or £78 for most organisations, including small and medium-sized businesses.
- Separate subscriber types.The ICO's B2B marketing guidance notes that PECR treats corporate subscribers differently from sole traders and some partnerships. Arrange qualified UK advice for the actual audience and channel.
- Test objection propagation.An unsubscribe or objection must reach the next scheduled action and every connected sending system. Use controlled records before any live audience.
- Review message logic.The ICO's detailed electronic-mail guidance covers the PECR rules and was updated in April 2026. Recheck it and the proposed lawful basis on publication and launch days.
Supplier and service design
- Define controller and processor roles.Identify who determines purposes and means, which sub-processors are involved, and where each party's obligations sit.
- Interrogate the contract.ICO contract guidance lists matters including instructions, confidentiality, security, sub-processors, assistance, end-of-contract handling and audits. It is under review and is not a replacement for legal advice.
- Assess security in proportion to the data.The NCSC's lightweight cloud assessment addresses encryption, access, logging, incidents and governance, while directing sensitive workloads to its fuller principles.
- Design an exit before entry.Specify export format, field mappings, suppression records, workflow documentation, deletion evidence, notice periods and the person who can run the migration.
Unit economics and pilot decision
- Model consistent units.Put contacts, interactions, sends, users, environments and support on separate rows. Add implementation, integration, training and exit work.
- Work a cost example.For a pilot with 20,000 contacts, three data systems, five users and a 12-month term, list implementation at 20 days, integration at 10 days, training at 3 days and exit at 5 days. Multiply those days by your own day rate rather than accepting one all-in price. Use that list as the pilot budget.
- Verify every commercial claim.Keep the dated quote, plan definition, tax treatment and assumptions. Avoid promised savings or conversion gains without a reproducible study that matches the use case.
- Set a pilot decision.Choose a bounded audience, comparison point, review period, success measure, harm threshold and stop control. Default to a 90-day pilot with 500 contacts against a holdout of at least 10%. Record staff time spent on exceptions as well as campaign metrics.
Starting the record from a public platform listing
A platform's public procurement listing can pre-fill the supplier and cost rows before any demo. The G-Cloud 14 Digital Marketplace listing for Sugar Market, a marketing automation platform resold by ENABLEIT TECHNOLOGIES LIMITED, prices it at £800 to £4,800 an instance a month with a free trial, which gives the unit economics row a dated price per instance to set beside your own day estimates. The same listing answers parts of the supplier row:
- Data storage and processing locations are in the United Kingdom.
- Penetration testing runs at least every 6 months, in-house.
- An API sandbox or test environment is available, which the pilot row needs for controlled test records.
- A full system data snapshot is provided at the termination of any service, the starting point of an exit plan.
Those are supplier declarations, so they go in the evidence column as such. The result column still needs your own test: the sandbox export reconciled, the contract terms reviewed, and the snapshot format checked against the field map.
Final go or no-go record
Assign an owner and evidence link to every tick. Items marked "not applicable" need a reason. Do not proceed if the workflow depends on unknown permission, an unowned integration, an unsupported market claim or a contract and security gap that qualified reviewers have not resolved.
The checklist is complete only when another person can reproduce the decision from the file. Lay the record out like this:
| Section | Entry | Owner | Evidence link | Result |
|---|---|---|---|---|
| Workflow | Trigger, action, exception and platform named | Journey owner | Workflow card | Pass, fail or not applicable with reason |
| Buyer and evidence | Unit, exclusions, discovery notes | Product lead | Discovery file | Pass or fail |
| Data and PECR | Field map, lawful basis, subscriber type, objection test | Data owner and privacy reviewer | Field map and test log | Pass or fail |
| Supplier | Controller and processor roles, contract review, security assessment, exit plan | Procurement and security lead | Contract notes | Pass or fail |
| Unit economics | Cost rows and day estimates at your rate | Finance owner | Cost model | Pass or fail |
| Pilot | Audience, holdout, review period, stop control | Journey owner | Pilot plan | Pass or fail |
| Decision | Go, no-go or go with named conditions | Accountable executive | Signed record and date | Go or no-go |
A single "fail" in the data, supplier or pilot rows means no-go until it is resolved; a "fail" elsewhere can become a go with a named condition, an owner and a date.
Common questions
What makes a marketing automation pilot reversible?
A reversible pilot requires a bounded audience, comparison point, review period, success measure, harm threshold and stop control. Record staff time spent on exceptions as well as campaign metrics, and confirm the platform can export your data and suppression records if the pilot ends.
Why does the article warn against using a large England business count?
A large England business count is not a substitute for a narrow workflow with a defined buyer, lawful data path, credible delivery model and reversible pilot. If a count is used, state whether the count covers enterprises, local units, registered firms or estimated unregistered activity.
What must happen before sending to a live audience?
Test objection propagation using controlled records before any live audience. An unsubscribe or objection must reach the next scheduled action and every connected sending system. Then review message logic and recheck the ICO electronic-mail guidance on publication and launch days.
