Costs and pricing
Part of How to budget for landing page software over its whole life
Why public landing page software offers do not form a clean price table
Compare landing page pricing models on common units, commitments and risks, without inventing a GBP price or treating unlike supplier offers as equal.
Pricing models shift cost and risk between supplier and buyer.
Research date: 6 September 2026.
Scope: hosted landing-page software considered by an organisation operating in England.
Inclusions: subscription, usage, user, hybrid and negotiated-order structures that a buyer may encounter.
Exclusions: market-average prices, currency conversion, discounts, tax conclusions, product performance and reseller offers.
Ranking: non-ranked. Each structure can be appropriate or costly under different use.
Conflicts: no supplier funded the comparison and no affiliate links were used. It is desk research; no checkout, invoice or account was tested.
What to take away
- Public pricing pages use different plan names, allowances and currencies, so they do not form one clean table.
- Compare charging mechanics first, then place actual quotes into a common whole-life-cost period.
- No model is cheapest without the buyer's quantities, contract terms and operating effort.
- A flat supplier fee can still sit beside substantial variable internal work.
Common comparison fields
Charge basis to request
- Fixed subscription
- edition for a stated period
- Usage based
- defined event or band
- Per user
- authorised, active or another user unit
- Hybrid
- base charge plus units or add-ons
- Negotiated order
- bespoke scope and commitment
Main sensitivity
- Fixed subscription
- renewal and included scope
- Usage based
- volume and overage
- Per user
- access and role growth
- Hybrid
- interacting limits
- Negotiated order
- unknown public comparability
Evidence needed
- Fixed subscription
- order, term, inclusions and change rights
- Usage based
- meter definition, timezone, exclusions and audit route
- Per user
- user definition, reassignment and minimum quantity
- Hybrid
- worked supplier invoice for buyer quantities
- Negotiated order
- signed order, service description and incorporated terms
These are commercial categories, not claims that every supplier offers each one.
Pricing models and what to request
Fixed subscription
- Charge basis
- edition, stated period
- Main sensitivity
- renewal, scope
- Evidence needed
- order, term, inclusions
Usage based
- Charge basis
- defined event or band
- Main sensitivity
- volume, overage
- Evidence needed
- meter, timezone, audit
Per user
- Charge basis
- user unit
- Main sensitivity
- access, role growth
- Evidence needed
- user definition, minimums
Hybrid
- Charge basis
- base plus units
- Main sensitivity
- interacting limits
- Evidence needed
- worked supplier invoice
Negotiated order
- Charge basis
- bespoke scope
- Main sensitivity
- public comparability
- Evidence needed
- signed order, terms
Why public offers do not form a clean price table
The first-party Leadpages pricing page, Unbounce pricing page and Instapage plans page use their own product groupings, plan names, allowances and supplier-published currencies. The pages were live on the research date, but this review does not reproduce their figures. They did not establish one common GBP, VAT, edition, minimum-term and usage basis for an England buyer.
Supplier pages reviewed (6 September 2026):
- Leadpages pricing page publishes plan names, monthly and annual billing, feature allowances and prices in US dollars.
- Unbounce pricing page publishes plan tiers, visitor and conversion allowances, overage rules and prices in US dollars.
- Instapage plans page publishes plan names, user and page limits and custom pricing for higher tiers, with prices in US dollars.
Instapage's terms also state that subscription terms define order-specific matters such as plan, users, volume limits, pricing and duration. That is a reason to compare the actual documents, not to infer an obligation from a web card.
Normalise without erasing differences
Choose a comparison period and retain each source quote unchanged. Build a second view:
normalised supplier charge = committed base charges + expected unit charges + add-ons + overages + non-optional support
Each variable must state currency, VAT position, unit, quantity, period, plan, term, source date and confidence. Do not convert currency until finance records the rate source and date. Show prepayment timing separately from economic cost.
Add buyer-side implementation, integration, content, accessibility, privacy and security review, administration, incident preparation, migration and exit.
Illustrative example. A buyer expects 20,000 visits a month for 12 months. Supplier A quotes a flat fee of £500 a month. Supplier B quotes £300 a month plus £20 for each 1,000 visits above 10,000 a month.
Normalised to a 12-month whole-life period, Supplier A's committed base is £6,000. Supplier B's expected charge is £300 × 12 = £3,600 plus £20 × 10 extra units per month × 12 = £2,400, giving £6,000.
Buyer-side implementation and administration add an estimated £2,000 for the year. The flat fee is not automatically cheaper or more expensive; the variable work and usage decide.
Check how the meter behaves
Ask for a sample invoice from the buyer's expected quantities. The supplier should define when a chargeable event counts, which timezone closes a period, whether duplicate or automated events are excluded, and how band moves are billed.
Record who can view the meter, how a disputed count is challenged, and whether an overage can be capped. A traffic or conversion label without an operational definition is not yet a usable budgeting unit.
Seat models need the same care. Establish whether invited, enabled, active or concurrent users count, whether accounts can be reassigned, and whether service identities consume a unit. For a hybrid offer, test the interaction between the base plan, add-ons and overages in one supplier-produced example. Do not construct that example on the supplier's behalf.
VAT-registered buyers may face reverse-charge treatment under HMRC's guidance on services bought from abroad; an accountant must confirm.
Reject a comparison when a supplier will not define a chargeable event, overage, term, renewal or exit cost that could materially affect the decision. The result can properly be "not comparable yet". That is more useful than a winner based on unlike headline prices.
Before you act
- Request a sample invoice built from your expected quantities.
- State currency, VAT position, unit, quantity, period and term for each variable.
- Ask when a chargeable event is counted and which timezone closes the period.
- Establish whether invited, enabled, active or concurrent users count.
- Add buyer-side implementation, integration, administration, migration and exit work.
- Reject comparisons where material terms remain undefined.
Common questions
Why can public landing page pricing pages not be compared directly?
Each supplier uses its own product groupings, plan names, allowances and published currencies. None established one common GBP, VAT, edition, minimum-term and usage basis for an England buyer.
What should a buyer ask for before trusting a usage-based quote?
Ask for a sample invoice built from your expected quantities. The supplier should define when a chargeable event is counted, which timezone closes a period, whether duplicate or automated events are excluded, and how a move between bands is billed. Also record who can view the meter and whether an overage can be capped.
How should VAT be handled in this comparison?
For VAT-registered buyers, HMRC's guidance on services bought from abroad identifies possible reverse-charge treatment. The purchasing facts decide whether and how it applies, so an accountant must complete that field. Do not convert currency until finance records the rate source and date, and show prepayment timing separately from economic cost.
