Only One Firm Can Quote for Changes to Your System. A Record You Hold Changes That.

The plant needs a change to the planning system. A new customer wants deliveries in returnable crates, and the system has no way to track them.

The head of IT asks the partner for a quotation. It comes back at a figure that seems high, with a start date three months away. The finance head asks the standard question: where are the other two quotes?

There are none. No other firm can quote, because no other firm knows what the system does, and there is nothing in writing to give them. The quotation is approved, as the last one was.

What We Found

For this article we went through the public record on firms that buy changes from the one party able to describe their systems: the sector’s own research, two surveys from outside manufacturing and one survey of small Indian firms.

We found no case of a partner overcharging a manufacturer, or refusing to hand anything over. This article is not an accusation. Most partners hold the knowledge because they did the work and nobody asked for a record. An honest partner is badly served too: when the client cannot read the scope, the partner has no way to show that its price is fair.

Where the written record and the system disagree, firms report harm. In one survey of several hundred technology leaders and practitioners in the US and UK, run by a firm that sells software tools, the great majority reported harm to the business when what had been built no longer matched the documented standards. It covers every sector and is about documents that no longer match what was built; a firm with no document has nothing for a second supplier to read.

The capacity to check a supplier’s work is often not in the firm. In one survey of more than 400 small and mid-size Indian firms across IT, manufacturing, education and retail, 56% cite a lack of technical skills to adopt modern solutions. That is about taking up technology in general, not about suppliers or quotations, and we use it only for that narrow point.

Firms stay where they are while the system works. In one survey of about 500 IT professionals in the US, run by a firm that sells software services, half said a reason they had not modernised was that their current system still worked, and more than four in ten named budget limits. That survey covers every sector, not manufacturing alone.

Our reading is that the single quote is not a pricing problem. It is a records problem. A second supplier can only price a change to a system it can describe, and in most firms in this position only one party can.

What a Firm Can Do Once Anyone Can Read the Scope

The usual answer to a single quote is to negotiate harder. Our reading is that the larger opening is elsewhere.

• A second quote becomes possible. Any competent supplier can price a change from a written description, without first learning the whole system at the firm’s expense.
• The present partner can show its price is fair. A quotation read against a shared description is easier to trust, for both sides.
• Renewal becomes a decision. Each year the firm can choose to stay, knowing what leaving would involve, instead of signing because there is nowhere else to go.
• The plant waits less on one diary. When the partner is busy, work can go elsewhere.

This is our reading of the evidence. It is not a measured market figure.

Four Ways Out of the Single Quote, Weighed

There are four real options. Each one is right for somebody.

Option	When it fits	What it risks
Stay as you are, and negotiate each quote	The partner is good, prices feel fair, and changes are few	Nothing is learnt. Every quote is still taken on trust, and every change makes the system a little more the partner’s
Ask the partner to document the system	The partner is willing, has the time, and it can be agreed in the contract	It is written by the one party that has no reason to make leaving easy, however honest it is, and it competes with the partner’s paid work
Bring in a second partner to learn the system	A second supplier is wanted anyway, and the firm can pay for the learning	The firm pays a newcomer to learn what is there, and ends with two firms holding the knowledge and still nothing in writing of its own
The firm’s own specification, written from the code, confirmed by the firm’s own people	The firm wants quotes it can compare and a renewal it can decide	It costs money and changes nothing in the system. It needs read-only code access, which the firm arranges, and a second supplier still has to learn the system from it

Where You Are Now, and Where You Should Be

Before any work begins we set a benchmark: a few measures taken from your own position, each with a target.

Measure	Typical starting point	Where it should be	How it is checked
What the system does	Known to the partner	Every function written down in plain words, confirmed by your own people	The specification
Firms able to quote for a change	One	More than one, each pricing from the same specification	The quotes set beside the specification
What a quote is read against	Nothing the firm holds	The written specification and the map of the system	The specification and the map
What leaving would involve	Not known	Set out, beside the cost of staying	The cost comparison
Where the code is held, and who holds access	With the partner; never asked	Named, with read-only access arranged by the firm	Confirmed before the assessment begins

The starting points above are what the public record suggests and what we expect to find. In an engagement they are replaced by your own figures, taken in the first review. The targets are what we would work towards with you. They are not results we have already achieved for a manufacturer.

How We Work With You

1. We listen: a free Reliability Review. A first conversation about your systems, who looks after them, and the changes only one firm can quote for. You leave with a short written note of what we found. You can start with a conversation about the system; we ask for read-only code access only when the assessment begins.
2. We research. We research your sector, the regulator’s position and what the public record says about firms in your situation. This article is an example of that work.
3. We read the system and propose: the Legacy System Specification Assessment. Here the system is the applications an outside partner built and looks after for you, with read-only access to the code arranged by you before the assessment begins. It produces a map of the system as it stands, a written specification of what it does, a risk register, a cost comparison between keeping and replacing the system, and a staged plan with a fixed quote. AI does a first pass, our senior engineers review it and trace it to the code, and your own experts confirm it. Code access is read-only and logged, never used for training, and deleted within 30 days of the evaluation ending unless we engage. You get the options and our recommendation.
4. If you approve, we build. We replace a system one module at a time while the old one keeps running. Here that means a rebuild only if you choose one; the specification lets your present partner, or any other supplier, quote for the same work. We never do a single cutover. Each module has a traceability matrix. The work is billed by milestone, each milestone tied to a module you accept, and you can pause after any accepted module.
5. We review against the benchmark. Before work starts we set the benchmark. After each module we show you where each measure stands, and the filled-in benchmark is yours at the end.

The Review is free. Every paid step is fixed price, agreed at scoping. Stop after any step. The findings are yours. The assessment fee is credited in full against the first build stage if it starts within 90 days of the report.

This approach has limits. The specification costs money and changes nothing in the system. A second supplier still has to learn the system from it: quicker than starting from nothing, but not free. Nothing here says a second quote will be lower; it says a quote can be compared. Your partner may be uneasy about the record; that conversation is yours, and we take no part in it. We give no legal advice on contracts or ownership. We do not maintain the specification after we hand it over, and a record nobody updates loses its value within a few changes. We do not work inside a packaged ERP product, on plant control systems, or in RPG or COBOL. We have no published case of this work for a manufacturer.

What changes for the business:

Role	What they gain
CEO	Staying with the present partner becomes a choice the firm makes, and can make again each year.
CTO or CIO	A second opinion on any change is possible, because the scope can be handed over in writing, subject to the firm’s own contract with its present supplier.
CFO	Quotes for changes can be compared, and a renewal is discussed knowing what leaving would involve.
COO	A change the plant needs is not held up because only one firm can do it.
Head of people	The firm can decide which knowledge to hold in-house and which to buy, as a plan.

The cases in this article, and what IOanyT does about that kind of problem:

The case	What IOanyT does
In one vendor’s survey of several hundred technology leaders and practitioners, the great majority reported harm to the business when what had been built no longer matched the documented standards.	We write the specification from the code itself, once the firm has arranged access, and the firm’s own people confirm it, so a second supplier reads what actually runs. Keeping it current afterwards is the firm’s own work.
In one vendor’s survey of about 500 IT professionals, half said their current system still worked as a reason for not modernising.	We do not ask anyone to replace a working system. The specification lets a firm compare quotes and decide its renewal while the system goes on working, and a rebuild follows only if the firm chooses one.

IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. We write down what your system does in a form anyone can price from, so the next quote is one of several.

Book a free Reliability Review →

Get a fixed quote →

See the Legacy System Specification Assessment →