Business Model

Origin & evolution

The phrase predates the formal frameworks, but the modern, structured version comes from Alexander Osterwalder. His 2004 PhD thesis under Yves Pigneur proposed a "business model ontology", a set of named building blocks that any model could be decomposed into. That ontology became the Business Model Canvas, popularised in Business Model Generation (Osterwalder and Pigneur, 2010). The canvas fixes nine blocks: customer segments, value propositions✨Value PropositionBusiness ModelA unique value offered to customersView reference →, channels, customer relationships🫶Customer RelationshipBusiness ModelA type of customer relationshipView reference →, revenue streams💵Revenue StreamBusiness ModelA source of revenueView reference →, key resources🏭Key ResourceBusiness ModelA key resource required by the businessView reference →, key activities🛠️Key ActivityBusiness ModelA key activity the business performsView reference →, key partnerships, and cost structure🧮Cost StructureBusiness ModelA cost category or structureView reference →.

The canvas earned its reach by being drawable on one page, which forced founders to see the whole machine and not just one favourite part of it. A common failure it exposed was the model that had a beautiful value proposition and no honest cost structure underneath it.

Two later refinements matter. Ash Maurya's Lean Canvas (2010) swapped four blocks for problem, solution🔧SolutionDiscoveryA proposed approach to address an opportunityView reference →, key metrics🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →, and unfair advantage, aimed at early-stage startups still searching for a model. And Osterwalder's own follow-up, Value Proposition Design (2014), zoomed into the single block most teams got wrong, pairing customer jobs🔨JobUserJob To Be Done: what the user is trying to accomplishView reference → and pains against the product's relievers and gain creators. The field settled on a layered view: the canvas is the map, and the value proposition is the part you stress-test first.

How it works in practice

A two-person team building a scheduling tool sketches a canvas. Value proposition: cut weekly rota admin from three hours to twenty minutes. Customer segment: independent café owners. Revenue stream: a flat subscription🔂SubscriptionSales & RevenueA recurring subscriptionView reference → at 29 GBP per month. Key activity: keeping the shift-swap engine reliable. Cost structure: two salaries plus hosting at roughly 4,000 GBP per month.

The numbers then do the arguing. At 29 GBP per month, the team needs🫀NeedUserA user need, pain, desire, or constraintView reference → about 140 paying cafés just to cover that 4,000, before any profit. That single line moves the founders from "do people like it?" to "can 140 cafés be reached and held?", which reshapes the channel block and the relationship block in the same sitting. The model has done its job: it turned an opinion into an arithmetic constraint🔒ConstraintStrategyA limit, requirement, or ceiling the product must respect, whether a self-imposed principle or an externally imposed boundaryView reference →.

Business model vs. its neighbours

• Value proposition is one block inside the business model: the specific benefit a segment is willing to pay for. The business model is the surrounding logic that turns that promise into sustainable money. You can have a strong value proposition inside a model that still does not pay for itself.
• Pricing strategy💱Pricing StrategyPricing & PackagingAn overarching pricing strategyView reference → sets the rules for what you charge and why. The business model decides whether charging at all is the right capture mechanism, or whether advertising, transaction fees, or a marketplace take rate fits better. Pricing operates one level down, once the capture mechanism is chosen.
• Revenue stream is the named source of incoming cash, such as a subscription or a one-off licence. The business model can hold several streams and weighs them against the cost structure. A revenue stream on its own says nothing about whether the business is viable.

In the graph

In the Unified Product Graph, business_model💰Business ModelBusiness ModelThe business model canvas or definition is the root of the Business, GTM and Growth region. The nine canvas blocks hang off it as hierarchy edges: business_model_delivers_value_propositionBusiness ModeldeliversValue Propositionhierarchy, business_model_earns_via_revenue_streamBusiness Modelearns viaRevenue Streamhierarchy, business_model_costs_via_cost_structureBusiness Modelcosts viaCost Structurehierarchy, and business_model_measured_by_unit_economicsBusiness Modelmeasured byUnit Economicshierarchy, among others. That structure makes the canvas queryable, so it stays a working artefact and does not decay into wall decoration. Because cost structure and unit economics💹Unit EconomicsBusiness ModelPer-unit economic metrics (CAC, LTV, etc.)View reference → are first-class children, a model that lists revenue but no costs is visibly incomplete, and the graph can flag the exact gap the one-page canvas was always meant to force.