Two teams reporting different numbers
A dashboard nobody opens
Board reporting assembled by hand each month
Salesforce reports that stop where the question starts
Arguments about dashboards are almost always arguments about definitions.
Tableau and CRM Analytics: agreed metric definitions, executive dashboards, row-level security and reporting embedded where people already work.
The monthly meeting spends its first twenty minutes reconciling figures instead of deciding anything. That is not a tooling problem. It is that two teams are calculating the same measure in two defensible but different ways, and no dashboard can settle an argument about what the number means.
So the work starts with definitions rather than charts: what counts as a win, when revenue is recognised, which records belong to whom. Reporting gets built on top of agreed numbers, with visibility set so each team sees its own patch without anyone keeping a private copy of the truth.
Where it breaks
Bookings, pipeline, active customer — defined differently by finance, sales and operations, so every number is defensible and none is shared.
Days of somebody's month spent copying figures between systems, with the errors that implies.
Made for a question that mattered once, never revisited, and now quietly wrong.
Technically accessible, practically unusable, because the business logic lives in people's heads.
Everyone empowered to build reports, so there are now four hundred and no agreement.
Salesforce reports answer Salesforce questions, and the interesting questions cross systems.
What we build
Eight steps from arguing about a number to agreeing on it, then putting it where people already work.
Agreeing what things mean before building anything that counts them. The unglamorous part that determines success.
A small number of views leadership actually opens, built around decisions rather than around available fields.
Day-to-day visibility for the people running the work, not just for the people reviewing it.
CRM Analytics, Tableau and native reporting used where each one earns its place.
Shaping and cleaning so the visualisation is not compensating for the source.
Certified sources, ownership and a route for retiring reports that have outlived their question.
Insight where the work happens rather than in a separate tool nobody opens.
Teaching your people to maintain it, so you are not dependent on us for a chart.
Beyond phase one
Each one came out of delivery work rather than a product roadmap. In most cases the client did not know to ask for it.
Three dashboards disagreeing about revenue is not a tooling problem. It is four people with four definitions and no owner. Settling that is a governance exercise that nobody budgets and everybody needs.
Usage data on your own reporting is free and almost never looked at. It tells you which dashboards to retire, which to fix, and which team has quietly gone back to a spreadsheet.
A regional manager should see their region without a separate copy of the dashboard. Getting this right once removes an entire category of maintenance that otherwise grows with every hire.
A metric without a threshold is decoration. Attaching the target, and who owns it, is what turns a chart into something that produces a decision.
When people download to Excel and rebuild, the dashboard has failed and the shadow report is now the source of truth. Watching for the export is the cheapest early warning you have.
Integrations
Analytics is only as trustworthy as its sources. These are the categories most often feeding it.
Pipeline, service and revenue data at the grain the question needs.
The numbers finance will actually stand behind.
Where cross-system questions get answered.
Field service, project and industry platforms carrying delivery reality.
Spend and engagement joined to the pipeline they produced.
Still a legitimate source when it is the only place a thing exists.
Sales Cloud · Campaign Management · Reporting
Sales Cloud · Reporting & Dashboards
There is always one. Tracing it back to where the two calculations diverge is the fastest way to find out what your reporting is really built on, and it is often not what anybody assumed.
