Managed IT is usually sold as insurance. What you are actually buying is a predictable number of technician hours each month and a named person who answers the phone. If nobody has explained that to you, you are paying for a vague promise.
What a Managed IT Week Actually Looks Like
Take a 25-seat office on a standard contract. Monday morning, a remote session clears the weekend’s queue: password resets, a printer that stopped spooling, someone locked out of a shared drive. Wednesday, a health check covering patch status, last night’s backup results and disk space. Friday, one on-site hour for the machine that needs hands on it.
That is roughly six to ten technician hours a month, and the contract is priced against that number. Inside those hours: ticket triage, OS and application patching, backup verification, account management, printer support and network troubleshooting. Everything quick, recurring and unglamorous.
Servers and network gear do not run on that weekly health check alone. Server monitoring best practices sets out the metrics and thresholds.
What an SLA Should Promise, and What It Should Not
An SLA is a commitment to respond, not a commitment to fix. Read the verbs.
SLA language is defensible when it commits to response times by severity, names an escalation path and sets a reporting cadence. It is not defensible when it promises resolution times for faults outside the provider’s control, guarantees uptime on a third-party internet circuit, or offers unlimited best-effort support with nothing measurable behind it.
An ISP outage, a failing disk and a misconfigured firewall have genuinely different fix times. A provider promising a two-hour fix on all three has not thought about it.
Ask for three things in writing:
- Response time per severity, measured in business hours, not round the clock
- A named technician or account manager, not a queue
- Monthly reporting built from actual ticket timestamps, not a summary paragraph
A Sample SLA, Line by Line
This is roughly what a defensible clause set looks like.
Coverage. Remote support Monday to Saturday, 09:00 to 21:00 IST. On-site visits on working days, 10:00 to 18:00. Public holidays excluded unless a separate round-the-clock block is contracted.
Critical (server, network or file-share outage affecting all users): remote response within 1 hour, on-site attendance within 4 hours.
High (multiple users affected, no full outage): response within 4 business hours. Standard (single-user faults, installs, changes): within 1 business day.
Response means a technician is actively working the ticket and has acknowledged the impact, not that the fault is fixed.
Exclusions. Hardware replacement cost, third-party software licences, faults caused by power surge or flood, and any system not on the signed asset schedule.
Term. Twelve months from date of agreement, 60 days written notice to terminate, no exit penalty.
Two lines do most of the work. The exclusions line stops “unlimited support” becoming unlimited billing. The asset schedule line stops your scope expanding after someone buys four new desktops.
Three Contracts Where Managed IT Is Overkill
Three people, one printer, no server. If everyone works from a laptop, a browser and a phone, a managed contract adds a monthly line item and a helpdesk nobody will call. Hold IT AMC services instead and pay when something breaks.
One office, recent hardware, bought as a single batch. If your desktops are under two years old and were purchased together, faults cluster around the same manufacturing window. That produces one bad batch to budget for, not a chronic condition.
Remote-first staff on managed devices. If your team runs on Google Workspace or Microsoft 365 with managed laptops, the software vendors handle most of it. You need helpdesk access, not an infrastructure partner.
In all three cases a smaller block of remote IT support with defined hours does the same job for a fraction of the fee.
How to Tell Managed IT From a Rebranded AMC
An AMC covers devices: they break, someone fixes them, parts get replaced. Managed IT covers a service: availability, patching, capacity planning and a person accountable for the whole environment. Ask who is responsible when file storage is unreachable for a day because a certificate expired. Under an AMC, usually nobody.
FAQ
How much does managed IT cost per month for a small office? Roughly ₹2,000-10,000 per month for a small office, rising into six figures annually as device count, server count and coverage hours grow. Insist the quote itemises by device rather than saying “workstations”, which hides whether servers and printers are in or out.
Is managed IT the same thing as an IT AMC? No. An AMC is reactive maintenance on hardware. Managed IT is proactive management of a service, with response commitments, reporting and accountability. Many providers sell the identical document under both names, so check whether response times appear in writing.
How many on-site visits should I expect each month? For a 20 to 30 seat office, one to three is normal, and most convert to remote sessions. A quote bundling four guaranteed visits is buying a physical presence, not a fix rate. On-site IT support is cleaner as an add-on block.
What happens if the provider misses a response time? Ideally a service credit against that month’s fee. That clause is the difference between an SLA and a marketing line. If nothing is attached to a miss, treat the response times as aspirations.
Do I need managed IT if everything already runs in the cloud? You still need someone accountable for accounts, devices, backups and access. What you shed is server and network management. Cloud-only businesses usually do well with a lighter, remote-first agreement.
Talk Through a Managed IT Proposal
24Bit System delivers managed IT services to Noida and Delhi NCR businesses with defined response times, a named contact and monthly ticket reporting. If you already have a proposal you want a second opinion on, call +91 7840002466.
