Compare Adding automation to a managed IT retainer vs. an operations partner
Your IT provider already has the logins, knows the network and answers the phone when something breaks. Asking them to automate the quoting process is a reasonable next question. The answer turns on whether the problem is the technology or the way the work runs.
Side-by-side comparison
| An operations partner | The managed IT retainer | |
|---|---|---|
| What the engagement is for | Changing how a workflow runs, and building what replaces it | Keeping the technology healthy - devices, network, identity, backup |
| Where the work starts | In the process: who does what, in what order, and what it costs today | In the stack: what is deployed, patched, licensed and secured |
| Shape of the engagement | A scoped project with a defined end and a handover | A ticket queue and a service level, month after month |
| What they are best at | Rebuilding repeated work into one system you own | Helpdesk, endpoints, security, backup and the network - genuinely better than us |
| Cost shape | A scoped build from $5,000, or an audit at $3,500 first | Per seat or per device, monthly, and already in the budget |
| Best when | The same work repeats and the friction is in the process | The friction is in the technology, or it is a security and continuity question |
Where the difference actually shows up
Two different kinds of good
A managed IT provider is measured on uptime, tickets closed and nothing being breached, and a good one earns the retainer several times over. That discipline - keep it running, change as little as possible - is exactly what you want guarding a network, and exactly the wrong reflex for redesigning how a quote becomes a job. Neither party is doing the other one badly. They are built for opposite outcomes.
Automation on a support contract tends to shrink to scripts
When automation lives on a retainer it gets done in the gaps between tickets, by whoever is free that week, and it takes the shape of a script or a connector because that is what fits in a gap. That is good work and often all that is needed. What rarely comes out of it is a system with a record, roles and screens, because nobody on a ticket queue has a day to spend interviewing a dispatcher. The Operations Platform is the opposite shape: a scoped project with an end date and a documented handover.
Ask who keeps the lights on afterward
A rebuild nobody supports is worse than no rebuild. If your IT provider is going to hold the backups, the identity and the endpoints either way, they belong in the room while the new system is designed, and the handover documentation should be written for them to read. We have no interest in owning your infrastructure. We would rather hand a documented system to the people who already answer the phone at seven in the morning.
When the other option is right
Keep it on the retainer when the problem is technology. If the complaint is that the file server is slow, laptops take a week to set up, the VPN drops, email is being spoofed, or nobody is certain the backups restore - that is an IT question, and a good provider will solve it faster and better than any operations firm, with tooling you are already paying for. The same holds for a great deal of light automation: user provisioning, patching, alerting, standing reports, a script that kills a recurring manual chore. There is no reason to hire anyone else to write that. And if your provider has a real applications team rather than an engineer doing it between tickets, use them - they already have the access, the context and the relationship, and none of that is worth trading for a different logo on the invoice. Bring in an operations partner only when the thing that is broken is the work itself, and would still be broken with every device on the network in perfect health.
FAQ
Common questions
Should we drop our IT provider?
No, and we would argue against it. Helpdesk, endpoint management, identity, patching, backup and network security are a specialty, and they are not ours. The two roles sit side by side: they keep the technology healthy, we change how a particular piece of work runs, and the handover documentation is written so they can support what gets built.
Our IT provider says they can build this too. How do we judge?
Ask who does it and what happens to it afterward. Specifically: is there a team that builds applications, or an engineer doing it between tickets; do you get source code and documentation or a login; and what becomes of the thing when that engineer leaves. Those three answers separate a real applications practice from automation done in the gaps, and plenty of providers answer them well.
Can you work with our IT provider rather than around them?
That is the normal arrangement. They hold infrastructure, access and security policy; we build the workflow and hand it over documented. Bringing them into the scoping call early is usually the cheapest hour in the project, because they know which constraints are real and which are habit.
Is a rebuild cheaper than adding hours to the retainer?
No, and that is the honest answer. A scoped rebuild costs more up front than adding a few hours to the retainer, and it only pays when the work repeats often enough that the process itself is the expense. A Workflow Map at $500 is the cheap way to find out which of the two you are looking at.
Or explore Process Automation.