I’ve interacted with hundreds of consultancies over the years – dozens of them were my clients; with others, I had in-depth conversations to understand better their pain points, goals, business models, value propositions, and mindsets.
This has allowed me to take a step back and look at the macro image – the paths different consultancies take and the decisions that significantly improve their chances of success in growing their boutique consultancy.
In the past few years, I have written extensively about what my highly successful clients have started doing. In this article, I’d like to elaborate on standardising and productising consulting services.
Consultancy firms and their founders/owners are highly client-oriented. And that makes sense, of course. That's pretty much a given in the service business.
However, many consultancies take this to mean that to secure and retain a client, they always have to offer highly customised services that, like window insulating foam, fill in every nook and cranny of a business process.
And that's why they say yes to most client requests and get drawn into doing work they've never done before, a draining and unsustainable approach in the long run.
Here's why.
Before I dive into the benefits of packaging consulting services, I'd like to clarify what I mean by packaging services or productisation in consulting.
There are many definitions, but most focus on the productisation of online services, and that’s a different space than consulting work. So here's how I define a packaged or productised consulting service.
"A productized service in consulting refers to a standardized offering where specific solutions are packaged and priced in a predefined manner. While tailored to address common challenges within a specific expertise domain, it streamlines the consulting process by setting clear parameters, deliverables, and pricing. This approach combines the consistency of a product with the expertise of consulting, ensuring both efficiency and value delivery."
My vision is rather extreme: I would never do fully customised projects as a small or medium-sized boutique consultancy. Seriously! The consultancy can maybe do additional customisation on top of a standardised approach, but that's about it.
Here’s why. As experts, consultancies have gathered tremendous experiences in their narrow expertise domain all those years, leading to incredible depth, compelling pattern recognition, and proprietary data and benchmarks.
Designing standardised approaches to solve the prototypical pains of ideal clients is remarkably uncomplicated. And if a consultancy can’t standardise it for 80-90%, they can carry out several well-defined sprints and execute them systematically. It’s more straightforward than most consulting leaders and owners believe.
Most consulting leaders I meet seem allergic to standardisation; they consider it as 'not doing real consulting'. Which is nonsense, of course. Maybe even quite naive. Sorry to say.
However, consultancies will most likely struggle to' sell' standardised approaches without focusing on a specific expertise domain and without a visible reputation (or authority) in the market. And that's why they don't get started—the vicious loop to gross margin hell.
Clients will challenge the consultancy, and it won’t be difficult to respond to their objections credibly. Focus, yes, please! As I explained in one of my articles, put all the eggs in one basket!
Recommended reading: Why Repetition Is the Path to Becoming a High-Performance Consultancy
Recommended reading: Why Hiring To Scale Is a Losing Battle for Mid-sized Consultancies
"Luk, the idea of standardising our services seems impractical. Every client we serve is unique, and they seek us out for a tailored approach that caters to their distinct requirements."
This sentiment resonates with many. "Won't a standardised service deter clients who are wary of generic solutions?"
Let me clarify a misconception: expertise in a narrow specialisation domain often reveals that while clients' contexts and business scenarios vary, their core issues are strikingly similar. These issues invariably trace back to a handful of fundamental pain points. If these pain points remain elusive to a consultancy, it's an indication that there's more depth to be explored in its domain.
"We must reimagine and redraft our offerings as solution sets; constellations of benefits designed to solve real-world business and marketing problems for our clients". (Tim Williams, professional services pricing expert)
Packaging consulting services aren't about delivering a carbon-copy solution to every client. Instead, it's about defining the scope of a consultancy's expertise – outlining what it's capable of, how its consultants approach a problem, and most crucially, which challenges the firm is adept at overcoming for its clients.
While the framework remains consistent, the application is always tailored. Consultancies are not just addressing a generic problem but diving deep into their client's unique business landscape. However, they do so with crystal-clear boundaries: defining the methodologies employed, the data benchmarks, the tools leveraged, the expected timelines, and drawing parallels with outcomes from analogous projects.
This approach ensures clarity, transparency, and a promise of delivering value – all while retaining the essence of contextual customisation.
I've written an article on Vertical Service Integration with two case studies of boutique consultancies (pitching and winning against the big firms all the time) who have packaged their expertise to the highest possible degree but are working with clients in totally different contexts. Why were they able to systematically productise (standardise)? Because (that's what they keep repeating to me) the core issues they face are strikingly similar in all their client organisations.
Here's what I always answered clients when I got challenged on customisation versus standardisation: 'We are using our proven methodology and we tailor this to your specific context'. I never got in trouble, I hardly ever got difficult reactions or questions.
It's building trust at a double level:
How to switch to a packaged service model
I need to be honest with consultancies here. Out of the blue, it won’t be easy to suggest a new way of (standardised) working for consultancies that have been working in a customised manner with their clients. Their existing clients will have difficulties understanding and accepting the change.
But consulting firms don’t have to jump off a cliff – there’s a way to do it gradually. And for new clients, there’s no problem, of course.
Here are a few suggestions on how consultancies can start delivering a more standardised approach:
Recommended reading: How Consultancies Can Get Started With Value Proposition Design (Without Getting Overwhelmed)
Never sell self-developed software tools as a consultancy.
I know, another black-and-white point of view. Why? Because most of the initiatives I've witnessed in the past decade have failed (I'd say 95%). Both in big consulting firms and boutique consultancies.
A while ago, a consultancy owner explained at a conference that they were selling their clients licenses of the tool they had developed. They developed the software tool in the past years to improve a specific consulting service's quality, speed, value, and pricing.
It was their way to productise their expertise. Well done! I love that.
But about a year ago, they started selling user licenses for this tool to their existing clients. I consider this a big (and naive) mistake.
Why?
As I've seen many times, they quickly lost 2 important clients who used the consultancy's (productized) service in the past. They are now using the tool and told the consultancy they will do most of the work - previously done by the consultancy - themselves.
The price of the license, that's what I was afraid of, was way too low to compensate for the client's loss.
The consultancy owner asked for my advice. My answer is relatively straightforward: there are only 2 approaches that can lead to success:
The consultancy uses the self-developed tool as its productized consulting approach and, with the help of the tool, delivers higher quality consulting faster, better, and at a fixed (high-end) price.
It's a perfect way to scale a consultancy's expertise and revenue. On top of that, it's helping the consultancy grow non-linearly, uncoupling revenue growth from linear headcount increase.
The consultancy builds a product 'the startup way', and they stop consulting with it.
Suppose a consultancy believes it can make money by scaling such a product. In that case, it will need to hire developers, build a tech stack, hire a product development expert, build a sales team, maybe even get investment money (or a bank loan), etc., to scale the product and sell a few 1000s rapidly.
As my good friend and consulting marketing expert Florian Heinrichs would say, by doing so, the consultancy is leaving 'the consulting category'.
Building, validating, selling, and scaling a product 'the startup way' is a totally different space for any consultancy, with different expertise, capabilities, and business models.
Never get into selling a few licenses to please or impress a few existing clients to use your clever software. If a consultancy decides to do so, it gives away years of expertise without the proper return. Even if you sell 100 licenses, they will most likely never compensate for the long-term consulting revenue.
You either do productised consulting with it (better, bigger, faster, more value, better data/benchmarks, more expensive), or you scale it the startup way (selling 1000s of licenses in the next 10 years to come).
It's either/or.
Don’t do something in between because it will cannibalise the consultancy's premium value consulting work and erode its reputation as experts in the market.
Halfway doesn't cut It. The Achilles' heel? Project management. Without uniformity here, we're just kidding ourselves.
Here’s the hard truth: project management is often a wild card. Each project manager has his/her playbook, leading to wildly varying deliveries. It’s like being promised a smooth flight only to find every pilot navigating their own route. The result? A service that's about as 'productized' from A to Z as a jigsaw puzzle with missing pieces.
Clients sign up expecting a seamless, proven methodology. If there's inconsistency in the final delivery due to non-standardized project management, it's the wrench in our productization gears.
If we're serious about true productization, the focus should be crystal clear: uniform project management is non-negotiable. It's an integral part of a productization and standardization approach.
Only then can we deliver the proven methodology we promise. Anything less, and we're just paying lip service to the concept of productization.
Being a consultancy leader can be an exciting and rewarding profession. I know it was and still is for me.
Unfortunately, I encounter too many consultancy founders, partners and leaders who feel overwhelmed, overburdened, and overworked. They struggle with a work-life balance, fear missing out on opportunities, and don’t see consistent business growth.
It’s time to re-evaluate the consultancy's approach to working with clients when that happens. Working in this chaotic, unpredictable, overburdening manner should scare consulting leaders more than the prospect of changing their business model toward more productisation or standardisation.
Consulting owners need to start doing less. It will force them to prioritise what they do and how they do it, to choose quality over quantity, and to strive to maximise the value their firms deliver for each client instead of maximising the number of clients.
Standardising consulting services is an essential element of the consulting business approach that I advocate. Still, it will only work if a boutique consultancy starts to understand and accept that full customisation of their consultancy projects is a road to trouble and profit erosion.
Unless a boutique consultancy can charge 2x or 3x more for it (which is exceptional), full customisation of every consultancy project is not what I would recommend (yes, that's me).
Recommended reading: [Case Study] Why Offering Too Many Services Destroyed This Boutique Consultancy
Interested in receiving all my learnings to build a better consultancy?
Subscribe to my newsletter.