Pricing Page Examples That Won A/B Tests

The best pricing page examples are the ones that won a controlled A/B test, not the ones that look good in a gallery.

Across the 28 pricing page tests in our database, the winners share a short list of moves: fewer and clearer plans, one plan visibly recommended, a feature table people can compare at a glance, and proof or answers placed next to the price.

Packaging changes, like switching to named tiers, moved revenue more than any visual tweak.

Below are the SaaS pricing page examples we can back with numbers, who ran each test, what changed, and where the result is weaker than the headline suggests.

You can browse every result in the full test database or the SaaS hub.

What the best pricing pages have in common

A pricing page has one job: help a visitor pick a plan and take the next step.

The pages that won tests made that choice easier.

The pages that lost added a step between the visitor and the decision.

One plan is marked as the default choice

Several winners singled out one plan. Jagex added a "Recommended" badge to one of four packages on RuneScape and saw about +6% purchases, a clean single-change test.

ArchiveSocial's redesign, run by VWO, simplified the plan options and marked the mid-priced plan as most popular, with a +64.76% lift in leads over seven weeks.

Planoly is the most detailed example. CodaLift LLC gave the Growth plan a contrasting color and its own CTA style, rewrote the heading around benefits, and showed annual savings per year instead of per month.

Revenue rose 38% and average order value 24%.

Plan CTA clicks rose on every tier, with the biggest jump (+74%) on the most expensive plan, not the highlighted one.

That pattern is close to what the decoy effect predicts, but the test bundled several changes, so it can't isolate the cause.

Plans fit on one screen and compare side by side

Wingify Services rebuilt Paltalk's subscription page so all plans sat above the fold in a feature comparison table, with testimonials added.

Over 53 days on all traffic, that version produced +6.74% purchases.

Whitepages moved to three plans side by side as vertical lists of inclusions with a monthly/annual toggle on top, and reported +23% pricing page conversion and +31% monthly memberships, though the test ran for only one week.

Visibility of price itself matters on long product pages.

On Hivelocity's dedicated server page, Cro Metrics moved pricing and filters above the fold and reported +187% checkouts.

The case study gives no sample size or significance, so treat it as a direction, not a forecast.

The next step is obvious and low-risk

Lyyti replaced four equal buttons (split between free trial and "Request a Quote") with a feature table, trial buttons above and below every plan, and the quote option demoted to a text link.

Visits to the trial page rose 93.71% over five months.

That metric is clicks to the sign-up page, not completed trials.

PayPanther turned a bare "Pricing and Signup" page into a longer one with pricing FAQs, testimonials and an extra sign-up CTA framed as a no-risk trial, for +372.6% sign-ups.

The sample was about 1,000 visitors over a month, so the true lift is likely much smaller.

The direction, answering objections on the page where people hesitate, matches other results.

Packaging beats polish

The largest revenue results came from changing what was sold, not how the page looked.

Server Density swapped configurable per-server pricing for packaged tiers starting at $99 a month.

The VWO case study reports revenue up 114% ($394 to $833), while free trial sign-ups fell 24.96% (6.92% to 5.19%).

Patrick McKenzie's write-up of the same test gives slightly different figures, 150 vs 113 trial sign-ups and $420 vs $876 in new monthly revenue, which we log as a separate entry with about +100% revenue.

Either way, it rested on only 20 vs 15 paid conversions.

Meebox, a Danish hosting provider, offered 20-40% off for customers who committed to a 2-year term.

That single change produced +121.56% revenue, +46.24% AOV and +51.85% conversions.

Powtoon (test run by Wingify Services) found that showing the Business plan at "10 GB" storage instead of "unlimited," against 2 GB on Pro, lifted revenue 27.9%.

A concrete number gave visitors something to compare.

If you want to test the offer itself rather than the layout, our guides to price testing and SaaS pricing strategy cover how to set those tests up.

SaaS pricing page examples, test by test

Here is the full set of SaaS pricing page examples above, plus a few more, in one table.

"Bundled" means the variant changed several things at once, so the result belongs to the whole page, not any one element.

"A/B test" means the case study describes a single change or a clean comparison of offers.

The metric column matters as much as the percentage.

A lift in clicks to a sign-up page is an early signal, while a lift in revenue or paid purchases is the outcome you actually want.

Compare examples on the same metric before deciding which idea to copy.

CompanyWhat changedResultRan byEvidence
ArchiveSocialSimpler plans, "most popular" mid plan, highlighted CTA+64.76% leadsVWOBundled
PlanolyHighlighted middle plan, benefit heading, yearly savings+38% revenueCodaLift LLCBundled
BaseKitBolder layout, testimonial, clearer currency choice+25% clicks to Buy NowBaseKitBundled
OmnisendCustom plans featured, value messaging by business size+22.97% demo requestsOmnisendBundled
WhitepagesSide-by-side plans, billing toggle+23% pricing page conversionWhitepagesBundled
LyytiFeature table, trial CTAs, quote demoted to link+93.71% trial visitsLyytiBundled
Meebox20-40% off for a 2-year term+121.56% revenueMeeboxA/B test
Server DensityPackaged tiers instead of per-server pricing+114% revenueServer DensityA/B test
Powtoon"10 GB" instead of "unlimited" storage+27.9% revenueVWOA/B test
RuneScape"Recommended" badge on one of four packagesabout +6% purchasesJagexA/B test
FortumPrice details moved into a modal-9% CTRConversionistaA/B test (lost)

Omnisend: a pricing page that sells the sales call

Not every SaaS pricing page should push self-serve sign-ups.

Omnisend featured custom plans prominently and tailored value messaging by business size.

Demo requests rose 22.97%, lead-to-customer rate went from 2.94% to 11.54%, and new business MRR rose 16.69%.

The test used a 90% confidence threshold, which is looser than the usual 95%.

BaseKit: clarity for paid traffic

BaseKit made the pricing layout bolder, added a testimonial and made currency selection more obvious, for +25% click-through to Buy Now.

The traffic was mostly paid, revenue wasn't tracked, and the test hit 95% significance within 24 hours.

That is fast enough to be wary of a novelty or day-of-week effect.

Fortum: an example of what to avoid

Losing tests are useful pricing page examples too.

Conversionista redesigned Fortum's electricity price blocks and moved deeper price details into a modal.

Click-through fell 9%, and of the visitors who opened the second-level details, 18% continued in the variant against 75% in the original.

The follow-up kept the drop-down, clarified the copy and color, and won +9% click-through.

Hiding price details behind an extra layer cost more than it saved in clutter.

Powtoon also lost a test on a new monthly vs annual price display, though the case study gives no numbers.

Billing toggles are not a guaranteed win; Whitepages' toggle won only as part of a wider layout change.

More losing results are collected in our losing A/B tests research.

How to use these examples on your own page

Most of these results are bundled redesigns from vendor case studies, which tend to publish wins.

Read the headline numbers as evidence that a direction can work, not as the lift you should expect.

Small samples (PayPanther, Server Density) and one-day or one-week tests (BaseKit, Whitepages) make the exact percentages unreliable.

A practical order to test in:

  1. Make every plan and its price visible without scrolling or clicking.
  2. Mark one plan as recommended and give its CTA a distinct style.
  3. Replace vague limits ("unlimited") with concrete numbers people can compare.
  4. Add FAQs and proof next to the plans, where objections come up.
  5. Then test packaging and term discounts, which move revenue most but carry the most risk.

Measure revenue or paid conversions, not just clicks.

Server Density's winner cut trial sign-ups by about a quarter while doubling revenue, so a click-based metric would have called it a loss.

For more element-level results see pricing plan tests, the SaaS pricing page hub, our pricing page best practices, and the wider SaaS A/B test results analysis.

Questions

What are the best pricing page examples?

The strongest examples are ones that won controlled tests: Planoly's highlighted middle plan (+38% revenue), Server Density's switch to packaged tiers (+114% revenue), Meebox's 2-year term discount (+121.56% revenue) and Lyyti's feature table with trial CTAs (+93.71% trial page visits).

What makes a good SaaS pricing page?

In our database, winning SaaS pricing pages show all plans side by side, mark one plan as recommended, use concrete limits instead of vague ones, and place FAQs or testimonials next to the price.

Hiding price details behind a modal lost a test at Fortum.

Should a pricing page highlight a 'most popular' plan?

Usually worth testing. Jagex's single-change test of a 'Recommended' badge on RuneScape gave about +6% purchases, and ArchiveSocial and Planoly both won with a highlighted plan, though as part of larger redesigns.

What should I measure in a pricing page A/B test?

Revenue or paid conversions where possible. Server Density's packaged pricing cut free trial sign-ups by 24.96% but more than doubled revenue, so a sign-up metric alone would have picked the wrong version.