Four testable hypotheses for where landing page software work exists in England

The four hypotheses below are the core deliverable. They are editorial hypotheses, not forecasts. Each needs direct evidence from a defined buyer population before investment.

What to take away

Start with the observed boundary

DBT estimated 5.0 million private-sector businesses in England at the start of 2025. The figure uses head-office geography and includes estimated unregistered businesses. It does not reveal which organisations advertise, build campaign pages or buy software.

The ONS Digital Economy Survey measures UK business ICT and e-commerce, with a VAT or PAYE-registered trading-business frame. Its paused 2023 collection and UK scope limit current England inference. These sources justify careful sampling, not a revenue calculation.

Hypothesis 1: controlled page production

Interpretation: some teams may need a clearer route from brief to approved, published and withdrawn page. Test: recruit eligible England organisations that can show a recent campaign-page task. Compare their current workflow with a synthetic page exercise, keeping content and acceptance tests constant. Evidence required: task time by stage, defects, approval record, ownership and recovery result. Stop rule: retire the proposition if the recurring problem or improvement is not demonstrated without weakening another gate.

Sample England local authority communications teams from the Local Government Association council directory.

Google Ads' landing page definition establishes a destination-page task within that platform. It is a global supplier record and does not prove England demand or a need for separate software.

Hypothesis 2: consent and tracking evidence

Interpretation: a service that exposes tags, purposes and changes for review may solve an assurance problem. Test: ask privacy reviewers to inspect a synthetic form and tracking map before and after a controlled configuration change. Evidence required: versioned inventory, purpose, storage or access mechanism, recipients, retention, user choice and rollback. Stop rule: stop if the product obscures technologies or cannot preserve the decision record.

Sample England-based charities from the Charity Commission for England and Wales register and their data protection leads.

The ICO finalised storage and access technologies guidance on 29 April 2026. It covers cookies, pixels, scripts, tags and link decoration. This is a regulatory work signal, not a claim that software can confer compliance.

Hypothesis 3: accessible release assurance

Interpretation: buyers may value repeatable testing of the delivered page rather than confidence based on an editor preview. Test: define keyboard, focus, label, error and mobile tasks for one realistic form. Include people using relevant assistive technologies where the research is properly designed. Evidence required: exact build, browser, device, task, result, defect owner and retest. Stop rule: do not continue if essential output cannot be corrected or an inaccessible component is outside buyer control.

Sample England higher education providers from the Office for Students register.

WCAG 2.2 provides technical criteria that can structure tests. A partial check is not a conformance claim or a legal opinion.

Hypothesis 4: migration and exit support

Interpretation: organisations with brittle page ownership may pay for inventory, export and recovery work. Test: attempt to reconstruct one synthetic page, domain route, asset set and form destination from an exported package. Evidence required: dependency map, credentials, formats, deletion record, recovery time and acceptance decision. Stop rule: reject the route if the buyer cannot regain operational control on supplier failure.

Sample England further education colleges from the Department for Education college list.

The NCSC's cloud-provider selection guidance tells buyers to define requirements, examine dependencies and understand shared responsibility. It supports the diligence task, not the size of an exit-services market.

Decide whether to proceed

Use the checklist above before testing. The examples below show a stop rule firing and a test that passes.

For a stop rule firing under Hypothesis 1, suppose a sampled England local authority communications team cannot show a recent campaign-page task. The owner stops the test before booking interviews and records the failure.

For a passing example under Hypothesis 1, suppose five of eight sampled England local authority digital teams show the same approval defect in the synthetic page exercise. The team proceeds to a paid pilot with the same threshold and a named statistician reviewing the result.

Before you act

Common questions

Why can't business counts show where landing page software work exists?

The DBT figure of 5.0 million private-sector businesses in England uses head-office geography and includes estimated unregistered businesses. The ONS Digital Economy Survey has UK scope and a paused 2023 collection. Both limit current England inference and require sampling buyers directly.

What evidence would test the consent and tracking hypothesis?

Ask privacy reviewers to inspect a synthetic form and tracking map before and after a controlled configuration change. Required evidence covers versioned inventory, purpose, storage or access mechanism, recipients, retention, user choice and rollback. Stop if the product obscures technologies or cannot preserve the decision record.

The ICO guidance is a regulatory work signal, not proof that software confers compliance.

What should happen before an investment case is published?

Use the checklist above. No extrapolation should survive if the frame excludes relevant buyers or the result depends on one supplier claim. A named statistician and qualified UK reviewers must approve any investment case.