Your technician is booked on an island your dispatcher can't reach because the morning sailing was pulled
Custom field service management software for a Nanaimo trades, marine-services, or utilities operation runs $40,000 to $120,000 over 4 to 7 months. ServiceTitan, Jobber, and Housecall Pro route technicians by road as if every site is drivable. Your service territory includes islands, tide-gated shorelines, and sites reached only by a sailing that the weather can cancel. Custom field service software here routes around the water, the tide, and the sailing, not just the road.
You run ServiceTitan and it dispatches your techs around town fine. Then a job comes in on a Gulf Island or a tide-gated marine site, and ServiceTitan routes it as a drive, books the tech, and has no idea the only way there is a sailing that was cancelled this morning. So your tech is en route to a ferry that isn't running, the customer is waiting, and your dispatcher is on the phone improvising a route the software should have known was impossible.
Jobber and Housecall Pro assume a continuous road network and drivable sites, because that's how mainland trades operate. Your territory has water gaps, tide windows, and sailing-dependent access that no road-routing engine models. The result is dispatch that looks efficient on the map and falls apart at the water's edge, with the real routing logic living in whichever dispatcher knows the sailings by heart.
What breaks first in Nanaimo
- Jobs on islands or tide-gated sites get routed as drives, ignoring the sailing or tide that actually gates access
- A cancelled sailing strands a dispatched tech mid-route with a customer waiting and no plan
- Tide windows constrain when shoreline work can happen, and the dispatch engine has no concept of them
- Sailing-aware routing lives in one dispatcher's head, not the system, so it leaves on their day off
The fix: field service management built for Nanaimo, not rented
You go custom on field service when access is gated by water, tide, and sailings the router can't see. A Nanaimo build routes technicians around sailing schedules and tide windows, replans when a sailing is cancelled, and tracks which sites need a crossing at all. That's dispatch that works at the water's edge, not just on the map. It connects to your CRM (Customer Relationship Management), scheduling, and booking systems so the customer, the job, and the route stay aligned even when a sailing disrupts the day.
What field service management costs in Nanaimo
| Project scope | Typical cost | Timeline |
|---|---|---|
| Sailing-aware routing module | $40k to $70k | 4 to 5 months |
| Full field service platform (routing + offline + tide) | $80k to $120k | 5 to 7 months |
| Access and routing layer over existing ServiceTitan | $35k to $60k | 3 to 5 months |
The capability list that earns its budget
Nanaimo field service management: the full scope
Digital Heroes builds the full field service management stack for Nanaimo teams. Typical engagements cover mobile field app, ServiceTitan alternative, Jobber alternative, route optimization, asset and maintenance tracking, field service management software and dispatch software.
Exactly what you get
Field service software that routes around the water, not over it. Concretely: sailing-and-tide-aware routing, disruption replanning when a sailing is cancelled, tide-window scheduling for shoreline work, an offline mobile app for low-signal islands, and site access profiles flagging crossings. You also get integration to your CRM, scheduling, and booking systems. What you don't get is a tech dispatched to a ferry that wasn't running and a customer left waiting.
How to choose a developer in Nanaimo
Find a team that asks how techs reach your island and shoreline sites before they talk routing efficiency. If they assume everything's drivable, they've never dispatched across a water gap. Ask for a marine or water-gapped reference. A strong partner connects the build to your CRM, scheduling, and booking software, designs a reliable offline app, and tells you honestly when ServiceTitan covers a fully drivable territory.
- !They route by road only; ask how they handle an island or tide-gated site
- !They've no marine or water-gapped reference; ask for one
- !They ignore sailing cancellations; ask how a stranded tech gets replanned
- !They build online-only mobile; ask how techs work on low-signal islands
- !They skip site access profiles; ask how the system knows a job needs a crossing
If field service management is on the roadmap, lms, crm, shopify usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Can ServiceTitan route around a ferry?
No. ServiceTitan routes on a road network and treats every site as drivable, so it can't model a sailing-gated island or a cancelled crossing. The gap is the water in your territory, which a road-routing engine has no concept of. A custom build routes around sailings and tide windows so dispatch survives the water's edge.
What happens when a sailing is cancelled mid-route?
The system replans: it flags the affected job, reroutes or reschedules the tech, and alerts the customer, instead of leaving a tech stranded at a closed terminal. That automatic disruption handling is exactly what off-the-shelf routing can't do, because it never knew the sailing existed in the first place.
Do techs need an offline app?
Yes, for island and shoreline sites where signal is poor. The mobile app captures job data, photos, and sign-offs offline and syncs when signal returns, so a low-signal site doesn't stop the work. That offline capability is essential where a connected-only app would simply fail at the dock.