Capabilities Team or Role Based Support: Which Fits?

A capabilities team gives you breadth: several people trained across many workflows, with work allocated as it arrives. Role based support gives you continuity: one named person in an ongoing role. The choice turns on whether your problem is a lot of varied work or one job that needs doing properly every day.

The question

Both models put people on your operational work and leave the function, the priorities and the approvals with you. What differs is how the capacity is shaped.

Getting this wrong is not expensive, because either can be changed. But starting with the right one means the first month is spent doing work rather than reorganising.

Option A: a capabilities team

A team dedicated to your business, trained across many of your documented workflows, with requests coordinated through one team lead and allocated to whoever is trained for them.

Works when

The work spans several functions and no single part of it justifies a hire
Volume is uneven, so capacity needs to move between workflows week to week
There is a long tail of small recurring tasks that nobody currently owns
Cover matters more than familiarity, because several people know each process
The processes are documented, or can be

Costs you

No single named person owns any one function, so there is nobody to build a long internal relationship with in the way an employee would
It depends on documentation. Work that lives only in someone's head cannot be allocated
Coordination sits with the team lead rather than with you, which is efficient but less direct
It is a poor fit for work needing continuous professional judgement

Option B: role based support

A named person focused on an ongoing role or function, recruited for the relevant experience and trained on your processes and systems.

Works when

One function has steady, predictable volume
Continuity matters: the same person, building knowledge of your business over time
The role needs particular experience, for example payroll or talent acquisition
The person needs to hold relationships inside your business, with managers or suppliers
The work involves judgement within a defined scope rather than pure execution

Costs you

Less flexible. Capacity is fixed to the role, so a quiet month is still paid for
Single point dependency, mitigated by cover but real
It only makes sense once the volume genuinely supports a role
Work outside the role's scope needs somewhere else to go

How to decide

Four questions, answered about your own firm:

Is the work one job or twenty small ones? Twenty small ones points to a capabilities team. One job points to a role.
Does the volume move? If it swings by more than about a third month to month, a team absorbs that better than a role does.
Is it written down anywhere? If not, a role is easier to start with, because one person can document as they learn. A team needs documentation to allocate against.
Does anyone need to know this person? If the work involves internal relationships or supplier conversations, that argues for a named role.

Most clients end up with both: a capabilities team across the long tail, and role based support in the one or two functions with the volume to justify it.

Where we would say hire instead

Neither model is right when the work is the capability you are trying to build in house. If you want a finance function that grows into a team you manage, with its own progression and succession, hire for it. We would be a stopgap, and you would be paying for a stopgap.

The same applies where the work is mostly judgement rather than execution: a controller, an HR business partner, a head of marketing. We staff the work underneath those roles, not the roles themselves.

And if the volume is genuinely small, one part time hire may simply be cheaper than either option. We will tell you if we think that is the case.

Related resources

What Is a Capabilities Team?

A team working across many documented workflows, coordinated through one team lead.

What Is Role Based Support?

A named person in an ongoing role, recruited for the experience the role needs.

Operations Support vs Hiring Internally

Cost, speed, cover and control, and the circumstances in which hiring directly is the better answer.

Not sure which shape your work needs?

Talk to us