Most prospective clients ask the same question on the first call: What does it look like when we work together? The answer isn't a deck. It's a sequence of findings, decisions, and changes that compound over the first ninety days. Here's what that actually looks like.

Week one: connect to the data, and let it speak

The first week is unglamorous. We connect to invoice feeds, contract repositories, inventory systems, and any existing reporting. We don't change anything. We don't propose anything. We pull the data that actually exists and put it in one place.

What we typically find in week one:

Invoice data is incomplete. Most organizations have invoices for the carriers they remember to track. Hosted services, smaller utility accounts, departmental cloud spend, and one-off circuits often live somewhere else, or nowhere at all.

Inventory is partial. The IT team's record of what's active rarely matches the carrier's record of what's billing. The variance is usually 8% to 22%.

Contracts are scattered. Master agreements, addenda, renewal letters, and rate schedules live across email threads, shared drives, and individual laptops. Pulling them into one repository takes longer than the contracts themselves are old.

None of this is a problem. It's just the starting condition. Almost every environment looks this way before someone is accountable for keeping it organized.

Week four: the baseline is real

By the end of week four, the environment has its first complete picture. Every active service is in the inventory. Every invoice maps to a contract and a location. Every contract has a renewal date in a single calendar. Every line item has been validated against its underlying agreement at least once.

This is the moment where most clients see the gap between what they thought they had and what they actually have. The numbers usually surprise people.

The first round of findings lands here. Some are small — a $400 monthly variance on a single circuit, a wireless plan that should have been retired. Some are large — a category of services billing 10% above contract rates across hundreds of locations.

What the client gets at week four is a single document that says, in plain language: here is your environment, here is what it's costing, here is where the variances are, and here is what we're recommending you do about each one. No surprises later. No findings that emerge after a year of engagement. The baseline is the floor, not the ceiling.

Week eight: governance starts to operate

Between weeks four and eight, the work shifts from finding to governing. Each invoice cycle now runs through validation before payment. Disputes are filed and tracked through resolution. Renewals 90 days out are flagged and reviewed. Any contract change goes through a documented decision process.

This is the operational rhythm that has to keep running for the value to compound. Without it, the environment drifts back to its starting condition within a year.

Reporting starts to firm up around week eight. Finance gets a monthly view that ties to the GL. IT gets a service-level view that ties to actual operations. Both views reconcile to the same underlying data, which is something most clients have never had before.

Week twelve: the system is running

By the end of the first ninety days, the environment is no longer a project. It's a managed system. New services flow through the same governance. Disconnects flow through the same disconnect process. Renewals are anticipated, not reacted to. Findings are reported, not discovered.

The before-and-after at week twelve usually looks something like this:

Before: spend visible across 60-75% of the technology environment. Inventory accurate to within 80% of actual. Contract renewals discovered when they auto-renew. Findings discovered when someone investigates them.

After: spend visible across the full environment. Inventory accurate to within 99% of actual. Renewals managed proactively against a single calendar. Findings produced by the system, on a recurring cadence, without anyone going looking.

This isn't the end of the engagement. It's the start of what the engagement actually produces over the long run, which is an environment that gets better, not worse, the longer it operates.

What the first ninety days isn't

Onboarding isn't an audit. Audits end. The findings get filed, the savings get booked, and the team moves on. Six months later, the same problems start re-emerging because nothing has changed about how the environment is governed.

What we're building in the first ninety days is the operating system, not the audit report. The audit-style findings are produced as a byproduct, but the value isn't in finding them once. The value is that the system keeps producing them, on a schedule, indefinitely.

That's what the first ninety days is for. After that, the work is just continuing what the operating system was built to do.