Field Service & Trades

Software that works in a basement with no bars.

Your team is in crawlspaces, plant rooms and buildings with thick walls. Any system that needs a connection to record a job will be worked around within a fortnight, and then the data stops being real.

Offline
capture, queue, reconcile
On site
invoice before leaving
Per tech
parts and van stock

What we hear

If any of this sounds familiar…

01

Paperwork happens at nine at night

Jobs get written up hours later from memory, which is when detail gets lost and invoices get delayed.

02

The app needs signal to save

So the technician takes a photo on their own phone and types it in later, and now the system is not the record.

03

Nobody knows what is on the van

Parts inventory lives in somebody's head, so jobs get booked without the part and a second visit gets scheduled.

What we build

The pieces this sector actually needs.

Offline work orders

The full job record captured on device with no connection, queued, and reconciled cleanly when the van gets back to signal.

Scheduling & dispatch

Assignment by skill, location and availability, with changes reaching the technician rather than sitting in an inbox.

Photo & signature capture

Evidence attached to the job at the time, uploaded when possible, never blocking the technician from finishing.

Van and parts inventory

Stock per vehicle and per technician, consumed as jobs complete, so restocking is driven by data.

Invoicing on site

Generate and take payment before leaving, with card readers that handle a dropped connection sensibly.

Customer portal

Job history, quotes and invoices in one place, so your office stops fielding calls asking what happened.

Where this comes from

Proven somewhere real.

Offline-first is the pattern we proved in Larder and shipped in Eshop: a local store that is authoritative while disconnected, queued operations as intent rather than absolute values, and an explicit conflict policy. Card readers and printers come from the same device work.

Go and read it

Tell us how your business actually runs.

The process, not the software you think you need. We’ll come back within one business day.

Reply time

One business day, from an engineer

Based in

Orlando, Florida · serving the United States

What happens next

  • A reply within one business day, from an engineer
  • A thirty-minute call, with no qualifying call before it
  • A written scope and a fixed number, if it fits