// blueprint

A commercial refrigeration company.

Paper tickets sit in trucks until Friday, and installed parts go unbilled.

// what they typedwe run a commercial refrigeration company with 6 field techs, 2 dispatchers, and me. dispatchers spend 70% of their day playing phone tag with clients and texting addresses to the techs. techs write up paper tickets, which sit in their trucks until friday. the dispatchers then have to decipher the handwriting and manually double-enter the parts and labor into quickbooks and a google sheet we use for payroll. we lose thousands a month on forgotten parts billing. we use quickbooks online, google calendar, and basic cell phones.

// read

A ticket does not exist until Friday. A part installed on Tuesday has four days to be forgotten, and dispatch cannot tell a job is done until a tech calls. The fix is a record of the work at the moment the work happens.

// the system

A field service app on the techs' phones replaces the paper ticket. The tech arrives, taps start, picks parts from a list tied to the truck's stock, and gets the customer's signature on the screen. The ticket closes before the tech leaves the parking lot.
Scheduling lives in that app. An assignment sends the address, the equipment history and the site notes to the tech's phone, which ends the texting of addresses.
Customers get an automatic text when the tech is on the way, with an arrival estimate. That one message removes most of the calls your dispatchers field.
Invoices sync to QuickBooks Online from the closed ticket, with parts and labor already itemized. Nobody retypes.
The one piece worth custom work: a nightly job compares parts used on tickets against parts invoiced, and emails dispatch a short exception list each morning. That is where your thousands go, and no off-the-shelf tool knows your truck stock rules.
Labor hours flow from ticket clock-in and clock-out into the payroll sheet on a schedule, or the sheet retires if the app's time tracking is good enough.

// buy vs build

Buy the core. Jobber, Housecall Pro, FieldEdge and ServiceTitan all do field service, and the last two are built for commercial HVAC and refrigeration, with equipment history kept per site. Before signing, verify that the QuickBooks sync runs both ways and handles your item list, that the plan at nine users includes API access, and that it keeps service agreements and equipment records per site rather than per customer.

Do not automate final invoice approval. One mis-keyed part number bills a client wrong, and the labor saved is small next to that. A dispatcher reviews the exception list and releases invoices.

// cost band

The field service app is a per-user subscription, so check current pricing at nine seats. The custom layer is the nightly parts check and the payroll sync. It talks to two systems, the field service app and the payroll sheet, because the app owns the QuickBooks sync. The data is mixed, since the item list needs a cleanup. That makes a build of $14,500–$20,000. No AI model runs in it, so running it is hosting, about $0–$25/mo. We can watch it and fix breaks for $400/mo.

// what we'd watch

Tech adoption. Six people who have used paper for years will keep using paper if the app takes more than about ninety seconds per ticket. Choose for speed over features.
Your QuickBooks item list is probably messy, and the sync is only as good as that list. Budget a cleanup week before go-live.
Offline mode. Refrigeration work happens in basements and walk-ins with no signal, so confirm the app queues work and syncs later.
The Google Sheet can linger as a half-used copy. Decide now whether it goes or stays.

// next

A real number takes a real conversation, and that is free.

This is a worked example on a composite business, drawn by the same desk that runs on the architect. Describe your own situation there and it will draw yours.

studio@anchor163.com // copied

// more architect services ai automation cost build vs buy ai automation