Consulting splits into two camps. The vertical specialist who speaks your industry’s dialect. The horizontal generalist who speaks none of them. The operator who wins hires neither.
Camp one: the specialist
The dominant consulting model right now: pick a vertical, learn its language, sell to that vertical. The HVAC consultant. The dental practice consultant. The law firm growth consultant. Ten years inside one industry, speaks the dialect on day one, and the prospect feels understood within the first five minutes of the conversation.
This works for transactional buying. The operator wants someone who already knows the lingo. They don’t want to spend the first three meetings explaining what a SEER rating is, or how dispatch boards work, or why their P&L looks different from a retail business. The vertical specialist arrives knowing all of it.
That’s the real strength of the niche-down playbook. It’s a moat against competition. If you’re the HVAC consultant and a generalist tries to compete with you, you win every transactional sale on familiarity alone.
The blind spot is what comes next. The vertical specialist has seen the symptom a hundred times. They’ve also seen the same wrong fix a hundred times, because everyone in their network is solving the same problem the same way. Pattern recognition turns into pattern repetition. The “this is how HVAC businesses solve X” answer becomes locked in, not because it’s the best fix, but because it’s the fix the network of HVAC consultants converged on years ago.
The operator who hires this consultant gets the well-known fix, fast. They don’t get the operationally correct fix, because the consultant’s lens has narrowed to one industry’s playbook.
Camp two: the generalist
The opposite pole is the “we help small businesses grow” consultant. The “AI for any company” generalist. The cross-industry practitioner who can name what’s broken at a structural level but doesn’t know how your shop floor, intake desk, or dispatch board actually runs day to day.
This consultant brings the right principles. They can talk about workflow design, data discipline, sequencing fixes correctly, when to automate and when not to. The principles are real. The principles work.
But they don’t know your industry. Which means the principles get applied with broad strokes. Light depth. The recommendations come out somewhere between “implement a CRM” (true but generic) and “improve your processes” (true but useless). The operator walks away with a deck full of principles they already half-believed and no idea how to translate them into their specific shop.
The opposite blind spot from camp one. Pattern recognition without specific recognition. The generalist can describe the structural shape of the problem accurately but can’t operate inside the operator’s actual environment to put fingers on the specific places the structure breaks.
If you’re the operator, hiring camp two feels like getting an MBA lecture instead of an actionable fix. The lecture might be technically correct. It doesn’t move what matters next Tuesday.
The third path
The third path is the operator who’s lived inside enough different operational contexts to pull patterns across them. Not a specialist, not a generalist. Someone who’s been in the back shop, the intake desk, the dispatch board, the sales funnel, and the finance dashboard of multiple businesses across different industries, and who can recognize the same operational structure showing up in three different costumes.
This isn’t “I’ve worked with lots of companies.” It’s “I’ve sat with the office manager of a manufacturing shop, the receptionist of a service business, and the inside salesperson of a retail operation, all of whom are managing the same underlying intake-to-handoff problem, and I can show how the fix that works in one of them translates to the other two.”
The credential here isn’t industry depth. It’s operational depth across enough industries that the structure under the symptom stops being industry-specific.
That posture is harder to credential. There’s no certification. Nobody puts “I’ve worked across enough industries to recognize patterns” on their LinkedIn header. The way to prove it is with concrete examples that hold up under probing: analogies between industries that come with specifics on both sides, not hand-waved principles.
Three analogies that pull weight
Three cross-industry patterns I look for in every assessment. Each has concrete examples from both sides, which is the bar that separates real cross-pollination from generalist hand-waving.
Manufacturing’s QC mindset applied to a service business’s intake desk.
In manufacturing, quality control catches defects before they leave the floor. The discipline is straightforward: every part gets inspected at the seams between operations. Defects caught early cost a fraction of what they cost when they reach the customer.
That same discipline applied to a service business’s customer intake catches dropped leads that would otherwise die in the gap between marketing and sales. The “leads that come in” is the parts coming off the line. The “leads that get worked” is the parts that pass QC. The gap between those two numbers is the operational leak the service business has been ignoring because they don’t think of intake as a quality-control problem. They should.
Print-farm batching applied to a law firm’s document workflow.
In a print farm, you don’t run small jobs one at a time. You batch them, run identical setups together, and amortize the setup cost across the batch. The discipline is: identify the duplicated work nobody flagged as duplicated, batch it, eliminate the redundant setup.
A law firm’s document workflow has the same shape. Multiple drafts, multiple reviews, multiple sign-offs, often on similar document classes that nobody groups together. The batching logic from print operations compresses three sequential review passes on three similar documents into one pass across all three. The lawyers don’t think of their workflow that way because law firm playbooks don’t talk about batching. Once you see it through the print-farm lens, the duplication is obvious.
ERP scoping discipline scaled from 500-person factories down to 12-person shops.
Enterprise resource planning was built for large manufacturing organizations. Vendors sell ERP packages designed for that scale. They don’t sell it well to a 12-person shop, because the 12-person shop can’t absorb the implementation cost or the change-management overhead.
The discipline behind ERP is straightforward: single source of truth for inventory, work-in-progress, and production schedule. That discipline applies cleanly to a 12-person shop. The implementation doesn’t. Cross-pollination here means scoping the discipline down to what a small shop can actually run. The production meeting goes from three printouts and a whiteboard to one dashboard everyone can see. Vendors don’t offer it because their products are built for the wrong scale.
Why this is the harder posture
The bar to pull this off is real. Every cross-industry analogy needs concrete examples from both sides. Hand-wave once and credibility evaporates. The operator on the other side of the table can tell instantly whether you actually know the industries you’re pulling from, or whether you’re using “cross-industry thinking” as cover for not knowing any of them deeply.
This is the trap that gives camp two its bad reputation. “I help businesses across industries” used as license to skip the specifics. The right version of cross-pollination doesn’t skip specifics. It adds them, on both sides of every comparison.
The way to verify a cross-pollinator from a generalist with good vocabulary: probe one of the analogies. Ask for a specific manufacturing QC scenario. Ask what print-farm batching actually looked like in practice. The cross-pollinator has the second-side details ready because they earned them. The generalist freezes or hand-waves.
The specialist sees your industry. The generalist sees nothing. The cross-pollinator sees the structure under the symptom.