Landing page software delivery models compared on one grid, without prices

Landing page software delivery models differ in where the work and the risk sit. Product category, delivery model and charging method are separate. A hosted builder such as Unbounce or Instapage may charge by workspace, user, traffic or another unit. A managed service may combine software with labour. No model is inherently best.

This desk comparison was prepared on 6 September 2026 for one bounded case: an organisation in England needs to create, approve, publish and later remove campaign pages. Paid media, copywriting and customer-record systems are outside the purchase unless the contract expressly includes them.

Current UK contract evidence sits in order forms, vendor security records and NCSC guidance.

What to take away

Compare the delivery routes on one grid

SaaS describes centrally hosted software, not a price plan. Each row names public examples of one delivery model. The grid then sets out who operates what, how the charge is built, what evidence to request and what the buyer must still check.

For the specialist hosted route, Unbounce and Instapage both run the application for the buyer. Unbounce publishes A/B tests and a Smart Traffic option that shifts visitors between page variants. Instapage adds dynamic text replacement for paid campaigns and review steps for teams. Both publish to a vendor subdomain or a custom domain.

Also in the specialist hosted route, Leadpages, Landingi and Swipe Pages sit at smaller scale. Leadpages pairs pages with forms and a built-in checkout. Swipe Pages builds mobile-first pages, including AMP output. Landingi supplies a template library and integrations with email and CRM tools.

In the broader website platform route, Webflow, Wix, Squarespace, HubSpot and Framer sell a wider site service with landing pages. Webflow publishes a whole site from one designer and CMS, so a campaign page shares the site publish cycle. HubSpot ties page forms to CRM lists and workflows. Wix and Squarespace bundle hosting, templates and commerce tools.

In the self-managed components route, WordPress with Elementor, Divi or Beaver Builder, or a framework such as Astro or Next.js, leaves code, hosting and updates with the buyer. Netlify, Vercel and Cloudflare Pages supply static hosting with deploy previews, rollbacks and custom domains.

For managed hosting on a self-hosted build, WP Engine, Kinsta and Pantheon sell hosting on top of that. The host runs the server, patching and backups, but the buyer still owns the software, plugins and content.

In the managed service route, managed labour comes through marketplaces and vendor directories. Codeable lists vetted WordPress developers. HubSpot Solutions Partners and Webflow Experts are vendor-run agency directories. In all three, acceptance tests, change control and handover terms sit in the contract.

The NCSC's SaaS security guidance says customers and providers share responsibility. It recommends checking access, data protection, audit and account management, and warns that a reviewed service can change. Treat those points as due diligence questions, not an endorsement.

Normalise the commercial unit

Ask every route for the same period and scope. Record the contracting entity, GBP or other currency, VAT treatment, minimum term and renewal.

Then record billable users, workspaces, domains, support and implementation. Add traffic or conversion limits, migration and exit. For example, fix a one-year term, five named users, three domains and a named traffic band, then ask every route to price that same unit.

The Small Business Commissioner's contract guide recommends clarity on parties, scope, duration, payment and ending a contract. Qualified legal review is still needed for the terms themselves.

VAT should not be guessed from a displayed figure. HMRC publishes the current UK VAT rates, but the supply, buyer status, invoice and recovery position decide the cash and accounting treatment. Keep the tax field blank until a qualified adviser checks it.

Keep quality gates non-compensating

A low quoted fee cannot cure an unacceptable privacy, security or accessibility gap. Test the same synthetic page and form through each viable route.

Record keyboard operation, labels, error messages and mobile layout. Then check publish and withdrawal controls, log evidence, export and restore.

WCAG 2.2 provides technical criteria for web content. It does not certify a supplier or settle every legal obligation.

Make a conditional decision

Shortlist a route only if its exact commercial unit is known, the operational task passes and each specialist gate has an accountable reviewer. Mark any missing evidence as unknown, not average.

Retain the existing process as the baseline. If, after full labour, assurance and exit work are counted, no route improves the defined task, do not buy new software.

Before you act

Common questions

Why does the article give no prices?

Comparable current contract evidence was not collected, so no figure is quoted and the grid compares mechanics rather than tariffs. The named products are public examples of each delivery route, not a ranking.

What should be recorded when normalising the commercial unit?

Record the contracting entity, currency, VAT treatment, minimum term and renewal. Add billable users, workspaces, domains and traffic or conversion limits. Add support, implementation, migration and exit. Ask every route for the same period and scope, and keep the tax field blank until a qualified adviser checks it.

When should an organisation not buy new software?

If no route improves the defined task after full labour, assurance and exit work are counted, do not buy new software. Retain the existing process as the baseline. Shortlist a route only when its exact commercial unit is known and each specialist gate has an accountable reviewer.