Pricing Pass-Through IT Field Support Services in an MSP Contract

Quick answer: MSPs price subcontracted IT field support services in four common ways: pass-through plus a coordination fee, cost plus markup, bundled into the managed services fee, or fixed per-visit or per-site pricing. With 63% of MSPs ranking profitability a top priority, the model must account for partner minimums, travel, after-hours multipliers and cancellation terms, or margin disappears on short and remote visits.

When an MSP subcontracts onsite work, pricing becomes a two-sided problem. The field partner charges the MSP under one set of rules; the MSP charges the client under another. If those rules do not line up, the MSP absorbs the difference on every ticket. Partners such as Techmate provide onsite IT support services through vetted technicians in 450+ US cities, which lets an MSP serve clients far outside its own drive radius. The pricing still has to work.

The stakes are rising. Canalys projected the global managed services market would reach $608 billion in 2025 (Canalys via Business of Tech, 2025), and Kaseya’s survey found 63% of MSPs rank profitability as a top or high priority (Kaseya State of the MSP via Channelweb, 2025). As MSPs win clients with more locations, subcontracted field work becomes a bigger share of the cost base.

This guide covers the common pricing models for pass-through field work, the partner terms that quietly erode margin, how to choose a model, and how to write client contracts and invoices that protect you.

What are the pricing models for subcontracted IT field support services?

Four models cover almost every MSP arrangement. Each shifts a different risk onto a different party.

Model	How it works	Pros	Cons	Who carries the risk
Pass-through plus coordination fee	Client pays partner cost plus a flat fee per ticket	Transparent; easy to explain	Exposes partner costs; margin capped by the fee	Client carries volume and duration risk
Cost plus markup	Client pays partner cost plus a percentage	Simple; margin scales with work	Client may question the markup	Client carries most risk; MSP carries collection risk
Bundled	Onsite work included in the managed services fee	Simple for the client; sticky contracts	MSP carries volume risk	MSP
Fixed per visit or per site	Client pays a set price per visit or per site	Predictable for both sides	MSP carries duration risk	MSP carries duration risk; client carries volume risk

Many MSPs combine models: routine onsite work bundled for local sites, per-visit pricing for remote sites and project pricing for rollouts. That hybrid is often the most honest reflection of the real cost structure, because a visit to a branch 20 minutes from your office and a visit to a site three states away are not the same product.

Pass-through plus coordination fee

This is the cleanest model for clients that want to see exactly what they pay. The coordination fee covers your dispatch effort: scoping the ticket, booking the technician, briefing them, monitoring the visit and closing it out. Price the fee to cover that labor honestly. If your team spends meaningful time per ticket on coordination, a token fee will lose money even though the model looks transparent.

Cost plus markup

Markup is simple and scales automatically as visits get longer or more frequent. The weakness is optics: clients sometimes compare the partner’s cost to your invoice and question the gap. Frame the markup as covering coordination, quality control, accountability and the risk of failed visits, which is true.

Bundled into managed services

Bundling is attractive in sales conversations because the client sees one number. It is also where MSPs lose the most money, because one bad quarter of hardware failures at remote sites can erase a year of margin. Bundling works when onsite needs are predictable and close to home, and only with defined limits.

Fixed per visit or per site

Fixed pricing works well for repeatable tasks: a workstation swap, a printer install, an access point replacement. It works poorly for open-ended troubleshooting. If you use it, define what the fixed price includes (for example, up to a set amount of onsite time) and what happens when the job runs long.

What partner terms affect MSP margin?

The partner’s rate card is only part of the cost. The terms around it decide whether a ticket is profitable.

Partner term	What it does to cost	How to protect margin
Minimum billable time	Short visits cost more than the task suggests	Quote short tasks at the minimum; bundle small tickets per site
Billing increments	Rounding up increases cost on every visit	Model the rounding in your client price
Trip charges and travel	Remote sites cost more	Price remote sites separately or by tier
After-hours multipliers	Change windows and weekends cost more	Define after-hours rates in the client contract
Cancellation and failed-visit fees	Client-caused failures hit the MSP	Pass client-caused fees through
Parts markup	Adds to pass-through cost	Decide whether you, the client or the partner supplies parts

Mirror these terms in your client contract where possible, so client-caused costs pass through. See minimums, trip charges, and cancellation fees.

How do you choose the right pricing model for a client?

Start with two questions: how predictable is the client’s onsite demand, and how much transparency does the client expect? Then apply these rules of thumb:

Predictable, local, low-volume onsite needs: bundle into managed services with a defined allowance.
Unpredictable onsite needs at remote sites: per-visit pricing or cost plus markup.
Clients who want transparency: pass-through plus coordination fee.
Projects: fixed per-site or project pricing. See fixed-fee vs. time-and-materials IT projects.

A short decision checklist before you quote:

List every client site with its distance from your nearest staff and its typical onsite volume.
Pull the last 12 months of onsite tickets, if the client has history, and sort them by site and type.
Separate break-fix, scheduled maintenance and project work, since they deserve different models.
Confirm your partner’s minimums, increments, travel rules and after-hours terms for those locations.
Choose a model per category, not one model for the whole account.

For a broader view of when on-demand field work beats a fully managed approach, see our comparison of on-demand vs. managed IT.

How should bundled pricing be protected?

If onsite work is bundled into a monthly fee:

Define how many visits or hours are included per month or quarter.
Exclude or separately price remote sites, after-hours work and projects.
State what counts as a visit (for example, one ticket at one site on one day).
Review actual usage quarterly and adjust the allowance or the fee.
Track cost per client to catch unprofitable accounts. See how to calculate your true cost per site.

A bundled contract without an allowance is effectively unlimited field support at a fixed price. That can work for a single-office client next door. It rarely works for a client with branches spread across several states.

How should client contracts reflect partner terms?

Your client contract should be a mirror of your partner agreement, adjusted for your margin. At a minimum:

Pass through failed-visit and late cancellation fees caused by the client.
Define after-hours rates for client-requested work.
Price remote site travel explicitly or through per-site rates.
Include site readiness obligations for the client. See the site readiness checklist.
Set approval thresholds for work exceeding estimates.
Specify who supplies parts and how parts are billed.
Define what documentation the client receives after each visit.

What does a failed visit usually look like?

Most failed visits are not technical. The technician arrives and the building is locked, the site contact has gone home, the closet key is missing, the replacement part never shipped or the ISP circuit was not delivered. Each of those is a client or third-party failure, and your contract should say so. Site readiness obligations, such as a named onsite contact, confirmed access and confirmed parts delivery, are your best defense.

How do you invoice IT field support services cleanly?

Clean invoicing is where many MSPs leak margin without noticing. A monthly routine:

Require partner invoices with ticket numbers, sites, arrival and departure times and rate details.
Reconcile partner invoices to client tickets monthly. See how to audit your IT services invoices.
Flag any partner charge that has no matching client ticket, or a client ticket that was never billed.
Bill client-caused fees in the same cycle, while the facts are fresh.
Present client invoices in your format with the level of detail your model requires.

In pass-through models, show line-level detail. In bundled models, show visits used against the allowance, so overage conversations are never a surprise.

What margin mistakes are most common?

Bundling unlimited onsite work without usage caps: one busy quarter wipes out the margin.
Ignoring partner minimums when quoting short tasks: a quick cable swap is billed at the minimum.
Absorbing client-caused failed visits: every locked door is a direct loss.
Flat pricing for remote sites that incur trip charges: distant sites subsidize nothing and cost more.
Vague scopes: a field technician who arrives without clear instructions spends paid time figuring out the job.
No quarterly review of actual onsite costs per client: unprofitable accounts stay unprofitable.

How do you pick a field partner that makes pricing predictable?

Your pricing model is only as stable as your partner’s terms and performance. When evaluating a provider of nationwide IT field services, look for:

Coverage where your clients are: a large network reduces travel charges at remote sites. Techmate’s network includes 7,000+ technicians across 450+ US cities.
Clear written terms: minimums, increments, travel, after-hours and cancellation rules you can mirror.
First-visit resolution: repeat visits are the hidden cost in every model. Techmate reports a 97% resolution rate.
Customer experience: the technician represents your brand onsite. Techmate holds a 4.7 out of 5 CSAT.
Usable documentation: notes, photos and times that support clean invoicing.

See how Techmate dispatch works for the process from request to closeout, and what a field technician does for a realistic view of onsite scope.

How do MSPs report IT field support services to clients?

Report onsite work by site, with tickets, visit times, outcomes and costs, in the same format as your managed services reports. Useful metrics include visits per site, first-visit resolution, failed visits by cause and cost per site over time. Clear reporting helps clients see the value of onsite work in their contract and makes renewal and repricing conversations easier, because both sides are looking at the same numbers.

The bottom line

Pass-through field work can be profitable for MSPs when pricing is designed deliberately. Choose a model that fits volume and client expectations, mirror partner terms in client contracts, protect bundled pricing with limits and reviews, and reconcile invoices monthly. For longer engagements that need a dedicated onsite person, consider IT staff augmentation services priced as their own line item.

Techmate partners with MSPs to provide field technicians across 450+ US cities. See Techmate partners or contact us.

Frequently Asked Questions

How do MSPs charge for subcontracted onsite work?

Most MSPs use one of four models: pass-through plus a coordination fee, cost plus a percentage markup, onsite work bundled into the managed services fee, or fixed per-visit or per-site pricing. Many combine them, bundling local routine work, pricing remote visits individually and quoting projects separately, so each type of work carries a price that reflects its real cost.

What markup do MSPs add to field services?

It varies by MSP, market and service model, so there is no single standard. Set the markup to cover your coordination effort, quality control, the risk of failed or repeat visits and your target margin. Always account for partner minimums, billing increments and travel charges before settling on a percentage, or short and remote visits will lose money.

Should onsite visits be included in a managed services fee?

They can be, for predictable local needs, as long as the contract defines an allowance of visits or hours. Price remote sites, after-hours work and projects separately, and review actual usage every quarter. Without an allowance, bundling turns into unlimited field support at a fixed price, which is the most common way MSPs lose margin on onsite work.

How do MSPs protect margin on field services?

Mirror partner terms in client contracts, pass through client-caused cancellation and failed-visit fees, and price remote sites explicitly. Write clear scopes so technicians do not spend paid time diagnosing the request. Reconcile partner invoices against client tickets monthly and review actual onsite cost per client every quarter so unprofitable accounts are caught early.

Who pays for a failed onsite visit in an MSP arrangement?

It depends on the contracts, which is why they need to line up. MSPs should pass client-caused failures (no access, no contact, missing parts) through to the client and hold partners accountable for partner-caused failures. Site readiness obligations in the client contract make it clear who is responsible before anyone is dispatched.

How should MSPs reconcile field partner invoices?

Match every partner invoice line to a client ticket, confirm rates, times and travel against the agreed terms and flag discrepancies in the same month. Look for partner charges with no client ticket and client tickets that were never billed. Bill client-caused fees in the same cycle so the details are still fresh for both parties.

Should MSPs show clients the cost of field services?

It depends on the model. Pass-through and cost-plus models show partner costs by design. Bundled and per-visit models present onsite work as part of the MSP’s own pricing, so the client sees visits used and outcomes rather than partner rates. Either way, consistent site-level reporting builds trust.

Want a second opinion on how your onsite costs and client pricing line up? Book a free 30-minute IT support audit and we will walk through your sites, partner terms and coverage gaps with you.