How do I create a pricing page from scratch?

Start with three plans and write the one-line difference for each. Add visible prices, a monthly and annual toggle with the saving, and an objections FAQ. Ship it on /pricing with plan names that match your app, then measure signups from sessions that began on that page.

What is a pricing page and what must it include?

It is the page where a visitor decides if they can afford your product and which plan fits. It must include visible prices, two to four plans with one recommended, one-line differences, a cadence toggle, and an objections FAQ. Add trust signals and a clear “Start free trial” under each plan.

How many plans should a SaaS pricing page have?

Keep it to two to four. Three is common because it reduces paralysis and lets you recommend one plan. Put Enterprise in a secondary position or a link when buyers need bespoke terms, not in the main compare row for founders.

Should I ask for a credit card before the trial?

Only if you sell to teams that expect a paywall upfront. For founder-led trials, asking for a card before value adds friction and reduces trials started. Let users see the first screen, then ask for a card at the end of the trial or at usage thresholds.

How do I measure if my pricing page works?

Track landing page conversion rate on /pricing over 28 days, signup conversion rate across your signup path, and trial-to-paid by cohort. Join your landing page to the signup event in product analytics so you can see what started on pricing and what converted later.

Can I copy a famous company’s pricing layout?

Copy the patterns, not the brand. Use three plans, one-line differences, visible prices and an objections FAQ. Keep plan names, limits and trust signals specific to your product so you do not mislead buyers or add support debt.

Pricing page examples: the patterns that convert, and why they work

You want pricing page examples that you can ship this week. Here are the patterns that convert, why they work for buyers and for search, and the mistakes to avoid. Every pattern is shown on a fictional product, yourproduct.com, so you can copy the shape without copying a rival.

By Théophile Louvart, founder of Porteur · Updated 14 September 2026 · Markdown

Three plans with one recommended

Why it matters for the buyer: choice without paralysis. A founder can compare fast and pick the obvious path. More than four plans raises confusion and support debt.

Why it matters for search: a clean layout keeps the core content visible and scannable. It earns clicks from brand and category queries where the visitor expects clear pricing, not a wall of options.

Pick the three tiers that map to usage
On yourproduct.com/pricing, show Starter, Growth, Scale. Hide edge cases like Enterprise on a secondary row or a link below.
Make one tier the default choice
Add a “Most popular” badge to Growth. Use a subtle highlight, not a billboard, so it still reads as a table.
Place a clear signup button under each plan
Use “Start free trial” or “Create account” so the next step is unambiguous.

What a fixed block looks like: three cards in one row, Growth has a soft border, each has one button and a short benefit line, no footnotes inside the card.

One-line difference that buyers can act on

Why it matters for the buyer: they can tell, in one glance, which plan fits. Do not bury the real limit in a tooltip or asterisks below the fold.

Why it matters for search: the page earns snippets in roundups when the value is explicit. It reduces pogo-sticking from visitors who came to compare limits across sites.

Plan	One-line difference	Reads as
Starter	For solo builders, up to 3 projects and 10k checks a month	Who it is for + the limit that matters
Growth	For small teams, up to 10 projects and 100k checks a month	A step up that matches team size
Scale	For product teams, unlimited projects, 1M checks a month	The ceiling and capacity are obvious

How to ship it: write the one line first, then remove every other line that repeats it. Keep the rest of the table for legal or security notes below the fold, not in the compare row.

Prices visible without a click

Why it matters for the buyer: trust. You respect their time. No hover, no “see price” modal, no “contact us” for a founder audience. If they are the buyer, show the number.

Why it matters for search: visitors who bounce on hidden pricing send a bad engagement signal. Clear numbers also earn citations from comparison pages that list prices in plain text.

Put the price in the plan header
Example: “$19/month” under Starter, set in body weight, not fine print. Do not hide it behind a toggle state.
Include currency and cadence
Show the monthly price and, when annual is selected, show the annual total with the per month equivalent nearby.
Use round numbers where possible
If metered, show the base price and the metered rate on one line: “$19/month + $0.10 per 1k checks”.

What a fixed card looks like: Starter shows “$19/month”, a short line “For solo builders”, one CTA. No expanders. No hover states needed to see totals.

Annual toggle with the saving stated

Why it matters for the buyer: they can compare monthly and annual without losing their place. The saving is explicit so finance does not need a calculator.

Why it matters for search: pricing pages with visible annual maths get linked in lists of “transparent pricing”. That link equity helps the whole site. It also avoids thin content flags on pages that say “contact us” and nothing else.

Add a simple toggle at the top right of the table
Labels: Monthly, Annual. Default to Monthly if your audience trials first. Default to Annual if you sell to finance-led teams.
State the saving in plain text
Example beside the toggle: “Pay annually and save 20%”. When Annual is on, show the annual total and the per month equivalent.
Keep URLs stable
Do not switch URLs on toggle. Render both sets client side so links to /pricing stay valid and indexable.

What a fixed toggle looks like: Monthly is selected by default, Annual shows a small “Save 20%” pill, and prices on each card change without a page reload.

An objections FAQ that support would sign off

Why it matters for the buyer: it answers the last blockers without email. Cover cancellation, cards, limits, trials, data and support. Keep answers short and specific to your model.

Why it matters for search: FAQs with real content help you serve the “pricing” intent before you sell. They also win featured snippets when written in plain language, and reduce thin content risk on a sparse page.

Can I cancel any time? You can cancel from Settings. Your plan ends at the current period.
Do I need a card for the trial? No card needed to start a 14 day trial.
What happens when I hit limits? We send an email at 80 percent. Overages are paused until you upgrade.
What happens after the trial? Your data stays for 30 days. If you add a card, your plan starts on the same project.
Where is my data stored? In the EU. We encrypt data in transit and at rest. See /security.
Do you offer discounts? Annual plans include a saving. We also offer a startup plan. Email [email protected].

Place the FAQ under the table, not in a modal. Use real policy language, not “contact sales”. Link to Terms, Privacy, Security and Status pages in the answers, not footers alone.

Plan names that match the app

Why it matters for the buyer: less confusion at signup and in invoices. When a plan is called Growth on /pricing, it should be Growth in the product, in emails and in docs. Do not rename tiers in marketing copy.

Why it matters for search: consistent names help branded queries disambiguate. It reduces duplicate pages that mention the same plan with different labels, which can split link equity and clicks across URLs.

Audit plan naming across touchpoints
Search your repo, emails and docs for plan names. Align them to the three names you show on /pricing.
Update metadata and schema
Match plan names in title tags, meta descriptions and any structured data you publish so search terms and on-page labels match.
Lock names before campaigns
Freeze names before any launch. Changing them later creates support tickets and refund requests.

What a fixed set looks like: Starter, Growth, Scale on /pricing, in the signup flow and on invoices. No synonyms like Basic, Pro, Team appearing elsewhere.

Trust signals that a small site can show

Why it matters for the buyer: money pages carry risk. Show that you exist, you care about security and you will be around next month. Use signals you can stand behind today.

About page with real names and roles, not avatars
Postal address and company registration on /legal
Security page: what is encrypted, where data lives, how to delete it
Status page and a changelog with dates
Screenshots of the real product, not mockups
Customer logos only with permission, quotes with a name and a company
Visible support address: [email protected]
Terms and Privacy in plain language, linked near prices
Links to third-party reviews on sites like G2 or Capterra

No customers yet? Use your own use of the product, a public roadmap, real numbers you have, and an honest comparison that names what you lack. Link these from the pricing page so a cautious buyer can verify without a call.

Common pricing page mistakes and how to fix them

You can avoid the traps that slow signups and kill trust. Here are the usual mistakes and a direct fix for each one on yourproduct.com/pricing.

Mistake	Why it hurts	Fix on yourproduct.com/pricing
“Contact us for pricing” aimed at founders	They will not book a call to see a number. They bounce and never return.	Publish Starter, Growth, Scale prices. Keep Enterprise as a link with a short “custom SSO and legal review” note.
A table of forty ticks	Buyers cannot see the real difference. They assume hidden limits.	Cut to one line per plan that names the limit that matters. Move long spec tables below the fold.
Prices hidden behind a toggle or hover	The number is invisible in screenshots and skimmable lists. It feels evasive.	Put the price under the plan name in static text. Leave toggles only for cadence.
Card required before any product screen	Friction before value. Founders leave and vent in communities.	Let trials start without a card. Ask for a card at the end of the trial or when usage exceeds free limits.
Email verification before the first screen	Adds a step with no value. Delays the aha moment.	Defer email verification until after the first session. Allow Google or GitHub sign-in.
Vague error messages on signup	People retry and fail. They give up.	Write errors that say what to fix. Show password rules inline. Allow paste from password managers.
Plan names differ across the site	Confusion at checkout and in invoices. Tickets spike.	Standardise names across pricing, app, docs and emails. Update old pages and redirects if needed.
No clear CTA near the decision point	The next step is below the fold or generic.	Place “Start free trial” under each plan. Repeat once after the FAQ with the same text. No modal popups.

Measure the change without hand-waving

You cannot manage what you do not measure. Ignore published averages. Your rate is the only one that matters, based on your traffic and model as of 2026.

Landing page conversion rate: conversions divided by sessions that began on /pricing over 28 days
Signup conversion rate: accounts created divided by visitors of the signup path over 28 days
Trial-to-paid rate: paying accounts divided by trials started in the same cohort
Model matters: free trial and freemium are different, with different rates and support costs

Set one primary goal for /pricing
Example: clicks on “Start free trial” or completed signups from sessions that began on /pricing.
Join landing and signup in product analytics
Track the page a session started on and the signup event. Attribute conversions to /pricing when it began there.
Run one change at a time
Ship the plan count and the one-line differences first. Wait for a few hundred sessions. Then test the annual toggle copy.

Worked example on yourproduct.com

Here is a full example you can ship this week. Replace copy and limits with your own numbers. Keep the shape and the order.

URL: https://yourproduct.com/pricing

Header: Pricing
Subheader: Plans for solo builders and small teams
Toggle: Monthly | Annual  Save 20%

Cards, left to right:

Starter  $19/month
For solo builders, up to 3 projects and 10k checks a month
CTA: Start free trial

Growth  $50/month   Most popular
For small teams, up to 10 projects and 100k checks a month
CTA: Start free trial

Scale  $199/month
For product teams, unlimited projects, 1M checks a month
CTA: Start free trial

Below cards:
- Overages: We pause checks at limits. Upgrade to resume.
- Add-ons: SSO $99/month on Growth and up.
- Taxes: Prices exclude tax where applicable.

FAQ:
- Can I cancel any time? Yes, from Settings. Your plan ends at the current period.
- Do I need a card for the trial? No card needed to start a 14 day trial.
- What happens after the trial? Your data stays for 30 days. Add a card to continue.
- Where is my data stored? In the EU. We encrypt data in transit and at rest. See /security.
- Do you offer discounts? Annual plans include a saving. Email [email protected].

Trust strip:
- Links: About, Security, Status, Changelog, Terms, Privacy, Reviews
- Logos: only with permission
- Screenshots: real product views, captioned

Questions

Check my site, free

Check your /pricing in about thirty seconds: paste your URL and see three findings on your page, the searches around it and the rivals on them, free.

Free check, no card
Read-only, your own accounts
Readable by your agent