Spreadsheets are the most successful business software ever made, and they run a surprising number of good manufacturing shops. They’re free, everyone knows how to use them, and you can model almost anything in a grid of cells. For a shop of three people running a handful of jobs a week, a well-built workbook is genuinely hard to beat.

The problem is not that spreadsheets are bad. The problem is that they don’t fail loudly. They degrade quietly, one workaround at a time, until one day you’re spending more effort feeding the spreadsheet than the spreadsheet saves you. The trick is recognizing that point — ideally a little before you reach it, not a year after.

Here are the specific signs that a shop has outgrown its spreadsheets, and a practical way to make the move without a painful rip-and-replace.

Sign 1: Two people can’t trust the same number

The first crack usually shows up in inventory. Someone opens the stock workbook, sees 40 of a part, and promises them to a customer. What they can’t see is that 30 of those 40 are already committed to a job in production. The single number — quantity on hand — was never the number that mattered. What matters is what’s available: on hand, minus what’s already spoken for.

A spreadsheet can model this, but only if every allocation is entered by hand the moment it happens, by everyone, every time. In practice that discipline breaks within a week. The day you double-promise material and find out on the floor is the day the spreadsheet stopped being the source of truth.

Sign 2: The workbook only works because one person knows its secrets

Every shop has the master file with the clever formulas, the hidden columns, and the tab nobody else dares touch. It works beautifully — as long as the person who built it is there. When they’re on vacation, things mysteriously stop adding up. When they leave, the file becomes a fragile artifact everyone is afraid to change.

This is a real operational risk, not a personality quirk. If your production planning depends on tribal knowledge of a spreadsheet, you have a single point of failure that no backup can fix. Software with defined fields and rules moves that logic out of one person’s head and into a system the whole team can use.

Sign 3: You’re reconciling instead of working

Count the copies. There’s the inventory workbook, the job tracker, the purchasing list, and the quality log — and the same part number lives in all four. When something changes, someone has to update it in every place, and they don’t, so the files drift apart. Now a chunk of someone’s week is spent reconciling: figuring out which file is right when they disagree.

Reconciliation is pure waste. It produces nothing a customer pays for. When you notice that a meaningful share of your admin time is just making spreadsheets agree with each other, the spreadsheets have become the job instead of the tool.

Sign 4: History is gone the moment a cell changes

A cell holds one value. Overwrite it and the previous value is gone — who changed it, when, and why all vanish with it. For a casual list that’s fine. For a shop that has to answer “what was the BOM revision when we built lot 4471?” or “who approved this change?”, it’s a serious gap.

If you do any regulated or audited work — AS9100, ISO 13485, customer source inspection — you need an audit trail that a spreadsheet structurally cannot provide. The moment an auditor asks for change history you don’t have is the moment the case for software makes itself.

Sign 5: You can’t see status without asking someone

In a spreadsheet-run shop, “where is job 5582?” is answered by walking the floor or pinging the lead. The data is technically in a file somewhere, but it’s a snapshot from whenever it was last updated, not a live picture. As the number of jobs in flight grows, the cost of not having real-time status grows with it — in missed dates, idle machines, and expedite fees.

What good software actually changes

Moving off spreadsheets isn’t about features for their own sake. The concrete differences that matter on a shop floor are narrow and specific:

How to move without the pain

The fear of switching is reasonable: shops have been burned by six-month ERP implementations that cost a fortune and never quite worked. The way to avoid that is to keep the move small and reversible.

  1. Start with your worst spreadsheet. Don’t migrate everything. Pick the one file that causes the most pain — usually inventory — and move just that.
  2. Bring your data with you. Export the spreadsheet to CSV and import it. A good system meets you where your data already is instead of demanding you re-enter it.
  3. Run parallel for two weeks. Keep the spreadsheet as a backup while you build confidence the new system matches reality. When it does for two weeks straight, retire the file.
  4. Expand one area at a time. Once inventory is solid, add BOMs, then work orders. Each step is small, and you can stop or roll back at any point.

Done this way, the switch is a series of low-risk steps, not a leap. You’re never betting the shop on a big-bang cutover, and the team learns the system by using it on one familiar problem at a time.

The honest test

You don’t need software because spreadsheets are uncool. You need it when the cost of keeping your spreadsheets honest — the reconciling, the double-checking, the one person who knows the formulas — has quietly grown larger than the cost of replacing them. If two or three of the signs above sound like your shop, that line has probably already been crossed. The good news is that crossing back, the right way, is easier and cheaper than it’s ever been.