The most profitable way to price client reporting as a BI agency is a per-client monthly retainer tied to the value of the decisions the reporting enables — not an hourly rate and not a one-off project fee. Hourly billing caps your income at your effort; per-project billing turns every engagement back to zero; a per-client retainer creates recurring, predictable revenue and rewards you for building efficient, reusable reporting. The framework: set a floor from your true delivery cost (including the licensing and capacity you often forget), then price up toward the value the client gets, and package it in tiers. The single biggest hidden margin-killer is per-viewer Power BI licensing — a fixed-capacity portal removes it.
Most BI agencies are excellent at building dashboards and mediocre at charging for them. They quote a project fee, deliver something genuinely valuable, and then watch the margin evaporate into "quick changes," ad-hoc requests, and per-user license bills nobody accounted for. This guide lays out the pricing models, a framework for choosing your number, and the operational moves — especially around licensing — that decide whether client reporting is a profit centre or a slow leak.
TL;DR — pricing client reporting
- Four models exist: hourly, per-project, per-dashboard, and per-client retainer. Only the retainer produces predictable, compounding revenue.
- Charge for the outcome, not the artifact. Clients don't buy a dashboard; they buy the decisions it lets them make. Price the decision.
- Set a floor, then price to value. Floor = your real delivery cost (build + capacity + support). Ceiling = the value the client gets. Your price lives between them, not at cost-plus-10%.
- Watch the licensing trap. Per-viewer Power BI Pro licensing scales with every client contact and silently erodes margin. A fixed-capacity portal makes reporting cost flat and predictable.
- Package in tiers. Good/Better/Best — with self-serve and AI insights as premium tiers — lets clients self-select and lifts your average revenue per client.
The four ways agencies price client reporting
1. Hourly
You bill for time spent. Simple and low-risk to start, but it has a hard ceiling: your income is capped at the hours you can sell, and — perversely — the better and faster you get, the less you earn for the same result. It also invites clients to scrutinise time instead of value. Fine for exploratory or one-off work; a poor basis for an ongoing reporting relationship.
2. Per-project (fixed fee)
You quote a fixed price to build a set of reports. Better than hourly because it prices an outcome, but every project ends at zero — you're perpetually re-selling. Scope creep is the killer: "one more visual" and "can you just tweak…" eat the margin you quoted. Good for an initial build; incomplete as a business model.
3. Per-dashboard
You charge per report or dashboard delivered. Easy for clients to understand and easy to upsell ("add another dashboard"), but it anchors the conversation to artifacts rather than value, and it doesn't capture the ongoing hosting, refreshing, and support that a live client portal actually requires.
4. Per-client monthly retainer
You charge a recurring monthly fee per client for delivering and maintaining their reporting. This is the model that compounds: predictable revenue, a rising valuation for your agency, and — crucially — an incentive to build efficient, reusable reporting because you keep the upside of your own productivity. It's also the model that aligns with how the underlying technology is actually priced (fixed capacity, not per hour).
Which model wins
The framework: floor, ceiling, and where your price lives
Good pricing sits between two numbers.
Your floor is your true delivery cost — and most agencies calculate it wrong because they count build time and forget the rest. The real floor includes the initial build (amortised over the contract), ongoing maintenance and support, and the licensing and capacity to actually serve the reports to the client. That last item is the one that surprises people (see the licensing section below). If your monthly floor to serve a client is €400, pricing at €500 leaves you one awkward quarter away from losing money on them.
Your ceiling is the value the client receives. A marketing agency's client-reporting portal might directly influence where that client spends six figures of ad budget. Reporting that improves those decisions is worth a great deal more than the hours it took to build. You'll rarely capture the full ceiling — but you should price toward it, not away from it.
Your price lives in between, and the gap is your margin. The quotable version: charge for the outcome — the decisions your client makes with the data — not the artifact you handed over. Agencies that price at "cost plus a bit" leave most of that gap on the table.
The margin-killer hiding in your reporting: per-viewer licensing
Here's the operational detail that decides whether the retainer math works: how you license the reports you deliver.
If you share Power BI reports with clients on the per-user model, every client contact who logs in needs a Power BI Pro license (around $14/user/month in 2026). Across a book of clients that scales viciously — 10 clients with 15 contacts each is 150 licenses, roughly $2,100/month in Microsoft fees that come straight out of your margin, growing every time a client adds a user. You either absorb it (margin shrinks) or itemise it (awkward conversation).
The fix is to serve reporting on fixed Fabric capacity instead of per viewer. On capacity, unlimited client viewers cost one predictable monthly fee regardless of headcount — so adding a user, or a whole client, doesn't add a license bill. That's what turns per-client retainers into genuine margin. A managed white-label portal delivers this without a build. (We quantify the per-viewer trap in the hidden cost of Power BI Pro for BI agencies, and compare the routes in Power BI client portal pricing.)
Worked example: 10 clients on retainer
Say you charge €750/client/month to deliver and maintain a branded reporting portal — €7,500/month in recurring revenue across 10 clients.
- On per-viewer licensing: 150 viewer licenses at ~$14 = ~$2,100/month in Microsoft fees alone, before your build and support time. Your floor is high and rises with every user the client adds.
- On fixed capacity + a portal: one capacity (an F2 is roughly $263/month) plus a portal subscription serves all 10 clients and all their viewers. Your floor is low, flat, and predictable — so the same €7,500 keeps far more margin, and onboarding client 11 barely moves your cost.
Same revenue, completely different business. The pricing model and the licensing model have to be designed together.
How to package your tiers
Don't sell one price — sell a ladder that lets clients self-select up:
- Good: a branded portal with their core dashboards, refreshed and supported.
- Better: add self-serve — clients filter and explore their own data, more reports, priority support.
- Best: add agentic AI so clients ask their dashboards questions in plain language — a clear premium worth a premium price.
Tiering raises average revenue per client without new sales effort, and gives you an upgrade path built into the relationship. (More on turning delivery into recurring product in the BI agency playbook.)
Frequently asked questions
How should a BI agency price client reporting?
The most profitable model is a per-client monthly retainer priced to the value of the decisions the reporting enables, rather than hourly or per-project. Set a floor from your true delivery cost — build, support, and the licensing/capacity to serve the reports — then price up toward the value the client receives, and package it in tiers. Retainers create predictable, recurring revenue and reward you for building efficient, reusable reporting.
How much should I charge per client for a reporting portal?
It depends on your market and the value delivered, but a per-client retainer commonly ranges from a few hundred to a few thousand euros/dollars per month. The key is to start from your real monthly cost to serve that client — including hosting and licensing — and price with a clear margin above it, then add premium tiers (self-serve, AI insights) rather than competing on a single low number.
Is hourly or retainer billing better for BI reporting?
Retainer, for ongoing reporting. Hourly caps your income at hours worked and penalises you for being efficient, while a per-client retainer produces predictable recurring revenue and rewards reusable, efficient delivery. Hourly still fits exploratory or one-off work, but it's a weak basis for a long-term client-reporting relationship.
Why does per-viewer Power BI licensing hurt agency margins?
Because it scales with every client user. On the per-user model, each client contact needs a Power BI Pro license (~$14/user/month in 2026), so your Microsoft bill grows with every user across every client and eats directly into your retainer margin. Serving reports on fixed Fabric capacity instead makes viewer cost flat regardless of headcount, protecting margin as you grow.
Should I charge clients separately for Power BI licenses?
Usually no — it's cleaner and more profitable to move off per-viewer licensing entirely and serve reporting on fixed capacity, then fold a predictable hosting cost into your retainer. Itemising per-user licenses creates awkward, rising bills and exposes you to the client questioning Microsoft's pricing. A capacity-based portal lets you offer simple, all-in pricing.
How do I price AI-powered client reporting?
Treat self-serve AI Q&A as a premium tier, not a giveaway. Because agentic AI lets clients answer their own questions, it reduces your ad-hoc reporting load while increasing the value clients get — a strong basis for a higher-priced "Best" tier on top of your standard reporting retainer.
