Dashboards without the BI project
A 5–50-staff service firm can get a live management dashboard without a BI platform, a data warehouse or a consultancy engagement. Three routes cover almost every case: the CRM's native dashboards, a free dashboard tool connected to the CRM's data, or a small self-hosted reporting layer. The choice is decided by where your data lives and who maintains the result — not by feature lists.
Why do dashboard projects balloon?
Because the industry sells dashboards as the visible tip of a data platform. The standard proposal stacks a warehouse, a transformation layer, a BI licence and a consulting engagement under one chart — reasonable at enterprise scale, absurd for a firm whose entire commercial dataset is a few thousand CRM records. The project takes months, the monthly cost outlives the enthusiasm, and the dashboard answers last quarter's questions.
The corrective is to start from the decisions, not the tooling. The dashboard exists so the MD can read a dozen numbers — pipeline, conversion, revenue, capacity — without asking anyone, as set out in The MD Dashboard Blueprint. Every tool decision follows from that reading list, and most of the list can be produced by software you already pay for.
What are the three realistic routes?
| Route | Typical cost | Build effort | Best when |
|---|---|---|---|
| Native CRM dashboards | Included in the CRM | Hours | All key data lives in the CRM |
| Free dashboard tool on top (e.g. Google's Looker Studio) | Free to low | Days | Data spans CRM + a sheet or two |
| Self-hosted reporting layer (e.g. Metabase or similar) | Hosting only, commonly a few pounds a month | Days, plus light upkeep | You want owned infrastructure and custom queries |
Route one: use the CRM's own dashboards. Most mid-market CRMs ship pipeline, conversion and activity reporting natively. It is the right default: zero new tools, live by definition, and maintained by the vendor. Its ceiling is cross-source questions — the moment you want CRM data beside delivery hours or invoicing, native dashboards run out.
Route two: a free dashboard tool on top. Tools in the Looker Studio class connect to a CRM export or a live sheet and produce shareable charts. Good for blending two or three sources; the trap is letting the "live sheet" become a hand-updated sheet, which quietly reintroduces the human compiler.
Route three: a small self-hosted layer. A lightweight open tool over the CRM's database or API gives you custom queries and full ownership for the price of hosting. The honest cost is maintenance — updates, backups, the occasional breakage — which needs a named owner or a partner who carries it.
What none of these routes includes is a data warehouse. At this scale, the CRM is the warehouse — provided the pipeline actually lives there rather than in a founder's spreadsheet, the threshold examined in when a spreadsheet stops being enough.
How do you build it without the project ballooning?
The mechanism is deliberately boring:
- Write the reading list first. When a number would not change a decision within a month, then it does not go on the dashboard. Ten to fifteen numbers is the working ceiling.
- Trace each number to a source of record. When a number cannot be produced automatically from the CRM or another system, then the fix is upstream — a field, a stage definition, a hygiene rule — never a manual cell.
- Build the ugliest version in a day. Native CRM reports, default charts, no branding. When the ugly version survives four weeks of actual use, then it has earned improvement; when a number is never looked at, then it comes off.
- Schedule the push. When Monday morning arrives, then the headline numbers are delivered to email or chat — the pattern from the weekly report that writes itself — because dashboards are visited erratically but inboxes are read.
- Review quarterly, not continuously. When the firm's questions change, then the page changes. Continuous fiddling is a hobby wearing a business case.
What actually makes a dashboard useful?
Speed of consequence, not visual polish. A dashboard earns its place when a number moving causes an action within days: pipeline coverage drops, so outbound volume rises; conversion at proposal stage sags, so pricing or qualification gets reviewed. That closes the loop between measurement and behaviour — and a loop closed weekly steers far better than one closed at quarter-end, for reasons unpacked in feedback loops: the physics of your pipeline. A beautiful dashboard nobody acts on is decoration; an ugly one that triggers Tuesday's decisions is a control system.
The same discipline applies to metric count. Every added chart dilutes the ones that matter, so the strongest dashboards at this scale look almost embarrassingly sparse.
Where does this stop being enough?
Later than vendors suggest. Genuine triggers for heavier tooling include data volumes the CRM cannot query quickly, regulatory reporting needs, or analysis across many systems with real transformation logic. Most firms under 50 staff never hit them. The nearer frontier is not more tooling but better questions — for instance, turning the same pipeline data into a forecast you would stake payroll on, which is the subject of forecasting revenue from pipeline, honestly.
Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks, including which numbers you cannot currently see, and what to build first.
Total Format builds the systems UK B2B service firms grow on — AI-powered outbound, automation, and reporting — so growth stops depending on the founder's time.
Map your growth system. The £450 audit takes seven days and is credited against any build.
BOOK THE AUDIT