When a spreadsheet isn't the answer
A shared spreadsheet has no real login, no accountability for who changed what, and no way to enforce that a record is actually finished rather than just sitting there. Past a certain point, the fix isn't a better spreadsheet — it's a small, purpose-built tool: real accounts, a defined workflow, and a database instead of a file that lives in someone's inbox.
What "small" means here
Deliberately not a platform, not a framework, not something with a six-month build. A login-gated front end, a handful of screens matching how the work actually happens, and a database that's queryable and backed up — built around the process as it exists, not a generic template it has to be bent to fit.
What this looks like when it's real
The internal data-entry tools case study is this exact build: a PHP/MySQL front end replacing a shared spreadsheet, with region-tagged entry and a real closeout workflow. Where the input is documents rather than manual typing, the PDF extraction pipeline feeds structured data into the same kind of tool.