Excel and Google Sheets can be excellent tools for keeping track of a business, especially a small one. But over time, even a system that was designed well can start getting in the way. And it isn't always about spreadsheets. Over the years, I've seen the same problems in all kinds of software. Here are five signs that it may be time to take another look at how you keep track of your business.
Symptoms
Remember how satisfying it was when you finally got that first formula to do exactly what you wanted? Then came more worksheets, links between them, and macros. Little by little, a handful of spreadsheets turned into a pretty respectable business management system. You built it yourself, and you knew how it worked. Whenever the business needed something new, you sat down and added the feature. Now try to remember the last time you made a significant change to it. Maybe you've had a list of improvements in mind for a long time, but you just can't bring yourself to tackle them. You'd have to get back under the hood, figure out why you wrote a particular formula, and remember what depends on it. And that's assuming you can still make sense of your own macros. Easier to leave it alone. It still works, right?
Diagnosis
The system has become difficult to change. It may have been beautifully built, but over the years it has accumulated business logic that's no longer easy to reconstruct. Especially if you only worked on it now and then, in between everything else you had to do.
I once worked with the owner of a tire shop who managed his inventory in Excel. At one point, he'd written a VBA macro that called a supplier's API to pull current prices. Later, a different supplier came along with better prices. But switching meant updating the macro to work with the new supplier's API. By then, the owner had forgotten how he'd written the code and what needed to change. He didn't want to dig back into it. So he kept buying from the original supplier, even though he could have made more money with the new one. Notice that nothing in the system was broken. It still worked. But changing it had become such a hassle that it was influencing his choice of supplier.
Treatment
Make a list of changes you've wanted to make but keep putting off. Not just technical changes: switching suppliers, changing how you calculate prices, adding services, or handling orders differently. Then look at why those changes haven't happened. Did you decide they weren't worth doing? Or do you keep stopping when you realize you'd have to rework the spreadsheets, formulas, and macros? If it's the latter, consider not only what the changes would cost, but also what the business is losing while you put them off. There are several possible answers: learn your way around the existing system again, bring in someone who can help, replace individual components, or move to another platform. You don't necessarily need to replace everything that's working. But if you're passing up profitable opportunities because you don't want to open the VBA editor again, that's worth thinking about.
Symptoms
At some point, you realize that doing something perfectly ordinary requires a rather unusual sequence of steps. Maybe you have to create a dummy transaction, move information into another spreadsheet, and then manually correct the result. Or perhaps the Notes field is being used to store information that really ought to have its own place in the system. How did that happen? At some point, someone needed a feature the software didn't have. Rebuilding the system for one situation seemed like too much trouble, so somebody came up with a workaround. It worked. Then it came in handy again. Before long, it was part of the instructions for new employees. In software, people often call these kinds of fixes “hacks” or “band-aids.” I wouldn't be too quick to criticize them. Sometimes a workaround is the most sensible way to solve a problem quickly, especially if the situation is temporary and nobody plans to build more processes around it. But temporary fixes have a way of sticking around.
Diagnosis
How many workarounds does it take before you have an architectural problem? It's a little like asking, “How many nuts make a pile?” One nut isn't a pile. A million nuts definitely are. So where's the line? There's no exact number for workarounds, either. One might cause no trouble for years. Another can create problems on day one.
At one garment manufacturer, the company regularly bought fabric from China. When a roll turned out to be defective, returning it to the supplier was practically impossible. Workers cut out the defective sections, used them as rags, or threw them away. But the inventory system had no transaction for writing off raw materials. The defective fabric still had to be removed from the inventory available for production. So the company created a separate warehouse location called “Defects” and started transferring the unusable material there.
At first glance, it worked. Defective fabric no longer got mixed in with usable fabric, and the quantities in the main warehouse looked right. The trouble was that fabric kept accumulating in the “Defects” location. Physically, it had been gone for ages. According to the system, though, the company still owned it. They had created a warehouse full of fabric that didn't exist. If those quantities were used to value inventory, the company was overstating its assets.
A perfectly practical solution to one problem had created another, much less obvious one.
Treatment
If your business relies on similar workarounds, try to remember why each one was introduced. What problem was it supposed to solve? Does that problem still exist? Has the workaround created new problems along the way? Pay particular attention to procedures employees explain with “That's just how we do it here” or “The software won't let us do it any other way.” You don't have to eliminate every workaround immediately. Some do their job just fine and aren't worth the cost of changing.
But it's worth understanding which problem you worked around—and whether you created another one in the process. In the garment manufacturer's case, the system was missing one operation: writing off raw materials. The workaround kept things moving, but it wasn't a substitute for that operation.
Symptoms
Imagine a customer calls your sales rep and says, “I need two pallets of Mars bars and one pallet of Mars MAX.” Sounds simple enough. Open an order and enter what the customer asked for. Instead, the sales rep reaches for a calculator. Or a piece of paper with numbers taped next to the monitor. Because the software doesn't understand pallets. It only understands individual candy bars. That's what happens when a business starts adapting its work to the way its software is built, instead of the other way around.
Diagnosis
I once worked with a company at a port that wholesaled candy bars. Mars, Snickers, and other familiar brands, just in industrial quantities. Its inventory system had been built in Microsoft Access. When products were received, quantities were recorded as individual pieces, so the developers decided that every other operation should use individual pieces too. But customers ordered by the box, case, and pallet. And when warehouse employees counted inventory, they dealt with packaged units, not individual candy bars.
To enter an order for two pallets of Mars bars, the sales rep had to multiply: 2 pallets × 48 blocks per pallet × 8 boxes per block × 36 bars per box. Mars MAX had different conversion factors. Whenever a new product arrived or the packaging changed, the sales reps wrote the new conversion factors on a piece of paper beside the monitor. Eventually, they memorized them. That company had some genuine mental-math geniuses. One of the key job skills was being able to multiply 36 by any number from 2 to 99, quickly and in your head.
Of course, the employees knew the conversions could be automated. That was one of the reasons I was asked to take a look at the system. The problem wasn't the math. The software was forcing employees to translate normal business transactions into a format that made sense to the software.
Treatment
I believe a business system should speak the same language as the customer. If a customer orders two pallets of Mars and one pallet of Mars MAX, the sales rep should be able to enter exactly that. No calculator, no conversion chart taped next to the screen. The software can still store quantities as individual pieces internally. That's a technical detail. The person entering the order shouldn't have to worry about it.
But there's another extreme to avoid. Every system needs rules, and sometimes an established business process really should change. Not every employee preference needs to become a new software feature. So it's worth asking one simple question: Why are we doing this extra step? If it's needed for oversight, verification, or a legitimate business rule, it may be perfectly reasonable. But if the only reason is “That's the only way the software can do it,” it's worth asking whether the business should really have to adapt.
Symptoms
You hire more people, hoping to free up your own time and increase sales. Somehow, neither happens. It feels like your business system has hit a capacity limit. You doubled your staff, hoping to double your sales. Instead, sales went up by just 20%, while the chaos increased by 200%. It wasn't always like this. You started with a few orders a day. You built a spreadsheet to keep track of things, added formulas, and worked out a process that made sense. The system helped you remember orders, track inventory, and handle growing sales. For a while, it let you do more without hiring more people. Then the business grew. There were more orders, more employees, and responsibilities to divide up. But the recordkeeping still worked much the way it had when you handled everything yourself. What once saved time now demands more and more of it.
Diagnosis
I was once brought in to review the operations of an online shoe store and recommend ways to automate them. The owner was doing everything she could to grow the business and stay ahead of her competitors. She had put together a photo catalog and price list for customers in Google Sheets, while tracking purchasing, sales, and inventory internally in Excel.
The store grew fairly quickly from zero to about 20 sales a day. Then growth stalled. Not because there weren't enough customers. Whenever the team tried to process more orders, things got mixed up: which customer ordered which shoes, where to ship them, who had paid, how much they'd paid, and what was actually left in stock.
The owner tried hiring more sales staff. But the number of orders they could process barely changed. There were simply more people who needed to exchange information, ask questions, and coordinate with each other. To keep purchasing, sales, and inventory under control, she had to be personally involved in almost every process. As soon as she left the office, information started piling up on handwritten scraps of paper. I spent a week studying how the store worked, then presented my recommendations and a proposal. We spent a long time discussing the details. She asked questions, and I explained what I was proposing and why. At the end of our conversation, she said:
“Funny... It took you a whole week to analyze my business. Last year I gave birth to my daughter, and I could only afford to stay away from the office for exactly one week, too. And I haven't had a vacation in four years. Please help me.”
Treatment
Your first recordkeeping system may have been exactly the right solution at the time. It helped you get organized, save time, and grow the business to a certain point. But take a look at where your employees' time goes today. Follow one order from the moment it comes in through payment and shipping. How many times does someone enter the same information in different places? How much time goes into reconciling records? How many questions have to go to the owner because nobody else knows the answer?
And here's another question: what happens if your order volume doubles? If you need more people to pack and ship products, that's normal. But if you need more people just to compare records and figure out who is supposed to ship what to whom, the problem probably isn't understaffing. Maybe you need to change how you keep records. Maybe you need to automate how information moves between employees or reconsider the tools you're using. If your employees spend more time coordinating and double-checking information than processing orders, perhaps it's not the headcount that needs to change. It's the way you manage the information.
Symptoms
You do a physical inventory count, compare what you actually have with what the system says you have, and can't explain the differences. According to the records, a product should be in the warehouse, but it isn't. Meanwhile, there's another product on the shelf that the system says shouldn't be there. Employees insist they did everything right. Maybe they did. But the numbers don't add up. You start reviewing transactions, asking questions, and looking for mistakes. And at some point, a thought creeps in: what if these aren't just mistakes? What if somebody is stealing? The worst part is that your system can't help you figure it out. You can see the result, but you can't reconstruct how you got there.
Diagnosis
I worked at a company that bought alcoholic beverages in bulk and sold smaller wholesale quantities to retail stores. Inventory was tracked in an aging system written in C specifically for that business. The main warehouse was counted once every three months. Every time, the results were terrible: major shortages and large discrepancies between product varieties. The owner, a former Navy sailor, had a straightforward solution. He ordered every office employee to come in on Saturdays and count the warehouse. And we'd keep doing it until the difference between the records and the actual inventory was down to two bottles. That's how we spent more than two months: counting bottles every Saturday, then comparing the results against inventory movements and the previous count. Gradually, we began to understand where the discrepancies were coming from. Sometimes the physical count itself was wrong. Sometimes real transactions never made it into the system at all. For example, a customer might order a case of Pshenichnaya vodka, then show up to pick it up and ask to swap it for a case of Stolichnaya. The warehouse employee would happily make the exchange. The two products cost the same, the customer was satisfied, and the total hadn't changed. Why bother updating the software? So the system still showed one brand in stock even though it had been shipped, while the other brand's recorded quantity was lower than what was actually on the shelves. Three months later, good luck figuring out where the discrepancy came from. As it turned out, the owner's suspicions weren't entirely unfounded, either. We also identified employees who stopped by the warehouse in the evenings to pick up their entertainment for the night. So the same inventory discrepancies included counting errors, gaps in the recordkeeping process, and actual misconduct. To handle the product swaps, I added a new transaction type to the software: “Product Substitution in an Order.” It allowed employees to replace one product with another, even when the prices were different. In that case, the difference was reflected in the customer's balance. It added a little time to the shipping process, but now the system could record what had actually happened. Eventually, we got the warehouse back under control. But it took a lot of stress and a lot of lost Saturdays.
Treatment
When your records stop matching reality, the first instinct is to find someone to blame. Sometimes there really is someone to blame. But first, it helps to understand which operations are causing the discrepancies. Pick a few specific cases and try to trace each one from beginning to end. What actually happened? Who did it, and when? What transaction should have been recorded in the system? Was it recorded at all? Pay special attention to things employees consider minor: swapping products, changing an order, processing a return, or writing off damaged goods. These are ordinary parts of doing business. Your system needs a clear way to account for each of them. Also check whether you can tell who changed a record, when, and why. And whether it's clear who is authorized to perform particular operations. Not every problem can be solved by writing code. Inventory-counting errors call for better counting procedures. Theft needs to be addressed separately, through control over access to inventory and clear accountability. But if employees routinely do something in the real world without recording it in the system, find out why. Maybe they don't understand the consequences. Or maybe the software simply doesn't offer a convenient way to record something that's perfectly normal in your business. In our case, one new transaction type was enough to solve one of those problems. And one more thing: don't wait three months to discover that your inventory is off again. The more time that passes between a transaction and the discovery of an error, the harder it is to figure out what happened. The goal isn't to make everyone afraid of the system. It's to make the records trustworthy again.
Over the years, I've noticed a pattern: business owners rarely reconsider their recordkeeping systems when the first inconveniences appear. They usually come back to the question later, when familiar tools are already making work harder and every change has become expensive and risky. How many of these five signs do you recognize in your own business? Maybe nothing serious is happening, and your spreadsheets will keep doing their job just fine for years to come. Or maybe it's worth looking at how much time and effort goes into keeping your current process running—and whether something should change while the system is still working. After all, you started your business to develop new bread recipes, create products, and serve customers. Not to spend your days figuring out who changed a number in a spreadsheet.