Work snippet
Looker Studio branch dashboard from Xero
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Branch managers in this service group were rebuilding the month’s figures from exports. A single Looker Studio view now covers revenue, margin, job count and money owed for each branch, with a written definition behind every number and a trace back to its source.
The problemEach month the branch pack is rebuilt by hand from exports.
What changesOne dashboard, by branch, with every figure defined and traceable.
- Area
- Dashboards
- Tools
- Looker Studio · Xero · ServiceM8 or Jobber
- Typical scope
- US$400-900
- Timeline
- About 6 weeks · fixed milestones
The problem
If managers doubt a dashboard they go back to their spreadsheets. The real work is agreeing definitions and showing the totals reconcile to Xero.
- A monthly pack that is late and different every time
- Branch margins that the finance lead and the managers argue about
- Completed jobs that were never invoiced, found weeks later
- No way to give each manager only their own numbers
Approach
- Look
A read-only review of the monthly pack, the job system exports and the Xero reports.
- Define
Every figure gets a written definition, a source, an owner and a refresh time.
- Build and connect
The loads, the reporting data and the dashboard are built together, one page at a time.
- Check
Dashboard totals are compared with Xero and the job system for three closed months.
Exhibit
Revenue by branch
Revenue, last six months ($k)
| Branch | Revenue | Margin % | Jobs |
|---|---|---|---|
| North | 148,200 | 41.2% | 412 |
| Central | 96,400 | 37.5% | 298 |
| East | 71,300 | 36.1% | 221 |
| South | 52,700 | 39.8% | 144 |
| West | 31,900 | 33.4% | 109 |
| Unallocated | 12,100 | - | 0 |
How to read it
- Revenue by branch shows an Unallocated bar for invoices with no branch, so nothing disappears.
- Each figure is tied to a written definition, one click away in the dashboard.
- A data quality line shows missing tracking and failed loads, so the dashboard reports its own gaps.
Scope
| Area | Included |
|---|---|
| Review | The current pack, exports and Xero reports, with findings |
| Definitions | A written definition for every figure, agreed with the finance lead |
| Data loads | Scheduled loads from Xero and the job system into a reporting sheet or dataset |
| Dashboard | Executive, branch, jobs and cash pages in Looker Studio, with one filter bar |
| Access | Managers see only their own branch |
| Check | Totals compared with Xero and the job system for three closed months |
| Handover | A walkthrough and the files, which you own |
Milestones and fee
| Milestone | Deliverable | Timing | Share of fee |
|---|---|---|---|
| M1 Review and definitions | Findings and written KPI definitions | Weeks 1 to 2 | 20% |
| M2 Data loads | Loads running and totals tied | Weeks 3 to 4 | 35% |
| M3 Dashboard | Pages built and checked on three months | Week 5 | 30% |
| M4 Handover | Access, walkthrough and files | Week 6 | 15% |
Typical scope for this kind of project: US$400-900
About 6 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.