Sell Systems, Not Time

The highest-leverage consultants are not necessarily the most expert. They are the ones who have encoded their expertise in something that works without them.

This is the distinction the previous two posts in this series have been building toward. First, we covered why static deliverables are a ceiling. Then, why replacing those deliverables with interfaces changes the client relationship. This post addresses the underlying business model shift: the difference between selling your time, selling a deliverable, and selling a system.

What a system actually is

A system, in this context, is reusable IP that generates value across multiple clients without requiring proportional input from you on each engagement.

It is not just a packaged service with a fixed price. A packaged service is still traded for time, even if the pricing no longer says so directly. The effort scales with the number of clients you take on.

A system breaks that relationship. One analyst can serve many clients because the intellectual labour has already been done and encoded. The client pays for access to the output of that encoding: a tool, a platform, a framework with software behind it, a methodology delivered through a structured interface rather than a human consultant reading from notes.

This is the form that the best consulting and advisory businesses have always aimed for. The tools to build it are now accessible to firms that are not McKinsey.

What the largest firms built first

McKinsey's product layer makes the pattern concrete. Over the past decade, QuantumBlack Labs has built a suite of software products from their consulting IP: OptimusAI for industrial plant efficiency, CustomerOne for customer value management, Value Maximizer for supply chain optimisation. These are not slide decks or frameworks. They are deployed software tools that clients access and operate. The consulting engagement produces and configures the tool; the tool then runs.

The most famous example of consulting IP becoming a global standard is Bain's Net Promoter Score. Fred Reichheld developed NPS from research into customer loyalty. It became the default framework for measuring customer experience across industries. Bain did not bill hourly for NPS. It became a credential, a standard, and a perpetual source of advisory relationships. The methodology outlasted every individual engagement it was built from.

BCG followed a similar path. BCG X, formerly BCG GAMMA, now employs more than 3,000 engineers, data scientists, and product designers who build technology alongside strategic advisory. The consulting firm and the product firm are the same firm.

The pattern is consistent: identify the intellectual work that gets repeated, encode it into something deployable, and sell access to the system rather than the hours it takes to operate it.

How smaller firms have done the same thing

This is not exclusive to global firms with thousands of staff. The mechanism scales down.

Traction on Demand, a Salesforce consulting firm, built custom tools for clients during engagements and realised they could retain the IP and sell those tools to other companies. The consulting project became the R&D cycle for a product. Each client engagement funded the development of something the firm could sell to the next ten clients without starting from scratch.

A design systems studio might spend an engagement building a component library for a client. If the client owns all the IP, the engagement ends and the knowledge walks out the door. If the studio retains a base layer of reusable components, each new engagement builds on top of a system rather than from scratch. The margin per engagement improves over time. The studio's differentiation compounds.

Blair Enns at Win Without Pitching documented this clearly: a training subscription he launched for $49-$99 per month generated net new revenue for ten years with no proportional effort increase. The methodology was encoded once. The revenue was recurring.

The structural shift in how you scope engagements

Selling systems changes how engagements begin, not just how they end.

When you sell time, the scoping question is: how many hours will this take? When you sell a deliverable, it is: what do we hand over at the end? When you sell a system, the question is: what part of this engagement produces something that will work for this client without my ongoing involvement, and could work for another client after that?

This reframes discovery. You are looking for the repeating problem: the diagnosis every new client in this sector needs, the model every finance team wants to run, the framework every growth team is trying to apply. If the same intellectual work keeps appearing across engagements, that is the system waiting to be built.

It also changes pricing. A system is not priced on the hours required to deploy it. It is priced on the value it delivers to the client over time. Outcome-based contracts, licences, and subscriptions all follow from this. McKinsey's 2025 figures showed 25% of global fees coming from outcome-based arrangements — a structure that requires an ongoing interface to track, measure, and demonstrate value. Static deliverables cannot support that pricing model. Systems can.

What this requires operationally

The shift is not just a commercial decision. It requires that your methodology be extractable.

Most consultants operate from tacit knowledge: the pattern recognition built over years of similar engagements, the intuition about which recommendations will land, the judgement calls made in the room. None of that transfers to a client automatically. Most of it does not make it into the deliverable either.

A system requires that knowledge to be made explicit. The model has to be documented. The decision logic has to be formalised. The process has to be structured so that a client can move through it without a consultant holding their hand at each step. This is uncomfortable work for people who have built their business on being the expert in the room. It is also the work that breaks the ceiling.

The firms that make this transition do not stop being expert. They become more expert, because the act of encoding a methodology forces clarity about what actually drives outcomes. Every ambiguity in the system is a place where the consulting work was not yet fully understood.

Forge's POV: deploy the system, not just the methodology

The operational challenge of selling systems is that the system needs somewhere to live. A framework in a Google Doc is not a system. A model in a spreadsheet that the client might accidentally break is not a system. A calculator the client bookmarks and returns to on their own terms, a portal they access when they need to run a new scenario, a tool their team uses independently: these are systems.

Forge's developer platform is designed to host exactly this kind of lightweight, client-facing web tool. Git-driven deployment means a new version of your system can go live in minutes. Branch-level previews mean you can test a change before a client sees it. The infrastructure required to turn your methodology into a hosted product is less complex than most consulting firms assume.

The shift from selling time to selling systems is ultimately a decision about what kind of business you are building. Time scales with headcount. Systems scale with the quality of the IP. The firms that have made this shift, at every size, have found that the second model is a more durable one.

If you are thinking about how to structure the first engagement that produces something reusable, the earlier posts in this series cover why your deliverable format may be the ceiling and what it looks like to ship an interface instead.