A prospect told me last month, fairly directly, that they were nervous about hiring "a one-person shop" for a VCF deployment touching twelve production clusters across two data centers. It's a reasonable concern. I'd share it too, if that's actually what boutique meant.
It isn't — and the distinction is worth walking through in detail, because the assumption behind that nervousness is wrong in a specific, identifiable way.
The Assumption Behind the Objection
When people hear "boutique" applied to infrastructure consulting, they tend to picture a smaller, lower-capability version of a large systems integrator. Fewer people, less bench depth, more exposure if something goes wrong at an inconvenient hour. That mental model makes sense if your only reference point for "small" is a side practice running off a templated website.
That's not what a senior-only boutique practice is. It's not a miniature SI. The difference isn't headcount — it's the number of people standing between the person who actually understands your environment and the person picking up the phone when you call.
What the Org Chart Actually Looks Like at Scale
I spent years on the other side of this chain earlier in my career, so I can describe it honestly. A pre-sales architect — genuinely sharp, usually — does discovery, writes the proposal, and closes the deal. That person then moves to the next sale, because that's what their billable hours are supposed to be doing. A delivery lead picks up the engagement and staffs it from whoever's available on the bench that quarter. The engineers actually running the SDDC Manager bring-up, configuring NSX-T, wiring up vSAN, are frequently meeting your environment for the first time the week the project kicks off.
When something doesn't match the design document — and something always doesn't — the question works its way up through a project manager before it reaches anyone with the context to actually answer it.
The firm had eleven engineers on that account. Eleven. And not one of them could explain a decision their own company had made two years earlier.
I watched this play out directly on an NSX-T remediation at a previous employer. The client's environment had two application tiers sharing a transport zone that should have been split — a leftover from a deployment two years prior. Three different engineers, across three separate calls, gave three different explanations for why it was built that way. Not because anyone was being dishonest. Nobody on those calls had been present for the original build, and the as-built documentation captured the result, not the reasoning behind it. The firm had eleven engineers staffed on that account. None of them could answer the question, because the knowledge that mattered had left the building along with whoever made the original decision.
That's not a staffing shortage. It's a structural feature of how leverage-based consulting works — the knowledge that matters lives with whoever happened to be in the room at the time, and that person is rarely in the room by the time you actually need them.
What Senior-Only Actually Removes
A boutique, senior-only model isn't a smaller version of that chain. It's the absence of the chain.
There's no pre-sales architect handing off to a delivery team, because the person scoping the engagement is the person executing it. There's no escalation path through a project manager, because there's nobody between you and the engineer who wrote your low-level design. When something doesn't match what was planned — a vSAN hardware compatibility surprise, a network team that pushes back on a VLAN allocation mid-deployment, a vendor firmware update that breaks an assumption baked into the design two weeks earlier — the person making the call on how to handle it is the same person who understood the original design intent. There's no telephone game, because there's no second party for the message to pass through.
- The as-built matches the deployment. The person writing it is the person who did the work — not someone compiling secondhand notes at the end of the engagement, weeks after the details have gone fuzzy.
- Status calls answer questions instead of deferring them. "We'll circle back on that" is what you hear when the person on the call doesn't have the context to answer. In a senior-only model, that context never left the room.
- Continuity survives the calendar. The engineer on your kickoff call is the engineer on your go-live call, six months later, because there's no roster to rotate.
What Boutique Doesn't Mean
To be fair to the original objection, there are real limits worth naming. A solo, senior-only practice isn't the right fit for every engagement. A multi-site rollout running in parallel across a dozen locations on a hard go-live date genuinely needs more hands than one person has — and a practice that pretends otherwise to win the deal isn't doing the client any favors. Engagements that scale past one person's reasonable capacity should bring in vetted, senior-level contractor support, named explicitly in the SOW, not quietly staffed with whoever happens to be available.
Boutique also doesn't mean cheaper by default, or faster by default. It means something more specific: the depth of the person you spoke with during scoping is the same depth executing the deployment. That's the actual trade you're making, and it's worth being precise about it instead of leaning on "boutique" as a vague selling point that means whatever the listener wants it to mean.
Whether you're evaluating a large SI or a boutique practice, the diagnostic question doesn't change: who specifically is doing the work, and what happens to your environment's institutional knowledge the day that person isn't available anymore?
At a large firm, the honest answer is often "it depends who's staffed that week." At a properly run boutique practice, the honest answer should be a name — and that name shouldn't change between your first call and your last one.
When I say McSherry Tech operates as a senior-only practice, here's what that means in concrete terms: I scope the work, I design the environment, I run the bring-up, I write the as-built, and I'm on every status call. There's no handoff, because there's no second person to hand anything off to. That's not a positioning line — it's just how the practice is structured, and it's the model that actually fits the kind of work a VCF engagement demands.