Customisation Should Earn Its Complexity Before You Price It

A commercial essay on pricing bespoke work through its operating consequences, from exceptions and coordination to maintenance after delivery.

The requested change is not always the whole change

A customer can request a small alteration that creates a much larger operating exception. A different format may affect review, delivery, support and future updates. The visible task is only one part of the commitment. Before quoting a price, the business should understand what must remain different after the original alteration is complete.

This essay proposes a commercial way to evaluate bespoke work. It does not claim that standardisation is always superior or that a particular surcharge produces the right result. Customisation can be the central value of a service. The question is whether the business understands its own promise well enough to price and deliver it deliberately, rather than discover the complexity after the customer has already relied on the offer.

Describe the exception as an operating arrangement

Begin by identifying which parts of the normal process change. Will the order need separate scheduling, a different reviewer or a unique handover? Does the alteration create a version that must be maintained independently? Those questions turn a vague request into a set of observable responsibilities.

Imagine a hypothetical reporting service asked to provide a customer-specific data format. Producing the first file may be straightforward. Maintaining the format after future system changes may require additional checks. The important distinction is between a one-time adjustment and an ongoing compatibility promise. Both can be sold, but they should not enter the price under the same description merely because the first delivery looks similar.

Charge for the commitment, not for the customer’s apparent wealth

A credible price explanation connects the additional charge to work, exposure or value the offer actually contains. It should not depend on an accusation that the customer is difficult or an assumption that they can afford an arbitrary amount. The customer needs to understand what the price buys and which decisions it leaves open.

An offer might separate design, implementation and continuing support. That makes it easier to accept the useful part without unintentionally purchasing an indefinite service. It also gives the supplier a basis for declining work outside the agreement. Precision can support a higher price when the obligation is substantial; it can equally reveal that a supposedly premium request is inexpensive to deliver and should not be burdened with invented complexity.

Decide which exceptions belong in the product

A repeated request can indicate an opportunity to improve the standard offer. It can also reflect a small group of customers with a distinct need that remains expensive to serve. The business should examine which explanation fits before turning every exception into a permanent feature.

The review concerns more than the number of requests. Can the proposed feature be delivered consistently? Does it serve the intended customer, and what does it add to testing or support? A new standard option should reduce uncertainty rather than distribute a complicated special case across the entire customer base. The right answer may be a separate tier, a genuinely bespoke service or a clear refusal to support that arrangement.

Make the customer choose between intelligible alternatives

A quote becomes more useful when it offers alternatives whose differences are explicit. The standard service may meet the main objective at lower cost. A customised version may add a defined capability with a longer timetable. A third option may provide a limited trial before either party accepts an ongoing obligation.

This is different from presenting a deliberately weak standard offer to make the expensive choice unavoidable. Each option should be viable on its own terms. The customer can then decide whether the additional capability matters enough to justify its price and constraints. The seller learns something valuable as well: whether the request represents a real priority or merely a preference that disappears when its consequences become visible.

Protect delivery from unrecorded changes

Customisation becomes harder to manage when each conversation quietly changes the specification. A helpful response to a customer can create a new promise that the delivery team has never seen. The original quote then ceases to describe the work, while both sides continue referring to it as the agreement.

Record accepted changes in a form that the people doing the work can use. Identify effects on scope, price, timing and later support. The process should distinguish correcting an error against the agreed specification from adding a new requirement. A customer should not pay again for the promised result, and a supplier should not pretend that a new result can always be absorbed without affecting any other obligation.

Review the service after the first successful delivery

A completed bespoke order can still leave an uneconomic arrangement in place. The supplier should compare the actual coordination, support and maintenance with what was anticipated. That review is not a justification for retrospectively changing the agreed price. It is information for the next offer and for any renewal decision.

The most useful outcome is a clearer product boundary. The business learns which requests it can support well, which require a different price and which it should decline. Customisation earns its place when its value and obligations can both be explained. The objective is not to eliminate complexity. It is to stop selling complexity unknowingly and expecting either the team or the customer to absorb the surprise.

Gabriel Nicolaev — CyGuru

Editorial photograph for illustration.

FOLLOW THE CONNECTION

Another angle on this subject

Continue through related ideas, decisions and consequences.

Money & Business

Payment Milestones Should Follow the Risk in the Work

A commercial essay on structuring project payments around observable progress, buyer protection and the supplier’s exposure before final delivery.

Money & Business

A Long Contract Should Explain How the Work Can Change

A commercial essay on long engagements: scope boundaries, changing assumptions, adaptation costs and the decisions that keep a contract workable after signature.

Money & Business

Supplier Payment Resilience Begins Before an Invoice Becomes Urgent

A commercial essay on mapping critical suppliers, payment decisions and operational consequences before a delayed invoice threatens delivery.