In practice · 04 of 09
We are committing money against a picture nobody trusts.
At the moment of largest commitment, the estate picture usually comes from the vendor who profits from the renewal, or from the integrator sizing the programme it intends to bid for.
The conflict is structural, not moral
Nobody is behaving badly. A vendor asked to describe your dependency on its platform will describe it accurately and completely, and the completeness is the problem: every integration point is real, and presenting all of them at once is also the strongest possible argument for renewal. An integrator scoping a migration will size it honestly against the risk it is being asked to carry, and that risk is reduced by scoping generously.
You are asking two parties with a direct financial interest in the answer to supply the only picture you have. Then you commit for three or five years against it.
Your own records will not rescue you
The usual fallback is internal documentation, and in most institutions it does not hold. The configuration management database is populated by a process that stopped being followed. The architecture diagrams are three reorganisations old and describe teams that no longer exist. The application inventory counts applications but cannot say what any of them do or which of them still matter.
This is not negligence. It is what happens to any hand-maintained description of a system that changes faster than the description does. Cloud spend telemetry and cost tooling do not fill the gap either. They can tell you what a thing costs to run. They cannot tell you what it does, who depends on it, or whether the logic inside it is still required.
What an independent picture actually separates
We build the picture from the systems themselves rather than from a questionnaire or a vendor deck, and the useful output is a separation rather than an inventory.
- What is genuinely locked in. Real dependency on a platform's proprietary behaviour, which is expensive to leave and worth knowing precisely.
- What is portable. Logic that happens to run on the platform but does not depend on it, which is frequently the larger share and is almost never presented as such.
- What is yours. In a heavily configured platform, a great deal of the institution's own intellectual property sits in customisation the vendor did not write and does not own. That is an asset in a negotiation and it is usually invisible.
- What is dead. Logic still being carried, priced and migrated that nothing has called in years.
Where the leverage sits in a renewal
Two things change the shape of a negotiation more than a discount conversation does. The first is knowing the true switching cost rather than the asserted one. The second is knowing how much of what you are paying to keep is actually your own.
It is also worth noticing what the pricing basis does over time. Where a platform is priced against a measure of business volume rather than usage, its cost rises with your growth whether or not anything about your use of it changes. That is a strategic question about the architecture, not a procurement question about the rate, and it is answered by knowing what could be made swappable.
Common questions
Can our systems integrator not just do this?
They can, and the output will be shaped by what they intend to bid for. That is not an accusation, it is an incentive. The reason to have an independent party produce the picture is the same reason you would not accept a survey commissioned by the seller.
How current does the picture stay?
It is dated and it refreshes rather than being rebuilt. That is the difference between an assessment you commission once per decision, and a description you can still rely on at the next one.
Does this work on commercial software we did not write?
Partly, and we are deliberate about where it stops. It is strongest on codebases it can read, which includes the customisation layer around a commercial platform, and that layer is usually where the institution's own logic lives. It is weaker where only configuration is visible, and on obscure stacks, where automated insight has to be supplemented by human capture. A tool pitched as having no limits is the trap this whole argument accuses others of.
When this comes up. Comes up at a contract renewal, an end-of-life platform, or a consolidation mandate.
How it is delivered
Compass produces the position and Blueprint the sequencing. Vault keeps the picture dated, which is what makes it usable at the next decision. Each module is a fixed deliverable behind a go or no-go gate, and the baseline earns the design. The full set of modules is here.
Related situations
- Technology and software due diligenceRead the estate inside the deal window instead of sampling it.
- Legacy modernisationRetire the dead logic before the programme commits to carrying it.
- Delivery and change economicsThe cost of not understanding your own systems, made visible against your own records.
Tell us what you are trying to land.
A short conversation about your situation and whether an independent accountable role is the right instrument. If it is not, we will say so. No deck follows automatically.