Key Resource

Origin & evolution

The block appears in Business Model Generation (2010) by Alexander Osterwalder and Yves Pigneur, sitting beside Key Activities🛠️Key ActivityBusiness ModelA key activity the business performsView reference → on the efficiency side of the canvas. Osterwalder and Pigneur grouped resources into four types: physical (factories, vehicles, retail networks), intellectual (brands, patents, proprietary data, customer databases), human (the people a knowledge or creative business runs on), and financial (cash, credit lines, the capital a model needs to operate). A resource can be owned, leased, or supplied by a partner, and the block records which.

The deeper theory underneath the block predates it by decades. The resource-based view of the firm holds that a company's durable advantage comes from the resources it controls, not from the market position it occupies. Edith Penrose laid the groundwork in The Theory of the Growth of the Firm (1959), framing a firm as a bundle of productive resources. Birger Wernerfelt named the view in A Resource-Based View of the Firm (1984). Jay Barney gave it its sharpest test in Firm Resources and Sustained Competitive Advantage (Journal of Management, 1991), arguing that a resource confers lasting advantage only when it is valuable, rare, imperfectly imitable, and not substitutable, the VRIN criteria.

That theory is why the Key Resource block carries more weight than its modest size suggests. The canvas asks you to list the resources the model needs. Barney's framework asks the harder follow-up: of those, which are rare and hard to copy, and which could any funded competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → acquire next quarter. A model resting only on easily acquired resources has a cost structure🧮Cost StructureBusiness ModelA cost category or structureView reference → with no moat behind it.

How it works in practice

A medical-imaging startup lists its key resources. Physical: a cluster of GPUs for training. Human: a team of radiologists who label scans. Financial: an eighteen-month runway. Intellectual: a dataset of two million annotated scans and a regulatory clearance for its diagnostic model.

Running the VRIN test sorts the list. The GPUs are valuable but neither rare nor hard to imitate; a competitor rents the same hardware by the hour. The runway is the same for anyone who raised a similar round. The labelled dataset and the clearance pass all four criteria: valuable, rare, slow and expensive to imitate, and without close substitute, because a rival cannot buy two million annotated scans or shortcut a regulator. The founders steer the model accordingly, treating the dataset as the asset to protect and compound, labelling as the engine that feeds it, and the GPUs as a commodity to optimise for cost. The canvas shows the list; the resource-based view tells them which line on it is the business.

Key Resource vs. its neighbours

• Key Activity is what the business does; Key Resource is what it does it with. The annotated dataset is a resource; labelling scans is the activity that builds it. The canvas links them because the two only create value in tandem: a resource no activity uses is idle, and an activity with no resource behind it cannot run.
• Value Proposition is the value delivered to the customer; Key Resource is the asset that makes that delivery possible. The block exists to surface the dependency⛓️DependencyTeam & OrganisationA cross-team or system dependencyView reference →, so a team can see which resource the whole proposition rests on.
• Capability💪CapabilityStrategyAn ability that enables value deliveryView reference → is an organisational know-how, a learned ability to do something well. A Key Resource is an asset the firm holds. The two are easy to blur: a patent is a resource, while the team's skill at inventing patentable things is a capability. Resources can often be bought; the capability to use them well usually has to be grown.

In the graph

In the Unified Product Graph, Key Resource sits in the business-model region and attaches to its model through business_model_requires_key_resourceBusiness ModelrequiresKey Resourcehierarchy. Its reason for existing is fixed by key_resource_enables_value_propositionKey ResourceenablesValue Propositioncross-domain, the link that says a resource earns the word "key" by being something the proposition cannot be delivered without. It connects to the work that uses it through key_activity_uses_key_resourceKey ActivityusesKey Resourcecross-domain, and to externally supplied assets through partnership_provides_key_resourcePartnershipprovidesKey Resourcecross-domain, which records the resources a model rents from partners rather than owning. The structure matters because it lets the resource-based view run as a query: trace which resources enable the value proposition, then ask which of those a competitor could acquire, and the model's real moat stops being a story and becomes a path through the graph.