Field Notes
What we learned building an electrical contractor's operating system
Kyrle Symons · 2026-09-05 · 2 minute read
We built a complete working model of an electrical contractor: projects, materials, procurement, warehouse, field crews, closeout. Real workflows end to end, on entirely synthetic data. A demonstration build, and we label it that way everywhere it appears. Here is what it taught us about putting the new operating model into a trade.
First lesson: the most valuable sentence in a contracting business is "we are actually ready." Our build will not release a job to the field until six readiness checks pass: materials planned, stock truth confirmed, dependencies present, schedule sane. Then a named authority reviews and releases, and the record keeps who authorized what, on which evidence, at what time. The demonstration runs twenty steps, and every one is evidence-gated: the next step will not open until the previous one proves it happened. "We think we are good" is the sentence that ruins Fridays; a release gate retires it.
Second lesson: inventory numbers are only useful if they admit what they do not know. Our stock view distinguishes on-hand from actually available, carries reservations atomically, and shows freshness and confidence on every count. The surprising part was how much behavior changed once numbers confessed their uncertainty: people stopped padding orders defensively, because they could finally tell which numbers deserved belief.
Third lesson: the field will use exactly as much system as fits in one hand at one moment. Our field assistant works at phone width: a foreman asks for material in plain words, the system does the checking, reserving, and chasing, and exceptions route to one named owner instead of a group chat. Adoption is not a training problem. It is a respect-for-the-moment problem.
Fourth lesson: closeout is where the compounding lives. Planned versus actual per phase, patterns surfaced instead of buried, and improvements promoted only when a human agrees. One recurring shortage pattern, caught and promoted into the plan, pays for a lot of software.
What generalizes: none of these lessons is about electricity. Readiness gates, honest inventory, one-hand interfaces, and governed learning are operating-model moves. The trade supplies the nouns. If your Tuesdays feel like the before pictures above, the briefing is where we walk through the after.