A customer asks for a modification. The sales team sees a larger opportunity. Engineering believes the change is feasible. The business agrees to customise the product and secures the contract.
Then another customer requests a different configuration. A third needs a special interface. A fourth requires a service arrangement that does not fit the existing model. Revenue grows, but engineering workload, procurement complexity, documentation and support obligations grow with it.
The company may be winning contracts while slowly losing the economics of its business.
Customisation is not inherently bad. The strategic problem is failing to distinguish valuable variation from variation that creates a different product or operating model every time.
The contract is not the full economic result
A bespoke requirement can carry a premium price and still be unattractive. The real economics include engineering hours, testing, supplier changes, production interruptions, inventory complexity, documentation, service training and future maintenance.
Some of these costs are visible before the contract is signed. Others appear later, when a customer requests a revision or the business must support several product variants in parallel.
If the sales team evaluates an opportunity on contract value while operations and engineering absorb the complexity, the business can mistake revenue growth for economic progress.
Separate three kinds of variation
Configurable variation uses a defined set of options within an architecture designed to support them. It gives customers choice without requiring a fundamentally different product each time.
Reusable engineering variation involves a new capability or module that can be used across several customers or applications. It creates an initial development cost but may expand the product platform.
Customer-specific variation is built for one customer and is unlikely to be reusable. It may still be worthwhile, but it should be priced and governed as a distinct investment or project rather than quietly absorbed into standard delivery.
The distinction helps leaders decide which requests to standardise, which to develop and which to decline.
Create a commercial gate for custom work
Before accepting a variation, examine its strategic fit, expected contribution, delivery effort, reuse potential, ownership of intellectual property, support burden and effect on the product roadmap.
Ask who pays for engineering changes and future revisions. Clarify acceptance criteria, change control and responsibility for validating customer-specific configurations. Consider whether the request creates a reference application that opens an attractive segment or merely satisfies one account at the expense of capacity elsewhere.
A customisation should not be approved solely because the customer is important or the technical team can perform it. Feasibility is not the same as strategic value.
Build a product architecture that absorbs useful variation
Where customer requirements repeat, the business may be able to create modules, standard interfaces, configurable workflows or a defined service catalogue. This preserves customer relevance while limiting the operational cost of variation.
The objective is not to force every customer into an identical solution. It is to identify which differences matter to the customer and which differences the supplier can support economically.
The strategic implication
Customisation becomes dangerous when every contract expands the company's obligations without strengthening a reusable capability or generating adequate returns.
The leadership question is not, “Can we build what this customer asked for?” It is, “Should this variation become part of our repeatable offer, be treated as a separately funded project, or be declined?”
That decision protects both customer responsiveness and the business's ability to scale.
Related reading
Continue exploring this collection: Execution — Sustaining the Advantage
Browse all articles · Ideas & Insights
Interested in the decisions behind technology-led growth? Explore Work With Me →
Continue reading in this collection
Build an Operating Rhythm That Converts Strategy into Results
A strategic operating rhythm connects milestones, evidence, accountability and resource decisions so leaders can adapt execution as conditions change.
Read article →
The Execution Gap Usually Begins with a Missing Decision
When priorities, ownership or authority remain unresolved, more activity cannot compensate for the decisions the organisation has not made.
Read article →
From 30 Ideas to 3–5 High-Value Growth Opportunities
Narrowing a broad idea set requires a common evaluation logic that tests customer value, strategic fit, capability, economics and evidence.
Read article →