SaaS pricing page design: what to show and how to lay it out
A SaaS pricing page should show prices, two to four plans, one recommended plan and the limits between them. Layout, billing toggles, tax and testing.
By Sohail Hussain21 November 20266 min read
A good SaaS pricing page shows the price of every self-serve plan, offers two to four plans built around distinct types of customer, marks one as recommended, and makes the differences between plans obvious in a few seconds: the limits that matter, in numbers, and the features that change, in plain words. Below that, a full comparison table and an FAQ answer the questions that stop people from buying. The page's job is to help a visitor pick the right plan quickly, not to show everything the product can do.
The pricing page is often the last page a visitor reads before deciding, and it deserves more care than it usually gets.
What must a SaaS pricing page answer?
Every visitor arrives with the same few questions. The page works when each is answered within a few seconds of scrolling:
- How much is it? A number, in my currency, per month or per year.
- Which plan is for me? A one-line description of who each plan suits.
- What do I get, and what are the limits? Users, projects, usage, storage: whatever grows with the customer.
- Can I try it first? Trial length, whether a card is needed, or a free plan.
- What happens if I outgrow it, or want to leave? Upgrades, downgrades, cancellation, refunds.
- Does it include tax? Especially for businesses that reclaim GST or VAT.
If your page cannot answer these, the problem is usually the pricing itself, not the design. Settle the model first: per seat, per usage, or flat tiers, matched to how customers think about value. Plan structure also shapes the billing integration, which is why we settle it early in our web app and SaaS development projects.
How should the plans be laid out?
Two to four plans, side by side
Each plan card shows, in this order: the plan name, a one-line "for teams who...", the price with its billing period, the main limits as numbers, the call to action, and three to six differences from the plan below it. Not every feature. Just what changes.
One plan marked as recommended
Most visitors want help choosing. Mark the plan that suits most of your customers, usually the middle one, with a label and a stronger button. If your data shows most customers choose a different plan, move the label.
Limits as numbers, features in words
"Up to 5 users", "10,000 contacts", "3 projects" are easy to compare. "Advanced reporting" is not; say what it does: "Scheduled reports by email". Avoid listing features every plan has as if they were plan features.
A full comparison table below
Visitors who need detail scroll down to a table with every feature across every plan. Group rows by area, keep ticks and crosses consistent, and repeat the plan names and buttons at the top of the table so they stay visible.
The enterprise tier last, briefly
A short card or a strip: "Need SSO, a contract or volume pricing? Talk to us." Do not let it compete with the self-serve plans.
Monthly or annual first?
Offer both with a toggle if you sell both. The default view is a choice about what you want more of.
| Default view | Effect | Fits |
|---|---|---|
| Monthly | Lower headline price; easier first purchase | Early products, small customers, price-sensitive markets |
| Annual, shown as a monthly equivalent | Lower per-month figure; more upfront cash | Products with proven retention, B2B buyers |
If you show annual prices as a monthly figure, say clearly that it is billed yearly and show the yearly total. "₹2,400 a month, billed ₹28,800 yearly" is honest. A monthly figure with the annual condition in small print erodes trust at the moment it matters most.
State the saving as an amount or a number of free months rather than a vague "save more". Keep the discount meaningful but not so large that the monthly price looks like a penalty.
Should you show prices at all?
For any plan a customer can buy without talking to you, yes. Hidden prices make comparison impossible, and buyers who want to compare quickly go to a competitor whose page lets them. They also fill your calendar with calls from people who cannot afford you.
There are honest exceptions. Enterprise contracts that depend on volume, integrations and security reviews can say "from" with a starting price, or "contact us". Products in very early pilots may prefer to price each customer by hand while they learn. For service businesses the question is more nuanced; should you show prices on your website covers that case.
How should you handle currencies and tax?
Show local currency where you can bill in it. A visitor in India expects rupees, in the UAE dirhams, in Saudi Arabia riyals. Billing providers support many currencies, but each currency is a set of prices you have to maintain. Start with the two or three that cover most customers.
Be clear about tax. State whether prices include GST, VAT or sales tax. Consumer-facing prices in some regions must include tax, while business buyers often expect prices before tax. The rules depend on where you and your customers are, so check with your accountant before launch.
Know what you will actually receive. Payment processing fees differ by card type, country and currency conversion. Our Stripe fee calculator shows what reaches your account from a given plan price, which is worth checking before you settle on the numbers.
Should you build the page or use an embed?
Stripe offers an embeddable pricing table that you configure in the Dashboard and add to your site with a script tag. It supports flat-rate, per-seat and tiered pricing and free trials, and sends visitors straight to Stripe Checkout. It is a fast way to launch, and it keeps prices in one place.
The trade-off is control. As of October 2026, Stripe's documentation lists its limits: up to four products with three prices each, no usage-based pricing, and no step between the plan button and checkout, such as creating an account in your app first. Design options are limited too. Most products start with the embed or a simple custom page, then build a fuller custom page once pricing settles and the page needs to do more, such as showing a signed-in customer their current plan. How to add subscriptions with Stripe covers the checkout side either way.
How do you test and improve a pricing page?
With little traffic, classic A/B tests take too long to reach a reliable answer. A page with a few hundred visitors a week usually needs months to tell a modest improvement from noise. How to run a simple A/B test explains the sample sizes involved.
Until traffic grows, improve the page with other evidence:
- Watch where visitors go next. Do they click a plan, scroll to the FAQ, or leave? Which questions bring them to support?
- Ask customers who just bought, and prospects who did not, which plan they nearly chose and what made them hesitate.
- Track plan mix. If almost everyone picks the cheapest plan, the middle plan's extra value is unclear or its price is too far away.
- Change one thing at a time, note the date, and compare a few weeks before and after.
Pricing changes affect revenue directly, so measure them in revenue terms, not clicks. A higher price with slightly fewer sign-ups can be a large win; our LTV calculator shows what a change in price or churn does to a customer's lifetime value. After the pricing page comes the first ten minutes in the product, covered in onboarding flows that reduce churn, and the full path from idea to revenue is in the pillar guide on how to build a SaaS product.
Was this guide useful?