Bench to Product
How services firms can systematically turn bench time and client-side learning into owned product IP without cannibalizing client work.
The paper.
Converting Services Capacity into Proprietary Software
15 min read
The full argument.
The bench problem
Every services firm has bench time. Consultants between engagements. Engineers waiting for the next project. The standard approach is to treat bench time as a cost: the firm tries to minimize it, to fill it, to reduce it. But bench time is also an opportunity. It is the only time the firm has to build something for itself. The question is how to convert that capacity into proprietary software assets without cannibalizing client work.
The client-side learning
The other input is client-side learning. Every client engagement generates insight: what problems exist in the market, what solutions work, what patterns repeat across industries. Most services firms let this learning dissipate. The consultants move to the next engagement, the insights stay in their heads, and the firm captures none of it. The firms that build products from services capture this learning systematically. They document the patterns, they identify the repeatable problems, and they build software that solves those problems once, for many clients.
The product thesis
A product built from services should solve a problem that the firm has seen repeatedly across clients. It should not be a custom solution for one client. It should be a generalized solution for a class of clients. The product should be something the firm can build, operate, and sell independently of its services business. It should have its own business unit, its own P&L, and its own team. If it does not have these things, it is not a product. It is an internal tool.
The cannibalization question
The fear is that a product will cannibalize services revenue: if the firm sells a product that solves a problem, clients will buy the product instead of the service. This fear is usually wrong. The product solves a different problem for a different buyer. The service is custom, high-touch, and expensive. The product is standardized, self-serve, and cheaper. The clients who buy the product were never going to buy the service. They were going to buy a competitor product or build nothing. The product expands the market, it does not cannibalize it.
The operating model
The product should be run as its own business unit with a General Manager who owns P&L. The team should be organized per-product, not centrally. Consultants can contribute to product builds during bench time, but the product team owns the roadmap, the quality, and the outcomes. The standard does not move with conditions.