Harper Insurance’s engineering team published a detailed account of how they run much of their brokerage back office with ambient agents on Grok Bot. That is insurance, not managed services. Still, if you run an MSP, you should read it carefully. Not because their results automatically transfer to your business, but because the operating model they describe is coming for work that looks a lot like ours.
The uncomfortable question is simple. If tools like Grok Bot can take care of a large slice of MSP work, and if the instructions for that work can be packaged and shared, what is left for the MSP, for the vendors that sell us tools, and for the customer who can download the same template?
What Harper says they built
In How AI agents run insurance’s back office, Harper describes ambient agents that do not wait for someone to type a prompt. Events wake them: an email lands, a customer replies, a deadline gets close. The agent works on its own cloud computer, with a real browser, and can act through websites that have no public API the way a broker would click through a portal.
They also describe an agentic harness around those agents: exploration of portals, typed copies of portal data, an abstraction layer that hides whether a carrier has an API or only a login, and mirroring so agents plan from a trusted copy and act on the live page. On premium-finance rescues, Harper’s account is that since September 2026 an ambient agent helped bring more than 200 small businesses current with their lender, covering over half a million dollars in annual premium, with none cancelled by the lender, and that a person still signs off before money moves.
That is Harper’s account of Harper’s business. It is not independent proof that every agentic workflow is reliable, cheap or transferable. It is evidence that at least one company is already treating Grok Bot as the place where back-office work gets done, not just discussed.
Map that onto an MSP
Now put the same pattern next to managed services. Ticket intake and triage. Remote desktop repair. Tenant checks across Entra, Intune, Defender and Outlook. Monthly reporting. Chasing renewals and missing approvals. Much of that work is event-driven. It spans documented Microsoft 365 APIs, scripts and some portal-only steps. Agents can coordinate those paths and, when needed, use approved desktop control. None of that removes licensing, service permissions or the need for authorised access.
I have already been writing about pieces of this. The How Grok Bot Can Resolve Help Desk Issues Through Remote Desktop guide describes how a bot can operate a compatible, approved remote-support session from its own computer. The screenshot and walkthrough in One Prompt, Three Tenants: The Benefits of Grok Bot Group Chat show one prompt producing separately scoped replies from tenant bots in a shared room. Those posts are about emerging workflows and deployment design. Publishing them is not proof that a production fix was executed end to end, and they are not independent validation that every ticket or hunt already runs unattended. They do show where technician work can start to move into the bot.
If that keeps expanding, I expect labour-per-device and labour-per-seat to stop being comfortable planning assumptions. Repetitive click-work erodes first. Undocumented know-how erodes next, because once a workflow is written as skills and tests, it can be repeated without the original person in the chair. Customers can self-serve common tasks, or need fewer people for them. Some work you currently outsource may come back in-house as a bot you operate. None of that means every MSP disappears, or that every task is already autonomous. It does mean the billable centre of gravity can move.
What happens when MSP bot templates get shared widely
Templates make the shift sharper. A Grok Bot template can package generalised memories, skills, routines and plugins into a shareable copy another business can import. Sharing a workflow does not confer the original owner’s account access. The recipient has to connect and authorise their own accounts, answer setup questions and earn the rights the workflow needs. Anyone creating or importing a template should review what is shared and make sure secrets, credentials and client-specific data are not packed in. Template access is still not the same as tenant access, vetted deployment, ongoing reliability, business context, tests or accountability.
I am not claiming a mature MSP template marketplace already exists, or that every useful MSP capability is cleanly exportable. The scenario we have to face is still real: when a method that used to live only in a senior technician’s head, or only inside a vendor’s product UI, becomes a downloadable bot template, then competitors and customers can acquire the same starting point. The scarce asset stops being “I know which buttons to press” and becomes “I can prove this runs safely in your environment, recovers when it fails, and someone accountable owns the outcome.”
Ask yourself the blunt version. If your client can download the bot instructions for password resets, mailbox restores, Intune compliance chasing or Entra sign-in hunts, what are they still buying from you?
Pressure on third-party MSP tools
Professional services automation (PSA), remote monitoring and management (RMM), documentation and reporting products have spent years encoding workflow into screens. An agent that can use those screens, or reach some of the same outcomes through documented APIs and scripts, exposes how much of the paid value was navigation and repetition. Seat-based economics can feel that pressure if fewer technicians need to live in the console all day. Automation layers that only saved clicks become less special when the bot is the one clicking.
That is not the same as saying Grok Bot replaces RMM agents, backup platforms or endpoint detection and response (EDR). It does not magically erase MFA, licensing, connectors, service permissions or approvals. Distinguish an agent taking over the use of a tool from replacing the tool’s underlying service. Endpoint presence, durable records, audit trails, rollback, security controls and legal obligations still matter. Vendors that offer reliable, agent-ready execution and evidence may stay valuable. Vendors that only sell a nicer sequence of forms may not. Some will bundle agent capabilities themselves. I would plan for fewer technician seats and pressure on per-seat or per-workflow pricing, rather than pretend those shifts are already measured facts about any named product.
What an MSP can do now
Here is where I would start.
- Map services by automatable outcome. Separate work that is mostly sequence and evidence from work that is judgment, relationship or regulated accountability.
- Pilot in an approved test environment. Baseline quality, cost, latency, error rate and rollback before you promise a client anything.
- Version the templates and the tests. If the workflow is worth running, it is worth knowing which revision ran and what proved it.
- Sell measured service levels, risk handling and outcomes, not keystrokes. AI efficiency does not automatically preserve the old price.
- Keep the hard parts close: business-specific integration, recovery and security responsibility, exceptional cases, and human approval where money, identity or destructive change is involved.
- Offer operated and customer-operated configurations deliberately. Some clients will want you to run the bots. Some will want the template and their own operators. Pretending only one model exists is how you get surprised.
Be honest about the economics. Some revenue can shrink even if you adopt AI well, because customer power rises when the instructions are portable. The MSP that survives is not the one that denies that. It is the one that still has something worth buying after the clicks are gone.
My take
Harper’s post is a glimpse of a back office that wakes when work arrives and only interrupts people for the decisions that matter. MSPs are not insurance brokerages, and Grok Bot will not swallow Microsoft 365, endpoint security or compliance overnight. But if ambient agents can work portals, email and desktops, and if MSP templates travel, then undifferentiated technician labour and tool-navigation value can get cheaper for everyone, including your customer. Plan for that world now: prove outcomes, keep accountability, and stop pricing as if the rare skill is knowing which menu to open.
