The business model canvas
A business model is the logic by which an organisation creates, delivers, and captures value. It answers a single hard question that most product plans skip: once the product works, where does the money come from, and does it cost less to make than someone will pay for it? The tension is that a product can be loved and still lose money on every customer, so the business model is the artefact that has to stay honest about both halves at once.
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 propositionsValue PropositionBusiness ModelA unique value offered to customersView reference →, channels, customer relationshipsCustomer RelationshipBusiness ModelA type of customer relationshipView reference →, revenue streamsRevenue StreamBusiness ModelA source of revenueView reference →, key resourcesKey ResourceBusiness ModelA key resource required by the businessView reference →, key activitiesKey ActivityBusiness ModelA key activity the business performsView reference →, key partnerships, and cost structureCost 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, solutionSolutionDiscoveryA proposed approach to address an opportunityView reference →, key metricsMetricStrategyA 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 jobsJobUserJob 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.
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 subscriptionSubscriptionSales & 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 needsNeedUserA 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 constraintConstraintStrategyA constraint entityView reference →.
In the Unified Product Graph, 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_modelBusiness ModeldeliversValue Propositionhierarchy, business_model_delivers_value_propositionBusiness Modelearns viaRevenue Streamhierarchy, business_model_earns_via_revenue_streamBusiness Modelcosts viaCost Structurehierarchy, and business_model_costs_via_cost_structureBusiness 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 economicsUnit 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.business_model_measured_by_unit_economics
Type-specific fields on BaseNode
framework_idstringFramework ID (references `UPGFramework.id`)
stagestringMaturity
patternstringCanonical pattern. Useful for benchmarking against peer businesses with the same shape.
monetisation_basisstringPrimary monetisation unit
north_star_metricstringThe single metric the business optimises for
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases — initial: drafted
12 edge types connected to this entity.
product_monetised_via_business_modelbusiness_model_delivers_value_propositionbusiness_model_earns_via_revenue_streambusiness_model_costs_via_cost_structurebusiness_model_measured_by_unit_economicsbusiness_model_partnered_via_partnershipbusiness_model_requires_key_resourcebusiness_model_performs_key_activitybusiness_model_maintains_customer_relationshipbusiness_model_reaches_via_distribution_channelbusiness_model_targets_market_segmentbusiness_model_distributes_via_distribution_channel