A plain-English guide to the model, its history, and the ownership question that matters more than any feature list. Written in San Antonio by a firm that has been doing this work since 1999.
Businesses do not merely use technology anymore. They run on it. When the network goes down, the business goes down with it: sales quotes stop going out, patients stop getting scheduled, crews stand around, and the phones go quiet in the worst possible way. That dependency is the reason managed IT services exist, and it is the reason waiting for something to break before fixing it stopped being a viable strategy years ago.
This page is the research half of the conversation, not the sales half. It explains what managed services providers are, where the model came from, how it differs from the break-fix support that preceded it, and the one question that separates a true managed services agreement from a dressed-up equipment lease: who owns what.
The True Cost Is Downtime, Not the Repair Bill
In a break-fix model, you pay for the repair. The repair bill is real money, but it is the small number. The much larger cost is the downtime wrapped around it. If a server fails or network connectivity drops, employees cannot work, customers cannot be served, and deadlines slide. None of that shows up on the invoice.
The structural problem is the clock. In a reactive model, the clock on a repair does not start until something is already broken and already hurting operations. Someone notices, someone calls, a technician is dispatched, parts are sourced. Every one of those steps happens while the business waits.
Proactive management inverts the clock. Systems are monitored around the clock so that failing drives, filling storage, aging batteries, expiring certificates, and network bottlenecks get caught while they are still maintenance items instead of outages. Industry analyses commonly put the preventable share of downtime in reactive environments at roughly 70 percent, and the deeper truth behind that number is simple: most failures announce themselves early to anyone who is listening.
What Does an Outage Actually Cost You?
Adjust the variables below to see how quickly a single outage flips the financial advantage away from the break-fix model:
- Downtime per year: $0
- Emergency repairs per year: $0
- One typical outage: $0
Assumptions: affected employees are unable to work for the duration of the outage, and figures exclude lost sales, reputation damage, and recovery from data loss. If part of the team can keep working, lower the employee count instead. The monthly investment slider tracks the employee count until you adjust it yourself.
According to Deloitte, cost savings and efficiency are leading reasons that managed IT services and helpdesk services are sought after..
Prevention Is Cheaper. Resilience Is the Proof.
Recovering from an incident costs dramatically more than preventing one. For a small business, a single ransomware incident can easily push costs beyond $50,000. At a major institution, the financial damage can climb into the millions once forensics, recovery, downtime, operational disruption, and lost revenue are factored in. That’s why proactive cybersecurity investments matter and why Texas is putting serious resources behind them.
The point was underscored on a macro scale when Governor Greg Abbott and the National Cyber Director launched Project Watershed 250 at UTSA’s downtown cybersecurity hub, targeting the protection of critical Texas water infrastructure. On the campus level, that same philosophy was put to the test during a cyber threat targeting UTSA in mid-August. The lesson is straightforward: reactive “break-fix” IT is no longer enough.
A break-fix model leaves systems vulnerable between service visit schedules and depends on manual, sporadic patching. That approach may keep yesterday’s problems contained, but it does little to address today’s continuously evolving threat landscape. A genuinely proactive managed environment is different. It combines continuous endpoint protection, enforced multi-factor authentication, network segmentation, real-time monitoring, automated threat response, and tightly controlled access at the perimeter.
Nothing makes an ecosystem completely un-breachable. The objective is to make compromise harder, detection faster, containment immediate, and recovery controlled. And that fundamentally changes the odds. In managed services, the odds are the whole game.
The recent attempted cyber-attack at UTSA is a compelling example. Administrators have understandably remained tight-lipped about the precise technical architecture involved, so any discussion of specific vendors or configurations should be treated as speculation rather than confirmed fact. What is clear is the outcome: the university was able to contain the incident, pause systems in a controlled manner, refresh campus credentials/passphrases, and ultimately begin the semester without the kind of prolonged disruption associated with a full-scale compromise.
That is what effective managed situation looks like. Not necessarily preventing every attempted intrusion but stopping an intrusion from becoming a catastrophe. The organizations that will fare best in the next wave of cyberattacks won’t be the ones asking, “How quickly can we fix this?” They’ll be the ones that invested early enough to ask, “How quickly can we detect, isolate, and contain it?”
The deeper layers of this subject live on our computer security page. The short version: choose enterprise class at SMB cost price points, prevention is a budget line, recovery is controlled.
Predictable Costs Instead of Punishing Ones
Break-fix looks cheaper on paper when everything is running smoothly. The trouble arrives on a Friday night, when emergency support carries surge pricing and a catastrophic failure creates a large, unbudgeted expense at the worst possible moment.
Managed IT services operate on a flat monthly fee, which turns unpredictable emergency spending into a predictable operating expense. One prevented ransomware incident or one avoided multi-day outage can pay for years of coverage. We publish what we charge rather than making you sit through a discovery call to hear a number: flat-rate plans are detailed on our managed IT services cost page, and one-time IT support pricing is published as well.
Break-Fix and Managed IT, Side by Side
The two models differ less in the tasks performed than in the incentives underneath them:
| Feature | Break-Fix | Managed IT Services |
|---|---|---|
| Approach | Reactive: wait until it breaks | Proactive: prevent the break |
| Cost structure | Unpredictable: hourly labor and emergency fees | Predictable: fixed monthly rate |
| Incentive | The provider profits when you have problems | The provider profits when your network is stable |
| Security | Addressed after an incident | Continuous monitoring and patching |
| Backups | Your responsibility to run and test | Managed, verified, and auditable |
What a Managed Services Provider Actually Does
A managed services provider, usually shortened to MSP, functions as an outsourced IT department. The provider monitors, manages, and supports a company’s technology for a predictable monthly fee, under a service level agreement that defines response times and responsibilities. In practice, that means:
- Help desk support: answering employee questions and resolving day-to-day computer and software problems.
- Network monitoring: watching servers, switches, firewalls, and internet connections around the clock as part of ongoing network support.
- Patch management: pushing security updates to every machine on a schedule, usually during off-hours.
- Backup and disaster recovery: running automatic, encrypted backups and actually testing that they restore.
- Security management: maintaining firewalls, endpoint protection, spam filtering, and multi-factor authentication.
- Technology planning: advising leadership on budgets, hardware replacement cycles, and compliance requirements.
The reasons businesses make the switch follow directly from that list: a full bench of specialists for less than the cost of one full-time hire, fewer and shorter outages, security handled continuously instead of episodically, an environment that scales without a hiring cycle, and compliance obligations met with documentation to prove it.
Where the Term Came From: A Short History
The business model is older than the name, and the gap between the two is a good story.
- 1962Ross Perot founds EDS on a then-radical idea called facilities management: running a client’s data processing under a long-term, fixed-price contract.
- 1963Frito-Lay becomes the landmark early client, with EDS setting up the systems and providing the staff to run them.
- 1967EDS executive Morton Meyerson proposes the broader model that would eventually be known as outsourcing.
- 1989IBM signs its Kodak data center deal, and the model goes mainstream under the name IT outsourcing.
- 1991IBM launches Global Services, built around outcome-based delivery with performance defined in service level agreements.
- Late 1990sApplication service providers appear, hosting software remotely, and the phrase managed services starts circulating as a smaller-scale alternative to the mega-deals.
- 2000 to 2005Remote monitoring and management platforms such as Kaseya and ConnectWise make flat-fee IT management practical for small and mid-sized businesses, and managed IT services becomes the standard term.
- 2006Attendees at the SMB Nation conference are still calling managed services a crazy new business model. It was neither.
- TodayThe stack has moved through cloud and SaaS, and the constant has never changed: a provider accepting continuing responsibility for an outcome, in writing.
The thread through all of it is the service level agreement. From the EDS facilities management contracts of the 1960s to the IBM and Kodak deal of 1989 to a modern managed services agreement, the model is a provider accepting continuing responsibility for an IT outcome rather than merely selling labor when something breaks. Robert Couture, who helped build IBM Global Services, has said plainly that the industry did not call it managed services at first. It called it IT outsourcing. The technology changed. The core idea did not.
I have been running ASAP Computer Services since 1999, which means I did not read about this transition afterward. I sold my way through it. In the early 2000s the agreements we wrote were called IT service contracts. Then Kaseya, ConnectWise, and a wave of remote monitoring and management platforms arrived, and with them a new name: managed IT services. The rename stuck because something real had changed underneath it, and that something is the subject of the next section.
The Real Difference Is Sovereignty
The old model had a trap in it, and anyone who leased a phone system in the nineties knows exactly what it was. The firm that managed your technology often owned your technology. Phones, computers, sometimes the server in the closet: provided as a service, owned by the provider, and clawed back the moment you stopped paying. You were not building an IT environment. You were renting your own dependency.
A true managed IT services agreement inverts that ownership, and this is the most practical test you can apply to any proposal in front of you. The customer holds title to the hardware. Software licenses are purchased in the customer’s name. The administrator accounts, the Microsoft 365 tenant, the domain registrations, the keys to everything: they belong to the business and are held internally, with access shared with a trusted partner so the work can be handled by people who do it for a living. If the relationship ever ends, everything stays exactly where it always was. With you.
That is the line we draw at ASAP, and it is why this page keeps using the word sovereignty. Sovereignty of data and control stays with the client. Management is our responsibility. Your data, your accounts, your hardware. Our job is keeping all of it healthy, secure, and boring, so the dependency on technology gets handled by professionals and the business gets back to the business.
Who Managed IT Services Are For
Managed IT services fit organizations of roughly 5 to 200 users. Below that, needs are usually simple enough for occasional support. Above that, companies typically build internal departments, often with an MSP handling co-managed overflow, projects, and escalations.
The industries we serve across San Antonio, Central Texas, South Texas, and the Texas Hill Country run the full width of the local economy: construction firms and specialty contractors, the trades, veterinary practices, medical and dental offices, legal and finance, wholesale and retail, manufacturers, energy companies, customs brokers and other government-adjacent operations, and small and mid-sized service and product companies of every kind.
Compliance is a first-class concern rather than an afterthought, because many of those industries carry regulatory obligations for the data they hold, from patient records to financial information to controlled trade documentation. The common thread is not the industry. It is that the business takes its technology seriously and wants a local presence accountable for it.
When Managed IT Is Not the Right Fit
Managed IT is not the right answer for everyone, and an informational page should say so. It is usually the wrong fit for very small operations with a handful of cloud accounts, no server, no compliance exposure, and no real cost when a laptop is down for a day. It is the wrong fit for a business that only wants the cheapest possible emergency visit and accepts the risk in between. And it is unnecessary for organizations that only need a defined project, such as an office buildout or a cabling installation, though that is work we do as well. If the honest answer for your situation is one-time support, our published hourly rates cover that with no contract required.
Questions People Ask While Researching
What is the difference between managed IT services and break-fix support?
Break-fix is reactive: something fails, you call, you pay by the hour, and the clock starts after the damage has already begun. Managed IT services are proactive: systems are monitored continuously, maintenance happens on a schedule, and support is covered by a flat monthly fee under a service level agreement. The incentives differ too. A break-fix provider earns money when you have problems. A managed services provider earns the same fee either way, so a quiet, stable network is in everyone’s interest.
Who owns the hardware, licenses, and accounts under a managed IT services agreement?
The client does, and this is the test of a true managed services agreement. Title to the hardware, the software licenses, the administrator accounts, the Microsoft 365 tenant, and the domain registrations all belong to the business and are held internally. The provider receives shared access so the environment can be managed professionally. If the relationship ends, everything stays with the client. If a provider owns the equipment and can take it back when the contract ends, that is a lease with a help desk, not managed IT.
When did managed IT services start?
The business model dates to the early 1960s, when EDS began running clients’ data processing under long-term fixed-price contracts, a practice then called facilities management. IBM took the model mainstream with its 1989 Kodak agreement under the name IT outsourcing. The term managed IT services emerged in the late 1990s and became standard in the early 2000s, when remote monitoring and management platforms such as Kaseya and ConnectWise made flat-fee IT management practical for small and mid-sized businesses.
What does a managed services provider actually do day to day?
Day to day, a managed services provider answers help desk requests, monitors servers and network equipment around the clock, applies security patches during off-hours, runs and verifies backups, and manages firewalls, endpoint protection, and user accounts. Over the longer term, the provider advises leadership on technology budgets, hardware replacement cycles, and compliance requirements.
What size and type of business uses managed IT services?
The model fits organizations of roughly 5 to 200 users, across construction and specialty contracting, the trades, veterinary, medical, dental, legal, finance, wholesale, retail, manufacturing, energy, customs brokerage, and other service and product businesses. The common thread is dependency: any organization that cannot afford to improvise through an outage, or that carries compliance obligations for the data it holds, is a candidate.
Why are managed IT services priced as a flat monthly fee?
Because the flat fee aligns incentives. A provider paid by the hour earns more when systems fail. A provider paid a fixed monthly amount earns more when systems stay healthy, because prevention costs less than firefighting. The model also converts unpredictable emergency spending into a predictable operating expense that a business can budget. ASAP Computer Services publishes its managed services rates openly instead of gating them behind a sales call.
Past the Research Stage?
If this page did its job, you now know what managed IT services are, where they came from, and the ownership question to put in front of any provider, including us. When you are ready for the commercial half of the conversation, our managed IT services in San Antonio page covers plans, monitoring, and what working with us looks like, or reach the team at 210-497-1424 and our contact page.
