Field operations · Treasure Valley and beyond

Fix the workflow between the office, field, and billing.

I build practical tools for service businesses whose work has outgrown paper, whiteboards, text threads, or a spreadsheet held together by one indispensable person.

20+
departments using field software
~10k
equipment records each season
Local
engineering and in-person discovery
One job · three fragile handoffs

The expensive problems usually live between systems.

Work comes in

Intake and estimating

Capture the right information once, route it correctly, and stop rebuilding the same job from texts and notes.

Work moves

Dispatch and field status

Give the office and field team a shared view of assignments, status, job details, and the next required action.

Work closes

Completion and billing

Bring photos, materials, signatures, reports, and billing information together while the work is still fresh.

Relevant proof

Built from the workflow outward.

The goal is a system the office and field team will actually use when the day gets busy.

Live and field-proven

FireGauge

20+ departments

A mobile-first, offline-capable workflow for capturing fire-equipment tests in the field and producing clean reports without later transcription.

Visit FireGauge
Website live · operations in development

Goff Plumbing

Service business

A modernization effort spanning customer intake and scheduling, with dispatch, field status, offline workflows, and completion-to-billing handoffs in development.

Visit Goff Plumbing
Good fit

You probably do not need to replace everything.

  • The whiteboard or spreadsheet has quietly become mission-critical
  • Dispatchers and technicians re-enter the same information
  • Field paperwork arrives late, incomplete, or in several formats
  • Existing software handles most of the job—but the important gap remains
01

Map the actual workflow

Walk through how a job enters, moves, and closes today—including the workarounds.

02

Build the smallest useful system

Focus first on the bottleneck with enough value to change the day-to-day operation.

03

Prove it with the crew

Test it in the real workflow, refine the handoffs, and leave the team with ownership.

Start with the problem

What's slowing your operation down?

You do not need a software specification. Tell me where work is repetitive, information disappears, or the current process depends too heavily on one person.

  • A field process still running on paper
  • A spreadsheet that has become a business system
  • Testing or reporting that consumes skilled time
  • Customer information getting lost between handoffs

Describe the bottleneck

A few plain sentences are enough.