SaaS pricing page specification

Make plan selection possible by showing the charging unit, included value, limits and buying path clearly. This worksheet supports the broader saas pricing plan.

The working template

A worked example

A plan advertised at $20 per user per month but billed annually should state the annual commitment next to the price.

The example is illustrative. It does not describe a measured customer result or create a promise about your own outcomes. Use it to understand the level of specificity the document needs.

How to complete the worksheet

1. Choose one project, account segment or decision. A document that attempts to cover the whole company usually hides important differences.
2. Gather the evidence required by the fields above. Use approved customer research, current product information and the relevant business records.
3. Draft the answers with the person responsible for doing the work. Keep unresolved questions visible and assign a next action to each one.
4. Review the document with the people who depend on it. Confirm scope, responsibilities and any constraints before treating it as an operating agreement.
5. Save the version and review date. Update it when the underlying offer, process or customer evidence changes.

Review before sharing

Do not bury mandatory fees or use a comparison table that hides the limits a buyer needs to choose.

A useful working document makes disagreements visible while there is still time to resolve them. Ask a colleague to explain the intended decision from the filled-in version without additional narration. If they cannot identify the next step or the evidence behind it, revise the relevant field.

Remove confidential customer details from any public copy. Keep names, prices and results only when you have permission and can explain their context. An empty evidence field is a signal to investigate, not an invitation to supply a plausible-sounding number.

Continue the work

• SaaS Pricing Models Compared
• How to Choose a Value Metric
• Usage Based Pricing for SaaS
• Good Better Best Packaging for SaaS
• How to Raise SaaS Prices

Find more templates and checklists for adjacent tasks.

Apply saas pricing page specification in a working review

Make a copy of the working file and complete one representative row before filling the entire document. Replace example values with evidence from the actual project. Add an owner and a review condition where the template calls for a decision. A blank marked unknown is more useful than an invented number that makes the file look finished.

For this topic, involve the pricing owner with finance, product and customer-facing input and work from offer scope, charging unit and scenario assumptions. The relevant unit is a defined customer segment and comparable commercial offer. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

A price is meaningful only with its package, quantity, terms and serving requirements. Test whether buyers can predict the bill and whether the charging unit supports useful adoption. Keep willingness-to-pay statements separate from observed purchasing behavior.

Two situations that can change the interpretation

When usage pricing makes buyers afraid to adopt

A usage dashboard can help only if it explains when data updates and how the displayed quantity relates to the invoice.

Use this check: Interview buyers about the uncertain usage unit and inspect available visibility or controls. Do not promise a hard cap unless the product actually enforces it.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When buyers cannot predict the pricing unit

A contact-based plan needs a clear definition of which contacts count rather than relying on a familiar-sounding label.

Use this check: Ask a suitable buyer to estimate an ordinary and high-usage invoice from the page. Do not imply that a public example covers every contract or usage case.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

An account may object to price because the required integration or implementation support is unclear. Discounting without resolving that concern can create a lower-priced failure. Compare the complete offer and the customer’s actual alternatives before treating every objection as a request for a concession.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.