Subscribe to The City Shift Finance Podcast
The pricing approach that helped a software company gain early market share can become less effective as the product matures, customer use expands, and the economics of serving enterprise customers become more complex.
I am Josh, and welcome back to the City Shift Finance podcast.
Today we are discussing SaaS monetization strategy and why the growing use of consumption-based pricing is forcing software companies to reconsider the relationship between what customers consume, what they pay, and the economic value they receive.
Seat-based subscriptions remain widespread across software, while consumption charges, API pricing, computational usage, committed spending, and outcome-related pricing are becoming increasingly important as products incorporate services whose delivery costs and customer use can vary considerably.
The financial problem begins when the unit used to calculate the customer’s bill has a weak relationship with the economic benefit the product produces. A company may charge for data processed, API calls, computational activity, transactions, or another measurable unit because that unit is easy to track and closely connected to product use, yet the customer may experience value through revenue generated, labor avoided, time saved, risk reduced, or a critical process completed.
When the billing unit and the economic benefit move at different rates, greater product use does not necessarily produce proportionately greater willingness to pay.
That gap becomes more consequential as consumption revenue becomes a larger part of the business. Customers can reduce unnecessary activity, improve the efficiency of their workflows, consolidate workloads, or change spending priorities, and those decisions can reduce consumption even when the product continues delivering significant value.
Revenue can therefore become more sensitive to customer behavior, while the software company continues carrying engineering, infrastructure, support, and commercial expenses required to serve the account.
“The presence of a commitment does not determine whether the company is capturing an appropriate share of the value created.”
Customer commitments can reduce some of that exposure by establishing a minimum level of contracted spending while allowing revenue to increase as consumption grows. A committed amount gives the software company greater economic certainty, while variable charges preserve a connection between customer activity and additional revenue; however, the presence of a commitment does not determine whether the company is capturing an appropriate share of the value created.
That question depends heavily on what the company chooses to charge for. A software product that creates substantial economic benefit with relatively little computational activity can become highly valuable to the customer without generating equivalent growth in consumption revenue, while another product may generate extensive computational activity without producing an equally large economic result.
In both cases, the billing unit influences how much of the economic benefit ultimately reaches the software company.
This is becoming increasingly important as artificial intelligence changes software economics. Products that complete work previously performed by employees, resolve customer requests, generate commercial output, or complete complex business processes create economic value that can extend well beyond the amount of computing activity required to produce the result.
Some software companies are therefore connecting charges more closely to completed transactions, verified resolutions, or other measurable outcomes, while others combine committed spending with variable usage charges to balance revenue certainty with customer activity.
Changing the way a SaaS company charges customers also affects decisions across finance, sales, and product teams because revenue behavior changes alongside the commercial proposition.
Finance must forecast customer consumption and contracted spending with enough precision to understand how changes in activity affect revenue and gross margin, sales teams must communicate why the chosen billing unit reflects the economic benefit customers receive, and product teams need to understand which forms of customer use contribute to retention, expansion, and sustainable economics.
The central financial question is whether revenue grows in proportion to the economic value the product creates while preserving acceptable margins and sufficient predictability for the business.
A company can achieve strong adoption while capturing too little revenue from highly valuable use, or generate growing consumption while absorbing enough delivery cost that the economics deteriorate as activity increases.
“SaaS monetization becomes stronger when pricing, customer economics, revenue behavior, and delivery costs support the same financial outcome over time.”
SaaS monetization becomes stronger when pricing, customer economics, revenue behavior, and delivery costs support the same financial outcome over time.
To discuss your SaaS pricing and monetization strategy with our team, visit cityshiftfinance.com.
Thanks for tuning in.
About the host
Josh is the Director of Strategy at City Shift Finance, overseeing firmwide strategic initiatives, proprietary frameworks, and long-term value creation.
