Nobody calls asking for a Technology Baseline. They call because a renewal is close, a cost is climbing, an acquisition landed, or a proposal needs an answer by Friday. The entry point is always a symptom, and the work still starts in the same place.
The urgency is real and it does not remove the need for evidence. What changes with the entry point is where the pressure is, not the order in which the questions have to be answered.
Usually from finance, often just before a budget cycle.
What it actually needs firstThe spend has to be established from documents before it can be explained, and compared to the market before anyone can say whether it is wrong.
Often with weeks left, sometimes with the notice window already closed.
What it actually needs firstWhat the agreement actually says, what the market looks like now, and what the alternatives cost. A renewal decided without those is a decision the vendor is making for you.
With requirements already drafted, and a shortlist in mind.
What it actually needs firstRequirements built from the estate rather than from memory, and a market position that says whether going out is warranted at all. Sourcing executes a decision; it does not discover one.
With a proposal on the table and a deadline attached to it.
What it actually needs firstA clear statement of what the decision has to solve, and what the current arrangement costs to keep and to leave, before a proposal is allowed to define the options.
With two of everything and no agreed picture of either.
What it actually needs firstBoth estates established on the same basis, with the gaps named, before anyone tries to rationalize across them.
After a departure, a migration, or a few years of nobody owning it.
What it actually needs firstReconstruction from source documents, with what cannot be recovered stated as missing rather than quietly inferred.
From whoever inherited the relationships.
What it actually needs firstThe vendor picture assembled and connected to what each one actually supports, before consolidation is discussed as if it were obviously right.
Usually after something was missed.
What it actually needs firstA current record to govern. Governance over a stale record is a calendar reminder with extra steps.
These are constructed illustrations of common situations. They are not customer case studies, and nothing in them describes a real client.
A 1,500-person company across 18 locations with 60+ vendors, no unified contract view, and renewals scattered across inboxes and shared drives.
A PE-backed manufacturer that acquired three businesses in two years and inherited overlapping telecom, cloud and security arrangements, with no clean view of what each entity spends.
A VP of IT weighing a communications platform migration with six proposals on the table, no structured evaluation framework, and a CFO asking for a business case by quarter end.
A CFO watching technology costs climb year over year with no breakdown of what is driving it, no contract inventory, and a board asking direct questions.
Where sites have made their own arrangements over years and nobody holds the whole picture.
Where a board wants a defensible technology story and the operating team does not yet have one. For private equity.
Where you can name the providers but not what each costs, supports, renews or risks.
Whichever door it comes through, the first move is the same: establish what is true.
