Improve Operations
When one person's memory is the scheduling system, everything works until they take a week off. Here's what changes.
Jobs get assigned by whoever knows the most — one person, usually, deciding who's closest and who's good at what. It works, because that person is good. It's a shared calendar and a phone and a lot of judgment.
Then they take a week off and it's a mess for a few days.
The other tell: techs driving back to the shop for parts they didn't know they'd need, because nobody knew what they were walking into until they got there.
The parts runs are countable. Four round trips a week at 45 minutes is 156 hours a year of paid technician time producing nothing. At a typical loaded rate that's around $6,000 — and that's the small half. The larger cost is the work that didn't get done in those hours, which we won't put a number on because it depends on whether you're capacity-constrained or demand-constrained, and most operators genuinely don't know which they are.
The single-point-of-failure problem doesn't have a clean dollar figure at all. It has a risk figure. If you've already named it — "it's a mess when she's out" — you've priced it more accurately than we could.
Worth being straight about: Operations is usually the second thing to fix, not the first. If you're missing calls, missed calls are costing you more, and they're cheaper to fix. We'd rather tell you that than sell you the bigger project.
Assignment happens against actual location, actual skills, and actual equipment history — not memory. Techs see what they're walking into before they leave, so the parts run stops being routine.
And when the person who runs the schedule takes a week off, nothing changes. That's the real deliverable.
Dispatch
Jobs route on real inputs: where the tech actually is, what they're actually certified on, what the site actually has installed. The scheduler stays in control — this replaces the mental arithmetic, not the judgment.
Job history
Equipment, prior work, and site notes surface to the tech before the truck moves. Most of this data already exists; it's just not where anyone can reach it.
The handoff problem
What lives in one person's head gets written down as rules the system runs. This is the part people resist and the part that matters most.
Fit with your stack
If you've got field software that works, we build on it. If you're on Google Calendar and a group text — that's most people, and it's fine until it isn't. We'll tell you which side of that line you're on.
Longer than the other pages, honestly. Weeks, not days, and it depends on how much of the operation lives in someone's head versus somewhere we can read. The discovery is the slow part; the build usually isn't.
Custom is more common here than anywhere else. Every operation dispatches a bit differently and the differences usually turn out to be the point.