This Week, Last Week, Last Year

The least impressive-sounding decision we made turned out to be the one that changed how people actually use the product.

This Week, Last Week, Last Year

The most useful thing we built into CounterCtrl Cloud is also the least impressive-sounding on paper. We made every number carry its own comparison — this week, last week, this week last year — on every screen, by default, with no extra click required.

It sounds like a minor formatting choice. In practice, it's the decision that changed how people actually use the product.

Take a single number: a store did $84,000 last week. On its own, that's not information — it's just a fact with nowhere to go. Is $84,000 good? Bad? Flat? You genuinely can't say without something to measure it against. Put last week's number and last year's number beside it, and the same $84,000 becomes a decision in about two seconds. A store director looking at that screen and a regional VP looking at the same screen independently reach the same conclusion, without a phone call to align on what the number means.

Most reporting tools treat comparison as an advanced feature — something a power user configures once they know to ask for it. We decided that was backwards. If context is what makes a number usable, then context that requires an extra step is context that mostly doesn't get used, because the people who need it most are usually the people with the least time to go looking for it.

That single default — never separate the number from what makes it meaningful — runs through every module, from Sales to Weekly Performance to Coupons. It's not a feature so much as a rule we hold ourselves to when we build anything new: if a number can't defend itself with context on the same screen, it isn't finished yet.