Business reporting fails in two opposite ways. The first is absence: numbers arrive once a year, from the accountant, as archaeology. The second is noise: a forty-metric dashboard, built in a burst of enthusiasm, that nobody has opened since March. Both share the same root cause — metrics matched to the wrong frequency. Every number has a natural cadence: the rate at which it changes meaningfully and at which someone can act on it. Look more often and you're managing noise; less often and you're managing history. Here's the full stack for an owner-led business, layer by layer.
Daily: two numbers, ninety seconds
The daily layer exists to catch fires while they're small, so it's brutally short: cash at bank (against the week's committed payments) and yesterday's sales/bookings (against a normal day). That's it. Both are glanceable from your phone via the bank feed and your POS/job system. The skill at this layer is restraint — daily P&Ls and daily margin are noise that trains you to overreact. Ninety seconds, two numbers, move on. Most days the entire output is "normal," and "normal," confirmed daily, is what buys the calm everything else runs on.
Weekly: the five-line pulse
Weekly is the operating layer — frequent enough to steer, spaced enough to be signal. The standing five for most SMEs: cash after commitments (the honest version of the balance), pipeline (quotes out / bookings ahead — the leading indicator that predicts revenue eight weeks early), debtors over terms (with one named chase action), labour against revenue or roster (the fastest-moving big cost), and one operational quality number native to your business — jobs completed on time, response time, complaints, NPS replies. Reviewed same time weekly, written in five lines, with at most one action arising. The weekly layer is where drift gets caught at week one instead of week six — which is its entire return on investment.
Monthly: the one-page verdict
Monthly is the decision layer — the full picture, properly closed (a five-day close makes this land while it's still actionable). The page: P&L versus budget and last year, with gross margin trend; the cash bridge and 13-week forecast; debtor days and creditor days as trends; the customer/product margin view quarterly-refreshed; and — the section that does the heavy lifting — commentary: three to five sentences from whoever owns the numbers on the biggest variance, the trend that needs watching, and the decision being recommended. Numbers describe; commentary commits. The monthly meeting then has one agenda: the page, the commentary, and the decisions — thirty to sixty minutes, same date monthly, decisions minuted with owners.
The monthly layer is also where the daily/weekly layers get audited: if something surprised you this month, ask which weekly number should have caught it — and add or fix that line. The stack improves by autopsy.
Quarterly: the questions, not just the numbers
Quarterly zooms out from "are we on plan?" to "is the plan right?" The pack: the quarter against budget with full-year reforecast if warranted; the margin-by-customer/product refresh; the working-capital trio (debtor, stock, creditor days); team and capacity view against the next two quarters' demand; and the compliance verification pass. But the numbers are pre-reading — the quarterly session itself runs on questions: What's working that we should double? What's drifted that needs a decision, not another month of watching? What did we say last quarter that we didn't do, and why? The quarterly layer is where the business gets steered; everything beneath it exists so that this conversation happens with facts instead of impressions.
Making the stack stand up
Three construction notes. Every layer has one owner — who produces it, by when, in what format; reporting that's everyone's job is no one's. Automate the plumbing once — bank feeds, dashboard tiles, report templates; the stack should cost minutes a week to run, or it won't survive busy season. And prune annually — any number that hasn't changed a decision in twelve months loses its slot. The test for every metric at every layer is identical: what would we do differently if this moved 20%? No answer, no place. A reporting stack isn't a measurement system, in the end. It's a decision system with numbers attached — and built at the right cadences, it's the closest thing a small business gets to flying on instruments.
If your reporting is either absent or ignored, the fix starts with knowing which numbers matter for your business. Our free Business Health Check is a five-minute first step.
About the author
Nick Lucock
Chief Executive Officer, Valont
Nick leads Valont's day-to-day operations across Finance, People, Operations and Growth. He writes about how the work actually gets done — the processes, systems, and tools that keep Australian SMEs compliant and growing.
LinkedIn →