Templates

Free template

A free SaaS pricing page template you can build in Webflow, Framer or code

This free SaaS pricing page template gives you the structure and the copy prompts for every block of a pricing page: header, plan cards, comparison table, proof, FAQ and the contact-sales path. It's a text template, not a Webflow or Framer file, so you copy it into a doc, fill it in, and then build it in whichever tool your site runs on.

At a glance

  • Six blocks, in the order buyers read a pricing page
  • A plan card spec you can fill in for every tier
  • Pricing FAQ prompts that answer the objections sales hears
  • How each block maps to Webflow, Framer and Next.js
  • A filled-in hypothetical example
  • ATQLeads
  • Update AI
  • LeanScale
  • CSSinc.ai
  • HeyInterests
  • JuPay
  • PowerPulse
  • WireFox
  • Reactive Growth
  • Minexa.ai
  • SmileJoy
  • LFG Business Group
  • ORBITX
  • Funnels.com
  • Sentipi
  • UNIVIT Research
  • LifeLink
  • Wolf Automation
  • Shaqir Hussyin
  • Q-TARO
  • MainPlume

What is in this SaaS pricing page template?

A SaaS pricing page template is the order of blocks and the questions each block has to answer, so the page helps a buyer pick a plan instead of just listing prices. This one has six blocks: the header, the plan cards, the feature comparison table, proof and trust, the pricing FAQ, and the closing path to buy or talk to sales.

We wrote it as copyable text on purpose. Most free Webflow SaaS templates give you a pretty layout with placeholder tiers, and the hard part, deciding what each plan is called, who it's for and what it says, is left blank. Do the words first, then the layout is quick in any tool. Our guide to the SaaS pricing page covers the strategy behind each choice.

How do you use the template?

  1. Settle the pricing model first

    Decide tiers, the value metric (seats, usage, projects) and whether you show prices at all. If you're unsure, read should you show pricing on your website before you write a word.

  2. Copy the six blocks into a doc

    Keep the headings below and write under each one. Leave a note wherever you need a decision from founders or finance.

  3. Fill in the plan card spec for every tier

    Use the same fields for each plan so the cards compare cleanly side by side.

  4. Collect the real objections

    Ask sales and support which pricing questions they hear most. Those become the FAQ.

  5. Build and check it on a phone

    Most of the layout problems on pricing pages show up on small screens: stacked cards, wide tables and a toggle that scrolls out of view.

Block 1: The pricing page header

  • Headline: say what the buyer gets or who the plans are for, not just "Pricing". For example, "Plans for teams from 5 to 500".
  • Subheadline: one sentence on the value metric, such as "Pay per active seat. Add or remove seats any time."
  • Billing toggle: monthly and annual, with the annual saving stated plainly. Our note on the annual vs monthly pricing toggle covers the default to choose.
  • Audience switch (optional): only if you truly sell different plans to different buyers, for example startups and enterprise.
  • Trial or free plan line: if there is one, state it here, with whether a card is required.

Block 2: The plan cards

Each plan card answers one question: is this plan for me? Use the same fields on every card and keep three or four tiers at most, because every extra card makes the choice harder. Our guide to pricing tiers explains how to split them.

Field

What to write

Example prompt

Plan name

A name that signals the buyer, not a metal

Starter, Team, Business

Who it's for

One line naming the buyer and size

For teams up to 10 people

Price

The number, the unit and the billing period

$__ per seat / month, billed annually

Key limits

The 2–3 limits that decide the upgrade

__ projects, __ GB, __ API calls

Top features

4–6 items, starting with what's new vs the tier below

Everything in Starter, plus…

CTA

A specific action, different per tier if needed

Start free trial / Talk to sales

Highlight

Mark one plan as the default choice and say why

Most teams start here

Block 3: The feature comparison table

The comparison table is for the buyer who has narrowed down to two plans and needs the detail. Put it below the cards, group rows by job, and keep the plan names in a sticky header so people never lose track of which column is which. Our deep dive on the pricing comparison table has layout patterns.

  • Row groups: for example Core features, Collaboration, Integrations, Security and admin, Support.
  • Cells: a check, a dash or a short value ("5 seats", "Unlimited"). No paragraphs in cells.
  • Tooltips: a one-line definition for any feature name a new buyer wouldn't recognize.
  • Mobile: show one plan at a time with a plan switcher, or let the table scroll sideways with the feature column fixed.

Block 4: Proof and trust near the price

The pricing page is where doubt peaks, so put proof right next to the decision. Use what you really have, and never invent logos, numbers or quotes.

  • Logo row of customers who agreed to be shown.
  • One or two short testimonials about value for money or ease of rollout, with name, role and company.
  • Security line: the certifications or reports you actually hold, linked to your trust page.
  • Risk reducers: trial length, cancellation terms, refund policy or a migration offer, stated exactly as they work.

Block 5: The pricing FAQ

Write the FAQ from the questions sales and support already answer every week. Each answer should be two to four plain sentences that work if quoted alone. That matters more now that many buyers start their research in AI chatbots, because clear text answers about price are what those tools can read and repeat. See our pricing page FAQ guide for more.

  1. What counts as a seat, a user or a unit of usage?
  2. What happens if we go over a limit?
  3. Can we switch plans or cancel at any time, and how is it prorated?
  4. Do you offer discounts for startups, nonprofits or annual billing?
  5. What payment methods and currencies do you accept, and do you invoice?
  6. Is there a free trial, and what happens when it ends?
  7. How is our data handled, and where can we see your security documentation?

Block 6: The closing path and the enterprise option

End the page with two clear routes: start on a self-serve plan, or talk to someone. The enterprise or custom tier usually sits here, with what it adds (SSO, contracts, support terms, volume pricing) and a sales CTA. If the product is sales-led, link a book a demo page built for that one action rather than a generic contact form.

Hypothetical example: a filled-in header and plan cards

For example, suppose a seed-stage scheduling tool for clinics fills in blocks 1 and 2.

Header: "Scheduling plans for clinics of every size." Subheadline: "Priced per practitioner. Add or remove practitioners any time." Toggle defaults to annual, labelled "2 months free". Trial line: "14-day free trial, no card required."

Cards: Solo (for one practitioner, $__ per month, online booking and reminders, CTA Start free trial). Clinic, highlighted as "Most clinics start here" (for 2 to 20 practitioners, adds shared calendars, intake forms and payments, CTA Start free trial). Group (for multi-site groups, custom pricing, adds SSO, a data processing agreement and a named contact, CTA Talk to sales). The numbers are placeholders: the point is that every card answers who it's for before it lists features.

How do you build this pricing page in Webflow, Framer or Next.js?

All three can build every block. The differences are in how you keep plan data in one place and how easy the toggle and table are to maintain. Platform features change, so check the current docs before you commit to an approach.

Block

Webflow

Framer

Next.js

Plan cards

A component, or a CMS collection for plans

A component with variants, or the CMS

A component fed from one plans data file

Billing toggle

Tabs or interactions swapping two price sets

Component variants switched on click

React state, prices from the same data file

Comparison table

Built by hand or from CMS fields

Built by hand; long tables get heavy

Generated from data, easy to keep in sync

FAQ

An accordion component

An accordion component

An accordion plus FAQ markup from the same source

If your pricing changes often or you have many plans, keeping the numbers in one data source matters more than the tool. We build pricing pages as part of our SaaS website design work: we designed and built the sites for Update.ai and Minexa AI. Our website package is $8,000 fixed for up to 6 pages, plus $500 per extra page, with copywriting, custom design, a Next.js build, a CMS and animation. If you're staying on Webflow, see our Webflow development service. Either way, the next step is a free 30-minute call.

What our clients had to say

Pricing

Fixed prices for fixed scopes, agreed before we start, or a monthly retainer when you need a team on call. All prices in USD.

Website

A multi-page marketing site, written and designed by us, developed in Next.js and animated.

What’s included

  • Up to 6 pages, written, designed and developed
  • Custom design, never a template
  • Built in Next.js, fully responsive
  • Animations and interactions
One-time, up to 6 pages

$8,000

+$500 for each extra page
Book a call
4.92 on Contra · 11 reviews

Free 30-minute intro call, no commitment

Not sure yet? Try a week together.

One week of design and development, so you can see how we work before you commit.

$1,000Book a trial week

Frequently asked questions

Is this a free Webflow SaaS template I can clone?
No. It's a text template: the structure, fields and copy prompts for a SaaS pricing page, which you copy into a doc. We don't offer a Webflow cloneable or a Framer remix. The layout is the quick part to build in any tool once the plan names, limits, proof and FAQ answers are written, so starting from the words saves more time than starting from a layout.
How many pricing tiers should a SaaS pricing page show?
Three is the usual choice: an entry plan, the plan most buyers should pick, and a higher or custom tier for larger teams. Two works when the product is simple. Five or more usually means the tiers aren't clearly separated by buyer, and visitors stall. Whatever the number, every tier should name who it's for before it lists features.
Should the pricing page default to monthly or annual billing?
Default to the option most of your customers actually choose, and state the annual saving in plain terms next to the toggle. Defaulting to annual shows a lower monthly number, but it can feel like a trick if the billed amount is hidden. Whichever you pick, show the total billed and the billing period on each card.
What if we sell mainly through sales and don't publish prices?
You still need a pricing page. Explain how pricing works (the value metric, what drives the price, typical plan shapes), show what each package includes, answer the common objections in an FAQ, and offer one clear route to a sales conversation. A buyer who finds no pricing information at all may assume it's out of reach and move on.
Where should the pricing page link to?
Link from each plan's features to the product pages that explain them, from the security line to your trust page, and from the enterprise tier to a demo or contact page. Link back to the pricing page from the main navigation, the homepage and the product pages, because it's one of the pages buyers look for first.

Ready to qualify better leads and boost brand perception?

We take craft seriously over at Designify Studio. We do deep research and do what we do best - pay attention to the smallest details and make sure we speak to the right audience.

Schedule Call