Software for places where the internet doesn't reach
150+ technicians repair surgical instruments from mobile vans — in hospital parking garages, loading docks, and rural facilities. We built them a field service application that treats connectivity as a bonus, not a requirement.
A van is not an office
Our client's field technicians drive fully equipped repair vans to hospitals across the country. They park where they're told — usually an underground garage — and repair surgical instruments on site, all day.
The first assumption everyone makes is "give them a web app and a hotspot." Real-world testing destroyed that assumption quickly: hotspots dropped mid-save, VPNs timed out, laptops went to sleep between customers, and coverage disappeared entirely below ground.
The requirement wasn't "works with slow internet." It was "works with no internet, for a full working day, without losing a single repair record."
Four architectures. Three rejected.
This is the part most vendors skip: what we didn't build, and why. Each alternative was evaluated — some in prototypes, one in painful real-world testing.
Traditional web application
Single database, no synchronization — the standard answer.
Web app + local cache
Partial offline capability through cached data.
Per-transaction sync
Each operation synced through its own API call.
Offline-first desktop + atomic snapshot sync
A local database on every laptop; synchronization moves the entire database as one compressed unit.
Synchronization as an all-or-nothing business event
Instead of keeping a connection alive, the application treats sync like a shipment: package everything, send it once, receive a complete replacement back.
Sync once, load the day
The technician synchronizes on any available connection: assigned customers, equipment, repair history, and pricing land in the local database.
Work at desktop speed
Create work orders and quotes, record repairs, track instrument trays, print reports — every operation runs locally. No spinner, no signal bars.
Sync once, done
The day's work uploads as one atomic package; a fresh database comes back. If the network fails, retry later — nothing is ever half-saved.
Versioned local databases
Every laptop keeps previous database versions — instant rollback, safe upgrades, and remote diagnostics without a support visit.
Self-updating deployment
The application updates itself on launch. 150+ non-technical users, zero manual installs, minimal IT involvement in the field.
Built for the actual user
Large controls, minimal navigation, fast data entry. The users are repair specialists, not software specialists — the UI respects that.
Reliability you stop thinking about
Users don't care whether synchronization happens every minute. They care that their work is never lost.Engineering lesson from eight years of field operations
More from this engagement
The platform its acquirer couldn't replace
The full eight-year story: 700k+ work orders, 2,000+ users, portals, contracts, BI — and the migration that never happened.
Read the story → Solution storyStaying fast at 700,000 work orders
Working vs. history tables — the lifecycle-aware data architecture that kept screens sub-second for eight years.
Read the story → Solution storyDon't replace the ERP — surround it
How the platform extended the client's ERP instead of fighting it, and why that decision paid off for a decade.
Read the story →Have workflows that live where connectivity doesn't?
Field teams, warehouses, vehicles, remote sites — we design systems around your operational reality, not ideal conditions.
Book a Strategy Call