A B2B revenue model is the structure by which a company generates income from its business customers -- specifically, the mechanism by which the value delivered is translated into money received. The revenue model defines: what the customer pays for (access to a platform, units consumed, hours delivered, outputs produced), how they pay (subscription, usage-based billing, project fees, per-unit pricing), and when they pay (upfront, monthly, annually, on milestone completion). The revenue model is distinct from but closely related to the pricing model (which sets the specific price points within the revenue model structure).
Main B2B revenue model types
- Subscription / SaaS model: customers pay a recurring fee (monthly or annual) for ongoing access to a software platform or service. The subscription model has become the dominant B2B software revenue model because it aligns vendor incentives with customer success (the vendor only keeps the revenue if the customer continues to renew), creates predictable recurring revenue streams (ARR/MRR), and enables data-driven optimisation of the customer lifecycle. The key financial metrics for subscription businesses: monthly recurring revenue (MRR), annual recurring revenue (ARR), net revenue retention (NRR), customer acquisition cost (CAC), and lifetime value (LTV). In India, the subscription model is widely adopted by SaaS companies like Freshworks, Zoho, Chargebee, Leadsquared, and CleverTap.
- Usage-based / consumption model: customers pay based on how much they use the product -- the number of API calls made, the volume of data processed, the number of messages sent, the number of minutes of video transcribed, or any other measurable unit of consumption. Usage-based pricing has grown rapidly in B2B SaaS because it directly ties cost to value realised and reduces the barrier to initial adoption (low upfront commitment, pay as you grow). The trade-off is revenue unpredictability: a customer who uses less in a given month pays less, which can create revenue volatility. Many companies combine usage-based pricing with a minimum commit (a base subscription fee that covers a defined usage tier) to provide revenue floor predictability while retaining the flexibility of usage-based billing above the minimum.
- Transactional / project model: customers pay per transaction or per project delivered rather than through a recurring fee. This is the dominant model for professional services firms (consulting, implementation, staffing), agencies, and project-based software development. Transactional revenue is typically recognised as the work is completed (milestone-based billing) rather than in advance. The strengths of the transactional model: large upfront revenue per engagement, no recurring payment dependency; the weaknesses: revenue is lumpy and unpredictable, growth requires a constantly refilled project pipeline, and the economics do not benefit from compounding customer relationships in the same way that subscription models do.
- Outcome-based / performance model: customers pay based on the outcomes delivered by the vendor's product or service rather than on access to the platform or hours of service delivered. Examples: a B2B lead generation agency that charges per qualified meeting booked (rather than per hour of SDR time); a CRO agency that charges a percentage of the revenue uplift they generate; a staffing firm that charges a fee only when a hired candidate stays for 90+ days. Outcome-based pricing aligns vendor and customer incentives perfectly and is highly compelling for buyers who are uncertain about whether a vendor can deliver results -- but it is challenging for vendors to sustain because outcome measurement is often contested, outcomes are influenced by factors outside the vendor's control (e.g., the quality of the sales team that receives the leads), and the model may generate insufficient revenue to fund the delivery cost in early-stage engagements.
- Marketplace / platform model: the vendor operates a marketplace or platform through which two or more parties transact, and charges a take rate (a percentage of the transaction value) or a listing fee. B2B marketplace models are common in procurement, freight, financial services, and staffing. The marketplace model is highly scalable (the vendor does not bear the cost of providing the underlying goods or services being transacted) but requires achieving significant liquidity (enough buyers and sellers transacting through the platform) to generate meaningful revenue.
Hybrid revenue models
Most sophisticated B2B companies use hybrid revenue models that combine elements of multiple pure model types. Common hybrid structures: platform subscription + usage overage (a base subscription fee that includes a usage allowance; usage above the allowance is billed at a per-unit rate); software subscription + professional services (recurring platform fee plus project-based implementation, training, and consulting fees); SaaS + marketplace (a core software platform plus a marketplace of third-party integrations, apps, or data providers that generates take-rate revenue). Hybrid models allow companies to capture multiple value streams from the same customer relationship and to match the revenue structure to the specific value delivered in each component of the offer.
Frequently asked questions
- What is a B2B revenue model?
- A B2B revenue model is the structure that defines how a B2B company generates income from its business customers -- specifically, what customers pay for, how they pay, and when they pay. The revenue model is distinct from but closely related to the pricing model (which sets specific price points): the revenue model defines the structure (subscription vs. usage-based vs. project-based), while the pricing model fills in the specific numbers within that structure. The main B2B revenue model types are: (1) Subscription/SaaS: recurring monthly or annual fee for platform access. (2) Usage-based/consumption: fee per unit of product consumed (API calls, messages sent, data processed). (3) Transactional/project: fee per project or transaction delivered. (4) Outcome/performance: fee tied to specific results achieved. (5) Marketplace/platform: percentage of transactions facilitated through the platform. Most B2B companies use some combination of these models (a hybrid model), such as a base subscription fee plus usage-based billing above a defined tier. The choice of revenue model is one of the most consequential strategic decisions a B2B company makes because it shapes the sales motion (subscription companies sell annual contracts; project companies sell scopes of work), the financial profile (subscription companies have predictable MRR; project companies have lumpy project revenues), and the customer relationship dynamics (subscription companies must prove ongoing value to retain; project companies must constantly re-sell).
- What is the difference between SaaS revenue model and usage-based revenue model?
- The SaaS subscription model and the usage-based (consumption) model both appear frequently in B2B technology businesses but differ in a fundamental way: SaaS subscription model: the customer pays a fixed recurring fee (monthly or annual) for access to the software platform, regardless of how much they actually use it. The price is typically based on a seat count (number of users), a feature tier (Starter, Growth, Enterprise), or a contact/record count (CRM pricing based on number of contacts). The customer's cost is predictable and does not vary based on actual usage during the billing period. The vendor's revenue is highly predictable and grows when customers add seats, upgrade tiers, or expand to additional products. Usage-based model: the customer pays based on their actual consumption of a measurable unit -- API calls, data volume, messages, minutes, transactions. Usage-based pricing has no fixed cost floor (unless combined with a minimum commit); a customer who uses less pays less. The key distinctions in practice: Revenue predictability: SaaS subscription is more predictable (revenue is known for the contract period); usage-based is more variable (revenue depends on customer activity). Adoption barrier: usage-based pricing lowers the barrier to initial adoption (customers can start small without committing to a fixed fee); SaaS subscription requires upfront commitment to a tier. Alignment with value: usage-based pricing aligns cost with value consumed (customers who get more value pay more); subscription pricing requires that the fixed fee be perceived as fair value even in low-usage periods. The trend in B2B SaaS since 2020 has been toward usage-based or hybrid models (subscription floor plus usage overage), driven by customer preference for paying proportionally to the value they receive.
- How do you choose the right revenue model for a B2B business?
- Framework for choosing a B2B revenue model: (1) Map to value delivery type: if your product delivers value continuously over time (access to a platform, ongoing data, always-on infrastructure), a subscription model is the natural fit. If value is delivered in discrete units or transactions (an API call processed, a parcel shipped, a lead generated), a usage-based or transactional model fits better. If value is delivered in one-off projects (a website built, a market study completed, a software integration developed), a project-based model fits better. (2) Consider buyer risk tolerance: buyers with high risk tolerance and high certainty about their usage level will accept annual subscription commitments. Buyers with high uncertainty about whether the product will work for them (new category, new vendor) prefer usage-based or outcome-based pricing that lets them pay proportionally to value received before making a larger commitment. Early-stage products in new categories often benefit from usage-based or trial-then-subscribe models that reduce the adoption barrier. (3) Consider your unit economics: subscription models require significant upfront investment in customer acquisition before recurring revenue builds up (it takes 12-18 months of subscription revenue to recover a typical enterprise CAC). Usage-based models generate revenue immediately but may produce less predictable cash flow. Project models produce large upfront revenue but require constant pipeline replenishment. (4) Benchmark against the competitive landscape: buyers in established categories have expectations about how vendors charge (SaaS buyers expect subscription pricing; staffing buyers expect placement fees; consulting buyers expect project fees). Deviating significantly from the market norm requires a compelling justification. (5) Consider India-specific factors: in the Indian market, annual upfront subscription payments are common (to reduce payment friction and improve cash flow), discounts for annual vs. monthly billing are standard (typically 20-30% discount for annual), and rupee-denominated pricing with India-specific pricing tiers (typically 40-60% of global equivalent pricing) improves conversion in the SMB and mid-market segments.
Keep reading
- What is MRR? Monthly recurring revenue explained for B2B SaaS
- What is ARR? Annual recurring revenue meaning and how to calculate it
- B2B SaaS metrics benchmarks: the key metrics and what good looks like
- B2B pricing strategy: how to price a B2B product or service
- B2B expansion revenue: how to drive expansion revenue in B2B SaaS