Your French entity reports in Power BI. Here is how to judge who builds it.

Ask them five questions. Where would they place a calculation rule shared by several reports: the right answer is "in the model, once". How do they handle a date table. What do they do when a report takes thirty seconds to open. How do they hand the report over to your teams. And what would they do if you only needed a single report. A consultant who answers all five precisely knows the trade; one who answers with a sales pitch will sell you a bigger project.

Three layers, and the third makes the difference. Power Query and the M language to prepare the data. Star-schema modelling and DAX so that measures are right and fast. And the design of the report itself: visual hierarchy, choice of charts, row-level security. Many people master the first two; the third decides whether your teams use the report or go back to Excel.

For a targeted report, an experienced consultant is enough and costs less. For a platform shared between several departments, a team brings what an individual cannot guarantee: continuity if someone leaves, peer review of the work, and the capacity to absorb a peak. We are eleven, and we designed the structure for exactly that reason.

It depends on the scope far more than on the number of reports. Our standard projects run from three to ten days: sources connected, semantic model, reports and training. We bill by the half hour, on the time actually spent, with the detail on every invoice. The scoping workshop that precedes the quote is free.

Both, depending on what serves the project. Most of the work happens on the data, so remotely. The moments that genuinely gain from being face to face are the scoping workshop, the arbitration of business rules and the training of your teams. We are in Saint-Priest, near Lyon, and we work in English as well as in French. We travel across the Auvergne-Rhône-Alpes region and to French-speaking Switzerland.