Close-up of tablet showing a hand-drawn landing page design, ideal for web development concepts.
Photo by Davide Baraldi on Pexels

Tools and providers

Part of Write the operating case before comparing landing page software products

Leadpages, Instapage and Landingi as a landing page software shortlist, with plan limits compared

A non-ranked shortlist of Leadpages, Instapage and Landingi for buyers in England, comparing published plan limits and the evidence to request before buying.

No landing page builder is best for every organisation in England. A fair shortlist depends on the page workflow, data, domain, accessibility needs, assurance threshold and exit plan. The three builders below are non-ranked starting points for a controlled buyer-side test.

Published plan limits are a starting point, not proof. Every capability stays unknown until the supplier shows it in the edition named on the order form.

What to take away

  • The shortlist names three suppliers to test, not a verdict on which is best.
  • Published limits use different unitsvisits, unique visitors, active pages or unlimited traffic.
  • Every capability is unknown until the supplier demonstrates it in the exact edition offered.
  • Ask each supplier for the same evidence and compare the answers side by side.
  • Selection ends with a tested operating and exit plan, not with a brand name.

How the shortlist was chosen

The three names are Leadpages, Instapage and Landingi, picked because each has a public first-party pricing page that lists plan limits. The site also publishes what UK buyers should ask Unbounce, Instapage and Leadpages.

General website builders, plugins, agencies and products found only in directories are left out. No ranking applies, because the word best reflects search intent. No supplier paid for a place, and no affiliate arrangement exists.

Nothing was tested hands-on: no account, form, integration, support route, export or deletion process. Prices are left out because currencies, billing options and units differ between suppliers.

The three candidates

Leadpages

Every Leadpages plan includes unlimited traffic, custom domains with SSL and AI page creation. A/B testing is included from the Grow plan up.

Grow adds unlimited pages and four custom domains with SSL. Smart Traffic, heatmaps and automatic personalisation belong to the next plan up. Ask which of these the edition on your order form includes.

Instapage

Every Instapage plan includes unlimited pages, conversions and contacts. The Create plan covers 15,000 unique monthly visitors. The next plan up covers 30,000 and adds server-side A/B testing and hypothesis setting.

Root domain publishing, for example on yoursite.com, is listed as a separate feature. Ask which plan unlocks it and what happens when visitors pass the plan's monthly figure.

Landingi

Landingi's Build plan allows 10 active landing pages, 2,000 visits a month and one custom domain. The next plan up allows 100 active pages, 30,000 visits a month and three custom domains.

That plan also adds server-side A/B testing and smart sections. Scale adds programmatic landing pages and client sub-accounts. Ask how extra domains and visits are charged.

Published limits side by side

SupplierTraffic measurePagesA/B testing starts at
LeadpagesUnlimited traffic on every planUnlimited from GrowGrow plan
Instapage15,000 unique monthly visitors on Create; 30,000 on the next plan upUnlimited on every planNext plan up
Landingi2,000 visits a month on Build; 30,000 on the next plan up10 on Build; 100 on the next plan upNext plan up

The units differ, so the rows are not like for like. The pricing models of landing page suppliers rarely reduce to one table. Convert each limit into your own expected visits before comparing anything.

Evidence to request from every supplier

The NCSC cloud guidance makes the method depend on the confidence needed in the service. A supplier that will not provide independent validation leaves the buyer relying on its own assertions.

A certificate counts only when the evidence behind it is recent and covers how and where the service is hosted.

For personal data, UK GDPR Article 28 requires a processor to act only on documented instructions from the controller. It also covers a processor that engages another processor, so ask each supplier for its sub-processor list. ICO guidance on controller and processor contracts is marked as under review, so recheck it before signature.

Match each answer with the checks in vendor due diligence. The data protection record should hold one row per purpose.

How to use the shortlist

Give each supplier the same synthetic-data script, as set out in the supplier comparison. Require one exact edition to publish and withdraw the same representative page, pass the same accessibility checks and complete the same export.

The tool implementation checklist describes a pilot and cutover. Review the actual legal entity on the order form. Hold the purchase if an essential field remains unknown.

Before you act

  • Give each supplier the same synthetic-data script.
  • Convert each published limit into your own expected visits.
  • Require one exact edition to publish and withdraw a page.
  • Ask each supplier for its sub-processor list and data terms.
  • Review the actual legal entity and order form.
  • Hold the purchase if an essential field remains unknown.

Common questions

Why are the three landing page builders not ranked?

The shortlist is non-ranked because the word best reflects search intent, not a verdict. A useful shortlist depends on the page workflow, data, domain, accessibility needs, assurance threshold and exit plan.

What did the desk research actually test?

Nothing hands-on. No account, form, integration, support route, export or deletion process was tested. The limits come from each supplier's published pricing page.

What should a buyer do before choosing a supplier?

Give each supplier the same synthetic-data script and require one exact edition to publish and withdraw the same page. Review the legal entity and order form, and hold the purchase if an essential field remains unknown.

More in Tools and providers