The work was fast. The paperwork was not.
A multi-state hazardous materials and environmental emergency response company, working out of East Texas. Crews who could be on a roadside within hours, and a billing cycle that waited days on a drive back to a filing cabinet.
What it looked like before
The operational record lived in Microsoft Access databases and on paper. Crews were dispatched through an off-the-shelf paging app that could alert a responder but capture nothing at all about what happened next.
So everything that happened at a scene came back to the office on paper and was re-keyed by hand. The job was done, the customer was taken care of, and the invoice sat waiting on someone's drive back to a desk. No one in that operation was slow. The record was.
What I built
One system on three surfaces — native iOS, native Android, and web — delivered across four phases against a standing two-week review cadence. The first iOS release went to the App Store in September 2020; Android followed in 2022.
- Dispatch with push notifications to responders, and live job status from the field
- GPS and location tracking, with photographs captured at the scene
- Incident reporting written from the mobile app rather than from a desk
- A public intake form for brokers that opened a tracked incident with a reference
- A web incident manager, a document vault with a written operating manual, response summary reports and incident search
- Manpower records, collections contacts and billing
- User registration and two-factor authentication
It was wired into the systems the business already ran on — a CRM, the accounting platform, and their Microsoft tenancy — and moved onto a dedicated server as the load grew.
It became how the company talked about its own work.
The system generated a job number in a particular format. After a while that format started turning up as the subject line of emails their own staff wrote to each other. No one instructed them to do that. They needed a way to refer to a job, the system had handed them one, and it quietly became the company's shorthand.
That is adoption you can see in how people talk. It does not show up in a usage report, and it is worth more than one.
Then the owner asked a question he could not have asked before.
Once several years of incidents had accumulated as data rather than as paper, he asked whether it could be used to predict call probability by geography, by day of week, and by time of day.
I am not sure he noticed he had crossed a line just by asking. That is not a question you can ask when your record lives in a filing cabinet. The system had stopped being somewhere to put information and become something the business could think with.
Still running, seven years on
The relationship started with a software conversation in late 2019 and is still going. That is the part I would point at rather than any single feature: not what shipped, but that it is still in use and still being extended by the same person who built it.
I have deliberately not named this company, quoted its owner, or published what the work cost. That stays true until they tell me in writing that I can.