Your competitor monitoring spreadsheet worked... until it didn't

How to identify when a manual monitoring process (prices, inventory, competition) hit its limit and adding more columns won't fix it

Someone built the competitor monitoring spreadsheet two years ago. Today nobody’s quite sure the data in there is reliable — and it’s still what the company uses to decide prices.

It’s a pattern that repeats across retail, distribution, hospitality, and any business where competitor pricing matters. At first, the spreadsheet works perfectly. Over time, without anyone deciding it explicitly, it stops working — and the company keeps using it anyway, because nobody stops to notice the exact moment it crossed that line.

How it starts (and why it works at first)

It almost always starts simple: three or four competitors, one product or a narrow category, one price to check each week. Someone visits the competitors’ sites, jots down prices in a spreadsheet, and in twenty minutes the weekly report is ready. It works well because the problem is small: few variables, low frequency of change, one person who understands the whole sheet.

This is exactly the kind of process where a spreadsheet is the right tool. Nothing more sophisticated is needed to solve a problem this size — and any consultant proposing a full platform for this is selling you more than you need.

How it breaks (without anyone noticing)

The problem shows up when the business grows in variables, not in spreadsheet size. More locations appear — it’s no longer one price, it’s ten, one per branch or city. More channels appear — physical store, delivery, marketplace, each with its own pricing logic. Promotions appear that change the real price even though the list price stays the same. Different hours appear where the same product costs differently depending on the time of day.

The spreadsheet keeps existing, and in fact keeps growing: more columns, more tabs, increasingly complex formulas that eventually only the person who built them fully understands. But the time available to maintain it doesn’t grow at the same pace — it’s still the same person with the same twenty minutes a week, now trying to cover ten times more variables.

The result, in most cases we see, is predictable: gaps start appearing. Data from three weeks ago that nobody updated. Comparisons that are no longer comparable because something changed in between (a competitor launched a promo, another switched suppliers, a third one simply stopped existing in that location). And most dangerously: the spreadsheet keeps getting used to decide prices, with the same confidence as when the data was reliable.

The signal almost nobody watches for

The clearest sign that a manual monitoring process has hit its limit isn’t “the spreadsheet looks huge” or “it takes us a lot of time.” It’s more specific: when the person maintaining it spends more time checking whether the data is right than actually analyzing it to decide something.

At that point, the process has inverted. It stopped being a tool that generates information for decisions, and became a permanent auditing job that consumes time without generating new value. It’s the difference between “I have data and I use it to decide” and “I have data and I’m no longer sure I can trust it, but I keep using it because there’s nothing else.”

Another, quieter signal: when two people in the company check the same spreadsheet and reach different conclusions, because each one interprets the gaps or inconsistencies they already know exist in their own way.

A typical case (composite, not a specific client)

Picture a regional distributor with a presence in five cities, selling through a physical store and a couple of marketplaces. Two years ago, when it operated in just one city and one channel, someone on the sales team maintained a spreadsheet tracking three direct competitors’ prices. It took half an hour a week and was enough to adjust prices with good judgment.

Today, that same person — with the same hours available — is trying to cover five cities, two channels, and seven competitors who also change pricing strategy more often than before (cross-promotions, volume discounts, different prices on each marketplace). The spreadsheet now has fifteen tabs. Nobody else in the company knows how it’s built. And when management asks for “the average competitor price in city X this week,” the answer takes two days and comes with a warning that “some data might be outdated.”

That’s the exact moment automating makes sense — not before, when the spreadsheet was still enough, and not years later, once pricing decisions were already made on information nobody could guarantee was correct.

When does automating make sense, and when doesn’t it?

Automating makes sense when two or more of these conditions apply at once: the number of variables to monitor (locations, channels, competitors) grew significantly since the original process was built; the person maintaining it spends more time correcting than analyzing; business decisions (pricing, promotions, purchasing) depend on that data on a weekly basis or more often; and errors or inconsistencies have already affected a real decision, not just in theory.

It doesn’t make sense to automate yet if the process is still manageable with the time available, if the variables are few and stable, or if the decisions depending on that data are infrequent (say, a quarterly review instead of a weekly one). Automating a process that’s still working fine by hand is spending budget on a problem that doesn’t exist yet.

It also doesn’t make sense to jump straight to a large price-monitoring platform if the real problem is smaller: sometimes it’s enough to automate just the data collection (so it no longer depends on someone copying and pasting prices by hand) and leave the analysis and the decision to the people already doing that part well. The size of the solution should match the actual size of the problem — over-automating has a cost too, in money and in implementation time that could go toward another priority for the business.

This week’s takeaway

If your company has a monitoring process — prices, competitors, inventory, anything — that started as a simple spreadsheet, ask yourself this specific question: does the person maintaining it spend more time correcting data than using it to decide something? If the answer is yes, you don’t need a bigger spreadsheet. You need to recognize that the process changed in nature, and the tool that worked for the small problem no longer works for the problem you have today.

FAQ

How do I know if my monitoring process has already hit its limit?

The clearest signal is maintenance time versus usage time: if correcting and updating the spreadsheet takes longer than analyzing it to make decisions, you’ve already hit the limit. Another signal is when two people in the company reach different conclusions from the same spreadsheet.

Does automating this always require an expensive platform?

No. Often it’s enough to automate just the data collection piece (so it no longer depends on manual copy-pasting) and leave the analysis to the people. The size of the solution should be proportional to the actual size of the problem, not to the fear of falling behind.

What happens if we keep using the spreadsheet even though it’s no longer reliable?

The risk isn’t just wasted time — it’s making business decisions (pricing, purchasing, promotions) based on information nobody can guarantee is correct. That’s a silent cost that doesn’t show up in any report, but affects real margin.

In which industries is this problem most common?

It’s especially common in retail, distribution, hospitality, and any business where competitor pricing or availability changes often and multiple locations or channels are involved. But the pattern — a manual process growing in complexity faster than the time available to maintain it — repeats in any area that depends on constantly updated data.

---

Want to find out if a process in your company has already reached this point? You can also check our article on migrating to the cloud is not a data strategy to understand the difference between having data and being able to trust it.