When you're evaluating business intelligence tools, the pricing model matters more than the sticker price. Two tools with similar monthly costs can produce very different invoices twelve months in — depending on how your users actually behave, how many clients or locations you support, and whether you ever read the fine print on what counts as a billable user.
Business intelligence software vendors use four main pricing models: per-seat, MAU (Monthly Active User), flat-rate, and capacity-based. Each one was designed with a specific usage pattern in mind. Choosing the wrong one for your situation is one of the most common — and most avoidable — reasons BI deployments go over budget.
This post explains how each model works, what it costs in practice, and which situations each one fits.
Per-Seat Pricing
Per-seat pricing charges a fixed amount for every user account provisioned in the system, billed monthly or annually — regardless of whether that user actually logs in during the billing period.
If you create 50 accounts, you pay for 50 seats. Every month. Whether 50 people log in or 12.
This model came from software designed for daily active use — email clients, CRMs, project management tools. If your entire team opens the tool every working day, per-seat pricing is predictable and straightforward. You know exactly what you'll pay, and the cost scales cleanly with headcount.
The problem is that most BI dashboards are not daily-active tools for most users. Executives review dashboards weekly or monthly. Clients log in when they need to check a number. Seasonal teams spike in Q4 and go quiet in Q1. Per-seat pricing doesn't account for any of that — you pay the same whether usage is high or zero.
Who uses per-seat pricing: Power BI ($14/user/mo Pro, $20+/user/mo Premium), Tableau ($15/user/mo Viewer, $75/user/mo Creator), Looker (custom enterprise pricing, per-seat).
Best fit: Teams where most provisioned users log in daily. Organizations already inside the Microsoft 365 ecosystem where Power BI licensing may be partially covered. Small, stable headcounts where seat count and active usage are nearly identical.
Watch out for: Idle seats accumulating as teams grow. Per-seat costs for client-facing or external user accounts where login frequency is inherently low.
MAU (Monthly Active User) Pricing
MAU pricing charges based on the number of distinct users who actually log into the platform during a calendar month — not the number of accounts that exist.
If you have 50 provisioned accounts but only 22 people log in this month, you pay for 22 MAU. The 28 who didn't log in cost nothing. There's no penalty for provisioning accounts in advance or for users who go inactive.
One additional nuance that matters for teams delivering reports to clients: users who receive scheduled email reports but never log into the dashboard directly typically don't count toward MAU. They get the data they need; you don't get billed for their passive consumption.
Who uses MAU pricing: DashboardFox ($99/mo for 5 MAU, $249/mo for 30 MAU, $499/mo for 100 MAU — white-label and row-level security included on all plans).
Best fit: Teams with a mix of power users and occasional viewers. Agencies, consultancies, and MSPs managing dashboards for multiple clients where individual login frequency is low. Organizations that deliver regular email reports alongside a live dashboard. Deployments where usage fluctuates by season or project cycle.
Watch out for: MAU tiers with hard caps — if you regularly exceed your tier, costs can step up quickly. Understand exactly how your vendor defines an MAU (some count any login, some count unique devices, some have grace periods).
Flat-Rate Pricing
Flat-rate pricing charges a single fixed monthly or annual fee for the platform regardless of user count — up to a defined limit or sometimes with no user cap at all.
This is the simplest model to budget for. You know your exact cost every month and can add or remove users without affecting your invoice.
The trade-off is that flat-rate pricing typically comes with restrictions elsewhere — feature gating, data row limits, connector limits, or user caps that kick in at a defined ceiling. The headline price is attractive; the fine print determines whether the plan actually covers your use case.
Who uses flat-rate pricing: Metabase Pro ($575/mo flat for up to 10 users — this tier unlocks row-level security, which the free tier lacks entirely). Some smaller BI and reporting tools use flat-rate tiers as entry-level plans.
Best fit: Teams with predictable, stable user counts who want billing simplicity. Organizations evaluating a specific feature set (like Metabase Pro's row-level security unlock) where the flat fee is justified by the feature access rather than user volume.
Watch out for: Flat-rate plans that look affordable but gate the features you actually need behind the next tier. The Metabase example is instructive — the free tier has no row-level security at all, and the jump to Pro is $575/mo regardless of how many users you have.
Capacity-Based Pricing
Capacity-based pricing charges for compute or storage capacity allocated to the platform rather than for individual users. User counts are typically unlimited or very high within the capacity tier purchased.
This model is common at the enterprise end of the BI market. You're paying for the infrastructure headroom — the ability to run queries at scale, serve many concurrent users, and process large datasets — rather than for individual seats.
Who uses capacity-based pricing: Power BI Premium Per Capacity ($4,995/mo) unlocks white-label embedding and removes per-user licensing for report consumers. Tableau Server licensing at enterprise scale uses a similar capacity model. Snowflake and data warehouse tools that integrate with BI layers often use compute-credit models that operate on similar principles.
Best fit: Large enterprises with high user volumes where per-seat costs would exceed capacity pricing. Organizations that need to serve large numbers of external users or embed analytics in client-facing products without per-user licensing overhead.
Watch out for: Capacity pricing is typically enterprise-tier and comes with enterprise-scale complexity and cost. For most mid-market teams it's not the right entry point — it's the model you grow into, not the one you start with.
The Math: Where the Models Diverge
The differences between models are clearest in a concrete example. Here's a scenario that reflects how mid-market BI deployments actually behave.
Scenario: A data consultancy with 40 provisioned user accounts across 8 clients. In a typical month, 22 of those users actively log into the dashboard. The other 18 receive scheduled email reports but don't log in directly.
Per-seat at $14/user/mo:
- 40 accounts × $14 = $560/mo
- 18 accounts generating zero activity, billed in full every month
MAU at DashboardFox Growth ($249/mo for 30 MAU):
- 22 logins counted as 22 MAU
- 18 email-only recipients = 0 MAU
- $249/mo — white-label and row-level security included
Flat-rate at Metabase Pro ($575/mo):
- Fixed cost regardless of whether 5 or 40 users log in
- Row-level security unlocked, but no white-label on any standard plan
- $575/mo
Same team. Same data. Three very different invoices. The right answer depends on whether white-label matters, whether RLS is needed, and how the 22 active users are distributed across those 8 clients.
For teams managing multiple client accounts specifically, the pricing model question intersects with white-label and data isolation requirements in ways that change the analysis significantly. The DashboardFox guide to white-label client reporting covers the full economics of that use case in depth.
The Question to Ask Before You Commit
Pull your last three months of actual login data from your current tool — or estimate honestly: out of everyone provisioned, how many actually log in each month?
- Consistently above 80% login rate → per-seat pricing is likely fine and simpler to budget
- Regularly below 60% login rate → MAU pricing will almost certainly cost less
- Stable small team, specific feature unlock needed → flat-rate may make sense
- Enterprise scale, external users, embedding needed → capacity-based is worth modeling
The pricing model is a structural decision that compounds over time. A 30% difference in monthly cost is manageable in month one — after three years it's a meaningful number.
See how DashboardFox's MAU pricing works → · Compare DashboardFox to Power BI → · Compare DashboardFox to Metabase → · Start a free trial →