Tableau consulting
Tableau consulting for environments that grew faster than anyone governed them
Nobody set out to have four hundred workbooks. It happened one urgent request at a time, and now the same metric is calculated three different ways and two of them turn up in the same meeting.
Buying more Tableau does not fix that, and neither does starting again.
What fixes it is one definition per metric, held somewhere every workbook reads from, and a path from any figure on a dashboard down to the rows behind it. Then the person looking at the number can check it themselves rather than opening a ticket about it.
5 years
Building analytics that runs in production
10+ years
Minimum experience, every consultant on your project
What Tableau consulting buys you
You are hiring a team to design, build, or repair the reporting layer you run in Tableau. That covers published data sources so a metric is defined once and inherited, workbooks built for the people who will actually open them, governance on Server or Cloud that holds as content grows, and the modelling underneath so the numbers are right before anyone worries about how they look.
The judgement that matters most is what does not belong in Tableau at all. Logic buried in calculated fields is invisible to everything else in your stack and has to be rebuilt by whoever inherits it. Pushing that upstream into the warehouse is usually the highest-value thing an engagement does, and it is the least visible.
If you have not settled on a BI tool yet, start with data visualization consulting instead.
When to hire, and when not to
An audit answers this in days and costs a fraction of a build. Finding out afterwards costs the build.
Worth hiring for
- You have hundreds of workbooks and no idea which ones are still used, let alone which are correct.
- The same calculation exists in a dozen workbooks with slightly different logic, and two of them disagree in the same meeting.
- Dashboards take thirty seconds to load, or the extract refresh fails overnight and nobody notices until someone opens it.
- You are paying for Creator seats that are being used like Viewer seats, and nobody can tell you what the licence spend is buying.
Probably not yet
These are questions of stage and fit rather than things we cannot do. A messy warehouse underneath is the work, not a reason to send you away.
- –You have not picked a BI tool yet. Choosing between Tableau, Power BI, and Looker is a different decision, and it is worth settling before anyone builds anything in one of them.
- –You are partway through moving off Tableau. Spending on the platform you are leaving rarely pays back; get the migration scoped instead.
- –Only a handful of people will ever open it. Tableau is licensed per seat, and at low headcount the maths often does not clear.
- –Your processes are still changing month to month. Dashboards encode how you operate, so they go stale faster than you can rebuild them.
What Tableau consulting services cover
Tableau consulting services are usually quoted as a dashboard count, which is the wrong unit. Your scope would be drawn from some of this and never all of it.
- Published and certified data sources, so a metric is defined once and inherited rather than rebuilt in every workbook.
- Workbook audits, which is what most Tableau consultants get hired for first: what is used, what is duplicated, what is wrong, and what can be retired without anyone noticing.
- Performance work using the performance recorder, which usually comes down to extract design, unnecessary quick filters, and calculations that should have happened upstream.
- Row-level security done with entitlement tables rather than user filters, so it survives someone duplicating the workbook.
- Extract strategy: what should be a live connection, what should be an extract, and what refresh schedule the source can actually support.
- Tableau Prep flows where they earn their place, and moving that logic into the warehouse where they do not.
- Migration work in both directions, including Tableau to Power BI and the reverse, without pretending either is a like-for-like port.
Tableau Server, Tableau Cloud, and the governance question
Workbook sprawl is a governance failure rather than a discipline failure. The people building duplicates are doing so because finding and trusting the existing one is harder than starting fresh.
Projects, permissions, and certification
A project structure that maps to how your business is organised, permissions set at the project rather than per workbook, and certified data sources that mean something because uncertified ones are visibly different.
Server or Cloud
Tableau Cloud removes the infrastructure work and the upgrade weekends. Server still wins when data residency or network constraints are real. If you are already on one and it works, that is usually the answer.
The part that decays
Governance is not a one-off configuration. Without an owner and a retirement process, workbook count grows and trust falls. We set up both and hand them over rather than leaving you a document about them.
Most of what makes a Tableau environment fast and trustworthy happens before Tableau opens a connection. If the numbers disagree or the extracts take too long, data warehouse consulting is the piece that fixes it.
Who your Tableau consultants would be
Most firms sell you one team and staff you another. You will meet someone senior during the sale, so ask whoever you are talking to, including us, whether that person is still on the project in week six.
- A US-based senior data leader designs the engagement and stays your point of contact throughout. You meet that person before you spend anything.
- The same engineers work in your Tableau environment and your warehouse week to week, so you explain your business once rather than to a new face every month.
- Every consultant on the project has ten years of experience or more, which means none of your budget pays for someone learning LOD expressions on your data.
- If your team wants to build part of it themselves, that is a normal way for this to go and it lowers the price.
What to ask any Tableau consultant before you sign
Put them to us as readily as to anyone else on your list. The answers separate Tableau consulting companies faster than the proposals do.
- How much of this belongs in the warehouse rather than in Tableau? A Tableau consultant who wants to solve everything in calculated fields will leave you with workbooks nobody can maintain.
- What will you retire? Any audit that only adds content has not looked properly.
- How will row-level security survive someone duplicating a workbook? If the answer is user filters, ask again.
- Who owns the certified data sources after you leave, and what happens when a definition needs to change?
- What does this do to our licence spend? The honest answer is sometimes that it goes up, and you should hear that before you sign.
Questions about Tableau consulting
The things people ask before the first call.
Tableau consulting is hiring a team to design, build, or repair the reporting layer you run in Tableau, rather than working it out between other priorities. In practice that means published data sources so metrics are defined once, workbooks built for the people who will open them, governance on Tableau Server or Cloud that holds up as content grows, and the modelling underneath so the numbers are right before they are pretty.
Get a scope and a price before you commit anything
A short working session with the senior lead who would run the engagement, and one specific problem priced in writing. Yours to act on however you like, including elsewhere.
