What we cut in a client's first 90 days

Most technology engagements start with a slide deck about the future. Ours start with a spreadsheet about the present — specifically, every vendor relationship and every contract the business is currently paying for, read line by line. It is unglamorous and it is the single highest-leverage thing we do in the first ninety days, because you cannot have an honest conversation about where the technology budget should go until you know where it is actually going.

When we took over technology for a Triangle-based non-profit, the audit surfaced two problems that had been sitting in plain sight for years. The first was an overpriced software contract from a vendor that had been steadily overcharging them — not dramatically in any single invoice, just consistently, the way these things almost always work. The second was a Spectrum agreement that had never once been renegotiated since the day someone signed it. Nobody on their side had been ignoring this out of carelessness. They simply had no one whose job was to look, with the time, the leverage, and the technical context to do anything about it.

What we did was not clever. It was just the work. We took over the entire IT operation as their outsourced technology team, audited every vendor relationship against what it actually delivered, renegotiated the Spectrum agreement, and replaced the overpriced software contract with a custom case-management system built specifically for how the organization actually operates — not generic software they'd been bending their process around for years.

The result was $7,000 a month cut from their technology spend. That is $84,000 a year, redirected out of waste and back into the mission, with no reduction in capability — in fact, with more capability, because the custom system fit their work instead of fighting it. We did not find that money with a pricing trick or a one-time discount. We found it the way a technology director finds it: by being the person whose job is to look.

I keep returning to that case because of what it proves about the alternatives, and the proof is more useful than any claim I could make. Most MSPs would have left the organization on the overpriced software, because switching is hard work and migrations create risk they don't get paid to absorb. Most MSPs could not have built the replacement at all — software development simply isn't a capability they have. And most MSPs do not renegotiate vendor contracts, because contract leverage is not the product they sell. We did all three, in the same ninety days, because all three are just what the job is.

I'm deliberately not promising you $7,000 a month. Your number depends entirely on what's already in your stack, and the honest version of this story is that I won't know your number until I've read your contracts. What I will tell you is that in nearly every business we've audited there is real money sitting in a renewal nobody questioned, a tool three people use that's licensed for thirty, or a platform you pay a premium for to get one feature you could own outright. The first ninety days is mostly about finding it and freeing it.

The deeper point is what funding the rest of the work looks like when you do this first. Cutting waste in the first quarter is not the goal — it's the mechanism. It buys back the budget that pays for the strategic work that actually moves the business, and it does it without asking the owner for a bigger check. Same budget, real capability. That sentence is the entire difference between IT support and technology leadership, and the first ninety days is where you find out which one you've actually hired.