A business capability model describes what an organization does — its abilities — independent of how it's organized or which tools it uses. "Manage customer relationships" is a capability; the CRM and the sales team are how that capability is delivered today.
Why capabilities, not processes or tools
Org charts change with every reorg. Tools change every renewal. Capabilities are stable — they're the durable layer you can plan against. A capability model lets you ask "where do we invest?" without getting lost in this quarter's structure.
How to build one
- Start at the top level — 10–20 capabilities that span the whole business.
- Decompose only where decisions require it; resist the urge to model everything.
- Map tools, teams, and spend to each capability to reveal over- and under-investment.
What it unlocks
Capability heat-mapping shows where friction concentrates, where redundant investment exists, and which abilities are single-threaded through one person or one tool — exactly the signals that matter in diligence and in growth planning.