Case Study: A Regulated Business Went From Paper Logs to a Passed Inspection
A regulated, multi-site business, a few hundred staff spread across several locations, had two problems that every mid-size business will recognize even if the details are different.
The first was paper. Regulated temperature logs for a few dozen refrigerators, freezers, and transport coolers were filled in by hand, reviewed by hand, and filed in binders. An inspection was coming, and the binders had gaps.
The second was the phone tree. Urgent pickups were dispatched to about thirty field staff by phone and radio. Whoever answered first got the job. Nobody could say, afterward, how long a pickup had waited or who had been closest.
Both problems were solved in under a year by one person, working alongside the company's own staff, using AI-assisted development. The inspector approved the new system on site. This is how it went, and what it cost.
TL;DR: Map the process first, in the room with the people who do it. Then build the smallest tool that removes the paper and makes the status visible. Two custom apps, built by one person with AI assistance, replaced binders and radios at a regulated business and passed inspection. The approach works for any office that runs on shared inboxes, clipboards, and "ask Sharon, she knows."
Step One: Sit With the People Who Do the Work
No code was written for the first several weeks. The work was watching.
How does a temperature reading get from a freezer to a binder? Who signs the daily review, and what happens when that person is on vacation? When a reading is out of range, who finds out, how long does it take, and what do they do? Where do the transport coolers go, and who knows whether a shipment was inside one when it got too warm?
The same questions for dispatch. Where does an urgent request arrive? A shared mailbox, it turned out, read by whoever was watching it. How does it reach a driver? A phone call, then a radio call if nobody picked up. How does the office know it was done? It mostly didn't, until the shipment showed up.
The output of this phase was not software. It was a written map of each process, with every hand-off, every place information was lost, and every step the regulator actually required versus the steps that had grown out of habit. The person responsible for compliance reviewed it and corrected it. That document became the spec.
Step Two: Replace the Binders
The temperature system reads directly from the sensors the company already owned, from two different vendors, and stores every reading. When a reading goes out of range or a unit loses power, it alerts the right people immediately instead of waiting for the next manual check.
The regulated paperwork is generated, not written. Daily review sign-offs, excursion acknowledgements, and inspection-ready PDFs come out of the system on demand. The compliance rule that drove the project is satisfied by design, not by diligence.
One feature came straight from the process map. Transport coolers travel with couriers, and couriers carry a phone. The system correlates cooler temperature with the courier's location and the chain-of-custody record, so a warm cooler with a shipment inside raises a different, louder alert than an empty one on a loading dock. Nobody asked for that feature. It fell out of watching the hand-offs.
The inspector reviewed the system on site, transport coolers included, and approved it.
Step Three: Replace the Radio
The dispatch app watches the same shared mailbox the office already used, so nothing changed for the customers sending requests. A new request pushes to every field phone and is read aloud by text-to-speech, even on a silenced or locked device, because a courier walking a corridor is not looking at a screen.
The first courier to claim it owns it. Pick-up, hand-off, and drop-off are each one tap, and every tap is broadcast live to the office. The dispatcher sees a map, a list, and a clock.
That clock was the real win. Time-to-claim, which used to be unknowable, became a number on a dashboard. Stale requests and dropped jobs are flagged automatically. Management had, for the first time, data about a process they had only ever had anecdotes about.
Staff sign in with the same Microsoft 365 account they already use. The app passed app store review and is distributed through the company's device management, so installing it on a new phone is zero effort for the courier.
What It Cost, and Why That Number Is Different Now
Both systems were built by one person, with AI-assisted development, in months rather than years, with automated testing and a deployment pipeline that cannot ship untested code. A decade ago this was a six-figure vendor contract or a project a business this size simply would not do.
That is the part worth sitting with if you run a mid-size business. The cost of a custom tool that fits your process exactly has dropped far enough that it is now cheaper than the ongoing cost of the workaround. The binders, the phone tree, the shared inbox that one person watches, the spreadsheet only Sharon understands. Those all have a price. It is just spread across every week.
What Transfers to Your Business
You probably do not ship temperature-sensitive goods. The shape is the same anywhere.
- A regulated or important record kept on paper or in a spreadsheet. Replace it with a system that generates the record from the source, so compliance is a property of the system rather than a chore.
- Work dispatched by phone, radio, group text, or a shared inbox. Replace it with push, claim, and status, so the office can see what is happening and measure it.
- A process that lives in one person's head. Map it first, in writing, with that person in the room. Half the value is the map. The software is the other half.
The method is always the same order: sit with the team, write the map, build the smallest tool that removes the paper, verify it, then build the next one.
If your office runs on clipboards and "ask Sharon," get in touch. The first step is a one-week audit, and it produces the map whether or not you ever build anything.