MSP Market Pulse — September 2026

The window in one paragraph

August was about vendors failing. September is about clients doubting. The biggest new cluster isn’t an incident. It’s providers losing ground to people who can’t see what they do: a board asking whether the provider is needed at all, a client angry about calling support even though every issue got fixed, and a client’s AI chat contradicting the provider’s advice for free. The vendor story from August kept going too, and this time the sharpest moment was two official statements that couldn’t both be true.

1. The client’s AI is now the second opinion

“A recommendation gets made, someone throws it into ChatGPT, gets a different answer… and suddenly we’re reopening the entire discussion. Then they change the prompt and get another answer” (⬆87, 71 comments). The original poster is pro-AI and precise about the cost: it gives less experienced staff “enough terminology and confidence to challenge decisions without actually having the experience or accountability to own the outcome.” One reply describes a client who pulled and reinserted drives on AI advice, and the database had to be restored from backup (⬆32).

The two answers that worked were about context, not authority. One provider (⬆69) runs the client’s own AI with the client, adding the licensing, the security baseline and the monthly cost the client’s prompt left out, so the client watches their own tool agree. Another (⬆6) just asks for the whole chat instead of the answer: “Every time I’ve done that the constraint that made my recommendation the right one was just missing from what they typed in.”

2. Work done well and invisibly reads as work not needed

A provider with two years left on the contract learned the client’s directors were asking whether they needed an MSP at all (⬆106, 96 comments). The top reply (⬆222) named the mistake: “your relationship is with the two IT guys, not the person signing the check.” Another commenter (⬆4) made it one line: “They’re telling you that they don’t know what you do. Tell/show them. If you can’t defend it, then you’re proving that they’re right.” The same pain showed up three more ways: a client two months into a three-year contract, angry that they have to call at all when every issue was fixed remotely (⬆57); “someone with partial knowledge and full confidence” wanting to take over part of the scope (⬆38); and a client who cancelled, went silent for 57 days of a 60-day handover, then asked to come back on day 58 (⬆41).

3. Two statements, one thread

The RMM vendor from August’s issue shipped two more hotfixes, one for a pre-authentication remote-code-execution flaw it reported as exploited in the wild. Its own notice said: “we have no confirmations that these vulnerabilities have been exploited in production environments.” In the same thread, the security firm that runs detection for many of its customers wrote that its investigation began “after a customer’s fully patched [RMM] environment was compromised” (⬆18). A customer set the two quotes side by side and asked which was true. A third incident hit the vendor’s password vault extension. Fairness notes the sub carried itself: the researcher praised the vendor’s response as “incredibly fast and cooperative,” and the most-upvoted defense (⬆17) set the standard: “How a company responds to the incident says far more about them.”

4. Enrollment is the unguarded moment

Three unrelated threads found the same gap: control planes govern what an identity does, and barely govern how something gets the right to act. An organization moved to passkeys and found a persuaded user can simply register more of them, with no native block on either major platform (⬆50). The working fix requires a single-use code before any new authentication method can be registered (⬆59). An MSP that adopted a management tool specifically to keep techs out of global admin found delegated access can’t reach the permissions they need, pushing them back toward standing admin (⬆33). And in a contested exit, a competing provider created its own domain and tenant admins inside a live client and disabled one of the incumbent’s (⬆51, 95 comments).

5. Margins set by announcement, terms kept in a mailbox

Distributor margins on a set of cloud-software SKUs are being reset to a flat 12% for every partner “regardless of their current margin level,” a detail the sub pieced together from a rep’s email rather than the announcement (⬆54). A security vendor raised prices 20% on 30 days’ notice (⬆47, 109 comments). And a one-person shop was invoiced six times the agreed rate. It escaped in two minutes only because the original deal was still in the owner’s inbox. One comment named why that isn’t a win: the evidence worked, but it sat outside the billing process. “That is a lucky control, not a reliable one.”

6. Questions your peers asked that nobody answered well

1. What do I do when my client’s AI disagrees with me? (Two working techniques, both about restoring missing context. Nobody turned them into a practice.)
2. How do I prove value to the person who signs the check, not the people who use us? (Always answered with meetings, never with something the client can read without the provider in the room.)
3. Do I trust a vendor statement its own security partner contradicts? (Left as an open question to the vendor, unanswered.)
4. What’s the finish line on a patched zero-day? (One operator argued installing the hotfix isn’t it. No runbook.)
5. How do I stop a user from registering an extra passkey on every platform, not just one? (There’s a fix on one major platform and no fix on the other.)
6. Where should agreed commercial terms live so the renewal process checks them?

---

Compiled by JieGou from public r/msp threads (four-week window ending September 7, 2026). New editions when there’s something worth reading.