Metabase vs Tableau for Consulting Firms: Utilization Reports

Billable utilization sounds straightforward: hours billed divided by hours available. The messy part is what counts as "available." Vacation, business development time, internal training, and bench time between engagements all need a consistent treatment or the number becomes useless for comparing consultants. Metabase lets you encode that logic directly in SQL and adjust it the moment the firm changes its policy on, say, whether business development counts toward utilization targets. That flexibility matters at a firm still refining its own definitions, which describes most consulting firms under a hundred people.

Settle each of these before building the metric:

• Decide whether vacation time counts as available hours, and apply that answer to every consultant the same way.
• Decide whether business development time counts toward utilization targets, and write the rule into the SQL so it can change with policy.
• Decide how internal training time is treated, and document it where consultants and partners can read it.
• Track involuntary bench time between engagements as a separate staffing-efficiency metric, not inside the utilization number.

A firm with several partners, each running their own book of engagements, has a reporting need Metabase does not solve as cleanly: each partner should see their own team's utilization and margin in detail, while the managing partner sees the consolidated view, without partners seeing each other's engagement economics. Tableau's row-level security handles that natively. Building the equivalent in Metabase means either duplicating dashboards per partner or managing database-level permissions that need updating every time a consultant moves between teams.

Disqualifier: skip Tableau if the firm is small enough, single-partner or a handful of principals who already share full visibility into every engagement. The access control Tableau adds has no audience yet at that size.

Say a consultant rolled off an engagement three weeks ago and has not been staffed since. In a monthly spreadsheet, that shows up as a utilization dip after the fact, usually noticed in the same meeting where staffing decisions get made for the next quarter. A live Metabase dashboard filtered by consultant and updated daily surfaces that gap the week it starts, giving a staffing lead time to place the person on a short engagement or business development work before three weeks becomes six.

The same view, tracked over several quarters, also shows patterns a single month never reveals: a specific service line consistently running lean on staffing right before a busy season, or a consultant repeatedly the last one placed after an engagement ends. Neither pattern is visible from a snapshot, only from a dashboard someone is actually watching over time.

Utilization tells you how busy people are. Margin tells you whether the firm is actually making money on a given engagement, and that requires blending billed hours at rate against the actual cost of staffing it, including any senior partner time given away at a discount to keep a relationship healthy. This is where a lot of firms discover an engagement they assumed was profitable was not, because a partner's own hours were never costed into the calculation. Both Metabase and Tableau can build this view once fully-loaded consultant costs are captured somewhere the dashboard can reach; the harder part is agreeing on those cost figures in the first place, which is a firm policy question, not a tooling one.

The fastest way to kill adoption of a new utilization dashboard is to launch it with numbers that disagree with what consultants already believe about their own hours. Run the new dashboard silently alongside the existing spreadsheet process for a few weeks first, and reconcile any differences before showing it to the full team. Most discrepancies trace back to inconsistent time-entry categorization rather than a bug in the dashboard itself, and finding that out privately is far better than finding it out in a partner meeting where the new number contradicts what someone has been telling clients for months.

Once the numbers are trusted, resist the urge to add every metric a partner asks for onto a single crowded view. A dashboard trying to show utilization, margin, pipeline, and business development activity all at once ends up answered by nobody, because the metric a given viewer actually needs is buried under three others they do not. Separate views for separate audiences, staffing leads, partners, and the managing partner's consolidated picture, keep each one focused and genuinely useful.