The problem
A lot of internal business process runs on a shared spreadsheet, emailed around and edited by whoever has it open — sales or job data logged inconsistently, no real login or accountability for who changed what, and no clean way to mark a job actually done versus just sitting there.
What was built
A purpose-built PHP/MySQL front end for entering and tracking sales/job data — real login and session handling instead of a shared file, region-based data entry so records land where they belong, and a defined closeout workflow so a job has a clear "done" state instead of living forever in an open spreadsheet.
Why this is the hard part
The technical build is the easy part — a login form and a database table aren't hard on their own. The actual work is understanding the real workflow well enough to build something people will use instead of quietly going back to the spreadsheet: what "done" actually means, who needs to see what, what happens when two people touch the same record. That discovery step is exactly what a Workflow Assessment exists to do before any code gets written.