Skip to content
Zoevin

Automation problem

The job that waits in the truck

The shop already has software. The blank page is which typing loop is the first build — not which platform to buy next.

Chris BoundsPublished 7 minute read

Evidence reviewed through September 3, 2026

Problem

The truck is done. The office has not started

The shop already has software. The truck still comes back with photos, receipts, and a verbal extra. The office types it so someone can invoice.

Consider a hypothetical HVAC shop of about fifteen people. A plumbing van, a tile crew, and a general contractor run the same week with different nouns. The blank page is which loop to close first, not which app to buy next.

The truck is done. The office has not started

The field job finished. The office job has not started until those things are typed.

On the truck

  • A completed ticket lives as a photo
  • A parts receipt sits in the visor
  • A verbal extra never becomes a change order
  • A sub texts that they are on site

In the office

  • Someone types the ticket so it can be invoiced
  • Someone codes the receipt to a job
  • Someone rebuilds the extra as a change order
  • Someone chases the COI that expired last month

On the truck: a ticket photo, a parts receipt, a verbal extra, and a sub on site. In the office: the ticket is typed, the receipt is coded, the extra is rebuilt, and the expired COI is chased.

Software is daily. Seams are not named.Sourced note

Examples

Four loops. One week

Monday a ticket photo sits in a group chat. Tuesday a parts receipt lives in the visor. Wednesday a sub's insurance PDF is missing. Thursday a web lead lands in a shared inbox.

Nobody designed it this way. Each tool got adopted on its own. Pick the loop that already repeats this week. That is the first build.

Four loops. One week

Choose a route. Work from the truck and work from the office share a start, then split. Every path ends on a draft or a named queue.

Choose a route

Truck is back → draft or named queue

From the truck

Scenario ATicket photo

On this route

Draft the lines. A person still invoices.

Scenario BReceipt needs a person

Off this route

Stop for a named owner.

From the office

Scenario CMissing packet

Off this route

Park it until the packet is complete.

Scenario DRoutine lead

Off this route

Draft the intake. A person still assigns the job.

Selected stop · start

The truck is back

What this is
Photo, paper, text, or web form
What happens
Keep the original file or note and start one tracked case.
What leaves this step
Original file or note, plus a case ID
  1. The truck is back, then the work splits.
  2. From the truck: a readable ticket becomes a draft, or a person reviews an unknown receipt.
  3. From the office: a missing packet waits in a queue, or a routine lead becomes a draft intake.
  4. No route sends a tech, prices a change, or invoices a customer.
  5. truck-back to which-loop: received
  6. which-loop to draft-ticket: photo is readable
  7. which-loop to review-receipt: needs review
  8. which-loop to packet-queue: packet incomplete
  9. which-loop to draft-lead: rules match
Name the loop, not the platformSourced note

Solutions

Draft the typing. Keep the call

If every job is one-off and you only close a few, a person reading the ticket is the honest answer. Don't buy an agent that just invoices.

Walk one closed job from the first call to the paid invoice. Circle every retype. Circle every yes. Automate one circle that is not a yes.

Draft the typing. Keep the call

The repeating work is transcription. The call is a judgment. Software can draft the first. It shouldn't do the second.

Draft the typing. Keep the call

Ticket fields, receipt fields, COI dates, and lead contact can move without a field or money decision. Diagnose, change-order pricing, payroll sign-off, and payment stay with a person.

Stays human

Arrow = copied with no decision

  1. Four transcription loops: ticket fields, receipt fields, COI dates, and lead contact.
  2. Four judgments stay with a person: diagnose, price a change order, sign certified payroll, and release a payment.
Close one named seamSourced note

How Zoevin helps

Where does your job wait after the truck?

A fixed-fee discovery ($695 up to 50 people; $1,495 for 50–200) names the seam, today's labor from numbers you already know, and whether a build is worth it — before anything gets built.

  • A named seam, written down.
  • Today's re-entry cost, from numbers you already know.
  • A yes or no on whether a build is worth it.
  • If yes, a handover date — not a running service.

Zoevin has no delivered automation projects yet. Discovery names the seam. If I build, I hand it over on a written date. You get the workflow, the logins, and the write-up. I don't stay on to run it. You buy the software.

See automation services

Evidence

Sources

Primary reporting first. Open the sources yourself rather than taking this account alone.

  1. primary source

    Associated General Contractors of America — 2025 Construction Hiring and Business Outlook

    Primary trade-association survey of 1,100+ contractors; source for the AI-investment and adoption-pace figures.

  2. secondary source

    MCAA — 5th Annual JBKnowledge Construction Technology Report

    Trade-association summary of JBKnowledge's annual survey of nearly 3,000 contractors; source for daily software-use and integration figures.

  3. secondary source

    Construction Dive — Construction app usage increases despite continued lack of integration

    Independent trade-press summary of the same JBKnowledge report's integration findings.

  4. secondary source

    Mercator.ai — Top Construction Permit Tracking Software Compared

    Cites NAHB's 2025 Technology Adoption Survey finding that permit-tracking-tool use among residential contractors rose from 11% in 2022 to 34% in 2025.

Related reading

  • Automation problem ·

    The estimate that gets retyped four times

    A platform-neutral look at where small construction firms lose a job's numbers to re-entry, and which seams are safe to automate without moving the judgment calls.

    4 minute read

  • Automation guide ·

    What should your company automate—and when?

    Learn what business processes can be automated, when a workflow is ready, and which decisions should stay with a person.

    11 minute read

  • Automation problem ·

    The unpaid pile and the unpaid bill

    A platform-neutral look at common payable and receivable loops, and which seams are safe to automate without moving a money decision.

    5 minute read