# SaaS Pricing Page Optimization > Tier order, anchors, feature table depth, annual toggles and CTA copy, with conversion data by page pattern and the three pricing page tests worth running first. Source: https://saas-marketing.net/guides/saas-pricing-page-optimization/ Topic: SaaS Pricing Type: guide Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-pricing-page-optimization/ ## Short answer A SaaS pricing page converts when the value metric is defined in plain language above the fold, tiers run left to right from cheapest to most expensive with the recommended tier visually anchored, the feature table stays under about 25 rows, and the annual toggle shows the saving in both percentage and dollars. Most pricing pages lose signups to confusion about what a seat, credit or contact actually counts as, not to price. ## Key takeaways - Define the value metric in one sentence near the top. Pages that hide it generate support tickets instead of signups. - Three or four tiers outperform five in nearly every test. Five tiers pushes decision time past the point of abandonment. - Annual default with a visible monthly switch lifts annual mix, but hurts trust if the monthly price is hard to find. - Feature tables past roughly 25 rows reduce conversion. Move the long list to a separate comparison page. - Enterprise CTA wording matters more than placement. 'Talk to sales' underperforms outcome-shaped wording like 'Get a quote'. - Structured pricing markup and a plain text price make your page extractable by AI answer engines that now field pricing questions. --- Your pricing page gets the most commercially valuable traffic on the site and usually the least design attention. It is the last screen before a purchase decision, which makes it a checkout, and checkouts get audited line by line. Most SaaS pricing pages have never been audited at all. The single biggest loss is not price. It is a visitor who cannot work out what they will be billed for. ## What breaks on most SaaS pricing pages The value metric is undefined. Datadog bills per host and per million events, Vercel bills on usage across several dimensions, Slack bills per active user rather than per invited user, and every one of those distinctions has cost a vendor a deal because a buyer assumed wrong. Write the definition in one sentence, near the top, in the buyer's words. "You are billed for people who send a message in a given month, not for everyone you invite." That sentence prevents more support tickets than any tooltip. Putting the value metric definition inside a hover tooltip means it does not exist on mobile, does not exist for screen readers, and does not exist for the AI assistant answering 'how does this product bill'. If the definition matters, it is body text. The second break is tier count. Five tiers on a page is a spreadsheet, and visitors do not want to do a spreadsheet exercise on a Tuesday afternoon. Three or four, with a clear reason to move up between each. ## The anatomy of a pricing page that works Seven blocks, in this order. Deviating is fine when you have a reason, but this is the order that survives most tests. **Pricing page block order** Look at how Linear handles tier cards: tight copy, obvious progression, no feature soup. Then look at HubSpot, where the page has to serve five product lines and the complexity is genuinely earned but still costs them clarity. Both are instructive for opposite reasons. ## Annual toggles and how to display the discount Annual default lifts annual mix because most people do not touch toggles. That is a real effect and a legitimate one, provided the monthly price stays visible and unambiguous. Display the discount two ways at once. "Save 20 percent" is abstract. "Save 20 percent, 288 dollars a year" is concrete. Show the monthly-equivalent price in the big number and the annual total in smaller text underneath, because buyers compare monthly numbers across vendors. | Toggle pattern | Effect on annual mix | Risk | Use when | | --- | --- | --- | --- | | Monthly default, annual optional | Baseline | None | Early product, unproven retention | | Annual default, clearly labelled | Lifts annual mix meaningfully | Low | Most self-serve SaaS | | Annual default, monthly price hidden until checkout | Highest annual mix | Trust damage, refund requests | Never | | Annual only, no monthly | Highest ACV, lowest volume | Cuts off SMB entirely | Products with long time to value | If your pricing has a usage component, model the scenarios before you design the page. The [usage based pricing simulator](/calculators/usage-based-pricing-simulator/) is the fastest way to see whether your tiers create a cliff where a customer's bill triples for one extra unit. Cliffs are where churn comes from, and no page layout fixes them. ## How deep should the feature comparison table go? Under 25 rows. Past that, scroll depth collapses and the table stops being read, which means the rows you added to win a comparison are being seen by nobody. Group rows into four or five sections with sticky headers. Use checkmarks for binary features and actual numbers for limits, never "unlimited*" with a footnote, which reads as a trap even when it is not. Every row should answer a question a real prospect asked. Go through the last 40 sales calls or support conversations, list the feature questions, and build the table from that list. Rows nobody asks about are there to make the table look complete, and completeness is not a conversion goal. The long list still has value for buyers deep in evaluation and for search. Put it on a dedicated comparison page and link to it from under the table. That page can also carry the competitor comparisons, which is where a lot of high-intent traffic lands. ## Pricing FAQ content that earns AI citations This block is now the most quoted part of a pricing page. Assistants answering "how much does X cost" and "what counts as a user in X" pull short factual spans, and a well-built FAQ is exactly that shape. Rules that make a difference: write the question the way a buyer types it, put the number in the first sentence of the answer, keep answers between 40 and 70 words, and never put the price inside an image. Mark the block up with FAQPage structured data and put your plain price in the page HTML rather than rendering it from a client-side pricing API, because extraction tools frequently do not execute that call. **82%** Share of B2B technology queries that trigger an AI Overview, which is why extractable pricing text now matters Twelve questions worth having on nearly every SaaS pricing page: what counts as a user, what happens when I exceed a limit, can I change plans mid-cycle, do you prorate, what is included in the free trial, do you require a card for the trial, what payment methods do you accept, can I pay by invoice, is there a discount for annual, what is your refund policy, what happens to my data if I cancel, and do you offer nonprofit or startup pricing. ## Mobile ordering and what changes on a small screen On mobile the tier cards stack, which destroys the left-to-right anchoring the desktop layout relies on. Two fixes work. Either lead with the recommended tier first in the stack, or collapse tiers into a compact selector at the top that swaps a single detailed card. Mobile pricing traffic for B2B SaaS is typically 25 to 40 percent of pricing page sessions and converts far worse, which is normal because the buyer is often previewing before a desktop session. Do not optimise mobile for immediate conversion. Optimise it for comprehension and for an easy way to send the page to themselves. ## The three tests worth running first Most pricing page testing is wasted on button colours. These three change revenue mix. A caution on the tradeoff. Shifting plan mix upward looks good in the test window and can raise churn three months later if the buyers you pushed into a higher tier did not need it. Always pair a pricing page test with a 90 day retention read on the cohort it produced. I have seen a "winning" test reverse completely on that view. ## Where the pricing page sits in the wider funnel It is one surface in a chain. If your product is sales-led, the pricing page hands off to a form, and that handoff is covered properly in [demo request conversion optimisation](/guides/demo-request-conversion-optimization/). If you are still deciding whether to publish prices at all, [public pricing vs contact sales](/comparisons/public-pricing-vs-contact-sales/) works through the tradeoff with the cases where hiding price is genuinely correct. For the strategy underneath the page, [SaaS pricing strategy](/saas-pricing/) covers model selection, and the page itself should be specced before anyone opens Figma. Use the [pricing page spec template](/templates/saas-pricing-page-spec/) for that, then run [the pricing page audit checklist](/checklists/pricing-page-conversion-audit/) against what shipped. Worked examples are in [SaaS pricing page teardowns](/examples/saas-pricing-page-teardowns/). Two adjacent surfaces are worth keeping consistent with the pricing page. Paid traffic often lands on a variant rather than the page itself, which is covered in [SaaS PPC landing pages](/guides/saas-ppc-landing-pages/), and when prices change, the announcement matters as much as the page, which is what [price increase announcement emails](/templates/price-increase-announcement-email/) are for. ## What to do this week Open your pricing page on a phone. Read it as someone who has never seen your product. Write down every question you cannot answer from the page alone. That list is your backlog, in priority order, and it will be shorter and more useful than any generic best-practice checklist including this one. Then fix the value metric sentence first. It is a one line change and it is nearly always the highest yield edit on the page. ## Frequently asked questions ### What is a good conversion rate for a SaaS pricing page? Pricing page to signup or trial start commonly runs 5 to 15 percent for self-serve products and 2 to 6 percent for sales-led ones where the action is a demo request. The wide range is mostly traffic mix. A pricing page fed by branded search converts far higher than one fed by cold paid traffic, so compare yourself to your own trend, not to a benchmark. ### Should a SaaS company show pricing publicly? Show it unless your price genuinely varies by more than about 40 percent between similar customers. Public pricing filters out unqualified demos, earns citations from comparison sites and AI assistants, and removes a friction point buyers now expect to be gone. Hiding it is defensible for complex enterprise contracts and rarely defensible below 25,000 dollars average contract value. ### How many pricing tiers should a SaaS product have? Three or four. Three works when the tiers map cleanly to team size or use case. Four works when you need a free or trial entry point plus an enterprise tier. Five or more forces the visitor into a comparison task they did not come to do, and comparison tasks are where people leave and say they will come back later. ### Should the annual plan be the default on a pricing page? Usually yes, with the monthly option one click away and clearly labelled. Annual-default pages lift annual mix by a meaningful margin because most visitors do not switch the toggle. The risk is trust: if a visitor discovers the displayed price was annual-only after they reach checkout, you have bought annual mix with churned goodwill. ### Where should the recommended or most popular badge go? On the tier you most want a self-serve buyer to pick, which is usually the second of three or third of four. The badge works as a decision shortcut for visitors who have no strong preference, and that is a large share of pricing page traffic. Do not badge the cheapest tier, because you lose the anchoring effect entirely. ### How do you write pricing page FAQs that also get cited by AI assistants? Write the question exactly as a buyer would type it, answer it in the first two sentences, and include the actual numbers in plain text rather than inside an image or a tooltip. Assistants extract short factual spans, so a question like 'what counts as a seat' answered with a specific definition is far more quotable than a paragraph of positioning language. ### What are the three highest value pricing page tests? Recommended tier placement, annual versus monthly default, and enterprise CTA wording. These three change revenue mix rather than just click rate, they can each be run without engineering work in most CMS setups, and each reliably produces a detectable effect on a page with reasonable traffic within three to four weeks.