Consumption-Based AI Shifts MSP Role from Access to Governance and Cost Control

[00:00:02] AI consumption billing turns adoption into financial exposure. Governing usage, managing output, controlling costs, and assigning accountability, those are the new operating requirements. Enabling access was never the hard part. As AI moves from per-seat software into consumption-based operations, who used the tool matters less than what did it cost, what did it produce, and who owns the outcome. This is the Business of Tech. I'm Dave Solbel.

[00:00:33] Start with Microsoft. In late April, Bleeping Computer reported that admins can now remove the Microsoft Copilot app from enterprise Windows 11 devices using a new policy. Specifically, a Remove Microsoft Copilot app setting delivered through Intune and Group Policy. That is an operational control, not a roadmap item. AI is moving from optional feature to managed estate.

[00:00:56] Now, zoom out to the economics. The Information's AI Agenda newsletter is tracking rising AI costs showing up as a problem even for investors. The reporting cites cases like Uber burning through its 2026 AI budget within months, and it describes usage costs that can run to roughly $1,000 a day per user in some scenarios. At scale, that moves AI from experimentation into budget exposure fast.

[00:01:23] The same reporting points out a blunt reality. A lot of organizations still can't clearly quantify what they're spending on AI. And on the demand side, we have signals coming directly from workers. The Register highlighted a survey of U.S. employees, more than 1,000 respondents, where a majority opposed their employer purchasing Microsoft's AI bundle. And large numbers said they could do their work just as well with an alternative AI tool.

[00:01:50] Finally, accountability is becoming financial, not just reputational. The New York Times reports Apple agreed to a $250 million settlement over claims it misled customers about Apple intelligence capabilities, with eligible iPhone buyers potentially receiving up to $95 per device. That matters because AI expectations are no longer abstract marketing promises. They are becoming measurable obligations with dollar figures attached.

[00:02:18] If you're listening to this and you haven't hit follow yet, on Apple Podcasts, search Business of Tech. It takes five seconds and you'll get tomorrow's show automatically. If you run a managed services business, you've probably discovered something frustrating. Most PSAs are great for tickets, but not always great for managing projects. And as your business grows, that becomes a real problem. More engineers, more projects, shared resources, dependencies across timelines.

[00:02:46] Suddenly, the PSA project module that worked fine early on starts to break down. That's exactly where Movala fits in. Movala is a purpose-built, AI-driven project management platform designed specifically for service organizations. It integrates directly with tools like ConnectWise, Autotask, and Halo PSA. So your PSA remains your system of record, where Movala handles the complex project planning and scheduling.

[00:03:12] The result is accurate timelines, clearer visibility, and projects that improve your margins. If you're ready for project timelines you can trust, visit movala.com slash msbradio. That's m-o-o-v-i-l-a dot com slash msbradio to learn more. The underlying driver here is that AI is turning work into a moving target faster than most organizations can standardize how work gets done.

[00:03:41] So the center of gravity shifts to whatever system can provide a consistent interface, consistent controls, and consistent execution. You can see that in the way Microsoft frames adoption. In its 2026 Work Trend Index covered by CNET, Microsoft points to a gap between the pressure employees feel to use AI and the degree to which leadership is actually aligned and modeling how it should be used.

[00:04:06] In GeekWire's coverage of the same research, the obstacle isn't framed as capability, it's culture, incentives, and management practice. Organizations already have tools that can draft a paragraph or summarize a document. What they lack is a shared definition of what good AI output looks like, how it gets reviewed, and how it connects to the work people are actually evaluated on. Platform vendors are reorganizing their stacks to handle incoherence.

[00:04:34] Bloomberg's Mark Gurman reports Apple is adopting an extensions model allowing third-party AI to power features like Siri and writing tools. This shift makes the OS a routing layer for swapping AI models without disrupting user experience, aiming to keep AI capabilities stable despite changing models and vendors. For clients, that means the visible tool may stay familiar while the underlying model, cost structure, and accountability chain keeps changing.

[00:05:03] The infrastructure layer points in the same direction. Gartner's prediction, reported by CIO Dive, shows IT spending climbing in 2026 with data center investments surging because compute is becoming the constraint. The deep views reporting on OpenAI's expanded AWS partnership shows the same pattern from another angle. Models and managed agents are being pushed into platforms like Amazon Bedrock. That matters because consumption, governance, and infrastructure are now connected.

[00:05:32] The more AI gets embedded into daily work, the more clients will rely on platforms to distribute it, meter it, and control it. And the more those platforms meter and control usage, the more MSPs need to translate that complexity into policy, reporting, and cost accountability. What this means for MSPs is that AI support is no longer a sidecar to the stack.

[00:05:56] It's becoming part of the operating model clients expect you to run because the automation is moving directly into the documents, decisions, and workflows where mistakes are expensive. Take Microsoft's move here, covered by The Verge. A new legal AI agent inside Word, designed to walk through contracts clause by clause against a defined playbook. That detail matters. Microsoft isn't selling magic, it's selling repeatable automation inside a controlled workflow.

[00:06:24] Something you can audit, standardize, and defend when a client asks, Why did it flag this clause? Or, who approved this output? When agents get embedded into the every tools clients live in, the MSP's job stops being keep the suite running and becomes keep the automation governed. Permission, policies, review steps, acceptable use rules, and the ability to show how the work was done. Now pair that with the performance bar.

[00:06:51] Business Insider reports in McKinsey's analysis of companies using its AI implementation framework, finding returns on the order of $3 for every dollar spent. When those organizations concentrate AI efforts into three or fewer domains instead of trying to spread it everywhere. Again, the point isn't the exact ratio.

[00:07:12] The point is that the winners are treating AI like an operational program with scope discipline, measurement, and management, not a license rollout. And that's exactly where MSPs get pulled in. Because once clients decide AI spend needs to produce measurable results, somebody has to own the configuration, the guardrails, and the reporting that ties usage to outcomes.

[00:07:37] Either you become the partner that simplifies and governs the automation layer, making it safe, measurable, and operationally coherent. Or you stay the generalist support layer underneath it, absorbing the chaos of unclear prompts, inconsistent usage, supplied consumption bills, and why did the agent do that escalations, without ever being paid for the responsibility you are carrying. This episode is supported by Halo.

[00:08:04] Automation is becoming a defining characteristic of modern managed services. But automation only works if the core platform supports it. Halo PSA gives service providers the flexibility to build powerful workflows, integrate automation tools, and design service processes around how their business actually runs. For MSPs building a more automation-driven operation, Halo PSA is one of the platforms increasingly showing up in those conversations.

[00:08:33] Learn more at usehalo.com This episode is brought to you by Control Map. Growing MSPs are using Control Map to build recurring revenue by expanding their GRC services. Starting now, Control Map is offering a free plan for MSPs looking to get started with providing compliance as a service. Create a free account and run an assessment. Track key items like policies, risks, and evidence in one place.

[00:09:00] It's a practical way to prove value to a client before deciding to expand your compliance offering. Try Control Map for free today. Visit scalepad.com slash Dave to get started. That's scalepad.com slash Dave. Why do we care? Because the bad decision for an MSP is to treat AI like another supported application. Consumption billing turns AI from a licensing issue into an accountability issue.

[00:09:30] A client may enable co-pilot, ChatGPT Enterprise, Bedrock Agents, or another AI service. But usage creates costs, outputs, permissions, workflow decisions, and business consequences someone has to govern. Most managed services agreements were not written for that. They usually cover support, uptime, administration, and security operations.

[00:09:52] They often do not define responsibility for AI output review, consumption thresholds, workflow approvals, prompt governance, or proof that a human approved an AI-assisted decision. That gap is the service opportunity. If MSPs leave AI governance inside general support, they will still get the escalations when the bill spikes, data is exposed, or an agent output causes a problem. They'll just handle it at flat fee margins.

[00:10:21] Now what to consider? Audit your current service agreements. Identify whether contracts address AI consumption overruns, output reviews, workflow approvals, and data access configuration. Separate AI access from AI governance. Enabling a license is not the same as managing usage, cost, policy, and accountability. Define the failure modes. Define the failure modes.

[00:10:47] Spell out what happens if an AI tool produces a wrong answer, exposes data, triggers unexpected spend, or is used outside an approved workflow. Build telemetry before selling governance. MSPs need visibility into who is using AI, where usage is growing, and whether spend maps to a business outcome. And price AI management as recurring control work, not bundled support.

[00:11:16] If this trend continues, AI management will become a separate recurring service line from Microsoft 365 and endpoint support within two years. The service will include usage governance, consumption reporting, workflow approval design, access review, exception handling, and ROI measurements. Providers that price that work will be paid to manage cost, control, and accountability.

[00:11:41] Providers that bundle it into general support will subsidize vendor complexity with their own margins. This is the Business of Tech. Want more from the Business of Tech? Join Business of Tech Plus for ad-free episodes, early interviews, extended cuts, subscriber-only shows, and exclusive member perks and analysis. Sign up at businessof.tech slash plus.

[00:12:09] And follow this show on your podcast app, and if you're on YouTube, hit subscribe and the bell so you never miss a story. Reviews and comments help spread the word too. Interested in advertising? Head to mspradio.com slash engage. The Business of Tech is written and produced by me, Dave Sobel, under ethics guidelines posted at businessof.tech. Thanks for listening. I'll see you on the next episode.

[00:12:38] Part of the MSP Radio Network. Part of the MSP Radio Network.