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

Power BI is rarely the thing that is broken in a Kortrijk reporting estate. What is broken is that the business logic lives in twelve separate files, each maintained by whoever needed it first.

Kortrijk is big enough to host serious reporting estates and small enough that one or two people usually hold all the knowledge. With around 80,000 people and an economy built on textiles, fashion and luxury goods, industrial machinery and engineering, and logistics and freight, 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 Kortrijk 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 Belgian Data Protection Act of 2018.

Why reporting breaks in Kortrijk specifically

Generic advice about Power BI is not very useful, because the failure modes follow the industry rather than the tool. Kortrijk's economy is weighted towards textiles, fashion and luxury goods, industrial machinery and engineering, and logistics and freight, with textile and interior products manufacturing and machinery and automation engineering 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.

Textiles, fashion and luxury goods

Short product lifecycles with size and colour variants multiplying SKU counts, plus wholesale, retail and online channels running on different calendars.

The characteristic failure is this: reporting at style level only, which hides that one size curve or colourway is carrying all the markdown risk. 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 option-grain sales and stock model with season and markdown dimensions, which is where buying and merchandising decisions are actually made.

Typical source systems: PLM, ERP, wholesale order management, retail EPOS and ecommerce platform. Supply-chain due diligence and product traceability obligations are expanding, and the underlying supplier data is rarely reportable today.

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.

Construction and real estate

Project cost and progress data with subcontractor valuations, variations and retentions, plus asset and tenancy data on the property side. Project reporting runs monthly on manually consolidated spreadsheets, so a problem contract is identified two months after it turned.

We would usually begin with a project cost and valuation model with variations and retentions explicit, so margin erosion is visible while the project is live. Source systems to expect: project costing systems, ERP, BIM and design systems, site progress apps and property management systems.

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

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.

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 Kortrijk business in textiles, fashion and luxury goods, 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. PLM, ERP and wholesale order management 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 textiles, fashion and luxury goods the argument that has to be settled first is normally sell-through by option, where option-level analysis requires a size and colour hierarchy that many models collapse too early. 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. the Kortrijk campuses of KU Leuven and Howest supply engineering and design graduates with good local retention.

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 Belgium, 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 Kortrijk 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 Kortrijk, 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 Kortrijk versus engaging a consultancy

This is a fair question and the honest answer is sometimes "hire". the Kortrijk campuses of KU Leuven and Howest supply engineering and design graduates with good local retention. Locally, a mid-level analytics engineer costs roughly €55,000 to €85,000, with Brussels at the upper end. An experienced external consultant runs at roughly €800 to €1,350 per day.

Where a Kortrijk client has told us they intend to build an internal team, we design for it from the start. Teams here expect to own what we build, and we design for that explicitly: scriptable models, conventional naming, documentation in their wiki, and a measure dictionary that survives our departure. Several clients have gone on to need us only for quarterly review, which is a perfectly good outcome.

Data residency and compliance for Kortrijk organisations

Most Belgian deployments land in West Europe, which is physically in the Netherlands, or in France Central. Microsoft has announced a Belgian datacentre region, so check current availability before committing to an architecture that assumes in-country residency, and in the meantime document the EU-but-not-Belgian position for your data protection officer. In practice, Kortrijk deployments normally use West Europe (Netherlands), with France Central (Paris) as the paired region.

Regulatory oversight relevant to analytics comes from the Data Protection Authority (APD / GBA) under the EU GDPR and the Belgian Data Protection Act of 2018, plus the sector bodies that matter here: FSMA for financial markets conduct supervision, National Bank of Belgium for prudential supervision and statistical reporting and APD / GBA for data protection enforcement.

• Belgium's federal structure means some reporting obligations sit with the regions (Flanders, Wallonia and Brussels) rather than nationally, which multiplies the datasets a single organisation must produce.
• Language legislation affects employee-facing systems: reporting used in employment contexts may need to be available in the language of the region where staff are employed.
• As the host of the EU institutions, Brussels has an unusual concentration of organisations working to EU-level reporting rules ahead of national implementation.

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

How we deliver into Kortrijk

• Bilingual or trilingual stakeholder groups are the norm: plan for Dutch, French and English in the same programme.
• Works council and trade union consultation applies to systems that can monitor individual performance, similar to Germany.
• Many Belgian organisations operate as the European hub of a larger group, so local analytics has to reconcile with group reporting standards.

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

How a Kortrijk organisation actually buys this

Most consultancy pages stop at what the work is and leave the buying process to email. Multilingual and split between local and group decision-making, with a federal structure that multiplies the authorities involved. Brussels adds a layer of organisations procuring under EU institutional rules.

In the private sector: Many Belgian organisations are the European hub of a larger group, so a local sponsor agrees the requirement and a group procurement function runs the contracting. Documentation frequently has to exist in Dutch and French as well as English, and works council consultation applies to anything that could monitor individual performance.

In the public sector: Federal bodies publish on the Belgian e-Procurement platform, with above-threshold notices on TED. Flanders, Wallonia and the Brussels-Capital Region each run their own procurement for regional competences. The EU institutions in Brussels procure through their own calls and framework contracts, which are a separate discipline with longer timescales and heavier formal requirements.

Documents you should expect to request, and that any supplier worth shortlisting will have ready, are kbo / bce enterprise number and registration extract, attestations for social security (onss / rsz) and tax, routinely requested in public procurement, insurance certificates including professional indemnity and data processing agreement under eu 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 Belgium and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Liège, Sint-Niklaas, La Louvière, Genk, Roeselare and Mouscron.

Frequently asked questions