Most agencies treat client reporting as a cost of doing business. The BI tool subscription sits on the overhead line. The hours spent building and maintaining dashboards get buried in project budgets or absorbed into retainers. Clients expect reporting; agencies deliver it and move on.
A smaller number of agencies have figured out that this is backwards. Reporting isn't overhead — it's a service. One that clients value, depend on monthly, and will pay for directly if you package it properly.
This post covers how that model works: the pricing math, the packaging decisions, the platform requirements, and the one feature that makes the whole thing cleaner than most people expect.
Why Reporting Is Already a Revenue Line — You're Just Not Charging for It
If you're delivering dashboards or reports to clients right now, you're providing ongoing value every month. Clients are making decisions based on your data. They're logging in, checking numbers, sharing reports with their leadership. That is a service.
The question isn't whether you're providing value — it's whether you're capturing any of it.
Most agencies aren't. Here's what the typical overhead model looks like:
- BI tool subscription: absorbed into operating costs
- Setup and configuration time: billed once as project hours, never again
- Ongoing maintenance (new reports, data source changes, user additions): handled ad hoc, often not billed at all
- Client asks "can you add a new dashboard?" — you do it as a favour to protect the relationship
The result is that reporting becomes an invisible service that costs you money every month and generates no predictable return. When clients churn, you don't just lose the retainer — you lose the BI tool cost you were absorbing for them.
The alternative is to treat reporting as what it actually is: a managed service with a recurring fee.
What "Reporting as a Service" Actually Looks Like
The model is simpler than it sounds. You're not creating a separate business — you're adding a line item to your existing client relationships.
The basic structure: clients pay a monthly fee for access to a branded reporting portal. What's included in that fee is up to you — dashboard access, a set number of reports, a monthly review call, scheduled email delivery, a defined SLA for new report requests. You define the service tier; you set the price.
The platform cost stays flat on your side. DashboardFox charges you $249/mo for up to 30 monthly active users across all your clients combined. What you charge each client for that access is entirely your decision. DashboardFox has no visibility into your client pricing and never communicates with your clients about cost.
Here's what the margin math looks like at different charging levels for a consultancy managing 8 clients on the Growth plan:
DashboardFox platform cost: $249/mo
- Charge each client $50/mo → $400/mo revenue → $151/mo margin
- Charge each client $75/mo → $600/mo revenue → $351/mo margin
- Charge each client $100/mo → $800/mo revenue → $551/mo margin
- Charge each client $150/mo → $1,200/mo revenue → $951/mo margin
The margin turns positive at 4 clients charging $75/mo. Everything above that is contribution margin on a fixed cost base.
The math improves further if you're on an annual plan — DashboardFox's Growth plan drops to $199/mo on annual billing, which widens the margin at every price point without changing anything your clients see.
How to Price Your Reporting Service Tier
There's no universal right answer here, but there are some useful anchors.
$50–$75/mo per client is appropriate for a basic tier: dashboard access, scheduled email reports, a defined set of standard reports, no custom work included. This is an easy yes for most clients — it's less than they spend on almost any other SaaS tool in their stack.
$100–$150/mo per client makes sense when you're including more: custom dashboards built to their specs, a monthly data review, user management, access to additional data sources. At this level you're positioning reporting as a managed analytics service, not just a tool subscription.
$200+/mo per client is the territory for clients with complex data environments, compliance requirements, dedicated dashboards for multiple departments, or regular hands-on analysis. Healthcare, financial services, and enterprise clients often justify this range.
The key principle is that your price should reflect the value your clients place on their data access — not the underlying platform cost. Most clients have no idea what your BI tool costs. They know what their data is worth to them. Price accordingly.
One practical note: many agencies find it easier to introduce reporting fees to new clients than to retrofit them onto existing relationships. If you're building this model from scratch, your next new engagement is the right place to start. For existing clients, a platform upgrade — new dashboards, better data, branded portal replacing a shared login — gives you a natural moment to introduce a reporting service line.
The Two Delivery Models and How They Affect Your Revenue Structure
How you deploy determines your operational flexibility. DashboardFox supports two approaches, and most agencies end up using both depending on the client.
Multi-tenant single instance — all clients on one DashboardFox instance, with row-level security (Data Tags) keeping each client's data isolated. This is the lower-overhead model: one subscription, one platform to maintain, pooled MAU across all clients. The trade-off is that Guest View branding is shared across clients — each client gets their own login domain, but the reporting portal branding is consistent rather than fully per-client.
This model works well for ongoing managed service relationships where you're the operator and clients just consume the reports.
Dedicated instance per client — each client gets their own isolated DashboardFox instance with their own database, their own branding, their own SMTP configuration. Fully independent. This is the higher-isolation model, and it comes with a capability that the multi-tenant model doesn't: Instance Transfer.
Instance Transfer: The Exit Strategy That Changes the Business Model
Instance Transfer is worth understanding properly because it opens up a revenue model that most agencies haven't considered.
Here's how it works: you set up a client's DashboardFox instance, connect their data sources, build their dashboards, configure their branding and custom domain. The client gets a fully operational reporting platform under their own brand. Then you transfer ownership — they take over the subscription and billing directly. All the dashboards, data connections, users, and configuration transfer with it.
From a revenue perspective, this creates a project-based model alongside the recurring service model:
- Project revenue: You charge for setup, configuration, and dashboard development — this is a defined engagement with a clear deliverable.
- Optional ongoing revenue: You can offer a retainer for ongoing maintenance, new reports, and data updates after the handoff. Some clients want to self-manage; others want you to stay involved.
- Clean exit: For clients who want full ownership and independence, you deliver a finished product and transfer it cleanly. No lingering subscription cost on your books for a client relationship that's ended.
This model is particularly useful for data consultancies and VARs who deliver one-time implementation projects. Instead of leaving clients with a login to a shared tool, you're delivering an owned reporting platform. That's a meaningfully different — and more valuable — deliverable.
For agencies running ongoing managed service relationships, the dedicated instance model without transfer works too: you own the platform, the client pays you monthly for access, and the instance stays on your account. The dedicated model just costs slightly more per client (one subscription per client vs pooled MAU across all clients on multi-tenant) — the trade-off is full isolation and transfer optionality.
What You Need From a Platform to Make This Work
Not every BI tool supports this model. The minimum requirements are:
White-label on every plan. If white-label is an enterprise add-on, your margin math collapses before you've signed a single client. You need custom domains, branded login pages, and email reports from your domain — not the platform vendor's — from day one. This is non-negotiable for client-facing delivery.
MAU-based pricing or a flat cost that doesn't scale with client count. Per-seat pricing is the margin killer for this model. If every client user adds a line item to your platform bill, your cost scales with every onboarding and your margin erodes every time a client adds a user. You need a pricing structure where your cost is predictable regardless of how many clients you're running.
Multi-client management. When you're running 8 or 12 client instances, logging in and out of separate accounts to manage each one is unsustainable. A single Account Manager console that lets you create, configure, and switch between clients without separate credentials is a practical requirement, not a nice-to-have.
Row-level security included, not paywalled. If you're running multi-tenant and need to isolate client data logically, row-level security needs to be available at your plan level. Tools that put this behind enterprise pricing — Metabase's $575/mo wall is the most obvious example — make the economics unworkable for smaller client portfolios.
DashboardFox includes all four from the entry-level plan at $99/mo. The full agency feature set covers the specifics.
The Margin Gets Better As You Scale
One useful property of the flat MAU model: your margin improves as you add clients, because your platform cost doesn't grow linearly with client count.
On DashboardFox Growth ($249/mo, 30 MAU), if each of your 8 clients has 3–4 active users per month, you're using roughly 24–32 MAU — comfortably within the tier. When you add a 9th client, your platform cost stays at $249/mo. Your revenue goes up by whatever you're charging that client. The margin on each incremental client is almost entirely contribution margin.
You only move to the next tier (Scale at $499/mo, 100 MAU) when your total active logins across all clients consistently exceed 30 per month. At that point you likely have enough client revenue to absorb the step-up comfortably.
This is the opposite of per-seat pricing, where every new client user is an immediate cost. With MAU pricing, growth is your friend.
Getting Started
The fastest way to test this model is to pick one existing client relationship where you're already delivering reporting and haven't formalized the fee. Propose a reporting service tier to them — a branded portal, regular scheduled reports, a defined set of dashboards, a monthly fee. See how they respond.
Most clients who already depend on your reporting will say yes without significant negotiation. You're not asking them to pay for something new — you're asking them to pay properly for something they're already using.
From there, build the template. Define your service tiers, standardize your dashboard setup process, set your pricing. Each new client becomes easier to onboard because you've done it before.
See how DashboardFox supports the agency model → · Start a free trial → · Talk to us about volume pricing →