Variable vs. Fixed Pricing: An A/B Testing Framework for SaaS
A practical framework for testing transparent pricing against request-a-quote models, grounded in live pricing experiments detected at Attio, Hotels.com, and Shopify Payments.
Aiko Tanaka
Design Director · · Updated
Pricing is the one page on your site where design decisions and revenue decisions are the same decision. Move a number, hide a tier, swap "See plans" for "Talk to sales" — and you've changed not just conversion rate but who converts and how much they pay. Most teams treat the pricing page like a static brochure. The brands actually winning at this treat it like a live experiment surface, and they're running variable-pricing and disclosure tests constantly. Here's what we're seeing in the wild, and a framework for running your own.
TL;DR
- Attio tested two pricing variants on its live site with Plus at $29 vs. $35/mo and Pro at $69 vs. $79/mo, detected 8 September 2026.
- Shopify Payments ran a yearly-pricing test showing Grow at $79 vs. $89/mo and Advanced at $299 vs. $359/mo, detected 14 August 2026.
- Hotels.com tested a full layout variant with an added "Last-minute deals, right on time" section, detected 15 August 2026.
- Unbounce's 2026 pricing A/B testing guide treats price itself as a standard testable landing-page element, same as headline or CTA.
- The pricing page is consistently flagged as the highest-intent, highest-abandonment page on a SaaS site per Aimers.io's 2026 CRO best practices.
Why does pricing disclosure strategy matter so much for SaaS conversion?
Pricing disclosure sets the trust and friction level before a visitor ever reaches checkout. Show a number and you filter fast — the visitor self-qualifies in seconds, and anyone who clicks "Start trial" already knows what they're paying. Hide the number behind "Request a quote" and you filter slow — you lose the price-sensitive browsers immediately, but you capture contact details on everyone else and give sales a chance to anchor value before cost enters the conversation. Neither approach is universally better. The mechanics of your funnel decide which one wins, and increasingly, teams are testing both live rather than guessing.
That's exactly what we caught at Attio on 8 September 2026: two live Safari sessions loading the identical page structure, but with materially different numbers underneath. One version priced Plus at $29/mo and Pro at $69/mo. The other showed $35 and $79. That's not a copy tweak — that's a 20%+ price variance being tested on real traffic, and the feature table structure diverged too, with a "Seats" row and an "MCP server" row appearing only in one variant, plus different "Objects" limits. This is a team testing whether more expensive, more feature-differentiated tiers convert better than cheaper, simpler ones — classic anchor-and-tier-width experimentation, run live rather than in a slide deck.
What does a fixed-price test actually look like in production?
A fixed-price test holds page structure constant and varies only the number or the monthly-equivalent framing shown to the visitor. Shopify Payments gave us a clean example of this on 14 August 2026: the yearly pricing row showed Grow at $79/mo and Advanced at $299/mo in one visit, and $89/mo and $359/mo in another — with every other element of the page, layout, and copy held identical. That's an isolated price-elasticity test. No confounding variables, no layout noise. It's the cleanest version of the fixed-pricing test pattern: same design, same hierarchy, same visual weight on the "yearly" toggle — just a different number sitting in that high-attention price slot.
This matters because the price row on a SaaS pricing page typically sits at the first fixation point in an F-pattern scan — top-left to top-right across the plan headers, then straight down the price line before anyone reads a single feature bullet. Any test that isolates just that number is measuring pure willingness-to-pay against a control, without contaminating the read with layout or copy changes. That's disciplined experiment design, and it's why isolated pricing tests like Shopify's are more statistically legible than tests that change five things at once.
When does variable or request-a-quote pricing outperform a transparent price?
Request-a-quote wins when deal sizes are large enough that a few percentage points of conversion rate matter less than qualifying leads before they hit sales. Transparent pricing wins when the buyer is self-serve, price-sensitive, and comparison-shopping across several tools in the same afternoon. The decision usually comes down to average contract value and sales-cycle length:
| Signal | Favors transparent pricing | Favors request-a-quote |
|---|---|---|
| Average deal size | Under ~$5K ACV | Over ~$25K ACV |
| Buyer type | Individual or small-team self-serve | Committee-based, procurement involved |
| Sales cycle | Days | Weeks to months |
| Competitive pressure | High — buyer is comparing tools openly | Low — differentiated or bespoke offering |
| Feature complexity | Fits in a 3-4 tier table | Requires custom scoping |
Most mid-market SaaS tools live in the messy middle of that table, which is exactly why so many of them A/B test the decision instead of committing to one model. Intempt's SaaS A/B testing guide points out that a lot of these tests start from a single painful metric — a 60% drop-off at paid signup, for instance — and pricing disclosure is one of the first variables teams reach for because it's cheap to test and has an outsized effect on funnel entry.
Does layout and content around the price matter as much as the number itself?
Yes — the surrounding layout controls what the visitor notices before they ever process the number itself. Hotels.com isn't a SaaS pricing page, but the layout test we caught there on 15 August 2026 is a useful lesson in how much surrounding content shifts perceived value. The variant (seen on Edge, and matching on Chrome/Firefox) added an entire "Last-minute deals, right on time" section with pricing and reviews baked directly into the module — content the control (Safari, and matching Chrome/Firefox) didn't show at all. The variant also swapped the sign-in prompt from "Unlock instant savings with Member Prices" to a flatter "Sign in with your email." That's two different psychological levers being tested in parallel: urgency-and-social-proof framing around price versus a plain account-gate prompt.
The design lesson for SaaS pricing pages: the number is never read in isolation. It's read in the context of whatever sits above the fold — a value-anchoring module, a logo bar, a savings callout — and that context does real work on perceived fairness before the eye even reaches the price line. If you're only testing the digit, you may be missing the bigger lever sitting right next to it.
How should you structure your own pricing A/B test this quarter?
Start with one isolated variable, a clean control, and a downstream revenue metric — not just page-level conversion. A few concrete rules:
- Isolate one variable per test. Shopify Payments' test is the model — same layout, same copy, only the number moves. If you change price and layout at once, you can't attribute the lift to either.
- Measure past the click. A pricing test that lifts free-trial starts by 12% but drops paid conversion by 8% is a loss, not a win. Track trial-to-paid and 90-day revenue per visitor, not just signups.
- Segment by traffic source. Paid search traffic is more price-sensitive than direct/branded traffic in most SaaS funnels. A price increase that holds steady for organic visitors can tank paid-channel conversion.
- Respect your tool's statistical requirements. Varify.io's 2026 breakdown of SaaS A/B testing tools notes that enterprise-scale programs budget $15K–$60K+/year specifically because a 1% conversion lift at scale is worth millions — the tooling cost is almost never the constraint, sample size and test duration are.
- Add an FAQ before you test disclosure removal. If you're testing a move toward request-a-quote, pair it with an objection-handling FAQ near the fold — Aimers.io's CRO guide specifically recommends this to reduce abandonment when transparency drops.
Common questions
Is it better to A/B test price amounts or price disclosure format first?
Test disclosure format first if you don't already show pricing publicly — it's a bigger structural change with bigger variance. If pricing is already public, test amounts next, isolated the way Shopify Payments did on 14 August 2026, changing only the number and holding layout constant.
How long should a SaaS pricing test run before calling a winner?
Run it long enough to capture at least one full sales-cycle length in trial-to-paid conversion, not just landing-page clicks. For self-serve SaaS with short cycles, that's often 3-4 weeks minimum; for anything with a sales-assisted close, plan for a full quarter to see revenue impact, not just top-of-funnel lift.
Can feature-table structure changes bias a pricing test result?
Yes — changing rows like "Seats" or feature limits alongside price, as seen in the Attio test detected 8 September 2026, means you're testing a bundle, not a price point. That's valid if the goal is tier redesign, but you can't cleanly attribute lift to price alone when the feature set moves too.
Should the "most popular" tier badge move during a pricing test?
Generally no — keep the visual anchor (badge, border, background shading) fixed on the same tier across variants unless tier-anchoring itself is the hypothesis. Moving both the price and the visual emphasis at once makes it impossible to know which one drove the behavior change.
What's the biggest mistake teams make when testing request-a-quote against transparent pricing?
Measuring only lead volume. Request-a-quote almost always generates more form fills than a self-serve checkout does, but if sales-qualified rate or close rate drops, you've traded a real metric for a vanity one. Always pair the test with a downstream win-rate or revenue-per-lead comparison.
Your next sprint
Pick one pricing surface — plan pricing, yearly toggle, or the quote-request gate — and run a single-variable test against it this sprint, the way Shopify Payments isolated its yearly row. Instrument trial-to-paid and revenue-per-visitor from day one, not just page conversion, so that when the test ends you're reporting a revenue number to your CFO, not just a click-through delta.
Read next
More from the ABWatcher blog
Nov 22, 2026
How to Calculate Confidence Intervals for Conversion Rate Lift
A practical guide to computing confidence intervals for A/B test conversion lift — frequentist and Bayesian methods, worked examples, and how to report ranges instead of fake certainty.
Nov 21, 2026
Why Your Conversion Rate Varies by Traffic Source (And What to Do About It)
A diagnostic guide to conversion rate variance across organic, paid, and referral traffic — how to separate real signal from source-quality noise before you spin up a new test.
Nov 20, 2026
Why Your A/B Test Winners Don't Replicate Across Traffic Sources
A test winner that holds for blended traffic often fails for a specific channel. Here's why, with real examples, and how to validate before you scale.
Nov 19, 2026
Session Recording for CRO: What to Watch When Users Bounce
A practical, intro-level guide to reading session replays for hidden friction and high-intent signals — plus how to turn what you see into testable hypotheses.
Nov 18, 2026
How to Build a Winning Landing Page Without A/B Testing
No traffic for statistical significance? Here's a design-led framework for building high-converting landing pages using proven patterns, not guesswork.
Nov 17, 2026
How to Find Your True Conversion Bottleneck (Not Just the Waterfall)
A step-by-step method for pinpointing the real cause of funnel drop-off using session recordings, heatmaps, and field-level friction data — before you waste a test cycle.
From the glossary
Vocabulary the article uses. See all terms →
- Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
- Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
- Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
- Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
- Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
- Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See more like this
ABWatcher catches A/B tests like this across 1,000+ brands.
Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.