Why We Stopped Keeping a Different Spreadsheet for Every Customer

At one point we were running the business out of seven different places at once: a spreadsheet for customer issues, a delivery calendar in Slack, an estimating queue in its own spreadsheet, our EOS documents in another, sales numbers in a fifth, a backorder list back in Slack, returns tracked on paper, and a separate project management sheet just for the larger builders juggling multiple jobs at once.

None of it was wrong, exactly. Each piece existed because it solved a real problem when it was set up. The trouble was that they never talked to each other, and they never got maintained the same way. Some people lived in one spreadsheet every day and never opened the others. Some got checked once a week. A few, if we're honest, almost never got checked at all.

That's not really a discipline problem. That's what happens when the systems themselves are disconnected — you can't blame someone for missing a backorder sitting in Slack when their whole day is estimating, and you can't blame the estimator for not knowing about a return that's sitting on paper at the counter. Nobody had the full picture, because the full picture didn't exist anywhere.

We knew we needed something that brought all of it together — one place where an estimate, a delivery, a return, and a backorder were all connected to the same job instead of scattered across seven unrelated files. What we didn't want was the other extreme: a six-figure first-year ERP implementation built for distributors ten times our size, sold through a quote-only process, that would take a year to stand up and lock us into per-seat pricing for good.

So we ended up building the thing in between ourselves — not because running a software project was the plan, but because nobody was selling what a business our size actually needed.