A consultancy turns its most popular engagement into three packages.
The scope becomes easier to explain. Sales can quote without waiting for a senior partner. Delivery follows a fixed sequence. A portal collects the inputs, templates produce the reports, and junior staff can handle more of the work.
The service is faster, cleaner, and more profitable on paper.
Then the exceptions begin. Clients complete the same intake form but mean different things by the answers. The standard recommendations fit the obvious cases and miss the consequential detail in the difficult ones. Senior people return late in the process to repair work that would have taken less effort to frame correctly at the start.
The company has successfully scaled the deliverable. It is less clear whether it has scaled the value.
Productizing a service can make expertise easier to buy and deliver. It can also remove diagnosis, adaptation, and judgment because those parts are harder to specify than a report, workshop, dashboard, or set of tasks. The danger is not standardization itself. It is standardizing the visible output before understanding what the customer was actually paying for.
Productization solves a real operating problem
Many services are difficult to sell because the customer cannot inspect the work before buying it. Scope is uncertain. Quality appears tied to particular people. Pricing requires a conversation. Delivery varies from one engagement to the next, and the business struggles to learn because every project seems unique.
Productization brings useful discipline to this problem. The firm can define the offer, make the process more tangible, establish quality controls, reuse knowledge, and reduce unnecessary variation. Research on professional-service firms describes productization as a set of practices that make abstract expertise more exchangeable, including specifying the offer, making expertise tangible, and systemizing processes.
This can improve the customer experience as much as the firm’s economics. Clear boundaries reduce uncertainty. A repeatable intake prevents basic information from being missed. Shared methods make quality less dependent on which employee happens to lead the work. Modular components can give customers a more appropriate service without requiring the provider to invent the whole engagement again.
The alternative is not charming craftsmanship. Uncontrolled customization can produce vague proposals, inconsistent work, poor margins, and a company that cannot grow without cloning its most experienced people.
The question is where the repeatability should live.
The deliverable is easier to see than the value
A service often produces something visible: an audit, legal document, strategy, design, implementation, diagnosis, or recommendation. That artifact matters. It may be the contractual output.
It is rarely the whole reason the customer pays.
Two firms can deliver reports with the same sections and create very different value. One notices that the apparent marketing problem begins in the product. One accepts the brief as written. One understands why the management team is avoiding a decision. One completes the requested analysis. One knows which evidence should change the recommendation and which detail is merely noise.
The difference sits in work that is difficult to package: framing, interpretation, challenge, sequencing, and judgment under incomplete information.
When a firm productizes around what is easiest to count, it can confuse the container with the service. The workshop becomes the product rather than the decision it is meant to improve. The dashboard becomes the product rather than the operating response it should support. The assessment becomes the product rather than the uncertainty it should reduce.
This is how a service keeps its professional appearance while becoming generic. The customer still receives the promised object. The object carries less understanding of the customer’s situation.
Standardization can delete information
Every service process filters information. An intake form asks some questions and excludes others. A fixed sequence decides what will be known before a recommendation is made. A package boundary determines which problems belong inside the engagement.
Good productization makes these choices deliberately. Weak productization treats anything that does not fit as inefficiency.
That is risky because variation is sometimes evidence. A customer who cannot answer the standard question may not be difficult; the question may contain the wrong assumption. A project that requires a different sequence may reveal that the visible problem begins somewhere else. An exception can expose a segment the service was never designed to serve, or a valuable need the firm has not yet named.
Customer participation matters especially in knowledge-intensive services. A study examining both provider and customer perspectives found that the production, delivery, and perceived value of these services depend heavily on customer participation. That does not mean the customer should manage the engagement. It means the service needs a designed way to absorb context that cannot be known in advance.
A rigid process often fails at this boundary. It either rejects useful variation or pushes the burden back onto the customer through longer forms, repeated explanations, and demands to translate a complex situation into the provider’s categories.
The firm gains internal consistency. The customer supplies the missing adaptation.
Modularity is more useful than uniformity
The choice is not between a bespoke service and an identical service for everyone.
Modularity offers a better model. Stable components can carry the repeatable work: data collection, project administration, baseline analysis, documentation, quality checks, and common implementation steps. Other components can change according to the customer’s situation. A small number of clear modules can preserve variety without letting every project become an invention.
Recent service research describes modularity as a structure that can support value co-creation while also warning that fragmented modules can limit customization and professional autonomy. The design challenge is therefore not to create the largest menu of modules. It is to decide which variation matters to the result and where judgment must connect the parts.
This changes the role of senior expertise. Experienced people do not need to perform every routine task. Their value may be greatest at the points where the service is framed, an exception is interpreted, a trade-off is made, or the standard path should be abandoned.
Removing experts from repetitive production can improve the service. Removing them from consequential decisions merely makes the work cheaper to reproduce.
Automation makes the boundary more important
AI is increasing the amount of professional work that can be standardized, searched, drafted, checked, and routed. The commercial pressure to redesign services around that capacity is understandable.
The 2026 Thomson Reuters survey of more than 1,500 professionals found AI use becoming embedded in legal, tax, accounting, risk, and government work, while firms were still working through changes to workflows, roles, billing, and business models. This is not simply a productivity question. If technology changes which tasks require scarce expertise, it also changes what the client should be paying for.
A firm can respond by hiding the efficiency and continuing to sell the old unit of effort. It can pass every saving to the customer and turn expertise into a commodity. Or it can redesign the service around a more accurate division of value.
Routine production can become faster. Evidence gathering can become broader. Quality checks can become more consistent. Experts can spend more time on ambiguity, negotiation, judgment, and decisions that carry consequence.
That outcome is not automatic. If the firm automates the visible task and leaves the underlying service model untouched, it may produce more deliverables while learning less about whether they help.
Test what the service is scaling
A productization review should begin with the customer outcome, then move backward into the service architecture.
What must be true for the engagement to be useful? Which decisions depend on context? Where does customer participation improve the result, and where does it merely compensate for the provider’s process? Which elements benefit from consistency? Which exceptions reveal something the firm should learn? Where can a module absorb meaningful variation? When does a person need enough authority to change the path?
The economics need the same treatment. Faster delivery is valuable only if rework, escalation, and customer disappointment do not rise elsewhere. A higher gross margin can hide senior rescue work. More predictable scope can be offset by weaker retention or price pressure if the offer becomes easier to compare and harder to distinguish.
Aalto University research on knowledge-intensive business services frames productization as a balance between efficiency and customer orientation, not a synonym for standardization. That distinction is practical. It keeps the firm from measuring success only by how closely delivery follows the designed process.
The process is a means. The service still has to understand enough of the customer’s reality to create the result.
Productization should make valuable expertise easier to access, apply, and trust. If it only makes the output easier to reproduce, the company may scale the least important part of what it knows.
