What is a builder-operator firm? (And why traditional consulting is broken)
The phrase “builder-operator firm” doesn't show up in McKinsey's glossary. You won't find it on Wikipedia. The reason isn't that the model is fringe — three of the most quietly successful firms in mid-market services fit the description. The reason is that the model exists in the gap between three categories that consulting's self-description has carved up for the last forty years: traditional consulting, venture studios, and freelance marketplaces.
What follows is a working definition, a head-to-head comparison, and an honest read on when this kind of firm is the right fit and when it isn't. If you're an owner trying to decide whether your next engagement should go to a Big-4 deck shop, a venture studio, a freelance marketplace, or a firm that does what we do — this is the piece I wish someone had handed me ten years ago.
A working definition
A builder-operator firm is a professional-services business that does three things, on purpose, in the same engagement:
- 1. Advises. Strategy, operations, technology decisions, hiring plans, acquisition diligence — the substance of a traditional consulting engagement.
- 2. Builds. Software, integrations, AI systems, dashboards, operational frameworks that survive the engagement and continue producing value. Working code, not specifications.
- 3. Operates. One or more of the firm's own businesses. Not slide-deck case studies. Companies with real customers, real revenue, and the same category of operational pain the firm helps clients solve.
Most professional-services firms do one of these three things. A few do two. The builder-operator model insists on all three, in the same engagement, with the same team. The third leg — operating a real business — is what makes the first two leg credible.
Why the third leg matters
A consulting firm that has never operated a business at scale can't tell you what dispatch chaos at 12 trucks feels like, or what a 30% customer-acquisition-cost spike does to a 14-person services company's payroll math. They can describe it from interviews. They can model it. But they have not personally been on the receiving end of a Monday morning where two service technicians no-call-no-show and a customer is on hold while a dispatcher tries to reroute a route.
The same applies to building software. A consulting firm that has never deployed AI to production for a real customer can describe the failure modes in theory. They cannot tell you what it's like at 2 AM when a hallucination causes a customer-facing chat to confidently cite a price that doesn't exist, and there is no incident response runbook because nobody writing the McKinsey deck has ever shipped to prod. The builder-operator model bakes those scars into the advice.
That's the third-leg test: when a builder-operator firm advises a client, the advice is informed by the firm's own running businesses, not by what looked good in last year's research report. The firm is eating its own cooking, in public, every day. If the cooking poisons the firm, the firm has the same problem the client has. That alignment of consequence is the model's defining feature.
Head-to-head: builder-operator vs. four common alternatives
The fastest way to disambiguate the model is to put it next to the four things it gets confused with: traditional consulting, venture studios, freelance marketplaces, and systems integrators.
| Model | What you buy | Pricing | Risk to client |
|---|---|---|---|
| Traditional consulting | Strategy + recommendations + decks | Hourly / retainer | Implementation is the client's problem |
| Venture studio | Co-built company w/ shared equity | Equity-heavy, often dilutive | Misaligned timeline; studio thesis dominates |
| Freelance marketplace | Discrete tasks completed by 1 person | Hourly, low rates, narrow scope | No system view; quality variance is enormous |
| Systems integrator | Vendor-product implementation | Hourly + product license markup | Vendor-locked; advice biased toward installed product |
| Builder-operator | Working systems + operational change | Fixed-fee per phase, milestone-gated | Engagement scope must be honestly defined up front |
The fifth row is what we are. The pricing model — fixed-fee per phase with milestones — is the operational tell. Hourly billing creates a perverse incentive to bill more hours; fixed-fee per phase creates a perverse incentive to scope honestly up front, because once the SOW is signed, the firm carries the overrun risk. That alignment is what makes builder-operator firms livable for owners who've been burned by open-ended consulting engagements.
Why the traditional consulting model breaks (for owners, not for firms)
The traditional consulting model is not broken for the consulting firms. They run the highest gross margins in professional services and have for forty years. The model is broken for many of their clients — particularly mid-market operators — for three structural reasons.
1. The handoff problem.A traditional engagement ends with a written recommendation. The client's internal team — who didn't write the recommendation — has to translate it into operational change. The expertise that produced the recommendation walks out the door at the engagement's close. Six months later, the deck sits in SharePoint and the operational change has half-happened.
2. The leverage problem. Consulting firms maximize margin by running engagements with a small senior team that scopes the work and a much larger junior bench that executes it. The owner who scoped the engagement on Monday isn't in the room on Wednesday when the senior team has rotated to the next pitch and a 25-year-old analyst is interviewing the operations director. The owner believes he's buying senior advice; he's buying a senior brand wrapped around a junior delivery layer.
3. The deliverable problem. The deliverable a traditional firm ships is a written artifact. The deliverable a business owner needs is operational change. These are not the same thing, and pretending they are is the original sin of the model. Builder-operator firms close that gap by treating the operational change as the deliverable, with the written artifact as a byproduct.
What “operating” actually means in practice
A builder-operator firm doesn't just say it operates businesses. The operating side has to be a real, functioning, revenue- generating set of companies — not a slide-deck case study, not an internal pet project, not a defunct logo on the about page.
In MSG's case, that means three companies — MFGBase (a global procurement marketplace for manufacturers), LocalAISource (an AI professional directory), and ServiceStorm (a CRM/FSM and marketing platform for home-service businesses) — each of which has paying customers, a real product roadmap, and the same operational complexity our consulting clients face. When we advise an oil-and-gas operator on integrating SCADA with production accounting, we're drawing on the integration work we did for our own platforms last quarter. When we tell a home-service company how to scale dispatch beyond five trucks, we're drawing on the dispatch logic we wrote into ServiceStorm. The advice is grounded in code we've shipped, not white papers we've written.
When a builder-operator firm is the right fit
The model fits owners who share three characteristics. First, they run a business in the $5M–$100M revenue range — enough to need real engineering and operational rigor, small enough that the founder is still in the room for big decisions. Second, they have hit a ceiling that more headcount won't break through — a systems problem, an integration problem, an operational-discipline problem, or a transformation that requires both technology and process change. Third, they are willing to act on the changes, not just review them.
The model does not fit Fortune 500 RFPs (those need a Big-4-style firm with a 50-person bench and procurement compliance), and it does not fit pure-research engagements (those are an academic exercise, not what we do). It also doesn't fit owners looking for a deck — there are firms that will sell you a deck. We aren't one of them.
Why now
The builder-operator model has been theoretically possible for decades. What changed in the last three years is the unit economics. AI-assisted engineering means a small senior team can ship production systems that previously required a ten-person consulting bench. Cloud infrastructure means the firm can deploy to the client's environment without a six-month migration project. SaaS APIs mean integrations that used to take half a year take six weeks. The same forces that are commoditizing pure-research consulting — and putting pressure on the freelance-marketplace tier from below — are making builder-operator firms newly viable for small senior teams. The model existed before. It's becoming more common because the math finally works.
The honest tradeoffs
The builder-operator model isn't free of tradeoffs. The biggest one: the firm has to scope honestly up front, because once the SOW is signed, the firm carries the overrun risk on a fixed-fee engagement. That means the discovery process is heavier than what most clients are used to from a traditional consulting firm. It also means the firm will sometimes turn down work — “we don't think we can deliver this in this scope at this price” — that an hourly-billing firm would happily accept. From a client's perspective, that scrutiny is a feature, but it can feel like friction in the sales cycle.
Second tradeoff: builder-operator firms tend to be small. There's no way to have a 50-person consulting bench AND operate three real businesses AND maintain senior-team-only delivery. The firms that try to scale the model past about 25 people tend to drift back toward traditional consulting economics, because those economics are what allow consulting firms to scale. That's why most builder-operator firms stay small on purpose. If your requirement is “a firm with 200 consultants on call,” we're not it. That's a Big-4 ask.
What this means for owners shopping engagements
If you're evaluating a consulting firm right now, three questions cut through the marketing copy faster than anything else:
- 1. What does the firm itself operate? Not what they advised on — what do theyrun? If the answer is “nothing,” the third leg is missing.
- 2.Will the team that scopes my engagement also be the team that builds it? If the answer involves a junior bench picking up after the senior team rotates out, you're buying a brand wrapper.
- 3.Is the engagement fixed-fee with milestones, or is it hourly? Hourly billing aligns the firm's incentive with billing more hours. Fixed-fee aligns the firm's incentive with shipping the work.
Three questions, three minutes, more clarity than reading a hundred-page proposal. If a firm flunks all three, you're looking at traditional consulting in builder-operator clothing. If a firm passes all three, you're probably looking at the real thing.
That's the model. We didn't invent it — we just gave it a name we could point at when an owner asks what kind of firm we are. We aren't a Big-4 in miniature. We aren't a venture studio looking for our next bet. We aren't a freelance marketplace. We're a small senior team that builds working systems for clients while operating real businesses of our own — and the second part is what makes the first part work.
If that sounds like the kind of partner your business needs, the next step is a 30-minute discovery call. We listen first, then tell you whether the problem is one we can solve and what it takes. If we're not a fit, we'll say so — and point you to someone who is.
Karl Gillihan is the founder of Manufacturing Solutions Group, a builder- operator firm based in Beaumont, Texas. Reach him at readyto@buildwithmsg.com.