Reporting:
the system that tells you what's actually working.

A reporting system is what converts the noise of running a business — enquiries, bookings, ad spend, reviews, revenue — into a short list of decisions you can actually make. Done well, you spend five minutes on a Monday and know what to change. Done badly, or not at all, you run on vibes, lean on your accountant's quarterly P&L, and find out six months late that one channel has been carrying the other three.

This page is what a good one actually looks like — the components, the failure modes, and what to build if you're doing it yourself.

Why most owners fly blind.

The data exists. It's in the CRM, the ad platforms, the calendar, the review sites, the bank account. The problem is that nobody has stitched it together, so the owner ends up making spend decisions on feel and revenue decisions on whatever the loudest customer said last week.

1 in 3

local business owners can't tell you their cost per booked customer

5 min

is all a weekly read should take. If it takes longer, the report is the wrong shape

6 weeks

average delay before a leaky channel shows up in the accountant's P&L

5

numbers is all most local businesses need, reliably, every week

The goal of reporting isn't more data. It's fewer decisions, each one better informed.

What a good reporting system actually does.

Five components. The order matters — skip the first and the rest are built on sand.

1. Lead source capture

What it does: every enquiry gets tagged with where it came from — specific ad, specific referrer, specific page, specific offer. Automatically, at the moment it arrives, not reconstructed later.

Why: without source attribution everything downstream is guesswork. You can't tell a good channel from a lucky month, you can't kill a losing campaign, and you can't repeat what worked.

2. Funnel visibility

What it does: tracks the same leads through the stages — enquiry → qualified → booked → completed → repeat — with a conversion rate at each step. One view, one place.

Why: "our numbers are down" is almost never true across the whole funnel. It's one specific step that's leaking. You can only fix the step you can see.

3. Revenue attribution

What it does: ties actual money paid back to the original source — so each channel has a real cost-per-customer and a real revenue number, not a cost-per-lead.

Why: cheap leads are usually cheap for a reason. A channel that costs 3x more per lead but converts 5x better is the one to double down on. You can't see that without revenue attribution.

4. Automated weekly summary

What it does: on a set morning, a short, same-shape-every-week report lands — five to ten numbers, week-on-week and month-on-month, plus the one or two items that changed materially.

Why: reports you have to go and fetch don't get read. Reports that arrive, in the same shape, at the same time, build a muscle memory that actually influences decisions.

5. Decision thresholds

What it does: pairs each number with a pre-agreed trigger. Response time over 10 minutes → flag. Cost per booked customer over £X → review creative. Review count flat for 2 weeks → check the ask flow.

Why: numbers without thresholds are scenery. The point of a report isn't to know; it's to act. Pre-agreed rules convert watching into doing.

Where most owners go wrong.

The five common reporting failure modes — often layered on top of each other:

  • The accountant-only view. Quarterly P&L is the only report the business ever sees. It's accurate and useless for operational decisions — by the time a problem shows up there, it's been running for months.
  • The 40-widget dashboard. An agency built a Looker Studio with every metric imaginable. Nobody opens it. When they do, they can't tell what matters. More data, less signal.
  • Vanity metrics. Impressions, reach, followers, clicks. None of them pay the rent. Any report that leads with them is optimising for the wrong thing and quietly teaching everyone to do the same.
  • Broken source tracking. The CRM captures "website" and "referral" and nothing else, so every channel blurs into one. Without clean sources upstream, every report downstream is a guess.
  • No decision rules. Numbers are watched, not acted on. The report becomes a weekly ritual of noticing and doing nothing. Thresholds and triggers are what turn reporting into a management tool.

What we build.

The reporting pillar from Flow Local is a complete working system — plumbing, dashboard, weekly email, thresholds — typically live inside two weeks.

  • ✓ Source tracking wired across website, ad platforms, CRM, phone, and booking tool.
  • ✓ One funnel view — enquiry → qualified → booked → completed → repeat — with conversion at each stage.
  • ✓ Revenue attribution back to channel, ad, and offer.
  • ✓ A single dashboard with the five to ten numbers you actually use.
  • ✓ A one-page Monday-morning email — no dashboard-opening required.
  • ✓ Pre-agreed decision thresholds and automatic flags when they're crossed.
  • ✓ Monthly review — what the numbers said, what we changed, what to watch next.
  • ✓ Designed to retire tools, not add them — if we can replace a dashboard with an email, we will.

Could you build this yourself?

Yes — the stack is well-travelled. Google Tag Manager and Google Analytics 4 for web. Looker Studio, Metabase, or Mode for dashboards. Supermetrics, Funnel.io, or Fivetran for pulling ad platform data. PostHog, Mixpanel, or Amplitude for product/funnel events. Whatagraph or AgencyAnalytics for client-style reports. Airtable, BigQuery, or a Postgres instance to hold the source-of-truth data. Zapier, Make, or n8n to stitch it together. Hex or Deepnote if you want notebooks.

Everything listed works. The trap is different here than elsewhere: reporting projects fail not at the tool-choice step but at the "keep it clean six months later" step. Source tags drift, new platforms get added without plumbing, and the dashboard you built in January is lying to you by June. The work isn't building it; it's owning it. If you'd rather own the business and have someone else own the reporting, that's us.

Common questions.

A dashboard shows numbers. A reporting system answers decisions. The difference is whether, at the end of a five-minute read, you know what to change next. Most dashboards fail that test — they display data and leave you to interpret it on top of running the business.

Accounting reports tell you what happened in money terms — they're looking backwards at the P&L. Operational reporting tells you what's happening in the funnel — enquiries, bookings, conversion, cost per customer — so you can change it before it shows up in the accounts. You want both.

Weekly for operational numbers (leads, bookings, response time, review count), monthly for strategic ones (cost per customer, revenue by channel, retention). Daily dashboards create anxiety and bad decisions; quarterly ones miss the window to fix things.

Five numbers: leads this week, booked jobs this week, revenue this month, cost per booked customer, review count. If you can see those reliably, on one page, every Monday morning, you're ahead of 90% of local businesses.

Good — we'd rather email you a one-page PDF on Monday mornings than build you a fourth dashboard to ignore. Reporting should reduce the tabs you open, not add to them.

The reporting pillar, live inside two weeks.

£125/month. No setup fee. No contract. First 14 days on us — payment only kicks in once the system is live and you're happy with it.

Book a 15-minute call

Worst case you'll leave with a list of fixes you can run with yourself.

← Back to the full five systems