How should a software product choose its revenue model?

Charge at the point where a defined party receives measurable value. Use subscriptions for continuing value, usage pricing when value and cost grow with consumption, service fees or commission for completed transactions, and advertising only when willingness to pay is low but traffic is stable. The first version should have one primary revenue stream and, at most, one supporting option.

A revenue model combines product value, billing unit, and cost structure; it is not a menu of payment features. The user, beneficiary, decision-maker, and payer may be different. A booking tool can charge the store by seat while remaining free to consumers; a marketplace may charge merchants for leads or take a transaction fee. Wavesteam identifies these roles during product planning.

When validating the product path and commercial loop, also compare How should an online community or information platform choose a revenue model?; the linked guidance adds context that should be considered in the same decision.

Model	Suitable value	Billing unit	Evidence required	Typical risk
Subscription	Continuing content, tools, storage, or service	Account, seat, plan, period	Activation, renewal, churn, service margin	Overpromising to win the first purchase
Usage	Value and supplier cost grow with use	Task, capacity, request, unit	Unit cost, distribution, bill predictability	Volatility discourages use
Licence plus service	Value concentrates in deployment, training, or customization	Project, module, annual maintenance	Delivery cost, collection time, support renewal	Irregular revenue and labour scaling
Commission	Platform genuinely enables and protects a transaction	Order or transaction value	Conversion, refund, off-platform leakage, dispute cost	Underestimated compliance and support
Advertising / sponsorship	Users access free while a third party buys attention	Impression, click, lead, period	Qualified traffic, fill, net ad revenue, retention loss	Insufficient scale and damaged experience

Subscription requires a reason to pay next month: updates, collaboration, cloud operation, specialist data, or recurring time savings. One-time generation may fit a credit pack or per-use model. Apple's subscription material requires ongoing value, and mobile digital services should check App Review Guidelines before building the payment path.

Usage pricing needs a unit customers understand and the provider can meter. Charging an AI product by successful task is often clearer than exposing tokens, while the service still tracks model, storage, and human-review cost internally. Usage dashboards, alerts, caps, and prepaid allowances reduce bill anxiety. A base subscription with included volume can work when its invoices trace every period and unit.

Commission is defensible only when the platform lowers acquisition, trust, payment, or fulfilment cost. If parties move offline after first contact, neither GMV nor a high rate is sustainable. Include cancellation, refund, split settlement, invoices, complaints, bad debt, and support time in contribution margin and review ecommerce and sector rules with legal and tax specialists.

Advertising follows a stable, describable audience and usage pattern. AdMob documentation shows that advertiser bidding and matching make returns vary by audience, region, and format. Test with real traffic and measure revenue alongside exits, task completion, and next-day retention rather than treating an industry eCPM as guaranteed income.

Test willingness to pay before building a complete billing platform through prototypes, pricing interviews, manually provisioned paid trials, or plan pages. Follow the full funnel from price view through payment, activation, continuing use, and refund. Compare net contribution after channel fees, infrastructure, content or fulfilment, support, and sales. Margin, retention, and acquisition payback must work together.

Wavesteam helps define the value event, billing unit, and cost ledger, then implements the minimum permission, order, and invoice loop. A second revenue stream follows only after observing a complete paid cycle. Our software project budget guide explains related project-cost scope.