Thread 01
The exception path is the business.
The normal path is fine enough. The leaks happen when a job does not fit the normal path. That is where owner-hours disappear.
NervaHous · Sample Diagnostic Summary
SAMPLE · Fictionalized company
Six-person Charlotte HVAC company. Five lenses, one Monday move.
This is a sample of the written summary a Diagnostic client receives after a 90-minute call. The company is fictionalized. The patterns are realistic for a local service operator.
Situation
Company: Carolina Air & Heat, fictionalized. Six people: owner, dispatcher, three technicians, one part-time bookkeeper. Revenue exists. Demand exists. The owner still spends two to three hours most evenings cleaning up the day.
Named problem: "We are busy but I cannot tell which jobs are actually good until the week is over."
The read in one page
| Lens | What showed up | Next move |
|---|---|---|
| Workflow | Jobs move through phone, paper notes, calendar, and invoice software. The dispatcher owns the front half. The owner owns every exception, which means the exception path is the real process. | Write the exception path first: no heat, warranty question, quote follow-up, part delay, and after-hours call. |
| Tooling | The calendar and invoice system both know pieces of the truth, but nothing shows the job state in one place. The team is not missing software. It is missing one shared job-status view. | Build a simple daily job board before buying another platform. |
| Data | The owner tracks revenue and cash. Nobody tracks quote age, callback rate, or margin by job type. The company cannot tell which "busy" is profitable. | Start with one Monday number: open quotes older than three days, grouped by job type. |
| People | The dispatcher can absorb one new habit if it saves calls. The technicians will not adopt a new app mid-season. The owner is willing to stop being the exception router, but only after trust is built. | Give the dispatcher the status board. Keep technician input to one text format for now. |
| Risk | The risk is not technical. It is trust. If the board is wrong twice in a week, the owner goes back to memory and text threads. | Run it for five business days in shadow mode. Owner keeps old process while comparing the board daily. |
The three threads that matter most
Thread 02
One number beats a dashboard.
Open quotes older than three days is the first number. It connects directly to follow-up, revenue, and owner time.
Thread 03
Do not ask technicians for a new workflow yet.
The team is already in peak season. Start with dispatcher and owner visibility. Add technician behavior only after the board earns trust.
Thread 04
The first system should be boring.
A daily job-status board is enough. If it works for two weeks, then it can become an automation.
Monday move
Make a shared job board with five statuses: New, Scheduled, Waiting on Part, Quote Sent, Needs Owner. Every open job gets one status before 5pm. The owner reviews only "Needs Owner" and "Quote Sent older than three days" each morning.
If this became a Sprint
- Map the full job path from first call through paid invoice.
- Score the five lenses with evidence from the week.
- Build the first status board and quote follow-up rhythm.
- Define a 30-day rollback if the board creates more confusion than clarity.