Talented Team, Fragile Delivery: Why Salesforce Consultancies Need Process, Not Just Talent
A few weeks into a recent subcontract with a boutique, under-ten-person Salesforce consultancy, the pattern became obvious. The team were genuinely excellent, sharp, hard-working, technically strong. But every project was being delivered on the back of that talent, not on anything the business had built to make results repeatable. Good outcomes happening in spite of the system, not because of one. Occasionally, that gap showed up as cost overruns.
Good outcomes happening in spite of the system
This is a more common pattern than most consultancies would like to admit, particularly at the boutique end of the market. A small, talented team can carry a business a long way on ability alone, client relationships held together by a couple of key people, delivery timelines held together by whoever's most senior in the room that week. It works. Right up until it doesn't.
It holds together until someone's off sick. Until scope creeps on a project and nobody has a scoping standard to point back to. Until the business tries to bring in offshore delivery capacity and discovers that most of what makes the team effective was never written down, it was just known, by the people who'd been there long enough to know it.
That's when the cost overruns start. Not because the work got harder. Because the thing making it consistent, institutional memory, walked out the door or didn't scale.
Having spent decades in production management before Salesforce, this is a pattern I know well. It's the classic difference between a business that runs on process and one that runs on people compensating for the absence of process. Both can produce good results. Only one produces them consistently, and only one can be scaled or handed over without everything wobbling.
Building the system behind the team
When I see this pattern, I don't start by questioning the team's ability, that's rarely the issue. I start by looking at what's actually repeatable versus what's being reinvented, or held together by memory, on every single project.
Define the delivery process. Pre-sales through workshops, UAT, feedback loops and handover, mapped out properly. This does two jobs at once: it gives the internal team something to follow instead of relying on whoever's most experienced being in the room, and, condensed to a single slide, it gives prospective clients a clear picture of what to expect before they've even signed. Clients trust a process they can see.
Set delivery standards. This is where the detail lives, and where most consultancies are weakest. Naming conventions, right down to individual fields and flow elements. Error handling requirements. How sprints get scoped, by level of effort rather than gut feel. A consistent way that user stories, acceptance criteria and implementation solutions get written, scoped, handed over and tested, whether the person doing the work is sitting in the office or delivering offshore. Standards like these are what let you scale a team without diluting the quality that made the original team good.
Standardise the collateral. Sales decks, training decks, client documentation. The instinct in a small, busy consultancy is to rebuild these from scratch every time because there's never a quiet moment to do it properly. Built once and reused properly, they save real hours on every subsequent project and pitch, and they make the business look as consistent to prospective clients as it should feel to work with.
Where it's landing
Some of this is being rolled out now, and it's early days. But it's already changing how consistently a very talented team can deliver, without needing quite so many heroics to get there.
If this sounds like your consultancy
If you're running a small, capable Salesforce practice and you recognise this, great delivery, but delivery that depends on who's available rather than what's documented, it's usually a solvable problem, and rarely one that requires slowing the team down to fix. It's exactly the kind of engagement I take on alongside delivery work. Happy to talk it through.

Comments