When to replace the spreadsheet

Spreadsheets are a good first system. They fail when three people edit the same truth, when the stall cannot open a laptop, or when day-close is a ritual of copy-paste. The signal is not “we hate Excel.” It is lost rows, unclear roles, and a process that only one person understands.

Replace the workflow, not every tab

An internal app should take the painful path — intake, orders, remittance, dispatch — and leave reporting in a CSV if that still works. RedN Farm did this offline on Android for farm-to-table ops. BusyStreet did it for crew ticketing and settlements on POS handhelds. Neither started as “build an ERP.”

What we ask before a sprint

• Who is blocked when the sheet is wrong?
• Does the work happen at a desk, a stall, a yard, or a bus?
• What must print or survive without signal?

If those answers are sharp, a 3–6 week Spreadsheet → System sprint is usually cheaper than another year of the tab.

Offering: Spreadsheet → System. Work: RedN Farm, BusyStreet.