Notes from
the studio.

A small-business dashboard is a file you open once a week to know whether the business is moving in the right direction. The temptation is to throw every available number at it and call it a dashboard. The result is a wall of numbers nobody reads. The five KPIs that earn a spot are monthly revenue, gross margin, CAC, cash conversion cycle, and MRR. Each one answers a separate question — did the business sell, is each sale profitable, are sales getting cheaper to land, is cash moving fast, is the recurring side growing — and each one computes from a separate sheet in a small-business file.

Handing a messy spreadsheet to a colleague is expensive. The first ten minutes are questions ('is this row a refund or a duplicate?'), the next twenty are formula errors that turned the totals wrong, and the afternoon is spent undoing duplication nobody meant to create. A short pre-handoff audit turns that scramble into a clean file the reader can use straight away. The pass is mechanical, takes an hour, and the savings show the same day.

The monthly report starts as an ad-hoc reproduction and stays that way for as long as the format keeps shifting. There is no schedule, just a Friday afternoon scramble. Then one quarter the input changes format and the whole report rebuilds itself. Then again. At some point the operator stops enjoying it, and the report becomes a recurring engagement rather than a special event — same cadence, same shape, same hand-off, just delivered without the scramble. The choice between ad-hoc and recurring isn't about file size; it's about whether the input has settled into a stable shape that can survive the next month.

A dashboard is a file you can re-open a month from now and read in two minutes. That sounds simple; it isn't. Most spreadsheet dashboards rot quickly because they were built around the question of the moment instead of the file that holds the data. The trick isn't a clever formula. The trick is to front-load a handful of boring decisions: which file is the source of truth, what the KPIs are, and which formulas live where. Once those are locked, the dashboard stays readable when the team changes and the data shape shifts underneath it.

Spreadsheets get messy long before anyone decides to fix them. A second SKU column gets added to handle a one-off reconciliation. A new date format slips in for a single export. Currency symbols creep into half of one column. By the time the file is opened for a real decision, the totals don't match and nobody can say why. A structured, named cleanup is the move that pays for itself the first time the file is read.