Power BI consultancy in Berlin: what it costs, what breaks and what to build first

Almost every Power BI problem we are asked to look at in Berlin arrives described as a performance problem and turns out to be a definition problem.

Berlin is large enough that most organisations here already have several analytics teams and the problem is reconciling them. With around 3,700,000 people and an economy built on software and technology, public sector, and media, advertising and creative, 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 Berlin 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 the EU GDPR and the Bundesdatenschutzgesetz (BDSG).

Why reporting breaks in Berlin specifically

Generic advice about Power BI is not very useful, because the failure modes follow the industry rather than the tool. Berlin's economy is weighted towards software and technology, public sector, and media, advertising and creative, with Germany's largest technology and start-up ecosystem and federal government and agency functions 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.

Software and technology

Product event streams at very high volume alongside subscription, billing and support data that must be joined at account grain to be useful.

The characteristic failure is this: ARR comes from a finance spreadsheet with manual adjustments, so restating a prior period requires archaeology and diligence becomes painful. 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 an effective-dated contract and movement model so ARR is reproducible for any historical date, then product events joined at account grain.

Typical source systems: billing and subscription platform, CRM, product event pipeline, support platform and finance system. Product telemetry on identifiable users needs a lawful basis and consent handling, and SOC 2 or ISO 27001 evidence often covers the analytics estate.

Professional and legal services

Time, billing and pipeline data where almost every meaningful figure is an allocation, and where confidentiality obligations constrain who may see matter-level detail.

Here the recurring problem is different: four definitions of utilisation circulate simultaneously, so partner behaviour responds to whichever figure appears in the meeting they attend. The fix is a time, billing and WIP model with one agreed utilisation and realisation definition, reported from practice group down to individual under agreed visibility rules. Matter confidentiality and information barriers must be inherited by analytics through row-level security, not re-implemented loosely.

Media, advertising and creative

Audience and campaign data from many external platforms, each with its own metric definitions, alongside project and resource data on the delivery side. Each platform's own numbers are reported side by side as if comparable, producing totals that exceed actual results.

We would usually begin with a campaign and revenue model with deduplicated attribution and a documented definition per platform metric, replacing a monthly spreadsheet merge. Source systems to expect: advertising platforms, audience measurement services, content management systems, project and resource management and finance system.

The metrics we check first in a Berlin 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 Berlin, derived from the industries that dominate here.

None of this is exotic. Two defensible definitions of the same measure will both end up implemented somewhere, and the gap between them gets explained at every review instead of being closed 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 large group with nine existing workspaces: decisions first, sources second, model third, reports last. Reports built before the model are the single most common cause of rework.

1. 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 Berlin business in software and technology, that usually surfaces three or four decisions worth building for and a dozen reports nobody needs.
2. Source profiling, weeks 1 to 2Each source system profiled for grain, volume, change tracking, quality and refresh window. billing and subscription platform, CRM and product event pipeline are the usual candidates here. This is where unpleasant surprises belong, not in week ten.
3. 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 software and technology the argument that has to be settled first is normally annual recurring revenue, where treatment of usage overages and services must be fixed and never silently changed. Settle it before any report exists, not after two of them disagree.
4. 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.
5. 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. TU Berlin, HU, FU and Charité plus a large international developer population make Berlin the deepest data engineering market in Germany.

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 Germany, and we publish them because a buyer cannot start an approval chain without a budget figure.

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 Berlin 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.

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 larger Berlin organisations with hundreds of report consumers, a capacity SKU is usually the right answer, and which one depends on measured consumption rather than headcount. We profile workloads on a short-lived trial capacity before anyone signs.

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 Berlin versus engaging a consultancy

This is a fair question and the honest answer is sometimes "hire". TU Berlin, HU, FU and Charité plus a large international developer population make Berlin the deepest data engineering market in Germany. Locally, a mid-level analytics engineer costs roughly €60,000 to €95,000, higher in Munich, Frankfurt and Stuttgart. An experienced external consultant runs at roughly €900 to €1,500 per day.

Where a Berlin client has told us they intend to build an internal team, we design for it from the start. We build on the assumption that we leave. That means a model your own engineers can change without us, naming that needs no explanation, documentation inside your systems rather than ours, and a measure dictionary that still makes sense in two years. Several clients have gone on to need us only for quarterly review, which is a perfectly good outcome.

Data residency and compliance for Berlin organisations

Germany West Central in Frankfurt is the usual choice and gives in-country residency with very low latency to the financial sector. Germany North provides a paired region. Residency alone does not satisfy a German works council or data protection officer. They will also ask about processor chains and access by support personnel, so those answers need preparing. In practice, Berlin deployments normally use Germany West Central (Frankfurt), with Germany North (Berlin) as the paired region.

Regulatory oversight relevant to analytics comes from the federal commissioner (BfDI) and the Land data protection authorities under the EU GDPR and the Bundesdatenschutzgesetz (BDSG), plus the sector bodies that matter here: BaFin for financial services supervision, including MaRisk data-quality expectations, Land data protection authorities for data protection enforcement, which varies in emphasis by Land and BNetzA for energy, telecoms and rail network reporting.

• Betriebsrat co-determination is the single most underestimated factor in German analytics projects: any reporting that could be used to assess individual employee performance generally needs a works agreement before launch.
• MaRisk and BAIT expectations mean financial-sector data lineage and documentation standards are explicit, not inferred.
• The Lieferkettensorgfaltspflichtengesetz requires supply-chain due-diligence data that most ERP estates do not hold in reportable form.

We cover this properly on the data governance and compliance page, and in more depth in our article on data governance for Berlin organisations.

How we deliver into Berlin

• Specification discipline is higher than in the UK: expect a written Fachkonzept and a documented acceptance process, and plan for it rather than resisting it.
• Works council consultation should be scheduled at the start of a project, not discovered during user acceptance testing.
• Many Mittelstand clients prefer German-language documentation and stakeholder sessions even where the project team works in English.

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 German and English, and stakeholder sessions run in whichever of those the room prefers.

How a Berlin organisation actually buys this

Most consultancy pages stop at what the work is and leave the buying process to email. Specification-driven and documented. The technical team and the Einkauf negotiate separately, references carry real weight, and a written proposal with itemised positions is expected rather than a slide deck.

In the private sector: The business area issues a Lastenheft describing what it needs, or asks the supplier to produce a Pflichtenheft specifying how it will be delivered. The supplier responds with a formal Angebot: itemised positions, a stated Tagessatz or fixed price, delivery dates and acceptance criteria. The Einkauf then negotiates commercial terms separately from the technical discussion, and a Betriebsrat consultation runs in parallel wherever the system could be used to assess individual employee performance.

In the public sector: Public bodies procure through e-Vergabe and the Land Vergabeportale under VgV above EU thresholds and UVgO below them, with above-threshold notices also published on TED. The process is formal, the award criteria are published in advance, and a submission that misses a formal requirement is excluded regardless of quality.

Documents you should expect to request, and that any supplier worth shortlisting will have ready, are handelsregisterauszug, a current commercial register extract, unbedenklichkeitsbescheinigung for tax and social security contributions, betriebshaftpflicht and professional indemnity insurance certificates and auftragsverarbeitungsvertrag (avv), the article 28 processing agreement, in german.

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 Germany and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Wiesbaden, Mainz, Potsdam, Offenbach am Main, Cologne and Munich.

Frequently asked questions