Your Vendors Reprice on a Calendar. You Don't.

On July 1, Microsoft raised the price of Microsoft 365, between 5 and 16 percent depending on the plan, and published the mechanics alongside the numbers: existing customers keep their price until renewal, then the new one lands. The same day, Sophos took its firewall hardware and the subscriptions attached to it up a flat 10 percent and named the component shortage behind it. Atera spent the summer moving every grandfathered account to current rates, monthly accounts in June, annual accounts at renewal. Three vendors, one quarter, and every increase came with a date, a mechanism, and a reason. That is what pricing looks like when a company runs it as a system.

Now look at the company you own. The MSP in your portfolio almost certainly runs pricing as an annual act of nerve.

The nine percent

Across the industry, 95 percent of MSPs put their clients on contracts, and 9 percent put a price increase in them. The figures come from a reader survey of MSPs published last year, and they describe the whole problem in one line: everyone signs paper, almost nobody writes the increase into it. The rest handle pricing by holding a review once a year and deciding whether to have the conversation.

So the cost side of the business moves by calendar and the price side moves by courage. Picture one renewal: the client’s licenses cost the MSP more in July than they did in June, and the MSP’s own price for that client is whatever the contract said two years ago. Multiply by every seat and every account. Each renewal that passes without the increase passed through is a quiet cut to gross margin, and it never shows up as a decision, because nobody made one. It happened one renewal at a time, which is exactly how Microsoft designed its side of the trade.

Why the fear is rational

The objection from management will be that raising prices loses clients, and the data says the fear is earned. WatchGuard surveyed MSP customers this spring and asked what would make them leave their provider. The answers start with a tie at 39 percent each: rising costs without added value, and a major security incident. Read that pairing again. A price increase with nothing attached to it sits in the same tier as getting breached.

What the same buyers accept

Ask the same market a different question and the answer flips. In Barracuda’s survey of two thousand organizations that buy from MSPs, 92 percent said they are prepared to pay more for help integrating their security tools, and about 70 percent put a number on it: up to 10 or up to 25 percent more. The client who leaves over a bare increase will fund a larger one that arrives attached to a capability with a name. The clause clients punish is cost without added value. So attach the value, and say its name in the increase letter.

What the owner does about it

Four moves, none of which need a new client to pay for themselves.

Audit the paper. Pull every client contract and count the ones with an escalation clause. The count will be low. Now you know the size of the retrofit.

Put the increase in writing. New contracts and every renewal get an escalation clause with a date, the way your vendors do it. An increase that arrives by calendar is infrastructure. An increase that arrives by phone call is a negotiation.

Never ship a bare increase. Pair every uplift with something the client can name, and let the security work carry it, since that is what buyers already say they will pay more for.

Put one number in the board pack: realized price against list across last quarter’s renewals, split between accounts that got a named capability with their increase and accounts that got a letter. That number is the company’s pricing discipline, measured. Nobody else measures it; there is no public benchmark for escalator adoption or realized increases anywhere in this industry. Run the metric for two quarters and the company holds better pricing data than the market it competes in.

The calendar test

Your vendors will do this again. Component costs, licensing changes, a new bundle: the reason varies and the calendar does not, and next summer’s increases are already being drafted in Redmond and Abingdon. The question for the next operating review is whether the company you own reprices with them, on paper and on schedule, or keeps absorbing its vendors’ increases into its own margin while it works up the nerve to have a conversation.