Configured, Not Commissioned: A UK Buyer’s Guide to Tailored Service Models

Customisation often arrives in a procurement process as a welcome sign. The supplier is listening, the proposal is adapting, and the service appears to be taking the buyer’s specific needs seriously. For UK organisations, that instinct is understandable. But a tailored service model is not automatically a better one. It is a change to the operating model, and it should be governed as such.

The practical question is not whether a supplier can customise. Most can. The question is what kind of customisation is being proposed, who will support it after the contract is signed, and how the buyer will prevent a sensible adjustment from becoming an unmanaged dependency. NHD Partners takes the view that customisation should be bought as a governed exception where the work genuinely demands it, not as a badge of commitment.

Two kinds of tailoring

UK buyers should begin by separating configuration from bespoke work. The distinction sounds technical, but it has commercial consequences.

Configuration means the supplier’s standard service has parameters that can be set without changing its core. Service levels, reporting frequency, approval routes, user roles, data fields and escalation contacts may all be adjustable. The underlying product or process remains the same, and the supplier can support it through normal channels.

Bespoke work is different. It introduces a new process, a unique deliverable, a non-standard integration or a reporting line that the supplier does not ordinarily maintain. It may be entirely justified. A regulated firm may need a control that reflects its own governance model. A mid-market company may need a service boundary that matches a complex group structure. But bespoke work carries a different support burden, and that burden should be visible before signature.

A useful procurement test is simple: ask the supplier to classify each requested change as configured, extended or newly built. Then ask who supports each category after go-live. If the answer is the same for all three, the buyer should probe further.

The support question comes first

Customisation is often sold during the sales phase and supported during the delivery phase. The gap between those two phases is where problems emerge.

Before agreeing to a tailored model, UK buyers should establish the support route in writing. Who owns the customised element once the implementation team steps away? Is support provided by the same named individuals, or does it pass to a general service desk? What documentation will exist, and in what form? Will the supplier maintain a runbook, a configuration record or a change log that the buyer can inspect?

Continuity matters as much as responsiveness. A bespoke process that depends on one specialist is a key-person risk. Buyers should ask how knowledge will be cross-trained, how the customisation will be described in handover materials, and what happens during holiday cover or staff turnover. These are not adversarial questions. They are the normal diligence expected of any organisation that intends to rely on a service for several years.

Cost creep and change control

Tailored models invite further tailoring. A small adjustment in year one can become a recurring cost in year two and a permanent overhead in year three. The risk is not that suppliers behave improperly; it is that changes accumulate without a clear decision point.

A robust agreement should include a change-control mechanism that is proportionate to the work. For lower-value customisations, a simple written request and approval threshold may be enough. For more material changes, buyers should expect an impact assessment covering cost, timetable, support implications and exit consequences.

It also helps to ask for a total cost of ownership view rather than a one-off build price. What will the customised element cost to maintain annually? What happens when the supplier updates its standard service? Will the customisation be re-tested, re-built or retired? Is there a versioning path, or does every upgrade become a project?

These questions protect both sides. A supplier that can answer them clearly is more likely to deliver a stable service than one that treats customisation as a sales concession.

Documentation, ownership and reversibility

Customisation can create value, but it can also create lock-in. UK buyers should establish what they will own and what they will be able to take elsewhere.

The starting point is documentation. Ask for a description of the customised process, the configuration settings, the data flows and any bespoke code or scripts. If the supplier regards these materials as commercially sensitive, ask for a practical alternative: an escrow arrangement, a handover obligation or a documented transition plan. The point is not to acquire the supplier’s intellectual property. The point is to avoid being unable to operate or replace the service at the end of the term.

Exit should be discussed at the same time as design. What transition assistance will the supplier provide? For how long? At what cost? Will the buyer receive data in a usable format, and will the supplier help a successor provider understand the customised elements? A tailored service that cannot be exited cleanly is not a partnership; it is a dependency.

A governance test for the board

Customisation decisions do not need to reach the board in every case, but they should sit within a clear governance framework. A proportionate test might include five questions.

First, what kind of tailoring is proposed, and why is standard delivery insufficient? Second, who owns the decision and at what value threshold? Third, what is the support model after go-live, including named roles and documentation? Fourth, how will changes be controlled, priced and reviewed? Fifth, what is the exit route if the customisation no longer serves its purpose?

If those questions can be answered before signature, customisation becomes a deliberate strategic choice rather than an open-ended commitment. If they cannot, the buyer should consider whether the standard service, with configuration only, would meet the need more safely.

The right conclusion

Bespoke is not a badge. It is a design choice with consequences for support, cost, continuity and exit. Some UK organisations will genuinely need a tailored model, particularly where regulation, group structure or operational complexity make standard delivery a poor fit. In those cases, customisation can be the right answer.

But it should be bought with the same discipline as any other strategic decision. The buyer should know what is being changed, who will maintain it, how it will be governed and how the relationship can end. That is not a lack of trust. It is clear thinking about the service relationship, and it is the foundation of a reliable partnership.