Pricing Models for Agency Client Reporting

For agencies considering a white-label reporting portal, the business case comes down to two numbers: what the portal costs to operate, and what value it delivers relative to manual PDF reporting. Getting this math right matters — both for your own margin and for determining whether to pass the cost through to clients or absorb it as an infrastructure investment.

This chapter covers the economics of BI pricing in an agency context, with specific attention to why most BI pricing models are structured against you.

Why Per-Seat Pricing Breaks the Agency Model

Most enterprise BI tools — Power BI, Tableau, Metabase — charge on a per-seat basis. Every user who can access the platform is a billable seat, regardless of how often they actually use it.

For agencies, this creates an immediate problem: your clients are occasional users. The marketing director who logs in three times a month to check campaign performance doesn't use the reporting portal as intensively as your internal analysts — but in a per-seat model, they cost the same. Worse, many clients have multiple stakeholders who need access: the primary contact, their manager, their finance counterpart who looks at invoices once a quarter. Each of those is another seat.

Multiply per-seat costs across 20 clients with 3 seats each, and you're paying for 60 seats — the vast majority of which are active only occasionally. The licensing cost scales with client count regardless of actual usage, which compresses your margin on every new client you add.

The MAU Model and What It Means for Your Costs

DashboardFox prices on MAU — Monthly Active Users. A user only counts toward your quota in months when they log in. A client stakeholder who checks their dashboard two or three times a month counts as 1 MAU. One who didn't log in at all doesn't count that month.

This matters significantly for agency economics. In a typical agency setup, clients have 2 to 4 stakeholders with portal access. Not all of them log in every month — some check monthly, some quarterly. The total seat count across your client base might be 80, but the actual MAU in any given month might be 35 to 45. You pay for 35 to 45, not 80.

The practical effect is that your per-client reporting cost stays relatively stable even as you add more clients and their associated stakeholders — assuming the pattern of occasional access holds. The cost scales with active logins, not with the roster of provisioned users.

Build vs. Buy: What Manual Reporting Actually Costs

Before evaluating portal pricing, it's worth pricing the current state honestly. Manual PDF reporting isn't free — it consumes staff time that has a real cost.

For an agency with 20 clients and one person spending roughly 2 hours per client per month on reporting (generating, reviewing, sending, and handling follow-up questions), that's 40 staff hours per month. At a fully-loaded cost of $50/hour, that's $2,000/month in labor attributable to reporting. At $75/hour, it's $3,000/month.

A DashboardFox Growth plan at $249/month — covering up to 30 MAU with white-label, branding policies, and custom domains — replaces most of that manual work. The portal handles data delivery automatically. Scheduled reports go out without manual intervention. Clients get current data on demand without sending a request. The labor cost drops to setup, maintenance, and genuine analysis — not report generation and delivery.

The ROI case is usually straightforward: if the tool costs $249/month and eliminates $1,500 to $2,500/month in manual reporting labor, the investment pays for itself many times over in the first month. The harder question is often organizational — convincing the team that the setup investment is worth it.

How to Price Reporting for Your Clients

Agencies handle the cost of their reporting portal in one of three ways: pass it through, absorb it, or productize it.

Pass-through: Add a reporting portal fee to client retainers — a line item that covers the cost of their access to the branded dashboard. This is transparent and keeps the cost off your P&L, but requires justifying the fee to clients. Works best when the portal is genuinely differentiated and clients can see the value.

Absorb it as infrastructure: Treat the portal cost like office rent — an overhead cost that enables your service delivery, priced into your retainer rate rather than itemized. Simpler administratively, but the cost is invisible in client pricing conversations. Works best when the portal is one of several tools in your stack and you don't want to itemize all of them.

Productize it: Position the reporting portal as a named deliverable in your service offering — "Client Analytics Portal" or "Live Reporting Dashboard" — and price it as a value-add that commands a premium. Rather than recovering the tool cost, you're charging for the capability and the access. This is the highest-margin approach and the most defensible positioning, because the portal becomes part of what clients are buying from you, not just a delivery mechanism you happen to use.

Comparing the Alternatives on Agency Unit Economics

At 30 MAU (a reasonable number for an agency with 8 to 12 active clients each having 2 to 3 logged-in stakeholders), here's what the major tools cost — with the features an agency actually needs:

The comparison makes the agency economics clear. DashboardFox at $249/month includes the full feature set agencies need — white-label, row-level security, custom domains, unlimited reports — for less than what Power BI charges for seats alone without any white-label capability. Metabase at $815/month gets you white-label and RLS, but at 3x the cost. Tableau gets you neither white-label nor RLS without an enterprise contract.

What Happens as You Scale

MAU-based pricing has a natural growth curve. As your client base grows and your active user count increases, you add MAU capacity in increments rather than jumping to a new tier immediately. DashboardFox's $49/month add-on for +10 MAU (or $39/month annual) means you can grow incrementally without a step-function cost increase every time you add a few clients.

The same logic applies to branding policies and custom domains. If you're on Growth and need a fourth branded domain before you're anywhere near the 30 MAU ceiling, a +1 Custom Domain add-on at $29/month is almost always cheaper than upgrading to Scale. Similarly, if you need a few more branding policies for additional co-branded client groups, +3 Branding Policies at $29/month extends Growth without an upgrade. Add-ons stack — you can add multiple packs of the same type.

The point at which Scale tier ($499/month, 100 MAU, unlimited branding policies) becomes the right fit is when you either consistently need more than Growth's 5 policies and don't want to manage stacked add-ons, your domain count is pushing toward 10, or your active user count is consistently above 70 to 80. Below those thresholds, Growth at $249/month with selective add-ons is almost always the more cost-efficient choice.

See the DashboardFox for Agencies page for more on how agencies structure their reporting practices around the platform.