How should a SaaS startup design its pricing page when buyers compare it with an established competitor?

A SaaS startup should design its pricing page so that a buyer who already pays an incumbent can rebuild their own invoice on it within a minute. That means the same team size, a clear plan shape, every fee printed beside the price, and a plain answer on what sits behind “contact sales”. Humbleteam designs SaaS and AI products for startups such as Synthesia, valued at $4B in its January 2026 Series E, and Cluely; after Humbleteam redesigned the Afternoon app, activation rose 32%.

Humbleteam, a digital product design agency, publishes this guide. It covers what an incumbent’s customer checks first, plan mapping without competitor names, team-size totals, switching offers, contact sales, trust rows, phone behavior, testing, a row sheet and an invented worked example. Sources are described as of November 13, 2026. Nothing here is legal advice.

What does a buyer who already pays the incumbent check first?

They hold an invoice, so they ask invoice questions: the unit, the cost for their team size, what is gated, what they commit to. Nielsen Norman Group (NN/g) reported that business customers rank pricing as the most needed information online and that participants went to competitors’ sites when a site hid it. A later NN/g article added that the first site to show a price can anchor expectations, and that hiding a price hurts most when the buyer is already anchored to a competitor’s starting price.

Published pages answer these questions differently. Every number and plan name below is the company’s own, as its page showed on November 13, 2026. Pages change.

Two patterns repeat. First, “per seat” is not one rule, because the definition of a seat changes the total. Second, the items that decide a security review sit on the top tier or in an add-on on the Linear, Notion and Atlassian pages.

How do you map your plans to the incumbent’s without naming it?

Build the table around buyer questions, not around the other company. NN/g’s guidance on comparison tables fits pricing packages: five items or fewer, consistent content in every column, short cells, attributes the reader cares about, and fixed column headers. We read that as: your own plans only, with the same rows in every plan.

Our method, not NN/g’s: start each plan column with a “Choose this plan if you need” line that lists needs the incumbent’s customers recognize, such as SSO, an audit log, invoice billing or 25 or more seats. Put named, dated comparisons on a separate page, as our guide to the comparison page explains.

On naming a rival, the FTC’s policy statement encourages naming competitors but requires clarity and, if necessary, disclosure. The UK’s CAP Code asks for documentary evidence before an objective claim runs (rule 3.7) and says price statements must not mislead by omission (rule 3.17). Rule 3.18 allows prices without VAT only when everyone addressed can recover it, with a prominent VAT statement. These rules are written for consumer marketing, so ask an advertising lawyer how they reach your page.

How do you show the total for a team size?

Show scenarios first and a calculator second. In 2013 NN/g found most pricing tools complex, time-consuming and error prone and advised sample prices for a few representative cases. Its 2016 article on B2B websites allowed simple calculators. So: three preset team sizes as complete totals, such as 5, 25 and 100 seats, then one input for seats and one toggle for annual or monthly.

Our rule for the total, which a buyer can check against an invoice: seats times rate, then each one-time fee, then each add-on incumbents charge for, such as SSO, then what is excluded, such as tax.

Stripe’s embeddable pricing table supports flat-rate, per-seat and tiered pricing and trials, shows at most four products with up to three prices each, and does not support usage-based pricing. For credits and usage, see our guide to AI SaaS pricing and credits.

What should a switching offer say, and what terms should it state?

Two vendors’ own pages show the terms. SoloFire’s switch page offers free use until the buyer’s current contract ends, up to six months, then a standard 12-month term. It states that migration is included, that historical analytics do not transfer, that proof of the end date may be requested, that it does not pay the old vendor, and that it may withdraw the program. OnPage’s page offers free service equal to the months left on the buyer’s current contract, up to 12, for a qualifying multi-year agreement, and says it does not pay the other vendor directly.

UK CAP rules 3.23 and 3.24 say a product must not be called “free” if the buyer pays more than unavoidable costs, and that the commitment needed to claim a free offer must be clear. Check how they apply to you.

When should a plan say “contact sales”?

NN/g warns that hiding the price adds a step, can make a product look unaffordable and can make the company look evasive. It recommends common scenarios, a starting price or range, and a reason for each question a sales form asks.

Our decision rule: keep “contact sales” on a plan only when the price depends on something you must discuss, such as volume, custom terms or a security review. Then print a “from” price or range, list what triggers the conversation, and say what the form asks and why. Linear’s Business card shows both “Get started” and “Contact sales”, so the buyer can choose to buy or to talk.

Which trust rows belong on the page?

Evaluators can check a public list. sso.tax names vendors that put single sign-on behind higher-priced plans and says such pricing can inflate cost by 3x, 5x, 10x or more. It dates each row. Its Linear row is dated June 9, 2022 and its Notion row October 15, 2023, while Linear’s page today lists SAML on Enterprise only and Notion’s lists SAML SSO under Business. Our view: your own page should be the current source on SSO.

Our trust rows: SSO and SCIM (which plan, what extra cost, or “included”), audit log, how to cancel, when renewal happens, what happens to seats removed mid-term, and what every price excludes. Figma’s page lets Professional customers cancel in the Admin Dashboard and sends Organization and Enterprise customers to Sales.

How should the table behave on a phone?

NN/g says wordy comparison cells may fit only two columns on a narrow screen and that rotating the phone is a last resort. Keep the column headers and first column fixed, and show a cut-off column or an arrow when the table scrolls sideways. NN/g’s comparison-table article suggests tabs or lists when a table is impractical, with the trade-off that tabs make side-by-side weighing harder.

Our additions: put the team-size totals above the table, keep cells short, and check the page at 375 px wide.

How do you test and measure the page?

Test with people who pay for an incumbent today. Give each a realistic situation, such as 12 people, SSO required, annual billing, and ask what one invoice would total, where cancellation is described and what sits behind contact sales. Fix the page where answers differ.

Track these events (names ours): team-size preset viewed, seats changed in the calculator, SSO row opened, contact sales clicked by plan, sign-up by plan. Add a row for every question your sales team hears twice. Our guides cover the step after the page, in free trial design, and seat changes inside the product, in billing and plan changes.

What does the pricing page row sheet look like?

Fill one row per buyer question before you design the page.

Illustrative worked example: Pemberlow against an established suite

The company, the incumbent and every price below are invented. Pemberlow sells a team planning tool. Its buyer is a 40-person product team that pays an established planning suite per user, billed yearly, with SSO sold as an add-on.

The test: six people who pay for a suite like this each get the same situation, 40 seats with SSO on yearly billing. The page passes when each reaches $11,520 without asking and finds the cancellation rule within a minute. The six and the minute are our example numbers.

Where does this approach fail?

• Usage-based pricing. A seat calculator misleads when cost follows consumption. Use scenarios and the cost per unit.
• Negotiated deals. A table cannot show a custom contract. Show the range and the trigger.
• Upkeep. Date the page, name an owner and set a review schedule.

What can you produce now?

1. A row sheet with an evidence link for each question.
2. Plan columns with shared rows and a “Choose this plan if you need” line.
3. Team-size totals and a one-input calculator that lists fees and exclusions.
4. A switching terms sheet, reviewed by counsel, and SSO and cancellation rows.

If you are choosing who designs the pricing page and the flows around it, our page on choosing a UX agency when a startup competes with established SaaS products compares design partners for that situation.