Luke's Inventory: when spreadsheets break

Every small business has a spreadsheet moment. That's the moment when your spreadsheet stops being a tool and becomes a liability. We hit that moment with Luke, and it's the reason we now build inventory software.

The Setup

Luke runs a parts distribution business. Auto parts, electrical components, industrial supplies — the kind of stuff that comes in bins and gets pulled off shelves. When we first met him, he was running his entire operation on a set of spreadsheets. Four of them, actually. One for inventory, one for incoming shipments, one for orders, and one that he called "the mess."

His team was good at what they did. They knew the parts. They knew where everything was. But the business had grown past what a spreadsheet could handle, and nobody wanted to admit it. Every time someone placed an order, someone had to open the inventory sheet, search for the part number, check the quantity, check the incoming sheet to see if more were on the way, and then manually update everything. This took fifteen minutes per order. Thirty if there was a return.

The breaking point came the week they processed a nine-thousand-dollar order and discovered after shipping that they'd sold stock they didn't have. Two thousand dollars of that order was phantom inventory — parts they'd received but never entered into the spreadsheet. That was when Luke called us.

What We Found

The spreadsheets weren't even the worst part. The worst part was that they were actually pretty well-maintained. Luke's team had been diligent about entering data. The problem was that the data lived in four different places and nobody had written a formula to cross-reference any of them in over a year.

Here's what we found:

- The inventory sheet showed three hundred items with a quantity of zero or less. Of those, two hundred had incoming shipments already in the pipeline that nobody had matched. - The orders sheet had six months of data but no way to tie an order back to what was actually in stock at the time it was placed. - There was no way to tell which parts were slow movers and which were about to run out. - Everything was manual entry, which meant every error propagated through the entire system.

This is the standard small business inventory problem. You're not lazy, you're not stupid. You just have a tool that wasn't designed for what you're asking it to do.

What We Built

We didn't build a full ERP. We built the smallest thing that could solve Luke's specific problems.

Three things:

1. A central inventory database. All parts in one place with their quantities, locations, and cross-reference numbers. That's it. Not comprehensive — just the four walls of his warehouse and everything inside them.

2. A simple search that found any part by any identifier. Manufacturer number, supplier number, the number on the physical box — search once, find everywhere.

3. An order intake form that pulled real-time stock data before the order was placed. If it showed zero, it showed zero. No more phantom inventory.

That's all we built. We did it in three weeks. We did it for what he'd been quoted for a full-featured system would have cost him over six months.

Why This Matters

Spreadsheets are great for lists. They're terrible for operations. The difference is that an operation requires real-time accuracy, cross-referencing, and auditability. A spreadsheet gives you none of those unless you build it yourself, and by the time you need it, you're already past what a spreadsheet can do.

What Luke needed wasn't a database. He needed a database that understood what a part number meant. Not just "where is this part?" but "where is this part, what's its relationship to every other part that fits in its place, and when do I order more?"

That's what we built. Not generic inventory software — inventory software that understood his specific problem.

What We Learned

Building for Luke taught us three things that we apply to every custom inventory project since:

First, the user is always right about the problem but almost always wrong about the solution. Luke knew his spreadsheets were killing him. He didn't know that what he needed was a cross-reference database that understood part relationships. That's something you'd only know if you'd built it before.

Second, the smallest possible solution is always the right answer. We could have built him a full inventory management system with purchasing, receiving, and reporting. Instead we built exactly what he needed — a search bar and an order form. Everything else came after.

Third, integration cost matters more than software cost. The expensive part wasn't our software — it was integrating his existing data into a new system. That's where the three weeks went. That's where every dollar gets spent.

What This Means for You

If you're running a business on spreadsheets and you're starting to feel the pain, here are the signs:

- You have more than two spreadsheets doing the same job - Multiple people need access to the same data at the same time - You're manually checking one sheet against another to make decisions - You've had an inventory error in the last ninety days that cost you money

Any of those is a sign. Two or more means you've already passed the spreadsheet breaking point.

The question isn't whether you need custom software. The question is whether you need custom software or whether you need the right tool that's already built for what you're doing. Most inventory systems are overkill for what small business actually needs.

We run this in production every day. If you want the same capability for your program, or help turning ops data into a clear decision, get in touch.