Insights

Product

What we learned building GeekOnSites field service software

Dispatch, technician mobile apps and offline job capture have constraints most SaaS teams never meet. Notes from the build.

ASI TECH INC · June 15, 2026 · 7 min read

Field service software lives where the network does not. That single fact reshapes the architecture.

Offline is the default state Technicians work in basements, plant rooms and rural sites. The mobile app treats the local database as the source of truth and syncs opportunistically with conflict resolution built in from day one.

Dispatch is an optimization problem Skills, certifications, parts on the van, travel time, service-level windows and overtime rules all interact. We solve it with constraints and let dispatchers override — the human always wins the tie.

What moved the metrics - Photo and signature capture that queues locally and uploads later - Parts availability visible before the technician accepts the job - Live customer ETA notifications, which cut inbound calls sharply - One-tap conversion from job notes to invoice line items

Measure the right thing First-time fix rate beats jobs-per-day. Sending the right person with the right part once is worth more than squeezing an extra visit into the route.

More notes like this