SaaS Pricing Pages, Annotated: What Twelve Pages Do to Reduce Doubt

What do twelve SaaS pricing pages do to reduce a buyer's doubt?

They mostly answer the cost doubt, and they answer the worth doubt least often. The points below are the short version, and every one of them rests on how Stigg's teardown describes the pages.

• Cost was the doubt described most often, at 18 of a possible 24 points, and worth (proof that the price pays back) was described least, at 5 of 24.
• Seven of the twelve are described with a price tied to a unit, and four of those seven give a live estimate through a slider or configurator: ChartMogul, Aircall, Miro and Scribe.
• Datadog scored highest at 7 of 10, because it is described as using a product filter, a pricing view per product and billing FAQs together.
• Snyk is described as putting exact limits in its table, which is the clearest answer to the limits doubt among the twelve.
• No source here measures conversion, so the scores describe devices, not results.

How were the twelve pages chosen and read?

Kanso did not open any of the twelve pricing pages for this article, and it has no screenshots of them. Every description comes from Stigg's article on 25 pricing pages and, where noted, from Veza Digital's guide, both retrieved on 19 October 2026.

Stigg describes more than twelve pages in enough detail to score. The twelve are Figma, Airtable, LaunchDarkly, Segment, Canva, ChartMogul, Snyk, Aircall, Stripe, Datadog, Miro and Scribe, chosen so that each major pattern (seats, tiers, modules, sliders, configurators, a flat fee and a metered catalog) appears at least once. Webflow, MongoDB Atlas, Slack and HubSpot were left out of the scoring and appear only in the structure section.

“Annotated” here means written notes, not marked-up images. Each note says what the source reports, then labels any inference as ours. If you want to see the pages themselves, galleries such as SaaS Landing Page's set of 64 pricing pages and Landingfolio's pricing section are built for that.

What are the five doubts, and how are they scored?

The first three questions come from Veza, which says a visitor arrives asking how much it will cost, which plan suits them and whether it is worth it. Veza also lists trust and finding help among what visitors want to confirm, and Stigg stresses long pages that must stay scannable, so worth and navigation became the last two doubts.

The levels in the table were written before any page was scored. A 0 means the source does not describe the device, which is not the same as the page lacking it.

How did the twelve pages score?

Scores ran from 2 (Snyk) to 7 (Datadog), and the twelve totalled 52 of a possible 120. The table gives each page's model as Stigg described it, its score on each doubt and its total.

The arithmetic is plain addition. Cost is 2+1+1+1+1+2+0+2+2+2+2+2 = 18, fit is 2+1+1+1+1+1+0+0+0+1+0+0 = 8, limits is 0+1+1+0+2+0+2+1+1+2+2+0 = 12, worth is 0+1+2+0+0+0+0+0+0+0+0+2 = 5 and navigation is 0+1+1+1+2+0+0+0+1+2+1+0 = 9. The five column totals add to 52, which matches the sum of the twelve row totals.

Do not read the totals as a league table. Snyk scores 2 because Stigg writes about one thing it does well, and Figma scores 4 because the source covers seat pricing and plan guidance but not its table or proof.

Which pages let a buyer work out the price themselves?

ChartMogul, Aircall, Miro and Scribe are described as letting the buyer move a control and watch the price change, and Stripe states its core fee at the top. All five score 2 on the cost doubt, the highest level in the rubric.

ChartMogul

Observed. Stigg describes an ARR slider on the Pro plan that adjusts the price to the buyer's revenue, tier descriptions that name the stage each plan suits, and both a free tier and a free trial.

Inferred. Tying the price to revenue and the plan to a stage answers cost and fit with one device each, which is why it scores 2 and 1 but 0 on limits and worth.

Aircall

Observed. Stigg reports that Aircall's price depends on location, license count and payment terms, that dropdowns, toggles and buttons update it as you choose, and that a personalized quote tool follows for a formal estimate.

Inferred. The tool exposes the variables that set the price, so it earns 1 on limits, but the source does not describe fit aids or proof.

Miro

Observed. Stigg describes four tiers, a feature comparison grouped by workflow (diagramming, collaboration, admin controls) and, on the Business tier, AI credits adjustable from 350 to 2,500 a month with a per-team price that updates as the slider moves. It adds that the credits come with real-world output estimates.

Inferred. The credit range is an exact limit, so limits scores 2 alongside cost.

Scribe

Observed. Stigg says Scribe opens with a slider that asks how many users you need and updates the Business plan price, then adds an ROI calculator that expresses time saved, guides created and dollar value recovered. The call to action it quotes is “Start your free trial”.

Inferred. Scribe is the only page of the twelve described as answering the worth doubt with a calculator, which is why it scores 2 on both cost and worth.

Stripe

Observed. Stigg says Stripe leads with its core transaction fee, uses no tiers or plans, and gives each product section the same structure: pricing, features, use cases and integration details.

Inferred. The fixed order lets a buyer compare products without relearning the page, which is a navigation device of the lighter kind and scores 1. The per-product features and integration details earn 1 on limits.

How do pages with a large catalog keep it readable?

Datadog, Canva and Segment each split a large catalog into parts the buyer can open one at a time. The method differs: Datadog filters by product, Canva collapses a table by category and Segment lets the buyer start from two options and add modules.

Datadog

Observed. Stigg says Datadog sells over 20 products, uses left-hand navigation to filter by product category, gives each product its own pricing view with a unit that fits it (per host, per million events, per committer) and answers billing mechanics in FAQs, such as how committers are counted and what a span includes.

Inferred. It is the highest-scoring page, with a device for four of the five doubts, and the FAQ covers the questions that would otherwise need a sales call.

Canva

Observed. Stigg describes four tiers from Free to Enterprise, each listing 15 or more specific features, a comparison table that collapses by category, an FAQ on AI usage across plans and a mid-page pitch aimed at team buyers.

Inferred. The collapse keeps depth available without forcing it on every visitor, and the AI usage FAQ is a limits answer, so both limits and navigation score 2.

Segment

Observed. Stigg says Segment starts with two foundation options, a customer data pipeline and a customer data platform, then lets the buyer add modules such as AI recommendations and audience building. Its comparison table is grouped around what the buyer wants to accomplish.

Inferred. The two-option start reduces the first decision, and the modules address the worry of paying for features that are not needed, but the source describes no limits or proof.

Which pages rely on tiers, exact limits and proof?

Figma, Airtable, LaunchDarkly and Snyk are described as using tiers or tables to answer fit, limits and worth, and only LaunchDarkly and Airtable are described as adding proof. Their notes are brief because Stigg describes them in fewer devices.

Figma

Observed. Stigg says Figma prices by seat and by role: Collab, Dev and Full seats each have a price within every tier, and the page carries “Choose this plan if you” copy below each tier, with indicators of which Figma products a seat unlocks.

Inferred. The role-based seats are the fit device, because a developer who only inspects designs can see why they pay less than someone building in the file.

Airtable

Observed. Stigg describes four tiers from Free to Enterprise Scale, a “Most popular” badge on the Team plan, features grouped under Data and Sync, AI, Project Management, Automations and Security, and logos from AWS, Walmart, HBO, TIME and BlackRock below the tier cards.

Inferred. It is the only page of the twelve scoring 1 on every doubt, which shows breadth without a standout device.

LaunchDarkly

Observed. Stigg says LaunchDarkly shows four tier cards on a dark header, a clean white comparison table below and, near the bottom, a Paramount case study carrying a “100X productivity” claim.

Inferred. The case study sits where a hesitant buyer finishes reading, which is how it earns 2 on worth. The figure is the case study's claim as Stigg reports it, and Kanso has not checked it.

Snyk

Observed. Stigg says Snyk's feature table states exact limits, including which SAST languages are supported, how many test runs a month are included and which compliance reports come with a plan. It contrasts this with dev-tool pages that hide such details behind “Contact us”.

Inferred. This is the strongest limits answer in the set, and it is the only page where Stigg describes nothing about cost or fit, so it scores 2 in total.

How many plans should a pricing page show, and what should they be called?

Veza recommends three or four plans, and the pages here are consistent with that where a tier count is given. Stigg states a count for five of the twelve (Airtable, LaunchDarkly, Canva and Miro at four, ChartMogul at three), and Veza's table adds four for Figma, which makes six of twelve inside the 3 to 4 range.

The other six sit outside the pattern:Stripe has no tiers, Segment starts with two options, and Datadog, Aircall, Snyk and Scribe are described by their device and not by a tier count. The table lists the layouts Veza recommends and Stigg's examples of each.

Four pages outside the twelve show the same patterns. Stigg describes Webflow collapsing Site, Ecommerce and Workspace plans, MongoDB Atlas using a calculator that recommends a tier, Slack leading with each tier's top features before the numbers and giving mobile visitors expandable sections, and HubSpot using a sidebar that works like a table of contents.

The sources lean towards plain names with a line beside them that says who the plan is for. Veza advises names that say what the user gets, and the table shows what the pages and Veza use.

What do FAQs and comparison tables do on a pricing page?

They answer the limits doubt, which the headline plan cards cannot, and the pages here use them for that more than for decoration. Datadog's billing FAQs, Canva's AI usage FAQ and Snyk's table of exact limits are all described as taking questions that would otherwise need a sales call.

Stigg adds that FAQs work best grouped by topic. Veza lists billing, limits, cancellation and upgrade as the questions an FAQ should answer, and it asks for a scannable table grouped by category and placed below the plan cards.

Both sources agree that a table should be grouped, and they differ on how much weight it carries. That difference is the subject of the next section.

Where do the two guides and the pages disagree?

Veza ranks the FAQ, the detailed comparison table and testimonials near calls to action as nice-to-have, while Stigg's examples lean on the FAQ and the table to answer the limits doubt. The sources do not contradict each other on facts, but they weight devices differently.

Veza also advises avoiding complex pricing that needs explanation, and warns of decision paralysis above five plans. Datadog (over 20 products), Segment (modules) and Aircall (variables set by location, licenses and terms) are described as handling complexity by explaining it on the page, with filters, estimators and a quote tool.

Our reading, labelled as analysis: the advice to keep pricing simple applies when a product can be simple, and the examples apply when it cannot. A founder with one product and two price points should follow Veza. A founder with metered usage should look at Datadog, Miro and Aircall.

Founders raise the same tension in public. The r/SaaS thread on an audit of pricing pages asks whether a company has a pricing page at all and raises the frustration of buyers who cannot decode costs behind pricing labelled simple. We use it only as a sign of what founders ask, and take no figure from it.

What is documented and what is our analysis?

The documented list is what the two sources say, and the analysis list is Kanso's interpretation. Keeping them apart lets you disagree with the second without doubting the first.

Documented (as reported by the sources)

• Which devices each of the twelve pages is described as using, as Stigg wrote them, retrieved 19 October 2026.
• That Veza lists three to four plans, a recommended badge, a billing toggle, trust signals near the call to action and an FAQ among its recommended elements, and ranks the FAQ and the detailed comparison table as nice-to-have.
• That Stigg and Veza are both companies with something to sell in this area: Stigg describes metering and entitlement infrastructure and refers to its own Stripe integration guide, and Veza builds Webflow sites.
• That neither source in this package gives conversion data for any of the twelve pages.

Analysis (ours)

• The five-doubt rubric, its levels and every score in the table. The scores record how fully each source describes a device, not how well the page works.
• The pattern that cost is described most often and worth least often. A source that spends its words on layout will under-describe proof.
• The suggestion that exact limits (Snyk) and billing FAQs (Datadog, Canva) matter more than Veza's nice-to-have ranking implies.
• Every sentence marked as inferred in the page notes, such as which doubt a device is aimed at.

None of it covers whether any of the twelve pages converts well, and one reading of two articles cannot support a claim about SaaS pricing pages in general. The facts about each company's pricing page were true as the sources described them on 19 October 2026 and need re-checking before you rely on them.

How do the pages that already rank for this differ?

The pages that rank are mostly lists and galleries, and the two read for this article give design advice but no way to score a page. Stigg's article walks through 25 pages with the devices each uses, and Veza's guide lists elements, priorities and layouts for a pricing page, with a table of ten example companies.

Neither gives a scoring scale that lets a reader compare their own page against another. The ranking gallery SaaS Landing Page says only that it is a curated selection of 64 pricing pages, and the text of Landingfolio's pricing page read for this article is a few lines long, so neither supplies method.

Those pages are the better read when you want to see the designs, which this page does not show. This page is the better read when you want a repeatable way to check which doubts your own page leaves open.

How do you score your own pricing page?

You can score it in about half an hour with the page open, using the same five doubts and levels as the scorecard. Because you own the page, a 0 means the device is truly missing, which is a stronger finding than the same 0 in the table above.

1. Date the page. Save the date and a screenshot of your own page as it stands, because pricing pages change and your notes should say which version was scored.
2. Write the five questions as a buyer. Use cost, fit, limits, worth and navigation, in your own words, and keep them at the top of your notes.
3. Score each doubt 0, 1 or 2. Use the levels in the rubric table and write the element that earned each score, such as the slider or the FAQ answer.
4. Find the lowest score. The doubt with the lowest score and the most traffic-relevant buyers is the one to fix first.
5. Pick one device from the twelve. A slider for cost, a “choose this if” line for fit, a table of exact limits for limits, a specific customer figure for worth, a product filter for navigation.
6. Re-score after the change. Record the new date, and check your own sign-up and plan data, because none of the sources here show that any device raises conversion.

Kanso's own pricing page is at /pricing. It was not scored for this article, and nothing here claims it would score better than the twelve above.

For the homepage side of the same question, the teardown of ten AI startup homepages and the claims they can prove applies a similar evidence check to what a page says about itself. If you track rivals weekly, the weekly growth checklist already asks you to log changes to a competitor's pricing page and plan names, and the Stripe documentation teardown covers a different part of a company that appears in the scorecard.

SaaS pricing page examples: frequently asked questions

Sources

• 25 SaaS pricing page examples that make complex pricing clear, retrieved 19 October 2026, Stigg
• Best SaaS Pricing Page Examples (2026 Guide), retrieved 19 October 2026, Veza Digital
• Best Pricing Page Examples [Design Inspiration], retrieved 19 October 2026, SaaS Landing Page
• The Best Pricing Design Inspiration & Examples, retrieved 19 October 2026, Landingfolio
• I analyzed 1000+ B2B SaaS pricing pages, here are 5 ... (r/SaaS thread, read only for the questions it raises), Reddit