Your Clients Are Funding AI. Is Your MSP Part of the Plan?

Your client asks you to lower the managed-services bill. In the same meeting, they mention a new AI project. There is money for technology. You just may not be part of the work they want to fund.

That is an illustrative renewal conversation, but the budget pressure behind it is documented. Companies are increasing AI investment, and some are paying for it by cutting outside IT help. For an MSP serving midsize and large organizations, the question is straightforward: can you help the client put AI to work, or will that budget go to someone else?

IT budgets are growing. The money is moving toward AI.

BCG's September 2026 IT Spending Pulse, based on a survey of 423 leaders at midsize and large companies, found that buyers expected IT budgets to grow 5.8% that year. AI was being funded through both new money and reductions elsewhere. AI and machine learning were the only product category where more buyers planned to add suppliers than consolidate them. Read BCG's findings.

That creates a difficult position for an existing provider. A bigger technology budget does not automatically mean a bigger support contract. The client may be looking for different work from different suppliers.

Futurum's September 2026 research makes the pressure more concrete. In a survey of 1,636 enterprise technology decision-makers, 46.9% reported AI spending above budget. Among the 297 organizations reallocating money within IT to cover that gap, 60.9% reduced external contractors and consultants. Read Futurum's survey results.

Contractors and consultants are a broader group than MSPs. These findings do not prove that every MSP is losing revenue. They do show that outside IT work can become a source of funding for AI.

Gartner's warning for the future of managed services

Gartner addressed the risk directly in its October 2025 report, Managed Services Disruption: Surviving an AI Agent-Dominated Market. Its public abstract predicts that the opportunities available to incumbent managed-service providers will halve by 2030. It calls on providers to move toward AI-driven services and reduce their dependence on manual labor.

This is a forecast about providers' opportunities, not a claim that every MSP's revenue will fall by half. The full research is available to Gartner clients; the warning above is in the public abstract.

There is also pressure on the price of the work you already do. In a February 2026 interview with CIO, Gartner analyst John-David Lovelock described buyers expecting service providers to use AI to cut delivery costs and pass those savings on.

So an MSP can face two conversations at once: how to make today's service less expensive, and who will deliver tomorrow's AI project. Being good at the first does not automatically win the second.

Clients are asking before every MSP is ready

In a conversation with NetZen, an AI implementation adviser who works with MSPs described the demand reaching part of their partner network:

This is one adviser's experience, not a survey of the market. But it describes a practical problem: a client asks for help, and the MSP needs an answer it can actually deliver.

The same adviser explained how partnering with a specialist can keep the MSP involved, recounting the response an MSP gives its client:

You do not have to build every capability yourself. You do need to understand the request, choose a credible way to deliver it, and agree who supports the result. A client asking about AI should leave with a next step.

Turn each client's knowledge and AI automations into a service

An MSP already knows a great deal about each client: how their systems work, which procedures employees should follow, and which tasks they repeat. NetZen gives you a way to put that knowledge and those workflows into an AI service the client's employees can use directly.

You configure the service in one platform. The client asks for help through your NetZen portal or a connected channel such as Teams or Slack. NetZen answers from the client's knowledge, uses the automations you have enabled for them, and brings in your team when a person is needed.

1. Add the client's knowledge. Upload their approved procedures, application instructions and support documents to the knowledge base. Set the client scope so those sources are used on that client's tickets.
2. Configure the AI automations. Enable relevant packs or create and test tasks for the client. NetZen's automation suite includes browser tasks, API actions, device scripts and run books that combine steps. Connect the systems each task needs, choose its client scope, and set who can request it and who must approve it.
3. Give employees direct access to the AI. They can ask a question, describe a device problem or request an enabled workflow themselves. The assistant follows your setup; required approvals still go to a person, and unresolved work goes to your technicians.
4. Repeat the process for the next client. Use the same platform and setup process, with that client's sources, connections and approvals. Reuse suitable automations across the clients you select, and test each client's setup before rollout.

For example, an employee asks how to request approved software. The AI answers from that client's procedure. Another asks to update a record in a business application; where you have built, tested and enabled the relevant API or browser automation, the AI can carry out that task with the required approval. A printer problem can use enabled device diagnostics. Device automation is one part of the service.

This is work you can package and charge for: preparing the knowledge, configuring the actions, onboarding users and keeping the service useful. You learn one platform and adapt its configuration for each client, instead of learning and building a separate AI solution for every account.

For a client seeking AI deployment across business departments, assess whether you can do that work. Bring in a specialist when it requires skills you do not have. A support improvement and a company-wide AI rollout have different scopes, costs and responsibilities.

Bring a small proposal to the next client review

Here is a hypothetical pilot for an MSP supporting a distributed organization. It is a proposal example, not a customer result or a promise of savings.

The problem

Employees reporting slow applications wait while support gathers basic device details and repeats diagnostic checks.

The pilot

One client team, one recurring ticket category, and an agreed review after 30 days.

The work

Add the client's troubleshooting procedures, connect the agreed devices, enable relevant diagnostics and give the pilot group access through the portal or a connected support channel. This pilot uses device automation; another could use a browser or API workflow.

The controls

Name the approver for changes. Define what the AI may do, when it must stop, and who takes over.

The buyer

Confirm which client leader owns the problem and which budget pays for setup and ongoing service.

The cost

Include configuration, software, training, support and review time. State the ongoing fee before the pilot starts.

The evidence

Compare technician effort, user waiting time, reopened tickets and repeat incidents with the same category before the pilot.

The decision

Agree in advance what would justify expanding, changing or stopping the service.

Do not count faster ticket closure as success if the user still has the problem. Check whether the fix worked and whether the issue returned. Keep work passed to a technician separate from work the AI completed.

Be equally clear about money. Ten hours released for other work is useful capacity. It becomes a cash saving only when spending actually falls. The client should be able to see both the benefit and the cost.

Start with AI your client can see working

NetZen brings together a service desk, RMM and automation for MSPs. The service you offer the client can combine answers from their knowledge base with browser, API, device and multi-step automations, delivered through NetZen's AI and backed by your team.

That gives you a concrete workflow to evaluate with a client. You choose the scope, configure the actions and approvals, and measure what improves. Moving the service desk to NetZen also takes onboarding work; include it in the proposal rather than treating implementation as free.

See how AI agents for MSPs work on technical issues, or explore how to offer AI to your clients. Bring a real support problem to the conversation and show what you can do about it.

Questions MSP owners ask

Research sources are linked beside the claims they support. The two anonymized excerpts are from the same adviser in a private conversation with NetZen. They illustrate that adviser's experience and are not customer endorsements or evidence of measured NetZen results.