IT support

Monthly flat fee or billing by the hour?

Both models are legitimate. They differ in who carries the risk, when somebody turns up and what incentive your provider has to fix problems for good.

The short answer

Is an IT flat fee or an hourly rate better?

Billing by effort suits businesses with few workstations and uncritical IT: you only pay for what happens. A flat fee suits the moment outages genuinely disrupt operations — it usually contains monitoring, maintenance and updates, exactly the work that gets postponed under hourly billing. The decisive point, however, is not the model but the scope: what is included, what is billed on top, how fast is the response, and what happens when hardware fails? Two offers only become comparable once those four points are in writing on both sides. NDVDL works with full-service support including hardware replacement and states up front what is not included.

The essentials in four points

  • Hourly billing rewards reaction, a flat fee rewards prevention — that is the real difference, not the price.
  • Without a defined scope a flat fee is just a word; without a response time an hourly rate is not a commitment.
  • Recurring work — updates, backup checks, monitoring — is the first thing postponed under hourly billing.
  • Four details decide the comparison: scope, response time, handling of hardware failure and notice period.
01

How billing by effort works out

Under the hourly model, cost only arises once something happens. That is honestly calculated and often enough for small businesses with uncritical IT: anyone with three workstations who could survive a day without file access does not need to fund permanent support.

The catch is the incentive. Preventive work — installing updates, checking backups, reviewing logs — creates cost without solving a visible problem. Those items are therefore postponed regularly, and by both sides: the client wants no invoice without a reason, the provider wants no argument about it. Two years later the state of the IT is the sum of those postponements.

  • Fits few workstations and uncritical processes
  • No fixed monthly cost, but no committed availability either
  • Prevention structurally falls behind
02

What a flat fee should cover

A flat fee only becomes one when it states what it covers. The usual core is monitoring of the systems, installing updates, checking the backup, resolving incidents and a named contact. What is not included — new purchases, moves, projects, work outside business hours — belongs in there just as explicitly.

The advantage lies in reversing the incentive: if incidents are covered by the price, the provider has an interest of their own in there being none. That is why monitoring and maintenance are a matter of course in a flat-fee contract — not out of generosity, but because they pay off for both sides.

  • Monitoring, maintenance, updates and incident resolution as the core
  • State explicitly what is not included
  • The incentive sits on avoidance rather than on billable hours
03

How two offers can really be compared

Price is the least meaningful figure in a support offer as long as the services underneath differ. Four details make offers comparable: which systems and how many devices are covered? Within what time is an incident responded to — and does that mean response or resolution? What happens when a device fails: replacement, loaner or a new purchase billed to you? And how long does the contract tie you in?

The fourth question is the most frequently overlooked and the most important in a dispute. A support contract you can only exit at year end with six months' notice is a different decision from one with a monthly notice period — however good the first conversation was.

  • Scope: which systems, how many devices, which sites
  • Response time — and whether response or resolution is meant
  • Hardware failure: replacement, loaner or new purchase?
  • Term and notice period
04

What neither model contains

Neither a flat fee nor an hourly rate replaces infrastructure that holds. A network without segmentation, a backup without a tested restore or a server room without cooling remain building sites even if somebody looks after them regularly. Support maintains the state; it does not improve it on its own.

That is why every engagement should start with an inventory and an honest finding: what is in order, what is missing, what is a risk. Signing a flat fee without having seen that finding means buying support for a state neither side knows.

  • Support preserves the state — it does not replace missing infrastructure
  • Inventory before signing, not after
  • Projects and new purchases are separate items in both models

What we advise businesses

With few workstations and IT whose failure you could absorb for a day, billing by effort is the more honest solution — provided maintenance and backup checks are still commissioned regularly. As soon as an outage stops the business, the flat fee is no longer a comfort but the cheaper option, because it contains the work that prevents outages. In both cases compare scope, response time, hardware arrangement and notice period rather than price. And have someone look at what is actually there first: our first conversation including the findings costs nothing.

How does it look at your site?

We look at your situation and say honestly which option fits — including when that is the smaller one.

footer.solutions.items.undefined

We look at your IT before you sign anything

Inventory, an honest finding and a proposal that fits your business — free and without obligation.

Rather talk it through? Call us — you reach someone who knows the technology.

+43 800 007075

Your data is used solely to process your inquiry.

Follow-ups

What else we get asked about this

Monitoring of the important systems, installing updates, regular verification of the backup, resolving incidents within the agreed scope and a named contact. The counter-list matters just as much: new purchases, projects, moves and work outside business hours are usually not included and should appear explicitly as separate items.

In a month without incidents, yes. Over the term it contains the preventive work that usually does not happen under hourly billing — so the comparison is not flat fee versus zero, but flat fee versus the consequences of skipped maintenance. For businesses that stop working during an outage, that calculation tips quickly.

Usually the time within which somebody takes on the problem — not the time until it is solved. That is a material difference and should be named clearly in the contract. It is also worth recording during which hours the commitment applies and how an incident is reported in the first place.

This is the question that separates offers most. The range runs from 'new purchase at the client's expense' through 'loaner for the duration of the repair' to support that includes the replacement. NDVDL works with full-service support including hardware replacement — what belongs to it in the individual case is settled before signing.

Yes, and it is often the most practical form: a flat fee for monitoring, maintenance and incident resolution, while projects, rebuilds and new purchases are billed by effort. The only important thing is that the boundary between the two is defined beforehand rather than negotiated afterwards.

We look at your IT before you sign anything

Inventory, an honest finding and a proposal that fits your business — free and without obligation.

Request a first consultation+43 800 007075