Fixed-fee managed IT: what changes compared with break-fix

Team IT al lavoro: modello di IT gestito a canone MSP

In a company with forty workstations the department printer stops working. Nobody calls the provider, because every call is charged: for three weeks the department prints on the floor above. Then a server stops, and that time the phone rings at once. In the break-fix model nobody checks systems while they work, so small warning signs grow undisturbed until something stops. That is the reason fixed-fee managed IT exists.

In the on-call model you pay for the intervention, when something breaks. The mechanism is easy to understand and carries a basic flaw: the provider earns when the company has a problem. Nobody says so and almost nobody takes advantage of it, but the economic incentive pushes that way, and the result shows in the activities nobody carries out. Postponed updates, backups nobody has ever tried to restore, documentation that does not exist because nobody pays for it.

The on-call support invoice is the small part of the cost

Break-fix invoices are visible and often modest. The real cost lies in items that no invoice records.

Part of it builds up in downtime hours spent waiting for someone to arrive. Another part concerns security, handled in response to emergencies rather than preventively. A third comes from the lack of history: every intervention starts from zero, because whoever arrives does not know what was done six months earlier. The fourth is unpredictability, which makes it impossible to budget for an item that swings from one year to the next.

There is also a less obvious effect, and in our experience it weighs more than all the others. When every call costs money, minor issues are not reported. The minor problem stays pending until it becomes a big one, and that is when the provider gets the call.

A case: the 2013 machine nobody had an interest in reporting

During an assessment we found a 2013 server still in production, running a department application. In another company we came across a machine decommissioned in the records but kept switched on, because every now and then someone asked to reconnect it to retrieve historical data.

Neither situation had caused an incident, and that is precisely why they had stayed in service. Someone in the company knew about them. Nobody, however, had taken them to management, because they did not fall within a billable intervention, and nobody had written down what would happen the day that hardware stopped.

The provider’s competence is not in question: what is missing is someone whose economic interest coincides with prevention. The move to a fixed fee reversed that logic within a few weeks. The two machines entered a monitored inventory with an end-of-life date written next to them: the first was replaced in a planned way together with the department application, the second switched off after the historical data was moved to a managed archive included in the backup. Continuous monitoring brought to management what previously lived only in one technician’s memory.

What goes into fixed-fee managed IT, item by item

A contract of this kind shifts the centre of gravity from repair to oversight. The scope includes continuous monitoring of servers, workstations and networks, scheduled updates, backup management with periodic restore checks, security oversight, user support and evolutionary maintenance.

The change shows on two fronts. The provider tackles recurring problems at the root, because repeating the same intervention becomes a cost for the provider rather than revenue. And the company ends up with a history it can consult: whoever intervenes knows what was done before, and whoever decides can read how much a system cost in a year.

In a direct comparison the two models differ on five aspects.

Aspect On-call support Fixed-fee managed IT
When you pay After a failure Every month, on a defined scope
Provider’s interest Earns when something breaks Earns if systems stay stable
Intervention history Starts from zero at every call Documented and available over time
Security Handled in response to emergencies Covered preventively, with periodic checks
IT budget Varies from year to year Predictable and comparable

MSP and MSSP: the difference only shows when there is an incident

The two acronyms often appear together in offers, and they indicate different scopes.

An MSP, Managed Service Provider, takes over the operational management of the infrastructure: servers, endpoints, networks, Microsoft 365 environments, backup, connectivity, monitoring, support and maintenance. It looks after the daily running of systems. An MSSP, Managed Security Service Provider, looks after protection: prevention, monitoring of security events, detection, incident response and improving the defensive posture over time.

The distinction matters because giving the two roles to different providers opens a grey area. When an attack succeeds, whoever runs the systems and whoever protects them tend to pass responsibility back and forth, and meanwhile the company stays stopped. We work as MSP and MSSP within a single contract precisely to close that gap: in an incident there is no second party to involve and no expert report to wait for. Those who want to examine the obligations concerning data processing will find the full picture in the article on GDPR IT requirements.

There is also a front that makes this choice ever harder to postpone: regulatory pressure. Large companies pass the security questionnaires they receive on to their suppliers, and small and mid-sized companies receive them along with orders, with questions on backup, access management and incident response that someone must be able to answer in writing. The NIS2 directive, whose text is available on EUR-Lex, widens the range of entities involved and shifts responsibility onto the supply chain. A provider working as MSP and MSSP under the same contract already holds the inventory, policies and logs those questionnaires ask for, and the answers become a data extraction instead of a frantic search.

How a fee is built, and what data the estimate starts from

Anyone assessing fixed-fee managed IT soon gets to the question of how the amount is calculated. Three variables determine it, and it is useful to know them before reading a proposal.

  • The number and type of devices to manage: servers, workstations, network devices, mobile devices.
  • The services within scope, from basic monitoring up to continuous security oversight.
  • The response times the provider commits to, by severity, and the hours of coverage.

A first estimate can be built remotely, starting from the figures the company declares: workstations, servers, active services. The final figure comes after checking the infrastructure, because unchecked assumptions are paid for later, in the form of activities excluded from the contract or times different from those expected.

The right benchmark for the fee is the sum of interventions, downtime and risks left uncovered in the previous year. Almost every company has this data in its accounts and almost none has ever put it together in a single statement.

Five points on which contracts only look alike

Managed service proposals use similar descriptions and differ in the details that determine their value. On these five points it pays to demand explicit answers, whichever provider presents the offer.

  • What the fee includes and what is billed separately. The most common grey area concerns evolutionary projects and new installations.
  • Which response times the contract states, by severity, and what happens when they are not met.
  • During which hours the service operates and who handles requests outside them.
  • Who holds system credentials and documentation, and what stays with the company if it changes provider.
  • How often someone tests restores, and who keeps the evidence of those tests.

The last two items say more than any brochure: a provider who hands over documentation and credentials and keeps evidence of restore tests is working to be renewed every year rather than to be hard to replace.

Serverless on site and DaaS: two terms to clarify before signing

When a project talks about reducing or removing physical servers from the premises, the term serverless has nothing to do with its technical meaning in software development. It means moving workloads to managed infrastructure, with less hardware to maintain on site and fewer constraints on the server room. This is where fixed-fee managed IT meets the cloud, two areas covered by the same business units, and it pays to tackle the two choices together rather than a year apart.

Device as a Service applies the same logic to workstations: devices are used as a service instead of being bought, with supply, configuration, lifecycle management and replacement included. The formula pays off when the fleet is mixed and must be renewed anyway, when replacements are frequent, or when management prefers to turn an investment into a predictable operating cost. The best time to assess it is when the fleet is renewed: that is when the advantage shows in full.

How the move to fixed-fee managed IT happens, week by week

The process starts before signing, with an assessment that captures hardware, licences, backups, access and critical issues. This is the phase in which situations like those described above emerge, and it lets the company assess what it is buying before committing.

From there the scope is defined, priorities are set and the fee is built. The first weeks are used to clear the backlog, and it is worth planning for it: a contract started on an infrastructure that is not aligned generates an initial number of interventions above average, and a serious provider says so beforehand instead of presenting it as a surprise.

In the projects we run, the assessment is the phase we invest most time in, because it determines whether the contract will be sustainable for both sides. We built the method at Aesir Srl on projects across Italy and, on specific request, in Switzerland, the United Kingdom and the United States, with an in-house SOC and ISO 9001 and ISO/IEC 27001 certifications: the same standards our customers find themselves having to demonstrate to their own customers.

Frequently asked questions

Does fixed-fee managed IT completely replace on-call interventions?

A fixed-fee managed IT contract covers the activities defined within its scope. New projects, migrations and extraordinary installations are quoted as dedicated activities, with scope, timing and responsibilities written into the contract.

What is the difference between MSP and MSSP?

An MSP manages the operation of the IT infrastructure, an MSSP looks after its security. The two roles can sit with different providers, and keeping them together reduces grey areas in incident management.

What happens to existing providers?

There is no need to replace them all. In many projects we coordinate the existing ones, for example the ERP or connectivity provider, reducing hand-offs between contacts.

How is the effectiveness of the service measured?

With a few concrete indicators: the number of outages that stopped work, average response time, the share of devices up to date, and the documented outcome of the latest restore test. If they do not improve after six months, the contract should be revised.

Let’s talk

The quickest way to assess whether fixed-fee managed IT pays off is to add up last year’s support invoices and the downtime hours recorded. It is a rough calculation, and it is usually enough to guide the decision.

If you would like to explore the topic or assess your company’s situation, fill in the form at the bottom of the page or write to support@aesir-tech.it: we will book a free consultation and start from your numbers.

Vuoi parlarne applicato alla tua azienda?

Ti rispondiamo con l’esperienza di progetto, non con una brochure.

Request a call