Boutique consultancies usually grow in one of two ways: add more people (hiring), or add more repeatability (productising what you already do). “Which is better?” sounds like a binary choice, but in practice it’s a sequencing problem.
Here’s a practical way to compare consulting productisation vs hiring—and decide what to do first.
Start with the real constraint: capacity or leverage?
Hiring increases capacity. Productisation increases leverage.
- Hiring: You buy more delivery bandwidth. Revenue can grow, but only by adding billable hours and managing more roles.
- Productisation: You keep your delivery bandwidth stable while reducing how much time is spent on non-differentiating work (questioning, intake, structuring, summarising, first drafts).
If your current bottleneck is “we can’t take enough clients,” hiring can look like the fastest fix. If your bottleneck is “every project is different, so delivery takes too long,” productisation usually wins.
The hiring model: fast to start, expensive to sustain
Hiring tends to work well at the beginning because the process is mostly manual and senior-led.
But hiring introduces several compounding costs:
-
Onboarding time New consultants need training, shadowing, and calibration. That time is not billable.
-
Quality drift Even with templates, interpretations vary. You end up re-reviewing more work to keep outputs consistent.
-
Manager bandwidth More people means more coordination. Managers spend time routing decisions rather than improving the system.
-
Revenue-per-person caps Eventually, your pricing power is limited by how much skilled attention you can allocate.
Hiring can scale revenue—but it scales it through cost. Your growth curve follows headcount.
The productisation model: slower at first, smoother later
Productisation is not “make a deck and call it a product.” It’s turning your proven methodology into a repeatable system.
In consulting, that typically means capturing:
- the question sequence you ask (and why)
- the branching logic (what you do differently depending on the client’s answers)
- the interpretation rules you apply using your case knowledge
- the output structure clients value (what goes into the report, what changes by scenario)
When you productise well, you don’t remove expertise—you encode it.
The benefits show up in operations:
-
Lower time per client Routine steps become faster because they’re guided, not reinvented.
-
More consistent outputs The “method” drives quality, not the mood or availability of a specific person.
-
Better utilisation of senior expertise Seniors can focus on the parts that really require judgment, while the system handles the structured groundwork.
-
Scalability without proportional coordination When delivery is systematic, you spend less energy managing variation.
Productisation can feel slow because you’re building the system once. But once it’s live, it scales across clients without multiplying the number of people involved in delivery.
Where the comparison gets interesting: decision points
Instead of asking “productisation or hiring?”, ask three sharper questions.
1) How much of your delivery time is “structured work” vs “interpretation work”?
If most of the time is structured (intake, questioning, synthesising inputs, generating drafts), productisation often delivers immediate leverage.
If most of the time is unstructured (high-touch facilitation, ongoing advisory, custom stakeholder negotiation), hiring may still be necessary—or you’ll productise only parts of the workflow.
2) Can you describe your methodology as a trail?
Productisation works when your work can be expressed as a sequence of steps with branching outcomes.
If you can’t articulate the pattern you follow, hiring might be the more honest path initially. You’ll need to make your methodology explicit before automation can help.
3) What happens when throughput increases by 20–30%?
If your quality drops or delivery times jump, you likely need productisation (or at least a delivery redesign).
If quality stays strong and constraints are purely manpower, hiring might be the next step.
A common winning strategy: productise first, then hire from a stronger base
For many firms, the best sequence looks like this:
- Productise the repeatable core of your engagement (intake → guided assessment → structured report).
- Measure output consistency and time-to-delivery with real client data.
- Hire to expand coverage, not to compensate for missing process.
In other words: use productisation to stabilise quality and speed up delivery, then hire to increase demand capture and market reach.
This approach also makes recruiting easier. New team members understand the system they’re operating in, and senior time can be reserved for higher-judgment tasks.
How Kitra fits into this decision
Kitra is built for consulting teams that want to turn their expertise into scalable guided assessments—so you can expand delivery capacity without treating every client as a bespoke starting point.
With Kitra, consultants encode their question sequence and interpretation logic into structured “assessment trails,” and the system gathers responses and produces personalised reports.
If you want to explore the productisation route, start here: how Kitra works.
Practical takeaway
- Choose hiring when the bottleneck is pure capacity and your delivery is already consistent.
- Choose productisation when delivery variability and manual structuring slow you down or degrade output quality.
- Combine both by productising first, then hiring to scale demand and coverage from a stable delivery engine.
If you’re unsure where your time is going, map one engagement end-to-end and label each step as structured vs interpretation-heavy. That simple audit usually makes the answer obvious.