Knowledge
Knowledge HubConcepts and strategic researchGlossaryDefinitions across six domainsFrameworksStructured strategy methodsTopicsConnected subject areasLibrary
PlaybooksPractical strategy guidesBooksBooks and long-form researchOperator VaultMember resources and toolkits
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
Revenue model
A revenue model specifies how an organization structures revenue streams for the value it delivers — for example subscription, usage, transaction fees, licensing, advertising, or hybrids. It is a capture-design choice inside a broader business model and is narrower than TSS’s revenue architecture concept. It should be distinguished from pricing tactics, cash collection timing, and accounting revenue recognition.
Why it matters
Choosing how you charge shapes customer behavior, sales motion, and margin profile. Confusing revenue model with the entire business model leads teams to debate “subscription vs usage” while ignoring who the customer is, what is delivered, and how costs scale.
Keep four layers distinct: (1) business model — overall value logic; (2) revenue architecture — TSS term for system design of value flows and capture points; (3) revenue model / stream design — which entitlements or events are chargeable; (4) pricing mechanics — meters, list prices, discounts. Separately, cash collection (when money arrives) and accounting revenue recognition (when revenue is recognized under applicable standards) can diverge from both packaging and invoices — especially with prepayments, multi-element arrangements, or usage true-ups.
Example (enterprise): A data platform sells an annual platform fee plus usage-based query charges. The revenue model is hybrid subscription + usage. Cash may arrive upfront annually while accounting recognition follows delivery/usage patterns; revenue architecture asks whether that mix reinforces learning, margins, and procurement fit.
Mechanisms
- Stream design — which chargeable events or entitlements create revenue.
- Packaging and meters — seats, usage, transactions, outcomes, or attention (pricing mechanics).
- Cash vs recognition — when cash is collected versus when revenue is recognized under accounting policy.
- Incentive effects — how the charge structure shapes expansion, consumption, and sales behavior.
Boundaries
- Revenue model ≠ business model as exact synonyms.
- Revenue model ≠ revenue architecture (TSS): architecture is the system of flows and capture; the revenue model is the charging-pattern design within it.
- Revenue model ≠ cash collection schedule or accounting revenue recognition policy.
- Revenue model ≠ a complete pricing strategy (discounts, fences, negotiation rules).
Related topics
None linked yet.
Related concepts & frameworks
Related Discover collections
Further research
No related resources yet.