The spreadsheet is the ERP: when to stop and build a real system

Every ERP we've built, for a college, for a small manufacturer, for a sales team, replaced the same thing: a spreadsheet that had quietly become mission-critical. Spreadsheets are a great first system. They're free, everyone knows them, and they bend to any process. The problem is they never tell you when they've stopped working.

Three signs the spreadsheet is done

First: two people need to edit the same data at the same time, and someone's changes get lost. Second: you have a “master” file plus copies with names like final-v2-REAL, and nobody trusts any of them. Third: a routine question, how many orders shipped last month, which students haven't paid, takes someone an afternoon to answer.

What a small ERP actually is

Forget the enterprise software imagery. For most small businesses an ERP is three screens: things coming in, things going out, and who owes what. One database, a few roles, and reports that answer the questions you're currently answering by hand. Built lean, it's weeks of work, not months.

The mistake is going straight from spreadsheet to a bloated off-the-shelf suite that models someone else's business. The systems that stick are the ones that model your process, just with a database, permissions, and history where the spreadsheet had hope.