A B2B SaaS pricing strategy defines what customers pay for, how charges change as they use more of the product, and what each package includes. Start with the problem the software solves and the value customers can substantiate. Then check the cost of acquiring and serving those customers.
Separate value, packaging and the charging unit
Customer value helps inform a price, but it does not establish what a buyer will pay. Compare the proposed price with their alternatives, budget and cost of switching. Use customer conversations and actual buying decisions to test your assumptions.
Packaging determines which capabilities and services belong together. The charging unit determines how the bill grows: by user, account or measured activity, for example. A package can use more than one charging unit, so check that a customer can explain the bill before adding complexity.
Compare B2B SaaS pricing models
A flat subscription charges a set amount for a defined package and period. Per-seat pricing charges for users. Usage-based pricing charges against a measured quantity. A hybrid can combine a fixed subscription with additional usage charges. Stripe’s pricing documentation describes these billing structures.
Test each model against how customers work. Per-seat pricing needs a clear definition of a billable user. Usage pricing needs a measure that customers can monitor and a bill they can forecast. Neither is automatically the right choice for every product.
Tiered packages separate features, limits or service levels. Show what changes between packages and what would require an upgrade. A free package also needs explicit limits and a reason to move to paid use; include the cost of supporting free accounts in your assessment.
Value-based pricing is an approach to setting a price, rather than a separate billing mechanism. You might use a customer’s estimated time saving to inform the price of a per-seat package. Record the assumptions behind that estimate and avoid presenting it as a guaranteed return.
Make the customer’s bill understandable
Consider this fictional example: a subscription costs $200 a month and includes 1,000 processed documents. Each additional document costs $0.10. At 1,250 documents, the monthly charge is $225 before any applicable taxes or other agreed charges. The extra 250 documents account for $25.
That arithmetic is only useful if “processed document” has a precise meaning. Explain whether failed attempts, duplicates and test runs count. Decide how customers see their usage, whether alerts are available and what happens at any spending limit. Test a sample invoice against the contract wording.
Use consistent unit economics
Customer acquisition cost compares acquisition spending with new customers acquired. Define the costs and period included. Average revenue per account uses accounts as its denominator; average revenue per user uses users. They answer different questions.
Customer lifetime value is an estimate. State whether your calculation uses revenue or adjusts for gross margin, and document the retention assumptions. An LTV-to-CAC ratio built from revenue does not have the same meaning as one built from gross profit. See Stripe’s SaaS metrics guide for the measures commonly reviewed together.
Use the same definitions when comparing customer groups. A price increase does not by itself prove that lifetime value improved: customers might buy less, downgrade or leave. Likewise, a lower acquisition cost does not establish that an account will be profitable to serve.
Check delivery costs and billing exceptions
Review which costs increase with customer activity and which require staff time. Include implementation and support demands when assessing an offer. A package that looks attractive at average usage still needs checking at heavier usage and against the service commitments it includes.
Before launch, test upgrades, downgrades, discounts, credits and contract exceptions in the billing system. Have sales and delivery staff review the same examples. Billing software can calculate charges, but the team still needs to agree what the customer has bought.
Review changes without assuming causation
Record what changed, who received the new offer and when. Compare conversion, discounting, package choices and cancellations on a consistent basis. Keep changes in product, customer mix and sales activity visible; revenue movement alone cannot isolate the effect of pricing.
When revising an existing customer’s terms, check the agreement and explain the proposed change clearly. Give the account team accurate information about options and effective dates. Use the review to identify confusing charges or unsuitable packages as well as opportunities to increase revenue.
