Pricing page and pricing table examples

Six reviewed pricing table examples

Use these pricing page design references to compare billing units, seat types, usage allowances, estimates, fee breakdowns and feature matrices. They are visual evidence, not verified current prices or conversion benchmarks.

Notes reviewed 2026-10-07. Screenshots and brand assets belong to their respective owners. Collection dates below are not individual inner-page capture timestamps.

Linear

Keep the billing unit beside each plan price

What the capture shows

Four plan columns put the amount and per-user/month unit above feature lists. The paid self-serve columns show yearly billing switches, while Enterprise says custom with annual billing only. Business offers both a start and sales route.

What to adapt and test

Separate the displayed monthly equivalent from the actual charge schedule. Give each tier a clear audience and action; make any difference between self-serve and sales understandable.

Limits of the reference

Only the captured billing state is observed. No switch interaction, current price, annual invoice total or conversion result is verified.

Figma

Explain seat types within each tier

What the capture shows

Paid columns separate Full, Dev and Collab seats instead of presenting one price for every user. Professional shows a Monthly/Annual control with Annual selected; the larger tiers carry annual billing labels. Prices use a CA$ prefix.

What to adapt and test

When access varies by role, define the seat types and their units before asking someone to choose. Keep the currency, billing state and included allowances visible together.

Limits of the reference

The captured Canadian-dollar display is not a US price quote or a current offer. Product access, credits and the alternate billing state were not tested.

Resend

Put usage allowances and overages next to the price

What the capture shows

Transactional and marketing tabs sit above a volume slider. The cards show monthly email allowances, overage text for paid self-serve plans, daily limits and different support levels. Custom takes a contact route.

What to adapt and test

Distinguish included volume, overage units and limits so a base subscription does not look like an unlimited total. Keep the chosen product and volume understandable after changing controls.

Limits of the reference

The still does not prove how the slider or tabs update prices, nor current deliverability, support or uptime claims. Those require separate verification.

Supabase

Break an estimate into subscription, compute and credits

What the capture shows

A plan selector sits beside a project configuration area. The estimate separates subscription, compute and a credit before showing a total. An add-project control, a drag-to-adjust affordance and a collapsed breakdown appear nearby.

What to adapt and test

If cost depends on configuration, show the components of the estimate and what each control changes. Label assumptions, credits and exclusions rather than suggesting a fixed guaranteed bill.

Limits of the reference

Only one configuration and estimate are visible. Calculator correctness, additional projects, keyboard control and the expanded breakdown are not established.

Clerk

Separate fee categories in a comparison

What the capture shows

Provider columns are compared across billing fees, transaction fees and an emphasized combined row. A note below limits the illustrated example to US credit-card transactions.

What to adapt and test

Name the fee basis and scope before comparing totals. Fixed charges and percentage charges need different units, and region or payment-method conditions belong beside the example.

Limits of the reference

These are historical third-party comparison claims, not independently verified current fees or a recommendation of the cheapest provider. Do not republish them as your own verified price research.

Notion

Keep feature rows interpretable when the table gets long

What the capture shows

A compact matrix compares guest limits and permission features with numbers, words and checks. The section crop does not include the tier headers, so it cannot identify the plan names for each column on its own.

What to adapt and test

Keep column headers available through sticky headers, repeated labels or a meaningful narrow-screen layout. Explain unavailable features in words as well as symbols.

Limits of the reference

This is a table excerpt, not the complete pricing page. Do not assign its columns to tiers or infer live feature availability from the cropped image.

A pricing page design checklist

• Define who each plan serves and make the difference understandable before listing every feature.
• Keep price, currency, billing unit and actual charge schedule together; label the selected monthly or annual state.
• Show important allowances, overages, seat roles and estimate assumptions before someone commits.
• Distinguish purchase, trial and sales routes. Compare CTA examples and sign-up page references for the next step.
• Check table headers, long plan names, keyboard controls, errors and narrow-screen reading. Use checkout patterns when a price choice becomes a transaction.
• Verify current source terms independently. This page supplies pricing page inspiration, not procurement advice.

Try an original billing clarity example

Invented USD prices for one example plan: $18 per seat/month billed monthly, or $15 per seat/month billed annually. This local demo does not create an account, start a trial, charge money or represent UI Discovery pricing.

Brief an original pricing interface

This is an editorial starting point, not a native-builder validation. Supply your approved plans and destinations; see the SaaS prompt guide for wider page context.

Build an original pricing interface using my approved plan data.
Show the currency, billing unit, selected period and actual charge schedule.
Keep allowances, overages, role entitlements and exclusions understandable.
Use real trial, purchase or sales destinations. Do not invent a checkout API.
Preserve table headers and action labels at 320px, 390px and desktop.
Test keyboard controls, long copy, invalid quantities and billing changes.
Report the checks performed. Do not copy the reference's assets or prices.