1 de noviembre de 2026 • Centoffer Editorial • 19 min de lectura
Field IT Service Pricing Models Compared: Hourly, Fixed-Fee, Per-Ticket and Retainer
Field IT Service Pricing Models Compared: Hourly, Fixed-Fee, Per-Ticket and Retainer
Ask three field IT providers to quote the same job and you will often get three answers that cannot be compared. One quotes an hourly rate with a two-hour minimum. One quotes a fixed fee per visit. One proposes a monthly retainer that “covers everything” up to an allowance. Each number looks reasonable on its own, and each hides a different set of assumptions about who pays when a job takes longer than expected, when an engineer has to come back, or when the request arrives at 2 a.m. on a Sunday.
Field IT service pricing — what you pay for engineers to go on site and install, repair, move or check IT equipment — is mostly a question of risk allocation. Every pricing model decides who carries the cost when reality does not match the plan. Choose the wrong model for the type of work and you either overpay for a risk premium you did not need, or you sign a blank cheque.
This guide compares the four core models — hourly (time-and-materials), fixed-fee, per-ticket and retainer — explains what drives a field IT price underneath the headline rate, works through a twelve-month example, and gives a checklist for reading quotes. It is written for IT procurement and operations leaders buying on-site support across many branches, stores or offices, often in more than one country.
What are the main field IT service pricing models?
There are four core field IT service pricing models: hourly (time-and-materials), fixed-fee per task or project, per-ticket (per-incident), and retainer (subscription). Most real contracts combine two or three of them.
In a sentence each:
- Hourly / time-and-materials (T&M). You pay for the engineer’s time on site (and often travel), plus any parts, at agreed rates.
- Fixed-fee. You pay a pre-agreed price for a defined task or project, regardless of how long it actually takes.
- Per-ticket / per-incident. You pay a set price each time a ticket results in an on-site visit, usually by severity or service type.
- Retainer / subscription. You pay a recurring fee for a reserved block of capacity or a defined scope of coverage, whether or not you use all of it.
The differences matter because field work is variable in a way remote support is not. Travel times differ by site, access to a building can be delayed, a “simple” device swap can turn into a cabling fault, and a part can fail to arrive. Each model handles that variability differently.
How does hourly (time-and-materials) pricing work — and when does it make sense?
Hourly or time-and-materials pricing charges for the actual time an engineer spends on the job at an agreed rate, plus materials. It makes sense when the scope of work genuinely cannot be estimated in advance, such as fault diagnosis or an unfamiliar legacy environment.
A typical hourly field IT quote contains:
- A base hourly rate, often tiered by engineer skill level (for example, desk-side technician versus network engineer).
- A minimum billable period per visit — commonly one to four hours — because the provider has to cover travel and scheduling even for a ten-minute task.
- Travel charges, either as billable travel time, a mileage rate or a flat zone fee.
- Time-of-day multipliers for after-hours, weekend and public-holiday work.
- Materials at cost plus a handling percentage.
The structural weakness of hourly pricing is well documented in public procurement rules. The U.S. Federal Acquisition Regulation, which governs how the U.S. government buys services, says a time-and-materials contract “provides no positive profit incentive to the contractor for cost control or labor efficiency” (FAR 16.601). For that reason, the FAR allows T&M only when it is “not possible at the time of placing the contract to estimate accurately the extent or duration of the work”, requires a ceiling price the contractor exceeds at its own risk, and requires active surveillance of the contractor’s performance.
Those three safeguards translate directly to commercial field IT buying:
- Use hourly pricing only where scope is genuinely unknown. Diagnostics, intermittent faults, legacy equipment, and “go and see what’s wrong” visits.
- Always set a not-to-exceed ceiling per job, after which the engineer must stop and request approval.
- Require time evidence. Check-in and check-out timestamps, ideally geotagged, so billed hours match time on site.
When hourly works well: low volumes, unpredictable diagnostic work, short-term projects with evolving scope, and pilots where you are still learning how long tasks take.
When it works badly: high-volume repeatable work (you pay for every inefficiency), and any environment where you cannot verify time on site.
What is fixed-fee pricing for field IT work?
Fixed-fee pricing sets a single, pre-agreed price for a defined deliverable — a laptop swap, a printer install, a point-of-sale device replacement, a site survey or a whole store opening — regardless of how long the work takes. It suits repeatable, well-scoped tasks.
Fixed-fee is the mirror image of hourly. The FAR describes a firm-fixed-price contract as placing “upon the contractor maximum risk and full responsibility for all costs and resulting profit or loss”, and notes it “provides maximum incentive for the contractor to control costs and perform effectively” (FAR 16.202-1). In field IT terms, the provider is rewarded for sending a well-prepared engineer with the right part who finishes the job in one visit.
That incentive is the main reason buyers like fixed fees, but it comes with conditions:
- The scope must be written down precisely. “Install workstation” is not a scope. “Unbox, image-verify, connect, test peripherals, remove packaging, update asset record, capture customer sign-off” is.
- There must be a clear out-of-scope rule. What happens if the engineer arrives and finds the network port is dead? A good fixed-fee contract defines a change process — usually a pre-priced add-on or a switch to capped hourly time.
- The provider will price in a risk premium. Because the provider absorbs overruns, a fixed fee is often higher than the average hourly cost of the same task. You are paying for certainty.
Fixed-fee pricing is particularly well suited to IMAC work (install, move, add, change), rollouts, store openings and closures, and scheduled checks, because these tasks repeat across hundreds of sites with only small variations.
When fixed-fee works well: repeatable tasks, multi-site rollouts, budgeting certainty, and any situation where you want the provider to own efficiency.
When it works badly: genuinely unknown scope, where the provider either refuses to quote or quotes defensively high.
How does per-ticket (per-incident) pricing work?
Per-ticket pricing charges a set fee each time a support ticket requires an on-site visit, usually banded by severity, response time or service type. It suits break-fix work whose volume is unpredictable but whose individual visits are broadly similar.
Per-ticket pricing is, in effect, a fixed fee applied to incidents rather than planned tasks. A typical per-ticket rate card might specify a price for a next-business-day visit, a higher price for a same-day or four-hour response, and a premium for out-of-hours dispatch, each including a standard amount of on-site time (for example, up to two hours) before hourly overtime applies.
It works because most break-fix visits — a dead monitor, a jammed receipt printer, a failed access point, a desk phone that will not register — share a similar shape: travel, diagnose, swap or repair, test, close. Pricing them per incident gives the buyer predictability per unit while leaving total volume variable. (Our break-fix glossary entry explains how break-fix differs from managed services.)
The key design questions in a per-ticket contract are:
- What counts as one ticket? If an engineer fixes three devices at the same branch on one visit, is that one ticket or three? Define it.
- What happens on a repeat visit? If the fault recurs within, say, seven days, a fair contract treats the return visit as part of the original ticket, not a new billable one. This protects your first-time-fix interest.
- What is included in the per-ticket price? Travel, a set amount of on-site time, standard consumables — and what triggers extra charges.
- Who decides severity? Price bands by severity only work if severity is defined by business impact and set by the buyer’s service desk, not upgraded by the provider.
When per-ticket works well: distributed break-fix across many sites, variable volumes, and buyers who want to pay only for what happens.
When it works badly: very low-volume sites where a provider cannot justify coverage at a per-incident price, or complex incidents that routinely exceed the included time.
What is a retainer or subscription model for field IT?
A retainer is a recurring fee — usually monthly — for reserved capacity or a defined scope of coverage, such as a set number of engineer days, a dedicated on-site engineer, or unlimited break-fix for a defined list of assets. It suits steady, predictable demand and situations where guaranteed availability matters more than unit price.
Retainers come in three common forms:
- Block-of-hours retainer. You pre-buy, say, 40 engineer hours a month at a discounted rate. Unused hours may roll over for a limited period, or may expire.
- Dedicated resource retainer. A named engineer (full-time or part-time) is assigned to your site or region. This is close to staff augmentation.
- Coverage subscription. A per-device or per-site monthly fee covers all break-fix (and sometimes preventive) work on a defined asset list, with exclusions for misuse, projects and new installs.
The economic logic of a retainer is that the provider gets predictable revenue and can plan capacity, so it can offer a lower effective rate and faster guaranteed response. The buyer’s risk is under-use: if demand drops, you keep paying.
When a retainer works well: stable demand, high-criticality sites that need guaranteed response, environments where a familiar engineer adds real value (for example, complex retail or clinical sites), and multi-year programmes.
When it works badly: seasonal or volatile demand, newly acquired sites with unknown volumes, and contracts with no reporting on how the capacity was actually used.
Field IT service pricing models compared side by side
The table below summarises how each field IT service pricing model allocates risk and where it fits best.
| Factor | Hourly (T&M) | Fixed-fee | Per-ticket | Retainer |
|---|---|---|---|---|
| Who carries overrun risk? | Buyer | Provider | Provider (within included time) | Shared — provider on response, buyer on under-use |
| Budget predictability | Low | High per task | High per incident, variable in total | High (fixed monthly) |
| Provider incentive for efficiency | Weak | Strong | Strong | Moderate |
| Best for | Unknown-scope diagnostics, pilots | Rollouts, IMAC, surveys, store openings | Distributed break-fix | Steady demand, critical sites |
| Main risk to watch | Padded hours | Vague scope, change-order creep | Ticket splitting, repeat visits billed twice | Paying for unused capacity |
| Evidence you need | Timestamped on-site time | Completion against a defined checklist | One completion record per ticket | Monthly utilisation report |
| Typical SLA attachment | Response time only | Completion date | Response and resolution by severity | Response, resolution and availability |
Notice that the “evidence you need” row differs for each model. A pricing model is only as good as your ability to verify what you are paying for, which is why proof-of-delivery matters so much in field IT (see below).
What actually drives a field IT price?
Behind every field IT rate are the same handful of cost drivers. Understanding them helps you see why two quotes differ and where there is room to negotiate.
1. Engineer labour. The engineer’s wage is only the starting point. For reference, the U.S. Bureau of Labor Statistics reported a national median wage of $28.48 an hour for computer user support specialists in May 2023 (BLS Occupational Employment and Wage Statistics, May 2023). A billed field rate must also cover employment costs, insurance, tools, training, certifications, management and profit — and, crucially, the unbillable time between jobs. Wage levels differ widely by country and city, so field rates in Singapore, Sydney, Jakarta and Manila will not look alike.
2. Travel and geography. Travel time is often the largest single variable. A dense metro with many sites in a small area is cheap to serve; remote or island sites are not. Providers price this through zone fees, travel-time billing or minimum call-outs.
3. Response time. A next-business-day SLA lets a provider batch work and route engineers efficiently. A four-hour SLA forces it to keep engineers available and nearby, which costs more whether or not they are used.
4. Time of day. After-hours, weekend and public-holiday work usually carries a multiplier because it requires premium pay or on-call arrangements.
5. Skill level. A structured cabling or network specialist costs more than a desk-side technician. Matching skill to task — not sending a senior engineer to swap a mouse — is one of the easiest savings available.
6. Parts and logistics. Who supplies the part, where it is stocked, and who handles returns all add cost. Some providers mark parts up; some charge a handling fee; some require you to supply them.
7. Coordination overhead. Scheduling, site access, permits, customer contact, reporting and invoicing all take effort. Some providers bundle this into the rate; others charge a separate project-management or coordination fee.
8. Risk and uncertainty. The less the provider knows about your sites, the more contingency it builds into fixed prices. Good site data — addresses, access hours, contacts, asset lists — directly lowers quotes.
How much does downtime change the pricing decision?
Downtime cost is the counterweight to field IT price: the cheaper model is not the better one if it leaves sites down longer. For larger organisations, an hour of downtime on important systems is expensive. ITIC’s 2024 Hourly Cost of Downtime Survey, a web survey of more than 1,000 firms, found that the average cost of a single hour of downtime exceeds $300,000 for over 90% of mid-size and large enterprises (ITIC, 2024).
A single branch printer is not a data centre, and most field tickets will cost far less than that when they fail. The point for pricing is proportional: pay for speed only where downtime is expensive. A four-hour response on point-of-sale terminals at a flagship store may be worth every cent; the same SLA on a back-office scanner is not. Build your rate card by site tier and asset criticality rather than buying one premium SLA for everything.
Worked example: the same twelve months of work priced four ways
To show how the models behave, here is an illustrative example. The figures below are hypothetical round numbers chosen to make the arithmetic easy to follow; they are not market rates or Centoffer prices.
Scenario. A retailer has 40 stores in one country. Over twelve months it expects roughly:
- 200 break-fix visits (failed devices, printers, network kit), averaging 1.5 hours on site each;
- 80 planned IMAC tasks (new devices, moves), averaging 2 hours each;
- 10 diagnostic visits with unknown scope.
Option A — all hourly. Suppose a rate of $80 an hour with a two-hour minimum per visit. Break-fix visits bill at the minimum two hours (not 1.5), so 200 × 2 × $80 = $32,000. IMAC at two hours: 80 × 2 × $80 = $12,800. Diagnostics, say averaging four hours: 10 × 4 × $80 = $3,200. Total about $48,000, with real uncertainty — if diagnostic visits run long or IMAC tasks take three hours, the total rises.
Option B — per-ticket for break-fix plus fixed fee for IMAC, hourly for diagnostics. Suppose $140 per break-fix ticket (including up to two hours on site) and $150 per IMAC task. Break-fix: 200 × $140 = $28,000. IMAC: 80 × $150 = $12,000. Diagnostics at capped hourly: $3,200. Total about $43,200, and the first two lines are now predictable per unit.
Option C — retainer. Suppose a coverage subscription at $90 per store per month covering all break-fix, plus IMAC and diagnostics billed separately as in Option B. Retainer: 40 × $90 × 12 = $43,200. Add IMAC $12,000 and diagnostics $3,200. Total about $58,400. This is only good value if the buyer needs the guaranteed response the retainer buys, or if break-fix volume turns out much higher than 200.
What the example shows:
- The minimum billable period quietly inflated Option A, because most break-fix visits were shorter than the minimum.
- Option B priced each type of work with the model that fits it — the “mixed model” most multi-site buyers end up with.
- Option C’s value depends almost entirely on volume and on how much the guaranteed response is worth. At 200 tickets it is the most expensive; at 400 tickets the retainer line would stay flat while Option B’s break-fix line doubled.
Run your own numbers with your real volumes and real quotes. The shape of the comparison is usually more informative than the totals.
How do you choose the right pricing model for each type of work?
Choose the pricing model by the nature of the work, not by vendor preference. A practical rule set:
- Is the scope known and repeatable? Use a fixed fee per task (rollouts, IMAC, surveys, store openings and closures, scheduled checks).
- Is it reactive break-fix with broadly similar visits? Use per-ticket pricing banded by response time and site tier.
- Is demand steady and is guaranteed response critical? Consider a retainer for those specific sites or asset classes — and ask for a monthly utilisation report.
- Is the scope genuinely unknown? Use hourly pricing with a not-to-exceed ceiling and timestamped evidence.
- Is it a one-off project? Ask for a fixed project price with milestones, plus a pre-priced change-request rate.
- Are you operating in several countries? Keep one structure everywhere (same service catalogue, same SLA tiers, same evidence rules) and let only the rates vary by country and currency.
What hidden costs should you look for in a field IT quote?
The headline rate is rarely the full cost. Before comparing quotes, put every provider’s pricing through the same checklist:
- Minimum billable time per visit and per day.
- Travel: billed time, mileage, zone fees, tolls, parking, flights and accommodation for remote sites.
- Time-of-day multipliers: after-hours, weekends, public holidays — and how each is defined in local time.
- Aborted or failed visits: what you pay if the site is closed, the contact is absent or the part did not arrive.
- Rescheduling and cancellation fees and notice periods.
- Waiting time on site (for example, waiting for building access or a carrier technician).
- Parts: mark-up, handling fee, return logistics and who owns dead-on-arrival risk.
- Coordination or project-management fees, and whether reporting costs extra.
- Currency and invoicing: which currency you are billed in, who carries FX risk, and how many invoices you receive.
- Repeat visits: whether a return visit for the same fault is billable.
- Minimum commitments: annual volume commitments or termination fees in retainers.
Normalise every quote into the same unit — cost per completed task by type — before comparing. A provider with a lower hourly rate and a higher minimum can easily be more expensive.
How should SLAs and proof-of-delivery attach to each pricing model?
Pricing tells you what you will pay; the SLA tells you what you get for it; proof-of-delivery (POD) tells you whether you actually got it. POD is a verifiable completion record — typically photos, timestamps, geolocation and a customer sign-off — captured at the end of each visit (see our POD glossary entry).
Each model needs a slightly different evidence rule:
- Hourly: POD must include check-in and check-out times, so billed hours can be reconciled against time on site.
- Fixed-fee: POD must show completion against the agreed task checklist — photos of the installed device, test results, the updated asset tag.
- Per-ticket: one POD per ticket, linked to the ticket number, so tickets cannot be split or duplicated, and repeat visits can be detected.
- Retainer: a monthly utilisation and SLA report built from individual PODs, so you can judge whether the reserved capacity was worth it.
The SLA should be priced explicitly. Rather than accepting one blended rate, ask for each response tier separately — for example, next-business-day, same-day and four-hour — and attach service credits when a target is missed. Our guide to IT SLA management and service quality covers how to structure severity tiers and penalties.
The simplest rule of all: no POD, no payment. An invoice line without a completion record should not be payable. This one clause removes most of the disputes that make field IT pricing feel opaque.
How do mixed models work in multi-country programmes?
Most enterprises with distributed sites end up with a mixed model — fixed fees for planned work, per-ticket for break-fix, a few retainers for critical locations, and capped hourly for the unknown. The challenge is keeping that mix coherent across countries.
Common problems in multi-country field IT buying include:
- A different contract, SLA and invoice per country, each with its own definitions, so performance cannot be compared.
- Inconsistent units: one country bills per hour, another per visit, another per device per month.
- Currency noise: invoices in many currencies, with FX applied inconsistently.
- Uneven evidence: strong reporting in one market, none in another.
The fix is to standardise the structure and localise the rates. Define one service catalogue (task types and what each includes), one set of SLA tiers, one evidence standard and one invoicing format, then maintain a rate card for each country and currency. That way a store opening in Kuala Lumpur and one in Ho Chi Minh City are the same line item at different local prices, and your finance team can compare them directly.
How does Centoffer approach field IT service pricing?
Centoffer is a global IT field services platform — the Services OS™ — that connects enterprises and IT service providers with vetted field engineers for SLA-backed on-site work. Its approach to pricing follows the principles in this guide:
- Transparent, pre-agreed pricing. Rates are agreed before work is dispatched, using rate cards maintained by service category, region and currency.
- Pay-per-delivery. Work is tied to a completed visit, and every field visit closes with proof-of-delivery — photos and a digital customer sign-off — that feeds straight into billing.
- SLA-backed dispatch. Response and resolution are tracked against the agreed SLA in real time, so you can see what each pricing tier actually delivered.
- One contract, one SLA, one invoice. Consolidated, multi-currency billing keeps a multi-country estate on a single invoice instead of dozens of local contracts.
You can see how this works end to end on our global IT field services solution page.
Next steps: build a pricing model you can defend
Field IT service pricing gets simpler once you stop asking “which provider is cheapest?” and start asking “which model fits this type of work, and how will I verify it?” Map your work into planned tasks, break-fix, critical coverage and unknown-scope diagnostics; price each with the model that fits; normalise every quote into cost per completed task; and make proof-of-delivery a condition of payment.
If you are reviewing field IT pricing for a multi-site or multi-country estate, talk to the Centoffer team about structuring a single rate card with SLA-backed, proof-of-delivery work across your locations.