"How much for someone to come fix this" is a simple question with a surprisingly variable answer, and most of that variability isn't arbitrary — it comes down to geography, contract structure, and what "onsite support" actually includes. Here's what actually drives the number in a region like the Fraser Valley, where "local" can mean anywhere from Abbotsford to Chilliwack to Langley to Mission.
Two pricing models, and why they produce different numbers
Break-fix / hourly dispatch. You call when something's broken, a technician comes out, you pay for the visit plus time on site. In the Fraser Valley, expect something in the range of $120–$180/hour for onsite technical work, often with a minimum call-out (commonly 1-2 hours) to cover travel. A same-day or emergency dispatch typically costs more than a scheduled next-day visit. This model looks cheap when nothing's broken and expensive exactly when you need it most — which is the core problem with it as a primary strategy.
Retainer / managed service with onsite included. You pay a predictable monthly amount that bundles remote support with a defined amount of onsite coverage — scheduled visits, a response-time SLA, and often no separate charge for routine onsite work within the plan. This is usually priced per-user or per-device rather than per-incident, and it converts an unpredictable expense into a budgeted one. The tradeoff is you're paying something even in a quiet month.
Most growing businesses land on a hybrid: a retainer that covers remote support and a baseline of onsite visits, with clearly priced rates for anything beyond scope, such as emergency after-hours work or large projects.
What actually drives the price in a spread-out region
Travel time is real cost, not padding. A provider based in Abbotsford dispatching to Chilliwack or Mission is looking at meaningful drive time each way, and that shows up in either the hourly rate or the retainer price. This is one of the practical arguments for using a provider with technicians actually based in the region you're in, rather than a national company dispatching from wherever their nearest tech happens to be — ask directly where the technician who'd actually show up is located, not just where the company's head office is.
Response-time commitments cost more to deliver, not just to promise. A provider guaranteeing 2-hour onsite response across a spread-out service area needs enough technician density to actually hit that number, which is more expensive to staff than a vague "we'll get there when we can." Cheap onsite contracts often have vague or unenforced response times for exactly this reason.
Scope of "onsite" varies a lot between providers. Some onsite contracts cover only specific categories — hardware failures, network issues — and exclude things like new equipment setup, cabling, or desk moves, which then get billed separately. Read what's actually included before comparing two quotes as apples to apples.
Volume and predictability matter. A business with several locations and a steady cadence of moves, new hires, and equipment refreshes is a more efficient onsite relationship for a provider to staff for than a single office calling sporadically — and that efficiency sometimes shows up in better retainer pricing.
What a fair retainer-based onsite rate looks like
For a small-to-mid-sized business in the Fraser Valley bundling remote support with regular onsite coverage, per-user managed IT pricing in the $100–$200/month range typically includes some baseline onsite coverage, with clearly priced add-ons for larger projects like office moves, hardware refreshes, or new site setups. If a quote is dramatically below that range, ask specifically what onsite response time and scope it actually commits to in writing — not what the sales conversation implied.
The real question to ask a prospective provider
Not "what's your hourly rate" but "if my server room has a hardware failure at 4pm on a Tuesday, who shows up, from where, and how fast — and what does that actually cost me under this contract." If they can't answer that specifically, the rate card doesn't mean much.