The situation
A product support manager at a Winona area manufacturing company was tracking customer support cases on a legal pad. Every case carries real detail: a customer name, a company, a product serial number, a machine make and model, what went wrong, whether a replacement part went out, and a QuickBooks reference for the paperwork. On paper, none of that is searchable. Finding an old case meant remembering it, or digging.
The slow part came first
Months before any rebuild, the process got written down properly. Every field a case needs, in the order he works through a call. Four statuses, from Open to Resolved. The rules that keep the record trustworthy: a resolution date is stamped the moment a case is marked Resolved, and records are never deleted, only resolved. Plus a written checklist for testing the system before trusting it.
That design work took longer than 90 minutes. I am not going to pretend it did not.
The rebuild
I rebuilt that written system as a standalone app, independent of the platform it was first designed for, so there is no subscription standing between him and his own case records.
It runs on his computer and his tablet, showing the same cases on both. On the tablet it works with no internet connection, which matters when support work happens away from a desk. Cases entered offline save on the tablet, show plainly that they are waiting to sync, and upload on their own when a connection comes back.
Each case gets its own permanent case number the moment it is created. His existing company list imports in one pass instead of being typed in one company at a time. His case records export to a spreadsheet file whenever he wants a copy outside the system. The whole thing is finished in his company's own colors, with his name and role on it, so it reads as his system, not a generic tracker.
Because the spec was already written, the rebuild itself fit inside one sitting.
Where it stands
The system is built and in testing. The fine-tuning happens with him at the table: how he wants the case numbers to read, his live company list, his currently active cases moved in, and a run through the written test checklist on his own tablet. After that it moves under his own hosting and his own name.
No time-saved numbers here yet. He has not run it for a month, and I do not publish results a client has not lived. When he has, this page gets updated with his real numbers, and his own words if he offers them.
The point
The build was the fast part because the thinking was already done and written down. That is the order that works: get one process out of your head and onto paper first, then build exactly that, nothing more.
Questions first? Email josh@promptingeveryday.net.