Ignalies

How to price your SaaS product: a guide to common models

Pricing a software product is not simply a matter of choosing a number. The price shapes who signs up, how customers budget for your service, and whether revenue covers hosting, support, sales, and the time required to keep improving the product. A price that seems attractive at launch can become unsustainable once usage grows or every new customer brings another support request.

A frequent mistake is to copy a competitor’s pricing page without examining what sits behind it. Another is to price only for the cost of building the software. Customers pay for a business outcome, while your business must still absorb cloud infrastructure, payment fees, onboarding, customer success, and acquisition. The strongest decisions connect those realities: customers perceive fair value, and the model produces healthy margins.

Australian conditions add useful context. Many small and medium-sized businesses in Sydney, Melbourne, Brisbane, and regional centres focus on predictable monthly costs, so a simple AUD price and a clear included plan can win over a complex tariff. Australian GST generally applies at 10% on taxable software subscriptions, although the exact treatment depends on the supplier, customer, and transaction; your pricing page should still explain whether displayed prices include GST.

The process below covers the main commercial models, the numbers that should guide a decision, and the practical steps for turning a price into a coherent offer. It applies to early-stage products, established subscription businesses, and software sold to Australian organisations alongside international customers.

Find the value your customer is buying

Begin with the problem the product solves, not a list of features. A construction manager may value fewer delays, while an accounting firm may value faster client onboarding and fewer errors. Write down the result that creates willingness to pay. This keeps pricing connected to customer value and prevents a technically impressive product from becoming an expensive discretionary purchase.

Choose a value metric that reflects that result. It might be the number of active users, invoices processed, documents handled, transactions completed, or team members who need access. The metric should increase as the customer gets more value, remain understandable during purchase, and be measurable without excessive manual work. It also gives each tier a logical boundary and makes upgrades easier to explain.

Research can turn an estimate into evidence. Interview current users and prospects about their alternatives, budget, renewal process, and definition of value. Review lost deals, support requests, and competing products to identify price objections. Then test two or three realistic price points with different messages. Willingness to pay is rarely identical across segments, so it is safer to learn early than to alter the price after the product is already established.

Compare the main pricing models

A flat-rate subscription charges a fixed amount for access over a defined period. Monthly plans give buyers flexibility, while annual plans can improve cash flow and reduce churn by committing customers for longer. This model works well when usage is broadly similar and customers mainly need a predictable budget. It can become inefficient if a small account consumes expensive support while a large account pays the same amount.

Tiered subscriptions divide the offer into packages based on features, limits, service levels, or outcomes. The plans should represent meaningful differences in value rather than arbitrary feature blocks. A freemium approach can widen the top of the funnel by giving users a restricted product at no charge, but it only makes sense when a realistic share of free users becomes paying customers and the free tier does not create unsustainable serving costs.

Per-seat pricing charges for each named user and is familiar to teams already managing software licences. It is straightforward to administer and can expand naturally as a company hires, but it may discourage broad adoption when every additional colleague adds cost. Value-based pricing charges according to the scale of customer benefit, such as revenue influenced or transactions processed. It can capture more value from large customers, although buyers may challenge the measurement and predictability of the charge.

Usage-based pricing meters consumption, such as API calls, stored data, automations, or completed jobs. It can suit products whose value naturally changes with usage and can reduce early purchasing friction. The challenge is unpredictability for the customer and revenue volatility for the supplier. A hybrid model combines a platform fee with metered usage, while transaction fees tie charges to completed sales or payments. One-time or perpetual licences also remain relevant for some desktop and on-premises products, usually with separate maintenance and upgrade terms. If metering records identifiable user activity, explain data handling in line with the Australian Privacy Act 1988 and the Australian Privacy Principles.

Build a price your margins can support

Work out the fully loaded cost of serving one customer before setting the target margin. Include hosting, third-party APIs, payment processing, support, onboarding, account management, and the sales commission required to win the account. A useful starting point is to divide the cost to serve by one minus your target gross margin to estimate the monthly break-even price. The formula is a floor, not necessarily the final price, because acquisition cost, churn, and lifetime value also shape the sustainable level.

Then compare that floor with customer value and market evidence. Price too far below the economic floor turns growth into a cash drain, while pricing too far above perceived value creates objections and longer sales cycles. Competitor prices are one reference point, not a substitute for your own economics. Track customer acquisition cost, gross margin, churn, and lifetime value by segment so you can see whether a discount produces enough additional revenue and retention.

Build a simple price architecture after the model is clear. Offer a default plan that fits the majority of suitable customers, an upgrade for heavier use, and an enterprise option where security, procurement, or service requirements justify it. Show monthly and annual prices, state included allowances, and make overages visible. A modest annual discount can reward commitment, but compare it with the value of retained cash and lower servicing costs. Test the offer with a limited pilot, establish a written price-change policy, and grandfather existing customers for a defined period where appropriate.

A pricing checklist for Australian software teams

Use a short decision record before publishing prices. It forces assumptions about value, delivery cost, and buyer behaviour into the open, and it gives the team something concrete to review after launch. The following checklist works well for a recurring-revenue product:

A completed list should lead to an operational decision rather than a collection of numbers. Record who approved the price, which evidence supports it, and the date for the next review. This is especially useful when founders, sales staff, and product leaders interpret customer feedback differently.

Publish, explain and revisit your pricing

A pricing page should make comparison easy. Give each plan a plain-language purpose, list its limits, separate base fees from usage charges, and explain what happens when a customer needs more. Avoid vague claims such as “best value” without evidence. For buyers comparing tools such as accounting, payroll, CRM, or project-management software, direct links to full feature and pricing details can reduce uncertainty.

Train sales and customer-success teams to discuss pricing as part of the product’s value. Provide a short example of where a customer sits on each tier, how usage is counted, and what triggers an upgrade. A transparent calculator can help with consumption-based plans, but it should also show a realistic monthly estimate. Commercial emails and trial follow-ups should comply with the Australian Spam Act 2003, including sender identification and appropriate consent, so a focused campaign does not undermine trust.

Treat the first price as a starting hypothesis, not a permanent verdict. Release it carefully, gather conversion, expansion, support, and retention data, and change one element at a time where possible. Communicate any increase well in advance and give customers a reasonable migration path. Choose your primary model, calculate the price floor for your next Australian customer, publish a clear pricing page, and schedule the first review date now.