A provider can look at several completed programmes and see the same software core in each. That is useful evidence. It may show that technical material has application beyond a single project and deserves further investment. It does not establish that the provider has already found one repeatable customer undertaking. The surrounding work can differ in ways that matter to introduction, operation and support. I want a service strategy to examine those differences before technical reuse becomes a claim about the whole business being offered.
In a fictional 2023 review at Xunveris Systems, twelve customer programmes shared a software core. Eight could fit the proposed standard proposition, while four required materially different operating workflows. I supported retaining the eight inside the standard offer and treating the other four as bespoke, with CNY 8.4 million in proposition and service-design expense. The choice did not deny the common technology. It recognised that the commercial description needed evidence about more than the most reusable part of the solution.
## Begin with the work the customer expects
The customer does not experience the provider's component inventory in isolation. It expects a service to support an activity, with responsibilities and conditions that make sense in its own organisation. Two programmes may use common technical material while asking different people to make decisions, supply inputs or handle exceptions. Those differences can affect the undertaking even when the code remains similar. I therefore begin by asking what the customer expects to be able to do, and what the provider would need to accept in helping it do that.
This is not an argument that every customer is unique beyond comparison. That view can preserve unnecessary variation and prevent useful standardisation. The question is which differences matter to the service being proposed. Some may be accommodated within an established offer without changing its central responsibility. Others may require a materially different workflow or support model. The strategy account should explain the basis for distinguishing them, with service designers and operating colleagues contributing evidence rather than receiving a conclusion already settled by a commercial label.
The sales team wanted all twelve programmes in the standard-service story. It had a legitimate concern: a narrower claim could make the provider appear less experienced than it was. I agreed that the company had relevant experience across the twelve. But experience of handling several requirements was not the same as evidence that all could be served through one standard undertaking. The wider experience could remain visible without being used to support a more specific claim than it justified.
Technical colleagues retained authority over suitability and the conditions of reuse. Contractual permissions and support commitments also required their proper assessments. A strategist should not treat the presence of an asset in an earlier programme as proof that it can be offered again on any chosen basis. My concern was the business proposition, but that proposition depended on evidence supplied by others. The useful role was to connect those assessments to a decision about what the provider would say it could repeat.
## A narrower standard offer can be the more exact choice
Keeping four programmes outside the standard proposition had a cost. It reduced the breadth of the initial commercial story and preserved the effort associated with bespoke work. The CNY 8.4 million response expense belonged in the decision, rather than being recast as a saving created by greater focus. The choice also required an explanation to colleagues whose previous work was not being included in the standard category. That work did not become unsuccessful or unimportant because the new proposition had a narrower boundary.
I wanted the four programmes described through their actual needs. If bespoke becomes a euphemism for a problem customer or an unfinished standard product, the classification can damage the quality of the discussion. A legitimate difference may justify a different commercial undertaking. Equally, a provider should not invoke customer uniqueness to protect every inherited variation. The distinction has to remain open to examination. It is valuable because it helps the institution choose, not because it gives each programme a permanent identity beyond challenge.
The standard offer also needs a positive account. Simply removing four programmes does not explain what makes the other eight repeatable. The proposition should identify the customer problem it addresses and the responsibilities that can be carried consistently across that group. Otherwise standardisation becomes a remainder category: whatever has not been declared exceptional. I would want the institution to understand why the common undertaking is credible, with the relevant technical and service conditions carried into the commercial description.
There is no general rule in the eight-and-four split. Another review could reach a different conclusion, and the same provider might later develop a broader offer with additional work. The fictional case establishes only that the evidence available supported a particular boundary at that time. A leadership account should not turn the selected boundary into proof of a universal method or a measured financial result that has not been demonstrated. Its value lies in the choice, the disagreement and the expense made visible.
## Preserve the distinction after the proposition is approved
The boundary can become blurred again as the offer travels through the organisation. A sales description may restore the broader claim because it is easier to explain. A delivery account may absorb a customer-specific requirement without changing the way the service is represented. A strategy presentation may then cite the enlarged group as evidence that the original standardisation decision succeeded. I would ask how the institution recognises a material change in the undertaking, without assuming that strategy should approve every operating detail.
The appropriate response depends on responsibility. Commercial owners need an accurate offer; service and technical teams need to explain the conditions they can support; the strategic account needs to describe the business the provider is developing. The point is not to create one committee that controls all those decisions. It is to ensure that a change in one part does not silently alter the claim relied on by the others. Reuse becomes a stronger business asset when its limits remain understandable.
For a leader preparing a public profile, this distinction produces a more revealing case than a headline about the number of reusable components created. Explain the customer problem, the proposed standardisation and the reason some work remained outside it. Retain the colleague who argued for a broader offer and the cost accepted in choosing a narrower one. State the strategist's contribution alongside the technical and commercial authorities that made the decision possible. Those details help another executive understand the kind of judgement being offered.
The fictional twelve-programme review is ultimately a case about what the word service includes. It includes technology, but also the work and responsibility surrounding that technology. A common core can be an important starting point. A repeatable customer undertaking requires a fuller account. I would want the provider to make that account before treating the reuse of code as evidence that it has already built the business it hopes to sell.