The question behind the question
When a fire, security or building services contractor asks whether to use Power BI, the licence is rarely the real decision. Power BI Pro is cheap per head. What costs money is getting job, invoice and pipeline data into one model that agrees with the finance figures, and then keeping it agreeing every week after the person who built it has moved on to other work.
So this page compares the two routes on the whole cost: Microsoft's published licence prices, plus the hours to build and look after the reports. The hours are assumptions, labelled as such, because they depend on your systems and your people. The licence prices are real and sourced. We also set out, plainly, when Power BI is the better answer.
What Power BI costs to license
Microsoft's UK Power BI pricing page lists these prices, excluding VAT, checked on 5 November 2026:
| Licence | Published price | What it adds |
|---|---|---|
| Free account | £0 | Build for yourself; sharing needs Pro or Premium |
| Power BI Pro | £10.80 per user per month, paid yearly | Publish and share reports. Included in Microsoft 365 E5 and Office 365 E5 |
| Premium Per User (PPU) | £18.50 per user per month, paid yearly | Pro features plus larger models and more frequent refresh |
| Fabric capacity | Variable, billed through Azure | Lakehouse, warehouse, pipelines and shared capacity for reports |
Fabric capacity is priced per capacity unit (CU). Microsoft's Azure retail prices API, filtered to Microsoft Fabric in GBP for UK South, gave on 6 November 2026, £0.1579 per CU hour pay-as-you-go and £822.5255 per CU for a one-year reservation. The smallest size, F2, has 2 CU.
Two licensing rules from Microsoft's Fabric licences guide shape the maths for a business of 10 to 500 staff. First, below F64 every person who views Power BI content still needs Pro, PPU or a trial licence; only on F64 or larger can viewers with a free licence read reports. Second, anyone creating Power BI items in a shared workspace needs Pro or PPU whatever the capacity. Microsoft's data refresh documentation adds a third: models on shared capacity (Pro) get eight scheduled refreshes a day, while PPU and Fabric capacity allow up to 48.
The cost model
Inputs
| Input | Source | Fixed or assumed |
|---|---|---|
| Report builders (creators) | Your org chart | Your number |
| Report readers (viewers) | Your org chart | Your number |
| Licence price per user per month | Microsoft pricing page | Published |
| Capacity price per CU | Azure retail prices | Published |
| Build hours by task | Your estimate or a supplier's | Assumed |
| Upkeep hours per month | Timesheets once live | Assumed, then measured |
| Hourly rate | Salary plus on-costs, or contractor day rate ÷ hours | Assumed |
What a field service model has to join
The build hours depend mostly on how many systems the reports need and how cleanly their keys line up.
| From | To | Join on | Typical problem |
|---|---|---|---|
| Job system site | Accounts customer | A customer reference stored in both | Site-level jobs, customer-level invoices |
| Job system job | Accounts invoice | Job reference typed on the invoice | Often missing or inconsistent; FSM and accounts invoice numbers need not match |
| CRM company | Job system client | A shared ID you maintain | Name matching fails on "Ltd" versus "Limited" |
| Any record | Date table | Completed, invoiced or closed date | Each measure needs the right date |
Getting the data out is its own task. Uptick, for example, states in its API fair use policy that any sync into a BI tool or reporting database must run through its Airbyte connector, and custom bulk-export scripts for BI are not permitted. That means a Power BI build on Uptick data needs an Airbyte pipeline and somewhere for it to land before Power BI sees anything. The Uptick integration page and the Uptick reports limitations guide cover this in more depth; the same planning applies to Simpro or any other job system.
Formulas
| Measure | Formula |
|---|---|
| Annual licences (Pro route) | (creators + viewers) × £10.80 × 12 |
| Annual licences (F2 route) | 2 × £822.5255 + (creators + viewers) × £10.80 × 12 |
| F64 break-even | 64 × £822.5255 ÷ (£10.80 × 12), rounded up to whole users |
| Build cost | build hours × hourly rate |
| Upkeep cost | upkeep hours per month × 12 × hourly rate |
| Year one | licences + build cost + upkeep cost |
| Year two onwards | licences + upkeep cost |
Power BI cost of ownership · Brackenstowe Fire & Security
Licences are 14% of year one.
The rest is people’s time.
3 report builders and 14 managers who read reports, 17 users in all. Licence prices are Microsoft’s published UK prices (GBP, excluding VAT, checked 6 November 2026). Hours and the hourly rate are assumptions.
- Year one
- £16,063.20
- Pro licences, build, upkeep
- Year two
- £9,463.20
- Pro licences and upkeep
- Pro licences
- £2,203.20
- 17 users, per year
- People time
- 252 h
- Build plus 12 months upkeep
Licence options for 17 users, per year
| Option | Calculation | Per year |
|---|---|---|
| Power BI Pro for everyoneReports and sharing; 8 scheduled refreshes a day | 17 users × £10.80 × 12 | £2,203.20 |
| Premium Per User for everyoneUp to 48 refreshes a day, larger models | 17 users × £18.50 × 12 | £3,774 |
| Fabric F2 (1-year reservation) + Pro for everyoneAdds lakehouse, warehouse and pipelines; viewers still need Pro below F64 | 2 CU × £822.53 + 17 × £129.60 | £3,848.25 |
| Fabric F64 (1-year reservation) + Pro for creatorsFree-licence viewers can read reports; sized for hundreds of viewers | 64 CU × £822.53 + 3 × £129.60 | £53,030.43 |
F64 only beats Pro for everyone at about 407 report users. Fabric F2 pay-as-you-go would be about £230.53 a month if left running 730 hours.
Build and upkeep (assumed hours at £55/hour)
| Task | Hours |
|---|---|
| Job system extract via its approved route (e.g. Airbyte for Uptick) | 16 |
| Accounts and CRM connections, credentials, gateway if needed | 12 |
| Model: customer and site matching, keys, date table, measures | 40 |
| Five reports (MD pack, PPM, unbilled, aged debt by site, utilisation) | 40 |
| Testing figures against finance and sign-off | 12 |
| One-off build | 120 |
| Failed refreshes, source field changes (monthly) | 4 |
| New measures and report requests (monthly) | 6 |
| Users, licences and workspace access (monthly) | 1 |
| Upkeep per month | 11 |
Upkeep hours logged, year one
Dashed line: plan of 11 hours. Gold months ran over. Total 132 hours.
Power BI is likely the better choice if
- Pro already comes with your Microsoft 365 E5 or Office 365 E5 licences
- Someone on staff writes Power Query and DAX and wants to keep doing it
- Most of your data sits in Excel, SharePoint or SQL Server
- Analysts want to explore and build their own visuals
- You only need reports, not anything that acts on them
Worked example (illustrative, fictional)
Brackenstowe Fire & Security is an invented contractor with 85 staff. Three people will build reports and 14 managers will read them, so 17 users need a licence. Nobody holds Microsoft 365 E5. All hours and the £55 hourly rate are assumptions.
Licences. Pro for all 17: 17 × £10.80 × 12 = £2,203.20 a year. PPU for all 17: 17 × £18.50 × 12 = £3,774.00. Adding an F2 reservation to get a Fabric warehouse: 2 × £822.5255 = £1,645.05, plus the same £2,203.20 of Pro, = £3,848.25. Moving to F64 so that viewers need no paid licence: 64 × £822.5255 = £52,641.63, plus Pro for the 3 creators (£388.80), = £53,030.43. F64 only beats Pro for everyone at 52,641.63 ÷ 129.60 = 406.2, so about 407 report users. At Brackenstowe's size, Pro is the sensible licence.
Build. Job system extract 16 hours, accounts and CRM connections 12, the model with its customer and site matching 40, five reports at 8 hours each 40, and testing against finance 12. That is 120 hours × £55 = £6,600.
Upkeep. Failed refreshes and source changes 4 hours a month, new requests 6, user access 1: 11 hours a month, 132 a year. 132 × £55 = £7,260.
Totals. Year one: £2,203.20 + £6,600 + £7,260 = £16,063.20. Year two: £2,203.20 + £7,260 = £9,463.20. Licences are 2,203.20 ÷ 16,063.20 = 13.7% of year one; people's time is the other 86.3%. Pipeline hosting for the Airbyte sync is not included.
The point of the example is the split, not the total. Halve the hourly rate or double the upkeep hours and the total swings by thousands, while the licence line hardly moves. If you are comparing Power BI to anything else, compare hours.
When Power BI is the better choice
There are good reasons to pick Power BI, and for some businesses it is clearly right:
- You already pay for it. If your staff have Microsoft 365 E5 or Office 365 E5, Pro is included, so the licence line is close to zero.
- You have the skills in-house. Someone who writes Power Query and DAX, enjoys it and has time for it every month turns the upkeep hours into part of a normal job rather than a project.
- Your data is mostly Microsoft-shaped. Excel on SharePoint and SQL Server are simple sources for Power BI. Fewer joins across vendor APIs means fewer build hours.
- You want people to explore. Power BI is built for analysts slicing data their own way. If that freedom is the goal, a fixed report set will feel narrow.
- Reporting is the whole job. If nobody needs anything to happen as a result of a report, such as a chaser drafted or a renewal priced, a BI tool is all you need.
If three or more of those describe you, start with Power BI. Our sibling guide on the cost of a reporting analyst helps size the people side honestly.
Where IVP.ai takes a different route
IVP.ai is not a BI tool you build in. It builds and runs the IVP.ai Data Layer, a governed data warehouse fed from your systems (anything with a REST API, any SQL database, Excel files), and keeps the joins in the tables above maintained for you. For Uptick, that connection runs through Airbyte, in line with Uptick's policy. Reports run on that layer, so the build and upkeep hours in the example are largely the work IVP.ai takes on.
The second difference is what happens after the report. Deskless by IVP.ai runs agents on the same data. By default a Deskless agent flags, drafts and waits for a person; it only acts, for example raising invoices or sending chasers, if a business configures it to. In the agents that know when to stop case study, renewal agents priced and reported on 100+ contracts in the first live run and sent 90+ renewal invoices in one dispatch, with no price changed without a person. A national fire safety and security company also unified HubSpot, Uptick and finance spreadsheets into one governed view, saving 10+ hours a week on reporting, and a franchise removed two days a week of manual reporting. None of those projects used Power BI, so they show the IVP.ai route, not a head-to-head result.
More report templates for contractors are on the field service reporting hub.
Test it on your own data
Run the cost model above with your own users and hours first. Then see the other route on real data with the free 48-hour pilot: we connect up to three sources, clean the data and set one report or agent running within 48 hours of read-only access. You have 14 days of access, then choose a plan or walk away.