Metabase vs Tableau for Architecture Studios: Phase Margin

Say a project is genuinely eighty percent through design development by the drawing set, but only sixty percent of the design development fee has been billed because the client has been slow signing off on milestones that trigger invoicing. A dashboard tracking only hours against budget would miss this entirely, since the studio's staff time is being spent appropriately. What actually needs surfacing is the gap between design progress and billing progress specifically, which requires joining two data sources project management tools rarely combine on their own: drawing milestone status and invoice history. Metabase handles that join directly once both systems feed a shared database, and the resulting chart gives a principal a reason to have the sign-off conversation with the client before the gap becomes a cash flow problem.

Printing, travel, courier fees, and consultant pass-through costs are supposed to be reimbursed by the client, but they are also the easiest line item to lose track of when they are tracked in a separate expense system from the project billing itself. A dashboard joining expense entries to project and phase, flagging any reimbursable expense not yet invoiced past a certain age, catches this leak while it is still small. Left unmonitored across enough projects, unbilled reimbursables quietly become a real drag on margin that nobody notices until an annual review.

The fix is rarely more diligent manual tracking, since that is exactly what was already failing to catch the leak. It is making the unbilled-reimbursable list something a specific person reviews weekly as a standing task, with the dashboard doing the work of surfacing which expenses are aging past the point they should have already appeared on a client invoice.

A reimbursable-expense check should cover these points:

• Join every expense entry to its project and phase, so printing, travel, courier, and consultant pass-through costs land against the phase that caused them.
• Flag any reimbursable expense that has not been invoiced past a set age, so it gets billed before anyone forgets it.
• Show pass-through consultant fees as a separate line from the studio's own fee, so earned revenue and margin are not overstated.
• Put the flagged list in front of whoever owns invoicing on a regular schedule, so leaks close while the client still remembers the expense.

Most studios do not have a dedicated resource scheduler, which means staffing decisions get made from a project manager's memory of who is busy and who has room. A dashboard showing hours committed per staff member across every active project, refreshed weekly, replaces that memory with an actual number and helps catch a designer quietly overcommitted across three concurrent construction document phases before a deadline forces the issue.

A small studio where the principal sees every project's numbers directly does not need Tableau's governance. A larger firm with multiple principals or studio directors, each running their own project roster with a degree of financial autonomy, benefits from Tableau's ability to scope each principal to their own projects while still rolling everything up correctly for firm-wide leadership. Building that same separation in Metabase at scale means ongoing manual permission work as staff move between project teams.

Disqualifier: skip Tableau if the studio is small enough, or transparent enough by culture, that every principal already sees every project's full financials as a matter of course, in which case the added governance has no real audience yet.

Architecture studios are often design-led cultures where financial dashboards can feel like an intrusion on the creative process if they are introduced badly, arriving as a policing tool rather than something that actually protects the creative work itself. Frame the rollout around protecting design time, not policing it: a phase-billing gap caught early means less pressure to rush a later phase to recover margin, which is a design-quality argument as much as a financial one. Median pay for the operations roles that typically own this kind of tracking runs $105,770 a year nationally¹, which is worth weighing against the hours a principal currently spends reconstructing project economics by hand every quarter, time that would otherwise go toward the design work the firm actually bills clients for in the first place.