Software for field service and mechanical contractors.

1. 01

   Request comes in

   A call, an email, or a portal submission. Somebody has to turn it into a job with an address, a customer and a scope.

2. 02

   Quote

   An estimator prices labour and materials, sends it, and then waits — chasing approval by phone or email.

3. 03

   Dispatch

   Someone decides which crew, which day, and in what order, balancing skills, certifications and drive time.

4. 04

   The job

   A tech arrives, runs safety checks, does the work, logs parts and hours, takes photos, gets a signature.

5. 05

   Sign-off

   Paperwork comes back to the office — or does not, until someone goes looking for it.

6. 06

   Invoice

   The job is re-typed into accounting, invoiced, and then chased if it goes past terms.

5 failures across the 6 steps above — and 1 step that holds fine without a system. Select a step to isolate it.

1. 01Request comes in

   Holds
2. 02Quote

   1 failure

   • The same job is typed into a quoting tool, a scheduling tool and accounting — three chances to get it wrong.
3. 03Dispatch

   1 failure

   • The schedule lives on a whiteboard or in one person's head, so nobody else can answer "where is that crew?"
4. 04The job

   1 failure

   • Techs call the office to ask what the scope was, because the detail never left the quote.
5. 05Sign-off

   1 failure

   • Signed sheets and photos arrive days later, so invoicing waits on paperwork rather than on work being finished.
6. 06Invoice

   1 failure

   • Nobody knows what has been done but not billed until someone builds a spreadsheet to find out.

• Enlarge

  Quote to job in one step

  An approved quote becomes the job, carrying the scope, site, customer and pricing with it. Nothing is re-entered, so nothing drifts between the two.

  A quote awaiting approval. When it is approved the job is created carrying the same scope, site and pricing — the step where most systems make somebody re-type everything.

• Enlarge

  A dispatch board that knows about drive time

  Crews, certifications and job sites on one board, with geocoded addresses so the schedule reflects the drive rather than just the clock.

  The dispatch board: crews, jobs and travel time on one row per crew, with unassigned work — including what is already past its promised window — visible rather than buried.

• Enlarge

  Hard safety gates

  A job cannot start and time cannot be logged until every required check passes. The blocked state is built and verified as carefully as the happy path.

  A crew on site at 07:52 and a job that will not start. Two attempts were refused and both are on the job record — a gate that only warns is not a gate.

• Enlarge

  Sign-off in the field

  Photos, parts, hours and a customer signature captured on a phone, attached to the job record the moment they are taken.

  Sign-off on the phone, in the customer's driveway. Parts, hours, photos and the signature attach to the job as they are taken — and are held on the device when there is no signal.

• Enlarge

  Invoice from the job

  The invoice is generated from what was actually done and lands in accounting directly. Overdue invoices chase themselves on rules the office sets.

  An overdue invoice chasing itself. Recipients, templates and the schedule live in Settings, so the office changes who gets chased and when — without us.

• Enlarge

  A command center for what needs attention

  Open jobs, work scheduled today, approvals waiting and unbilled revenue on one screen — so problems surface before anyone goes looking.

  One screen of things that need a decision today, each one a link to the record underneath it. This is a queue, not a report.