It is 8:40 on a Monday. The file server is not responding, the only person who knows how to restart it is on vacation, and the vendor who installed the firewall wants a purchase order before logging in. Nobody did anything wrong: nobody was simply responsible for making sure this didn't happen.
Managed IT services exist to solve exactly that situation. Instead of paying by the hour when something breaks, the company hands a provider responsibility for running part of its technology —the help desk, the infrastructure, the cloud, an application— under agreed service levels and predictable pricing. This article explains what a managed service includes, how it differs from other forms of IT outsourcing, how it is priced and when it really pays off.
What managed IT services are
A managed service is a contract in which the provider commits to an operational outcome, not to a number of hours. The difference looks subtle, but it changes everything:
- Who is accountable. The provider is responsible for the service working within what was agreed, not just for handling what it is asked to do.
- How it is measured. With indicators defined upfront: availability, response and resolution times, completion of scheduled maintenance.
- How the work is done. With documented processes (incident, change and problem management), monitoring tools and regular reporting. Many providers rely on frameworks such as ITIL to structure this.
- How it is paid. Usually with a fixed or semi-fixed monthly fee based on scope, not per ticket.
The most common managed IT services cover user help desk, server and network administration, cloud operations (Azure, for example), backup and recovery, security and patching, and support for business applications such as an ERP.
Managed service, staff augmentation or squad: not the same thing
In Chile, "IT outsourcing" is used for almost anything. It helps to separate three models, because the risk and the way you control the outcome are different.
| Managed service | Staff augmentation | Squad or cell | |
|---|---|---|---|
| What you buy | An operational outcome with an SLA | People who join your team | A complete team for a goal |
| Who runs the day-to-day | The provider | You | Shared: you prioritize, the team self-organizes |
| How it is measured | Service indicators | Hours and individual performance | Deliverables and progress per iteration |
| Turnover risk | Absorbed by the provider | You feel it directly | Mitigated by the team |
| Best for | Ongoing, stable operations | Reinforcing a team that has its own technical leadership | Projects or products whose scope evolves |
None is better in the abstract. If you have an IT manager with sound technical judgment and you are just short of hands, staff augmentation may be the most efficient option. If what you need is for operations to stop depending on one or two people, a managed service is a better fit. And if you are building something new, a squad or a software factory makes more sense; to evaluate that option, see Software factory in Chile: 10 questions before you sign.
What a good contract should include: SLA and coverage
The service level agreement (SLA) is the heart of the contract. A useful SLA is not an availability figure on the cover of the proposal; it is a set of concrete commitments:
- Priority classification. What counts as critical (operations are stopped), high, medium or low, with examples from your business.
- Response and resolution time per priority. Responding is not resolving; the contract must distinguish them.
- Coverage hours. 9x5 coverage (business days, office hours) is enough for many companies. 24x7 coverage is justified when operations run continuously: shifts, e-commerce, plants, logistics. A common middle ground is 9x5 for requests and 24x7 only for critical incidents.
- Escalation. Who gets called if the SLA is not met, with names and timeframes.
- Reporting. What is reported each month: tickets, compliance, recurring incidents and recommendations.
- Penalties or credits. What happens if the provider falls short. Without consequences, the SLA is just an intention.
- Exclusions. What is out of scope (projects, licenses, hardware) and how it is quoted.
One point that is often forgotten: if the provider accesses systems containing personal data of customers or employees, the contract must make clear its role as data processor, the security measures it applies and what happens to the data when the contract ends. With Chile's Law 21.719 on personal data protection about to take effect, it is better to include this from the start than to renegotiate later.
How managed services are priced
The most common pricing models are:
- Fixed monthly fee by scope. One amount for running a defined set of services. The most predictable model.
- Per user or per device. Common for help desk and endpoint management: the fee scales with company size.
- Per managed asset. Per server, database, cloud subscription or application.
- Complementary bank of hours. For out-of-scope requests (small projects, changes), at an agreed hourly rate.
- Hybrid. A fixed base plus variable charges for volume or extended coverage.
When comparing quotes, don't look only at the monthly total. Check what is included, what counts as "out of scope", whether 24x7 coverage carries a surcharge and how extra hours are billed. Two proposals with the same price can cover very different things.
When they pay off (and when they don't)
Managed IT services usually pay off when:
- Operations depend on one or two key people and their absence has already caused problems.
- The internal team spends most of its time firefighting and makes no progress on projects.
- You need coverage outside office hours without hiring shifts.
- You use specialized technologies (an ERP, Azure, legacy systems) that require knowledge that doesn't justify a full-time hire.
- You want a predictable IT cost you can compare year over year.
They probably don't pay off, or not yet, when:
- You don't know what you have. Without a minimum inventory of systems, contracts and access credentials, no provider can commit to a serious SLA. The first step is an assessment.
- The need is one-off. Something with a start and an end is better handled as a project.
- You are only looking to cut costs. A well-run managed service brings order and continuity, but it is not always cheaper than an in-house employee. Its value lies in reducing risk and dependency.
It is not all or nothing, either. Many companies outsource one part —the help desk or ERP support, as we discuss in SAP Business One: support, upgrades and roadmap— and keep the relationship with the business and architecture decisions in-house.
How to start without losing control
Before signing, three practices prevent bad surprises:
- A defined transition period. In the first weeks the provider gathers information, documents and gets up to speed. That period must have a plan, deliverables and an end date.
- Access and documentation in your name. Administrative credentials, cloud subscriptions and documentation must belong to your company, not the provider.
- An exit clause. How the service is handed over if you decide to change providers or bring it in-house, with timeframes and deliverables.
A good IT services company in Chile should have no problem committing to these three things in writing. If it resists, take that as a signal.
Frequently asked questions
What is the difference between managed IT services and hourly support?
With hourly support you pay for the time used and you decide what gets done. With a managed service you pay for an outcome with service levels, and the provider is responsible for preventing and resolving issues within what was agreed.
Do I need 24x7 coverage?
Only if an outage outside office hours stops your operations or affects customers. Many companies combine 9x5 coverage for requests with 24x7 support limited to critical incidents.
Do I lose control of my technology by outsourcing it?
Not if the contract guarantees it: access and documentation in your company's name, monthly reports, an SLA with consequences and an exit clause. What you outsource is the operation, not ownership or decision-making.
Let's talk about your operations
At Disrupsoft we provide IT outsourcing for Chilean companies: managed services, staff augmentation and squads, with experience in Microsoft Azure, Microsoft 365, Dynamics 365, SAP Business One and JD Edwards. If you are considering outsourcing part of your IT, we start by understanding what you have and what you need covered, and we propose the model and SLA that fit your operations.
