Revenue Model Design
The architecture of how a business earns money. Tiers, metrics, packaging, and expansion mechanics designed to scale with the company and capture more of the value it creates.
In one paragraph
Revenue model design is the architecture of how a business earns money: what to charge, on what unit, in what packages, with what expansion mechanics, and how it all evolves as the company scales. Crescendo designs revenue models for software, AI, services, marketplaces, and platforms across subscription, usage-based, hybrid, and outcome-based structures. Past work includes models for Cloudflare, AppFolio, Loom, HeyGen, PlanetScale, Triple Whale, and 130+ others.
When to engage Crescendo
Learn more
Companies often think of pricing as a single number on a pricing page. Revenue model design is the broader system that sits behind that number: the value metric (what unit you charge on), the packaging logic (which features sit in which tier), the expansion mechanics (how spending grows as customers grow), and the deal-desk policies (how you handle exceptions, discounts, multi-year deals).
Model design has to anticipate the company's next decade. A model that works at $5M ARR almost always breaks at $50M, and one that works at $50M usually breaks at $500M. Good revenue model design builds in the levers (tier structure, expansion variables, packaging cadence) that let the model evolve without ripping it out and starting over.
Common revenue model archetypes Crescendo designs: pure subscription (SaaS tiers), usage-based (consumption pricing), hybrid (subscription floor + usage overage), marketplace take rates (commission on transaction value), platform fees (developer ecosystems), and outcome-based (pay for delivered value). The right one depends on how customers experience and quantify the value the product creates.
1. Diagnose the current model
Where is it leaking value? Where does it create friction in the sales cycle? Where does it constrain expansion? Quantify each gap.
2. Map value creation to value metrics
Identify the unit that best tracks customer-perceived value: seats, usage, outcomes, GMV, transactions. The metric becomes the spine of the model.
3. Design tier and packaging structure
Which features sit in which tier. Where the price jumps. How tiers fence each other. Tested against segment willingness-to-pay so each tier captures its segment cleanly.
4. Build expansion mechanics
How does spending grow as customers grow? Auto-expansion, usage overages, seat tiers, add-on modules. Designs that tie revenue to customer success.
5. Stress-test the financials
Multi-scenario forecasts. What happens to NRR, LTV, gross margin, and EBITDA under different adoption curves? The model has to work under pessimistic cases, not just the plan.
Pricing is the number. Revenue model design is the structure: the metric, tiers, packaging, expansion logic, and deal-desk policies that determine how the company earns revenue across customers and time. Most companies need help with the model, not just the number.
Depends on how the customer experiences value. Subscription works when value is access-based. Usage-based works when value scales linearly with consumption. Hybrid works when there's a baseline of access plus variable value on top, which is most modern AI and infrastructure products.
A value metric is the unit you charge on: seats, GB, API calls, transactions, GMV, outcomes. The right value metric makes the rest of the revenue model design easy: pricing scales naturally with value, expansion happens without sales effort, and customers don't feel penalized for using the product.
Substantive redesign every 18-36 months on average for high-growth companies. Smaller adjustments (price points, tier additions, packaging tweaks) more frequently. The mistake is leaving a model that worked at the prior stage in place too long.
Both. Redesign work tends to be more common; most engagements are with companies that have an existing model that's beginning to show its age.
