Daily briefing
Auto-generated at 6:00 a.m. Jobs on deck, parts arriving, crew changes, weather flags, callouts that need a return visit.
← All work
Case 07 — Operations Optimization
An ops workspace the field actually trusts.
For a commercial mechanical contractor, we wired the dispatch board, the daily briefing, the SOP library, and the management dashboards into one workspace — quiet, fast, and trusted by people who don’t want to talk to a chatbot.
The knowledge was in three heads. That’s a liability.
This is a 70-person commercial mechanical shop. They install boilers, chillers, controls, plant rooms. The work is real, the margins are tight, and the company runs because three people remember everything.
The leadership knew what was at risk. If any of those three got hit by a bus — or simply went on vacation — dispatch slowed, billing slipped, and quotes got stale. The tools they had bought to fix this never quite clicked into how the day actually moved.
The brief: get the knowledge out of heads and into a workspace the field would open every morning without being asked.
Get the knowledge out of three heads.
-
Decision 01
Write the knowledge down where the work happens.
A versioned, searchable SOP library, tied to the equipment lines and customers it applies to. The shop stops depending on three memories.
-
Decision 02
Build on the actual floor, not in a sandbox.
A week with the dispatcher, a week with the estimator, ride-alongs on installs. Each two-week slice solved one friction the team had named.
-
Decision 03
Treat adoption as a design problem.
Every slice shipped with a written SOP, a short Loom, and a named GFW owner for its first two weeks of use.
One workspace. Six things it does without being asked.
Dispatch command center
One view across crews, trucks, parts, and customer windows. Reroute logic surfaces options instead of waiting on a human to math it out.
SOP library
The knowledge that was in three heads, written down and searchable. Versioned. Tied to the equipment lines and customers it actually applies to.
Quote-prep assistant
Pulls historical jobs by equipment and customer. Drafts the quote skeleton. The estimator finishes it in a fraction of the time.
Service callback flag
If a job comes back inside the warranty window, the system flags it before billing closes. No more silent margin leaks.
Leadership dashboard
Weekly view: backlog, win rate by sector, gross margin by job, parts on order, crew utilization. One screen. Boardroom-ready.
No pilot. Built on the actual floor.
We didn’t build a sandbox. We sat with the dispatcher for a week. We sat with the estimator for a week. We rode along on installs. The system was shipped in vertical slices, each one solving one specific friction the team had named that week.
Every slice came with a written SOP, a short Loom, and a named human on the GFW side who owned it through the first two weeks of usage. Adoption was a design problem, not a training problem.
The field crews didn’t care that we used Claude under the hood. They cared that the morning briefing was right. That was the only metric that ever mattered.
Surface
One workspace
Build cadence
Two-week slices
Owner
Ops director
What changed on the floor.
6:00 a.m.
The daily briefing generates itself: jobs on deck, parts arriving, crew changes, weather flags, and callouts that need a return visit.
One workspace
Dispatch, SOPs, quote prep, callback flags, and the leadership dashboard in one place, owned by the ops director.
Callbacks caught before billing
Jobs that come back inside the warranty window are flagged before billing closes.
A workspace built for boots, not boardrooms.
The night I left for vacation and dispatch didn’t call me — that was the moment we knew this thing worked.Operations director — Northeast Mechanical
Other engagements in this neighborhood of work.
Skip the slides. Have the conversation.
A 30-minute conversation. No deck. We map your operations and tell you honestly where to start.