Two companies sell the same thing at the same price in the same town, and one quietly out-earns the other for a decade. Outside-in strategy, five forces, market trends, the competitor matrix, struggles to explain that gap, because the inputs look identical. The resource-based view (RBV) explains it by looking inside the firm, at the resources and capabilities one company has and the other can't buy off the shelf.

The quick version

  • The resource-based view says lasting advantage comes from what a firm owns and can do, not just the market it sits in. Resources that are unevenly spread and hard to copy are the engine of profit.
  • VRIO is the four-question test for whether a resource actually creates durable advantage: is it Valuable, Rare, costly to Imitate, and is the firm Organised to exploit it? Miss any one and the advantage weakens or never lands.
  • Core competencies (Prahalad & Hamel) are the deep, cross-cutting skills that spawn many products, the "roots," not the "fruit." They're a way of finding the resources VRIO then tests.
  • The honest caveat: it's easy to use these tools backwards, to flatter whatever you already have. Done well they're a discipline; done lazily they're a horoscope.

The idea in depth: why some advantages stick

The resource-based view grew out of one observation: firms in the same industry, facing the same forces, earn persistently different returns. Birger Wernerfelt's 1984 paper A Resource-Based View of the Firm (Strategic Management Journal, 5(2):171–180) proposed analysing a company "from the resource side rather than from the product side", treating its bundle of assets, skills and routines as the real unit of strategy. Where you compete (the product-market choice) follows from what you have, not the other way round.

Jay Barney sharpened this into a testable theory. His 1991 article Firm Resources and Sustained Competitive Advantage (Journal of Management, 17(1):99–120) argued that resources only create sustained advantage when they meet four conditions, originally VRIN: valuable, rare, imperfectly imitable, and non-substitutable. The logic is almost arithmetical. A resource has to be valuable (it raises revenue or cuts cost) or it's irrelevant. It has to be rare, or every rival has it and it's just the price of entry. It has to be hard to imitate or substitute, or any edge gets competed away the moment it shows up in your results.

So the move is: stop benchmarking only against what rivals do and start auditing what you own. List the handful of resources behind your best margins, a proprietary dataset, a 20-year supplier relationship, a hiring brand that lands talent rivals can't, and ask, bluntly, which of them a well-funded competitor could replicate inside a year. The ones they can't are your real strategy. Everything else is table stakes.

From VRIN to VRIO: the bit most people skip

By 1995 Barney had reframed the test as VRIO, swapping the non-substitutability check for a question that turns out to be where most advantages die: Organisation. In Looking Inside for Competitive Advantage (Academy of Management Executive, 9(4):49–61), he made the point that a firm can hold a valuable, rare, inimitable resource and still capture nothing from it, because its structure, incentives, culture or processes aren't set up to exploit it. The resource is necessary; the organisation around it is what converts potential into profit.

That single letter is the most practical part of the whole framework. Plenty of companies sit on a genuinely scarce asset, Kodak and the digital camera it invented is the textbook case, and watch someone else monetise it because their own systems were built to defend the old business.

flowchart TD
  A(["A resource or capability"]) --> V{"Valuable?"}
  V -- No --> X1(["Competitive disadvantage"])
  V -- Yes --> R{"Rare?"}
  R -- No --> X2(["Competitive parity"])
  R -- Yes --> I{"Costly to imitate?"}
  I -- No --> X3(["Temporary advantage"])
  I -- Yes --> O{"Organised to exploit it?"}
  O -- No --> X4(["Advantage left on the table"])
  O -- Yes --> X5(["Sustained competitive advantage"])
The VRIO decision flow: an advantage is only as strong as its weakest answer. Leaders Loop

Where the advantage actually comes from

If rare resources are so valuable, why can't rivals just buy them? Ingemar Dierickx and Karel Cool answered this in Asset Stock Accumulation and Sustainability of Competitive Advantage (Management Science, 1989, 35(12):1504–1511). The strongest resources, they argued, are accumulated over time, not acquired in a market, a reputation, a base of customer trust, an engineering culture. These come with "time-compression diseconomies": you can't buy ten years of brand trust by spending ten years' budget in one quarter. The history is the moat. That's also why the second strand of this toolkit, core competencies, matters, it tells you what to accumulate.

C.K. Prahalad and Gary Hamel made that case in The Core Competence of the Corporation (Harvard Business Review, May–June 1990, 68(3):79–91). Their metaphor is a tree: end products are the leaves and fruit, but the core competence is the root system, "the collective learning in the organisation, especially how to coordinate diverse production skills and integrate multiple streams of technologies." A genuine core competence, they said, passes three tests: it opens access to many markets, it makes a real difference to the customer's perceived benefit, and it's hard for competitors to imitate. Their canonical example was Honda's deep competence in engines and powertrains, which let it compete across cars, motorcycles, generators and lawnmowers from one root.

So the move is: name the two or three things your organisation is deeply, unusually good at underneath its products, the capability, not the SKU. Then ask whether your roadmap is feeding those roots or just harvesting fruit. If every project sits on a different capability, you may have a portfolio of products and no core competence at all.

The honest limitation. RBV has a real and well-aired weakness: it can be tautological. Richard Priem and John Butler made the charge directly in Is the Resource-Based "View" a Useful Perspective for Strategic Management Research? (Academy of Management Review, 2001, 26(1):22–40). The trap: we observe that a firm wins, conclude its resources must be "valuable and rare," and call it strategy, when really we've just relabelled the outcome. "Value," they point out, is set by the market, not by the resource itself, so the framework can't tell you in advance what to invest in. Treat VRIO as a hypothesis to test against evidence, not a verdict you reverse-engineer from last year's profit, and the critique loses most of its bite.

A worked example: two coffee roasters

The figures below are illustrative, chosen to show the method rather than to report a real company.

Imagine two regional coffee roasters, each turning over about £6m. Northbeam competes on a slick app and aggressive discounting. Casswell & Pike looks sleepier, no app, full prices, yet earns a roughly 14% operating margin to Northbeam's 4%, year after year. Run both through VRIO.

Northbeam's app is valuable but not rare (every rival has one) and cheap to imitate, so it buys parity, not advantage. Its discounting is valuable to customers but trivially copyable, so it just compresses everyone's margins. Northbeam is busy and advantage-free.

Casswell & Pike's edge is quieter. Over fifteen years it has built direct relationships with a dozen smallholder farms and a roasting team whose palate and process are tacit, written nowhere, lived in people. That's valuable (it commands a premium), rare (those farm relationships are exclusive), and costly to imitate (you can't compress fifteen years of trust into a procurement drive, exactly Dierickx and Cool's point). The "O" is the clincher: the firm is organised around it, sourcing, training and brand all reinforce the same root competence, "relationship-led specialty sourcing." Strip out any single VRIO letter and the margin gap closes. That's the test working as a diagnosis, not a horoscope.

flowchart LR
  C(["Core competence:
relationship-led sourcing"]) --> P1(["Single-origin retail bags"])
  C --> P2(["Wholesale to cafés"])
  C --> P3(["Subscription club"])
  C --> P4(["Barista training arm"])
Prahalad & Hamel's tree, applied: one root competence feeds several product "branches." Leaders Loop

Frequently asked questions

Is the resource-based view the opposite of Porter's Five Forces?

They're complementary lenses, not rivals. Porter looks outside-in at industry structure; RBV looks inside-out at the firm's resources. A complete strategy needs both, an attractive market you can't defend is a trap, and a strong capability in a doomed market is a sunk cost. Pair this with Porter's Five Forces rather than choosing between them.

What's the difference between a resource and a capability?

A resource is something you have, a patent, a brand, a cash pile, a location. A capability is something you can do repeatedly, ship reliably, learn fast, integrate acquisitions well. Capabilities are usually harder to copy because they're embedded in routines and people, which is why they tend to score higher on the "costly to imitate" test.

How is VRIO different from a SWOT analysis?

SWOT lists strengths; VRIO grades them. A SWOT might call your "experienced team" a strength and stop there. VRIO asks whether that experience is rare, hard to imitate and actually organised into results, turning a flattering list into a ranked one. Many teams run VRIO on the "S" column of their SWOT to find which strengths are real advantages.

How often should we redo this?

Resource value is set by the market, so it decays as the market shifts (the Priem & Butler point). A resource that was rare and valuable can become parity once rivals catch up or technology moves. Revisit your VRIO audit when something structural changes, a new entrant, a platform shift, a regulation, rather than on a fixed annual calendar.

Can a small company really have a core competence?

Yes, and often more clearly than a big one, because focus is forced on it. A two-person studio can have a genuinely rare, hard-to-imitate capability. The risk for small firms isn't lacking a competence, it's failing the "O," because the systems to exploit it (hiring, pricing, repeatable delivery) haven't been built yet.

Related in the Toolkit

Where to go next