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

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

Locarno is a market of mostly owner-managed and mid-sized organisations, where analytics is one person's responsibility alongside three others. With around 16,000 people and an economy built on tourism, hospitality and events, media, advertising and creative, and healthcare provision, 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 Locarno 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 revised Federal Act on Data Protection (revFADP / revDSG), in force since September 2023.

Why reporting breaks in Locarno specifically

Generic advice about Power BI is not very useful, because the failure modes follow the industry rather than the tool. Locarno's economy is weighted towards tourism, hospitality and events, media, advertising and creative, and healthcare provision, with a festival and visitor economy and hospitality and second-home property 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.

Tourism, hospitality and events

Booking, channel and rate data with heavy seasonality, plus on-site spend and occupancy that only reconcile once channel commission is accounted for.

The characteristic failure is this: gross booking value from online travel agents is compared with direct booking revenue, making the most expensive channel look like the best one. 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 stay-grain model joining rooms, ancillary spend and channel cost, which is where true channel profitability becomes visible.

Typical source systems: property management system, booking channels and OTAs, revenue management system, EPOS and CRM. Guest data is personal data with cross-border transfer implications when group systems sit outside the region.

Construction and real estate

Project cost and progress data with subcontractor valuations, variations and retentions, plus asset and tenancy data on the property side.

Here the recurring problem is different: project reporting runs monthly on manually consolidated spreadsheets, so a problem contract is identified two months after it turned. The fix is a project cost and valuation model with variations and retentions explicit, so margin erosion is visible while the project is live. Subcontractor payment and tax reporting obligations apply, and health and safety records carry their own retention duties.

Public sector

Case and service data locked inside line-of-business systems with restrictive reporting modules, feeding statutory returns with precisely defined rules. Returns are assembled by hand each cycle by a small number of experienced staff, concentrating risk in individuals.

We would usually begin with a governed model that produces both the statutory return and internal performance reporting, so published and internal figures cannot diverge. Source systems to expect: case management systems, finance and ERP, HR and payroll, GIS and gazetteers and grant management.

The metrics we check first in a Locarno 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 Locarno, 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 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.

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 Locarno business in tourism, hospitality and events, 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. property management system, booking channels and OTAs and revenue management system 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 tourism, hospitality and events the argument that has to be settled first is normally RevPAR, where out-of-order rooms treatment changes the denominator and is handled differently by each system. 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. Locarno relies on the Lugano and Bellinzona catchments for specialist skills.

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

Running it afterwards is a separate line: CHF 3,000 to CHF 8,000 a month for a small estate, CHF 8,000 to CHF 20,000 for a mid-sized one, CHF 20,000 to CHF 50,000+ for a large multi-domain platform. Microsoft licensing is separate again, and is covered next.

Licensing: what Locarno 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 most organisations in Locarno, 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 Locarno versus engaging a consultancy

This is a fair question and the honest answer is sometimes "hire". Locarno relies on the Lugano and Bellinzona catchments for specialist skills. Locally, a mid-level analytics engineer costs roughly CHF 110,000 to CHF 160,000, with Zurich and Zug at the top. An experienced external consultant runs at roughly CHF 1,300 to CHF 2,200 per day.

Where a Locarno 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 Locarno organisations

Switzerland North and Switzerland West give in-country residency, which matters more here than almost anywhere else in Europe: banking secrecy, professional secrecy obligations and client expectation all push Swiss data to stay Swiss. Verify per service, because not every Azure or Fabric feature is available in both Swiss regions. In practice, Locarno deployments normally use Switzerland North (Zurich), with Switzerland West (Geneva) as the paired region.

Regulatory oversight relevant to analytics comes from the Federal Data Protection and Information Commissioner (FDPIC / EDÖB) under the revised Federal Act on Data Protection (revFADP / revDSG), in force since September 2023, plus the sector bodies that matter here: FINMA for banking, insurance and asset management supervision, including outsourcing circulars, FDPIC for federal data protection oversight and ElCom for electricity market and grid reporting.

• The revFADP brought Swiss law closer to the GDPR but not identical to it: records of processing, impact assessments and breach notification follow Swiss rules, and an EU-shaped compliance pack needs adapting rather than copying.
• FINMA outsourcing expectations require documented control over cloud providers, including the right to audit and a tested exit plan.
• Article 321 of the Criminal Code and sectoral secrecy duties restrict who may see client-identifying data, which has direct consequences for row-level security design.

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

How we deliver into Locarno

• Swiss engagements are precise about scope and documentation, and tolerate fewer surprises than UK projects.
• Multilingual stakeholder groups are normal: German-speaking head office, French-speaking region, English-language group reporting.
• Expect strict supplier onboarding, including security questionnaires and in some cases background checks before any data access.

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

How a Locarno organisation actually buys this

Most consultancy pages stop at what the work is and leave the buying process to email. Relationship-led but heavily documented, with supplier due diligence that goes further than anywhere else in our markets, particularly in banking and pharmaceuticals.

In the private sector: A relationship and a reference open the door; a formal supplier onboarding then decides whether the work can proceed. Expect a security questionnaire, financial checks and, in financial services, an outsourcing assessment against the FINMA circular with documented audit rights and a tested exit plan. Background checks on individual engineers are routine in banking, and some clients require that named staff never move data outside Switzerland.

In the public sector: Federal and cantonal bodies publish on SIMAP under BöB at federal level and IVöB at cantonal level, with WTO/GPA thresholds determining the procedure. Cantonal rules differ, and language requirements follow the canton.

Documents you should expect to request, and that any supplier worth shortlisting will have ready, are handelsregisterauszug, current commercial register extract, betreibungsregisterauszug, a debt enforcement register extract, requested more often than people expect, insurance certificates including professional indemnity, in chf cover levels and data processing agreement drafted against the revfadp, not a translated eu template.

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 who also looks after three other systems, 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 Switzerland and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Bellinzona, Chur, Montreux, Thun, Sion and Solothurn.

Frequently asked questions