Power BI consultancy in Plymouth: what it costs, what breaks and what to build first
A practical guide to Power BI consultancy in Plymouth: the definition traps in defence and security and ports, terminals and maritime, honest licensing arithmetic, hire-versus-engage costs, and the compliance position under UK GDPR and the Data Protection Act 2018.
Local view for Plymouth, United Kingdom
The call from Plymouth usually starts the same way: two reports disagree, both have a defender, and the meeting where it matters is on Thursday.
Plymouth is big enough to host serious reporting estates and small enough that one or two people usually hold all the knowledge. With around 265,000 people and an economy built on defence and security, ports, terminals and maritime, and industrial machinery and engineering, the reporting questions here are specific rather than generic, and so are the ways they go wrong. This page sets out what a Power BI engagement in Plymouth actually involves: the metrics we check first, what it costs, how licensing should be chosen, whether you would be better off hiring, and what the compliance position looks like under UK GDPR and the Data Protection Act 2018.
Why reporting breaks in Plymouth specifically
Generic advice about Power BI is not very useful, because the failure modes follow the industry rather than the tool. Plymouth's economy is weighted towards defence and security, ports, terminals and maritime, and industrial machinery and engineering, with naval dockyard and defence engineering and marine and port operations shaping much of the local employment base. That mix produces a predictable set of reporting problems, and we have seen each of them here more than once.
Ports, terminals and maritime
Vessel, container and yard movement data at very high event volume, with berth planning and customs status driving operational decisions hour by hour.
The characteristic failure is this: equipment telemetry and the terminal operating system disagree on what counts as a move, so productivity figures vary by source. Where that has already happened, the first deliverable is not a dashboard. It is a written reconciliation that establishes which number is correct and why. In practice we start by building a movement and dwell model joining terminal operations to customs status, which exposes whether delays are operational or regulatory.
Typical source systems: terminal operating system, vessel traffic systems, customs and single-window platforms, crane and equipment telemetry and ERP. Customs and security data is tightly controlled, and NIS2 applies to many port operators as critical infrastructure.
Higher education and research
Student lifecycle, research grant and estates data in separate systems, with statutory returns and league-table submissions on fixed annual cycles.
Here the recurring problem is different: statutory returns and internal management reporting are produced through separate routes, so published figures and internal figures disagree. The fix is a student lifecycle model aligned to the statutory return definitions, which removes the annual manual assembly exercise. Student data is personal data with additional duties around special-category attributes, and research data may carry funder-specific restrictions.
Defence and security
Programme and contract data under security classification, with configuration control, export restrictions and long-lived support obligations. Analytics is built outside the accredited environment, which makes the most important programme data the only data excluded from it.
We would usually begin with a programme cost and earned-value model with controlled baselines, deployed inside the security boundary the contract requires. Source systems to expect: ERP, PLM, programme management systems, quality and configuration records and secure document stores.
The metrics we check first in a Plymouth engagement
Sector knowledge in analytics is mostly knowing which definitions destroy a number when they drift. Before we design anything we go through the measures that matter to you and establish, in writing, exactly how each one is calculated and who owns that definition. The table below is the starting list for Plymouth, derived from the industries that dominate here.
| Metric | Where it comes from | The trap that breaks it |
|---|---|---|
| availability of supported fleet | defence and security | Contractual availability definitions differ per contract and must be implemented individually |
| obsolescence exposure | defence and security | Requires component-level lifecycle data that is often held only by suppliers |
| crane moves per hour | ports, terminals and maritime | Working time must exclude planned stoppages or productivity comparisons are meaningless |
| container dwell time | ports, terminals and maritime | Customs hold periods need separating from commercial dwell to locate the real constraint |
| first-time fix rate | industrial machinery and engineering | Multi-visit jobs need an explicit rule or field performance looks better than it is |
| project margin at completion | industrial machinery and engineering | Requires a cost-to-complete estimate, so the measure is only as honest as the forecast feeding it |
| bed occupancy | healthcare provision | Escalation and closed beds need an explicit rule; midnight census differs from continuous measurement |
| waiting time from referral to treatment | healthcare provision | Clock pauses and re-referrals must be modelled explicitly, especially at the tail |
| student-to-staff ratio | higher education and research | Which staff categories count is a definitional choice with reputational consequences |
| research income per academic FTE | higher education and research | FTE basis and the treatment of fractional appointments must be fixed |
None of this is exotic. A measure with two plausible definitions will acquire both, and the resulting variance is then explained away every month instead of being fixed once. The output of this stage is a measure dictionary: every KPI, its business definition, its owner, and the DAX that implements it.
What a first Power BI engagement looks like
We work the same way whether the client is a mid-sized business with one overworked analyst: decisions first, sources second, model third, reports last. Reports built before the model are the single most common cause of rework.
- Decision inventory, week 1We start from the recurring decisions that need numbers, not from the data that happens to be available. Who decides, on what cadence, and what currently blocks them. For a Plymouth business in ports, terminals and maritime, that usually surfaces three or four decisions worth building for and a dozen reports nobody needs.
- Source profiling, weeks 1 to 2Each source system profiled for grain, volume, change tracking, quality and refresh window. terminal operating system, vessel traffic systems and customs and single-window platforms are the usual candidates here. This is where unpleasant surprises belong, not in week ten.
- Model build, weeks 3 to 7A star schema with conformed dimensions, measures written against the agreed definitions, and row-level security applied from the start. For ports, terminals and maritime the argument that has to be settled first is normally crane moves per hour, where working time must exclude planned stoppages or productivity comparisons are meaningless. Settle it before any report exists, not after two of them disagree.
- Report build and validation, weeks 6 to 10Reports built with the people who will use them and validated line by line against the source of record until the numbers tie out. Disagreements get resolved and written down, never averaged.
- Handover, weeks 10 to 14Workshops with your team, documentation in your own systems, and a thirty-day period where we fix what breaks while your people drive. The University of Plymouth has genuine strength in marine science and engineering, feeding defence and maritime employers.
What that costs
Build cost follows project size rather than report count, the number of source systems and their state drive almost all of it. These are the bands we quote in United Kingdom, and we publish them because a buyer cannot start an approval chain without a budget figure.
| Project size | What that covers | Indicative cost | Elapsed time |
|---|---|---|---|
| Small | One or two source systems, one business area, three to five reports, a straightforward star schema | £15,000 to £40,000 | 3 to 6 weeks |
| Medium | Three to six sources, two or three business areas, several fact tables, non-trivial DAX, basic governance | £40,000 to £120,000 | 6 to 12 weeks |
| Large | Heterogeneous sources including ERP and CRM, multiple business areas, a dedicated data layer, formal governance | £120,000 to £400,000+ | 3 to 6 months |
Running it afterwards is a separate line: £3,000 to £8,000 a month for a small estate, £8,000 to £20,000 for a mid-sized one, £20,000 to £50,000+ for a large multi-domain platform. Microsoft licensing is separate again, and is covered next.
Licensing: what Plymouth organisations should actually pay
This is where money is most often wasted, in both directions. Power BI Pro is listed at around US$14 per user per month and Power BI Premium Per User at around US$24 following the 2025 price revision. Local list prices in sterling, euro and Swiss francs track those figures with regional adjustment, and enterprise agreements usually land below list.
| Option | Who it suits | Approximate list price | The catch |
|---|---|---|---|
| Power BI Free | One person exploring data with no sharing | No charge | Cannot share into a workspace, so it is not a business option |
| Power BI Pro | Small reader populations, typically under about 200 people | Around US$14 per user per month at list | Every reader needs a licence, so cost scales linearly with the audience |
| Premium Per User | Teams needing larger models, higher refresh rates or paginated reports | Around US$24 per user per month at list | Still per-user, so a large reader base gets expensive quickly |
| Fabric F2, F32 capacity | Data engineering workloads with a modest reader population | From roughly US$260 a month for an F2, pay-as-you-go | Readers still need Pro licences below F64, and small SKUs throttle under load |
| Fabric F64 capacity | Large reader populations and in-platform data engineering | Roughly US$8,400 a month pay-as-you-go, around US$5,000 reserved | Only pays for itself above roughly 350 to 600 readers, depending on your discount |
The arithmetic that matters: F64 only becomes cheaper than per-user licensing somewhere in the region of 350 to 600 readers, depending on the discount you actually pay and whether you reserve capacity. Below that, Pro or PPU per user is normally the right answer, and buying capacity for prestige is a straightforward waste of money.
For most organisations in Plymouth, per-user licensing is the correct answer and will remain so for years. We have told several clients here that the Fabric capacity they were quoted would be a straightforward waste of money, and we would rather do that than sell the larger number.
Always price from the current Microsoft rate card for your region and agreement. Any figure in an article older than a quarter should be treated as an order of magnitude, not a quote.
Hiring in Plymouth versus engaging a consultancy
This is a fair question and the honest answer is sometimes "hire". The University of Plymouth has genuine strength in marine science and engineering, feeding defence and maritime employers. Locally, a mid-level analytics engineer costs roughly £45,000 to £75,000 outside London, and £60,000 to £95,000 in London. An experienced external consultant runs at roughly £750 to £1,400 per day, and more through a large systems integrator.
| Approach | When it is the right call | What it costs you |
|---|---|---|
| Hire internally | Steady ongoing demand, an existing platform to maintain, and a manager who can judge the work | Roughly £45,000 to £75,000 outside London, and £60,000 to £95,000 in London a year, plus recruitment time and the risk that one person holds all the knowledge |
| Engage a consultancy | A first platform, a migration, a specialist problem, or a deadline that cannot absorb a hiring cycle | Roughly £750 to £1,400 per day, and more through a large systems integrator, for a defined scope with documentation and handover included |
| Both | The most common answer: internal ownership of business engagement, external depth for architecture and peak delivery | A smaller internal salary plus a modest retainer, which is usually cheaper than either extreme |
Where a Plymouth client has told us they intend to build an internal team, we design for it from the start. Everything is built to be handed over: scriptable models rather than click-built ones, a naming convention written down, documentation in the tools your team already uses, and a dictionary of measures that outlasts the engagement. Several clients have gone on to need us only for quarterly review, which is a perfectly good outcome.
Data residency and compliance for Plymouth organisations
Azure UK South and UK West give genuine in-country data residency, and Power BI tenants can be provisioned in the United Kingdom region. Note that some workloads, certain preview features and a handful of AI services, still process outside the region, so residency claims should be checked per service rather than assumed tenant-wide. In practice, Plymouth deployments normally use UK South (London), with UK West (Cardiff) as the paired region.
Regulatory oversight relevant to analytics comes from the Information Commissioner's Office (ICO) under UK GDPR and the Data Protection Act 2018, plus the sector bodies that matter here: FCA and PRA for financial services conduct and prudential reporting, ICO for data protection, including analytics on personal data and Ofgem and Ofwat for energy and water price-control and performance submissions.
- UK GDPR data-minimisation and storage-limitation duties apply directly to analytics copies of personal data, which is where most estates quietly fail.
- Consumer Duty outcome monitoring has made customer-level analytics a supervisory expectation for regulated firms, not an optional capability.
- SECR energy and carbon reporting requires auditable activity data, which usually means the same lineage discipline as financial reporting.
We cover this properly on the data governance and compliance page, and in more depth in our article on data governance for Plymouth organisations.
How we deliver into Plymouth
- Most UK engagements run remote-first with on-site workshops for definition sessions and go-live.
- IR35 and off-payroll rules make a fixed-scope statement of work cleaner than a day-rate contractor arrangement for many clients.
- Public-sector buyers typically route analytics work through established frameworks rather than open tenders.
Delivery is remote-first with on-site workshops at the points where being in the room genuinely helps: definition sessions, validation and go-live. We work in English.
How a Plymouth organisation actually buys this
Most consultancy pages stop at what the work is and leave the buying process to email. Relatively fast and relationship-led, with procurement entering late unless the value is high. Day rates and fixed prices are both normal, and buyers expect them early rather than after three meetings.
In the private sector: Introduction or inbound enquiry, a technical call, then a written proposal with a fixed price or a day rate. Above roughly £50,000 a procurement team joins and the supplier is checked for insurance, financial standing and security posture. Many larger organisations buy only from a preferred-supplier list, so getting onto that list is a separate exercise from winning the work.
In the public sector: Public bodies buy through Crown Commercial Service frameworks, most often G-Cloud on the Digital Marketplace for cloud and analytics services, or through Digital Outcomes-style routes for delivery teams. Above-threshold requirements are advertised on Find a Tender, and the Procurement Act 2023 regime governs the process. Direct award is possible under a framework and is far quicker than an open competition.
| Stage | Who is involved | What they need from a supplier |
|---|---|---|
| Qualification | Budget holder, usually a finance director, CIO or head of data | A clear statement of what would be built, in what order, with an indicative price range |
| Technical review | IT and information security review, increasingly including a supplier questionnaire | An architecture position that survives questioning, and references in a comparable sector |
| Risk and compliance | Procurement, for value above the delegated authority threshold and Legal, for the master agreement rather than the statement of work | Certificate of incorporation and latest filed accounts, Professional indemnity, public liability and employer's liability insurance certificates and Cyber Essentials or Cyber Essentials Plus, effectively mandatory for public-sector work |
| Commercial | Legal, for the master agreement rather than the statement of work | Contract shape, payment terms and liability. English. |
Documents you should expect to request, and that any supplier worth shortlisting will have ready, are certificate of incorporation and latest filed accounts, professional indemnity, public liability and employer's liability insurance certificates, cyber essentials or cyber essentials plus, effectively mandatory for public-sector work and data processing agreement under uk gdpr article 28.
Our own entity details, insurance, processing agreements and contracting shapes are published on the procurement page, so your buying team can start without waiting for a reply.
Signals it is time to call someone
The usual triggers are two reports disagreeing on a headline number, an overnight refresh someone re-runs by hand each morning, a largest model that is one file owned by one person, finance still rebuilding the board pack in a spreadsheet, a legacy BI renewal whose price no longer makes sense, or a question about who can see a sensitive dataset that took a week to answer honestly. If two or more are true, a two to three week paid discovery will tell you what to do about it, and you keep the output whether or not you engage us further. Book a technical review, or read what we actually build:
We work across United Kingdom and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Portsmouth, Sheffield, Southampton, Glasgow, Liverpool and Nottingham.
Frequently asked questions
Do you have an office in Plymouth?
We are deliberately a distributed consultancy rather than a network of nameplate offices, so we will not claim a Plymouth address we do not occupy. We deliver into Plymouth remotely with on-site workshops at the stages where presence matters, definition sessions, validation and go-live, and we are explicit about travel in the statement of work rather than burying it.
How much does a Power BI project cost for a Plymouth business?
Discovery is a fixed fee in the low five figures. Build cost follows project size: £15,000 to £40,000 for a small project of three to six weeks, £40,000 to £120,000 for a medium one of six to twelve weeks, and £120,000 to £400,000+ for a large platform running three to six months. What moves a project between bands is the number of source systems and their state, not the number of reports. Running it afterwards costs £3,000 to £8,000 a month for a small estate, £8,000 to £20,000 for a mid-sized one, £20,000 to £50,000+ for a large multi-domain platform. We give a written estimate range before discovery and a fixed price after it, because an estimate based on an average rather than on your data is worth very little.
Which industries in Plymouth do you work with?
The local mix means most of our Plymouth work sits in defence and security suppliers, port and terminal operators, and machinery builders and engineering firms. We publish what we expect to find in each sector, the metrics, the source systems and the specific traps, so you can judge whether we understand your business before the first call.
Can you work with the Power BI estate we already have?
Yes, and it is usually the cheaper route. We begin with an estate review: which models are worth keeping, which should be consolidated into a shared semantic model, and which can be retired because nobody has opened them in six months. A full rebuild is occasionally correct, but it should be a conclusion rather than a starting assumption.
Do we need Fabric capacity, or will Power BI Pro do?
The arithmetic that matters: F64 only becomes cheaper than per-user licensing somewhere in the region of 350 to 600 readers, depending on the discount you actually pay and whether you reserve capacity. Below that, Pro or PPU per user is normally the right answer, and buying capacity for prestige is a straightforward waste of money. For most organisations of the size typically found in Plymouth, per-user licensing is cheaper and will stay cheaper. We model your actual reader mix and give you the break-even point in writing.
How long does it take to get a project started in United Kingdom?
Three to eight weeks from first conversation to signature in the private sector. Framework direct award can be two to four weeks; an open public competition is three to five months. The variable is rarely the commercial negotiation. It is supplier onboarding, security review and, where it applies, works council or outsourcing committee consultation. We publish our entity details, insurance, processing agreements and contracting shapes on the procurement page so your buying team can begin that in parallel rather than afterwards.
Who owns the work when the project ends?
You do, in a form you can change without us. You get a model under version control that a script can rebuild, a documented naming convention, a dictionary that says what each measure is for, and training that runs alongside the build instead of after it. Exit assistance is written into every agreement rather than negotiated at an awkward moment.
Read next
Microsoft Fabric and Azure data platforms in Plymouth: architecture, capacity and cost
How to build a Microsoft Fabric or Azure data platform for a Plymouth organisation: medallion layout for defence and security and ports, terminals and maritime, honest capacity sizing, Direct Lake trade-offs and the United Kingdom residency position.
Data governance and GDPR for Plymouth organisations: controls that produce evidence
Practical data governance for analytics estates in Plymouth: what the Information Commissioner's Office (ICO) expects under UK GDPR and the Data Protection Act 2018, the sector rules that bite locally, Microsoft Purview in practice, and a 90-day plan.
Power BI licensing in 2026: Pro, Premium Per User or Fabric capacity, with the break-even arithmetic
The honest comparison of Power BI Pro, Premium Per User and Fabric capacity: what each one actually includes, where the break-even point sits, and the four ways organisations overspend.