Businesses are often told to become more customer-centric. That frequently means becoming more flexible.
A major customer wants a customised contract. Another needs different delivery terms. A strategic supplier requires an exception to the standard procurement process. A sales team requests unusual pricing to close an important deal.
Individually, each decision can make sense. Collectively, they can create a business that is increasingly difficult to operate. Many organisations are therefore confronting an overlooked cost of growth: exceptions.
The tension between customer flexibility and operational complexity is not new. In its influential article The Four Faces of Mass Customization, Harvard Business Review argued that trying to invent new programmes and procedures for every request can add unnecessary cost and complexity. The modern version of the problem is broader because exceptions now travel through contracts, software, finance systems, customer support and automated workflows.
Customisation Creates Commercial Value
There are good reasons companies make exceptions. Large customers may genuinely require different terms. International markets can have different legal requirements. Complex products may need customised implementation. Strategic partnerships can justify arrangements that would not make sense for smaller relationships.
Rigid standardisation can therefore become commercially limiting. The problem begins when exceptions become routine. If half of all customer contracts require special approval, the exception has effectively become part of the normal operating model, even if the company still treats it as unusual.
Every Exception Has a Lifecycle
The cost of an exception does not end when it is approved. Consider a customised customer contract. Sales may negotiate the arrangement. Legal reviews the clause. Finance approves the pricing. Operations agrees to a different delivery model. Technology modifies a workflow. Customer service needs to remember the special conditions.
Months later, someone has to renew the contract without losing track of those variations. What appeared to be one commercial decision has created a continuing operational obligation. Companies often measure the immediate revenue gained from customisation. They are less likely to measure the cost of supporting it over time.
Complexity Accumulates Quietly
Operational complexity rarely appears all at once. It accumulates. A product gains another pricing tier. One market receives a different approval process. A customer gets a unique billing arrangement. An acquired business continues using a separate workflow.
Each addition may be manageable. Years later, the organisation can have hundreds of slightly different ways of performing activities that once had a single process. McKinsey’s work on platforms and modularity illustrates why standardised modules and clear rules can help companies offer more choice without allowing product variety to generate uncontrolled complexity across development and the wider value chain.
The same logic applies beyond manufactured products. Exceptions in contracts, customer service, pricing and operations create process variants. Employees then become responsible for remembering the differences, and institutional memory becomes a hidden part of the operating model.
Exceptions Create Technology Work
Software systems are usually designed around rules. Exceptions create workarounds. Employees may manually adjust invoices. Operations teams may maintain spreadsheets outside the primary system. Developers may build custom features for one customer. Finance teams may reconcile transactions differently.
Over time, these modifications create technology complexity. A system becomes harder to upgrade because several customers depend on custom behaviour. Automation becomes more difficult because workflows are inconsistent. Data becomes harder to compare because similar transactions are recorded differently.
What began as a commercial accommodation can eventually become technical debt.
Pricing Needs to Reflect Complexity
Two customers buying the same nominal service can create very different operating costs. One follows standard processes. The other requires specialised reporting, manual billing, unusual service levels and extensive account management.
If pricing does not reflect that difference, the business may mistake revenue for profitability. This suggests that operational complexity itself can become a pricing variable. A customised arrangement may still be worthwhile, but management should understand what it costs to deliver.
The Most Valuable Customers Are Not Always the Largest
A large account can produce substantial revenue while requiring constant operational intervention. A smaller customer using the standard product may generate lower revenue but considerably higher margins.
Traditional account analysis can miss this distinction if it focuses heavily on sales. Companies may therefore need to understand complexity-adjusted customer profitability. How many exceptions does the relationship require? How much senior management time does it consume? Does the customer use standard systems? How frequently are billing or service issues escalated? Does the account require custom technology development?
These costs can materially alter the economics of the relationship.
Standardisation Is Not the Same as Inflexibility
The goal is not to eliminate every exception. It is to make exceptions deliberate. A healthy operating model may have clear standard processes and equally clear rules for when deviation is justified.
One way to preserve flexibility without uncontrolled variation is modularity. McKinsey’s modularity research describes how standard modules can support a broader range of offerings while controlling complexity and associated costs.
The principle can extend to service businesses. Instead of creating a unique solution for every customer, companies can build a limited number of configurable options, contract structures, service levels or workflow modules. The organisation provides flexibility within defined boundaries.
Approval Processes Need to Consider Future Cost
Many approval systems focus on immediate risk. Legal checks whether a clause is acceptable. Finance checks whether pricing meets margin requirements. Operations checks whether delivery is possible.
A stronger process also asks about future complexity. Will this exception require manual work every month? Does the technology platform support it? Can the arrangement be scaled? Will the company still want to support it in three years?
These questions can change the decision. An exception may be technically possible but strategically undesirable.
AI Could Make Customisation Easier — and More Dangerous
Artificial intelligence may reduce the cost of supporting certain exceptions. AI systems can interpret contract differences, generate customised communications, adapt workflows and help employees navigate non-standard processes.
That could allow companies to provide more personalised services without adding proportional headcount. But it could also encourage businesses to create even more variation. If customisation appears inexpensive, commercial teams may offer it more frequently.
The complexity does not necessarily disappear. It may simply move into systems that become harder to govern. Companies therefore need to distinguish between automating complexity and actually reducing it.
Product Design Can Absorb Variation
A practical alternative to repeated exceptions is modular design. Customers can select from a defined set of modules, permissions or service levels without requiring a completely separate product or operating process.
The same idea can apply to contracts, logistics, financial terms and professional services. Standardisation remains underneath, while customers still receive meaningful choice.
Exceptions Need Owners
Another problem is that no one may own the total complexity created by exceptions. Sales owns the commercial relationship. Legal owns contract terms. Finance owns billing. Operations owns delivery. Technology owns system changes. Each department sees only part of the cost.
Some companies may eventually track exception volumes in the same way they track operational incidents: how many non-standard contracts exist, how many manual workflows are active, which exceptions create the greatest cost and which customers generate the most operational variation.
The Case for an Exception Budget
Companies could even think of flexibility as having a limited budget. Every business can absorb some variation. Too much begins to damage efficiency.
An exception budget does not need to be a literal financial amount. It can represent the maximum level of operational customisation a business is willing to support. Strategic customers may consume more of that capacity. Routine customers remain closer to standard processes.
The concept forces management to recognise that flexibility is not free.
Simplification Becomes a Growth Strategy
Many businesses simplify only when costs become too high. They consolidate products, retire legacy systems, standardise contracts and reduce unnecessary approvals. Simplification can also be proactive.
A company that periodically removes old exceptions prevents complexity from accumulating indefinitely. Temporary arrangements can expire. Product variants can be reviewed. Acquired businesses can migrate toward common processes. Customer-specific workflows can be challenged at renewal.
The Business Value of Saying No
One of the hardest commercial decisions is declining a customer request. Businesses naturally fear losing revenue. Yet saying yes to every request can gradually create an operating model that serves nobody particularly well.
The strongest companies are not necessarily those offering unlimited flexibility. They may be those that understand where customisation creates genuine value and where it merely creates complexity.
The exception economy requires businesses to recognise that every deviation from the standard model creates an obligation. Some obligations are worthwhile. Others quietly consume capacity for years. Growth therefore requires more than winning customers. It requires designing an organisation capable of supporting the promises made to them.
References
1. Harvard Business Review — The Four Faces of Mass Customization — https://hbr.org/1997/01/the-four-faces-of-mass-customization
2. McKinsey & Company — Platforms and Modularity: Setup for Success — https://www.mckinsey.com/capabilities/operations/our-insights/platforms-and-modularity-setup-for-success
3. Deloitte — Transforming Product Portfolios: The Power of Product Mining — https://www.deloitte.com/ch/en/services/consulting/perspectives/transforming-product-portfolios.html