Deal Mechanics

Business models & revenue models, explained

Two founders can both say "we're a marketplace" and mean completely different businesses once you ask how they actually make money. Business model and revenue model are separate questions — knowing both, and not confusing them, sharpens every pitch you evaluate.

Why these are two different questions


A business model describes how a company is structured to create and deliver value — who it connects, what role it plays between them. A revenue model describes the specific mechanism it uses to charge money. The same business model can pair with several different revenue models, and the same revenue model can sit inside several different business models — which is exactly why conflating the two leads to bad comparisons between deals.

Revenue models


Subscription

A recurring fee (monthly or annual) for ongoing access to a product or service, independent of how much it is actually used.

Read the deep dive →

Freemium

A free base tier available to everyone, with a paid tier unlocking premium features, higher capacity, or removing limits.

Read the deep dive →

Advertising

The core product is free to users; revenue comes from selling their attention or data-informed targeting to advertisers.

Read the deep dive →

Transaction / take-rate

A percentage cut of the value of each transaction flowing through the platform, so revenue scales directly with usage rather than being fixed.

Read the deep dive →

Usage-based / consumption

Customers pay per unit consumed — API calls, compute, deliveries, transactions processed — rather than a flat fee, aligning cost with value received.

Read the deep dive →

Asset-heavy build-operate

The company builds and owns physical assets (fleets, warehouses, energy infrastructure) and earns revenue operating them directly — far more capital-intensive than software-only models, but can create real barriers to entry.

Read the deep dive →

Exclusive / access-based

Charges for privileged access rather than a discrete feature set — exclusive deal flow, a premium community, or licensed proprietary content or data.

Read the deep dive →

Data monetization

Revenue from aggregating, anonymizing and licensing data generated through the core product — used carefully, given privacy and regulatory sensitivity around how that data was collected.

Read the deep dive →

How real companies combine both

Simplified and illustrative — real companies often layer several revenue models onto one business model, and mixes shift over time.

CompanyBusiness modelRevenue model(s)
MercadoLibreMarketplace + fintech/logistics platformTransaction take-rate, advertising, financial-services fees
RappiAggregatorTransaction take-rate, delivery fees, subscription (RappiPrime)
NubankPlatform (digital bank)Interchange fees, interest income, fee-based products
A typical B2B SaaS startupPlatform or D2C softwareSubscription, sometimes usage-based add-ons

Frequently asked questions

Can a company have more than one revenue model at once?
Yes, and most successful companies do — MercadoLibre, for example, combines transaction take-rates, advertising, and financial-services fees rather than relying on a single mechanism. Ask which revenue model actually drives the majority of revenue today, not just which ones exist in theory.
Which revenue model is "best" for an angel to back?
None universally — each has different risk and growth characteristics. Subscription and take-rate models tend to produce more predictable revenue; advertising and freemium depend heavily on reaching real scale; asset-heavy build-operate models need more capital but can be more defensible once established. Evaluate fit with the specific business, not a general ranking.
How does this relate to our sector guides?
Business and revenue models cut across every sector — a fintech, a SaaS company and a marketplace can all use a subscription revenue model, for instance. Use this page alongside our sector guides, not as a replacement for the sector-specific diligence questions covered there.
What is the difference between "platform" and "aggregator"?
A platform provides infrastructure others build on top of, generally without owning the end customer relationship for what gets built. An aggregator sits directly between suppliers and customers, owning the customer relationship and often the brand experience, even though it does not own the underlying supply — the distinction matters because it changes who has pricing power.