Core competency framework
Definition
Core competency framework
A core competency framework is a way of deciding which capabilities your firm keeps and which it can buy. It scores each capability on how distinctive it is and how much value it creates. The unit of analysis is the firm, not the person.
Readers mix this up with a competency framework constantly, and the two are not variants of one idea. That one is about people: the skills and behaviours expected in a role. This one is about the firm.
Same word, different unit of analysis. Confusing them causes a real mistake — outsourcing a capability because no individual is currently good at it, when the capability itself is the reason customers pay you.
Key takeaways
- A core competency framework asks what the firm should do itself, before any sourcing choice.
- It is about capabilities, not about the skills expected of individual employees.
- Two tests decide it: is the capability hard to copy, and do customers pay for it?
- The framework decides whether to buy at all; negotiation only starts once that answer is yes.
How it works
You test each capability against two questions: can rivals copy it easily, and do customers actually pay for it? The answers sort your capabilities into four groups, and each group gets a different sourcing decision.
| Capability type | Hard to copy? | Customers pay for it? | Sourcing decision |
|---|---|---|---|
| Core | Yes | Yes | Keep and invest |
| Enabling | No | Yes | Partner, keep the design |
| Supporting | No | No | Buy from the market |
| Legacy | Yes | No | Fix, retire or sell |
The grid only works if the capability is described honestly. “Customer service” is too broad to place; “resolving billing disputes within one contact” is specific enough to test, and it is the level at which a sourcing decision can be made.
Scoring is a judgement, not a calculation. Put the two questions to a group that includes operations, finance and someone facing the customer — a capability rated core by only its own department is usually not core.
One warning about the grid. Capabilities you are simply bad at will look cheap to hand over, but weakness and irrelevance are not the same thing, and a weak core capability needs investment instead.
Two strategy layers feed it. Corporate level strategy says which markets you are in, and business level strategy says how you win in each one. A capability is core only relative to those answers.
The output is a sourcing map. Supporting work becomes non-core outsourcing, enabling work becomes strategic outsourcing with tighter governance, and core work stays with people who report to you.
Public bodies draw a version of this line in law. The Federal Acquisition Regulation requires that inherently governmental functions are not performed by contractors, which settles part of the answer before any commercial analysis begins.
Appraisal discipline keeps the exercise honest. HM Treasury’s Green Book, the United Kingdom’s guidance on appraisal, describes assessing the costs, benefits and risks of options rather than defending a preferred answer.
Examples
The test reads differently by sector, but the shape holds. Three cases show it: a retail bank, a mid market retailer, and a software firm deciding what to do with its first line of customer support.
A retail bank keeps credit risk modelling because the model is the product and regulators hold the bank accountable for it. Statement printing and card fulfilment go to specialists, where scale, not distinctiveness, sets the price.
A retailer keeps buying and assortment planning, because choosing what to sell is the firm’s judgment. Warehousing and last mile delivery are bought, since two competitors using the same carrier still compete on what sits in the basket.
A software firm keeps product design and second line engineering support. First line triage is outsourced to a provider in Manila — where the sector has decades of voice and chat experience — with escalation paths back into engineering.
That last case is where teams most often slip. The reason to keep second line support is not that it is technical; it is that the fixes feed back into the roadmap, and that loop is hard for a rival to copy.
Public bodies face the same sorting task with a narrower menu. A statutory duty cannot be handed over, so the analysis starts from what the law already reserves and works outward to the support functions around it.
Related terms
These terms surround the framework without replacing it. Each names either a sourcing outcome the framework produces or a planning artefact it consumes, so the distinction is usually about whether it decides something or records something.
- Strategic outsourcing: buying enabling capability under close governance rather than at arm’s length.
- Non-core outsourcing: buying supporting work that creates no competitive difference.
- Business level strategy: how a unit wins in its chosen market, which sets what counts as core.
- Business capability map: the inventory of what the firm can do, before any scoring happens.
- Core outsourcing: the deliberate and rarer choice to place distinctive work with a partner.
FAQ
What is the difference between a core competency framework and a competency framework?
A core competency framework is about the firm and asks which capabilities are distinctive enough to keep. A competency framework is about people and lists the skills expected in a role.
How do you identify a core competency?
Test whether rivals can copy it quickly and whether customers pay a premium because you have it. A capability that fails either test is a candidate for the market. Ask the two questions about the capability, not about the team currently running it.
Does the framework tell you what to pay a supplier?
No. It decides whether to buy at all. Price, risk and exit terms are settled afterwards by a negotiation strategy, once the sourcing answer is already yes, so keep the two decisions separate in your governance.
Can a core competency stop being core?
Yes, and it usually does so quietly. When a capability becomes standard across the sector, it drops into supporting work and should be tested again rather than defended out of habit. Payroll processing made that journey decades ago.
How granular should each capability be?
Granular enough that one team could own it and one supplier could quote for it. If neither is true, the description is still too broad.
Once you know what to keep and what to hand over, compare vetted specialists in the Outsource Accelerator directory.







Independent




