A pricing page should explain how the bill is calculated, what each plan includes and leaves out, what triggers a move to the next tier or an overage charge, and how renewal and cancellation work, even when the final number needs a quote. Buyers use it to decide whether your billing model fits their budget before they talk to anyone. Terms that change the charge belong next to the price, not in a footnote.
Software pricing has more moving parts than most product pricing. A seat may mean any named user or only an active one. Usage may be counted per record, per workflow run, or per location. An annual plan may be billed up front with a different monthly equivalent. A buyer who cannot work out which of those applies to them cannot compare you with anyone, and a finance approver who cannot model year two will not sign year one.
This page is content planning for SaaS marketing and revenue teams. It is not legal or billing advice, and counsel should review any page that describes free offers, trials, or automatic renewal.
Explain the billing unit before the price
Start with the unit you charge for, and define it in one sentence a finance approver could repeat. Then show what moves a customer from one plan to the next. The table below lists the elements that most often need a sentence of their own.
| Pricing element | Question it raises | What the page should state |
|---|---|---|
| Billing unit | Who or what counts? | The definition of a seat, user, record, or location, including inactive or guest users |
| Tier thresholds | When do we move up? | The limit that triggers the next plan and whether the move is automatic |
| Usage limits | What happens at the cap? | Whether the product stops, slows, or bills an overage, and at what rate |
| Billing term | Monthly or annual, and what changes? | Both prices, how annual is billed, and whether seats can be added mid-term |
| Add-ons and minimums | What else might we pay? | Paid add-ons, platform fees, onboarding fees, and seat minimums |
| Renewal and cancellation | How do we stop? | Renewal timing, notice, and the cancellation method |
Where the arithmetic is not obvious, add a worked example. A short paragraph showing what a team of a stated size pays in month one, and what changes when it adds people or crosses a usage limit, answers the question a finance approver would otherwise send back by email. Use plainly illustrative figures drawn from your actual price list, label them as an example, and update them when the list changes. A worked example that no longer matches the plan table does more harm than none at all.
"Contact sales" still needs an explanation
Many SaaS companies quote their top tier individually, and there are sound reasons to. The pricing page can still say what drives that quote: volume, contract length, deployment options, support level, or required security features. Hiding the number is not the same as hiding the method. A buyer who understands the inputs can tell whether the call is worth booking, and the sales rep starts from a shared vocabulary rather than a guessing game.
Be specific about which capabilities sit only in the quoted tier. If single sign-on, audit logs, or a data processing agreement require it, say so in the plan comparison. Leaving that out invites the buyer to discover it on the third call, which is where trust in the rest of the page goes.
Free plans, trials, and automatic renewal
Federal rules reach some of the most common SaaS pricing patterns. The FTC's guide on use of the word "free," at 16 CFR Part 251, says that when making free offers, "all the terms, conditions and obligations upon which receipt and retention of the 'Free' item are contingent should be set forth clearly and conspicuously at the outset of the offer." If a free trial turns into a paid plan unless the customer cancels, or a subscription renews on its own, the Restore Online Shoppers' Confidence Act may come into play. At 15 U.S.C. 8403, it covers charging consumers for goods or services sold on the Internet through a negative option feature, a term it takes from the FTC's Telemarketing Sales Rule, and it requires the seller to disclose all material terms clearly and conspicuously before obtaining billing information, obtain express informed consent before charging, and provide "simple mechanisms for a consumer to stop recurring charges."
The statute speaks of consumers, and how these rules apply to a self-serve business signup is a question for counsel, along with any state rules on automatic renewal. For the page itself, the planning point is simpler: put the trial length, what happens when it ends, the renewal date, and how to cancel where a buyer will read them before entering a card. A good check is to ask finance, "What is the most common reason a customer is surprised by an invoice?" and make sure the pricing page answers it near the price.
A fictional pricing rewrite
Here is a fictional example. A customer support platform in Texas charges per agent, with a monthly cap on automated workflow runs per plan. Its pricing page lists three plan names, three prices, and a feature grid, and the word "agent" appears without a definition. Prospects keep asking whether part-time and seasonal staff count, and finance teams ask what happens when workflow runs exceed the cap in a busy month. The rewritten page defines an agent, states that runs above the cap are billed at a listed rate rather than stopped, and shows a worked example for a team of 15 agents moving to 25. The billing team already knows how proration, seat changes, and overages work, so the writer should not have to reconstruct any of those rules from old invoices; the billing lead supplies them and approves the final wording.
Date the page, too. A line stating when prices were last updated tells a buyer, and anyone summarizing the page, which version they are reading. If the site uses software app structured data, keep the price in the markup the same as the visible price.
Where pricing connects to the rest of the site
Pricing questions rarely arrive alone. They come with questions about limits and about what the product does not include, which explaining what your product does not do covers, and they shape whether a buyer books a demo at all, covered in what buyers ask before booking a software demo. Hudson South's four steps apply here in order. Authority Asset gathers the approved pricing rules, plan definitions, and the explanations your sales and billing teams give. Hudson Twenty-One records how your company explains money and terms, one of the many things it tracks across 21 dimensions. Market Intelligence studies how buyers in your category describe budgets and billing models, and how competing vendors present theirs. AEO Creation turns those inputs into a pricing page that answers the billing question first. For the full set of pages, see the software and SaaS overview.
See how your pricing page reads to a finance approver
Bring your current pricing page. In a free 30-minute call, we set it beside competing vendors' pricing pages and look at how each explains plans, limits, and renewal.
Get your free competitor analysisSources
- 16 CFR Part 251, Guide Concerning Use of the Word "Free" and Similar Representations. Electronic Code of Federal Regulations. Read 2026-10-16.
- 15 U.S.C. 8403, Negative option marketing on the Internet. U.S. Government Publishing Office. Read 2026-10-16.
- 16 CFR 310.2, Definitions. Electronic Code of Federal Regulations. Read 2026-10-16.