Skip to content
Contact

Arrange a technical review

A 45-minute working session with an engineer who has shipped this before. We will tell you what we would build, in what order, and roughly what it costs, or that you do not need us, which happens several times a quarter.

Enquiry

We reply within one working day
Before you write

Before you write

Including prices, because withholding them wastes everyone's afternoon.

We design and build the data layer that reporting and AI sit on: semantic models in Power BI, lakehouses and warehouses in Microsoft Fabric and Azure, the pipelines that feed them, and the governance that keeps them trustworthy. We also migrate legacy BI estates onto the Microsoft stack and operate platforms as a managed service. We are a consultancy, not a software vendor. There is no product you have to buy with us.

With a short paid discovery, typically two to three weeks, producing an architecture recommendation, a delivery plan and a cost estimate based on your actual data rather than an average. You keep that output whether or not you continue. We avoid open-ended time and materials for first engagements because neither side can judge value without a defined scope.

Discovery is a fixed fee in the low five figures. Build work is priced by project size rather than by report count: a small project (one or two sources, one business area, three to five reports) runs £15,000 to £40,000 and takes three to six weeks. A medium one, with three to six sources, several business areas and real governance, runs £40,000 to £120,000 over six to twelve weeks. A large platform with ERP and CRM integration, a dedicated data layer and formal governance runs £120,000 to £400,000+ across three to six months. The same figures apply in euro and Swiss francs in our other markets. Managed service starts at £3,000 a month for a small estate. We give a written estimate range before discovery and a fixed price after it.

The United Kingdom, Ireland, Germany, Switzerland and Belgium. Delivery is predominantly remote with on-site workshops at the points where being in the room matters, definition workshops, go-live and stakeholder sessions. We work in English and German, and we handle Dutch and French-language stakeholder sessions through our network where needed.

Work with them, in almost every case. The most common pattern is an internal analytics team that owns business engagement, with us covering platform engineering, architecture and the work that needs specialist depth. We build in the open, document as we go, and run enablement during delivery rather than in a final week.

We work exclusively on the Microsoft data stack and maintain certification across Power BI, Fabric and Azure data engineering. We are deliberately independent on licensing: we have no incentive to recommend a larger capacity than you need, and we will tell you when a cheaper licensing model fits your reader population.

For a well-defined first use case with accessible sources, six to eight weeks from kick-off to a production report is realistic. The variable is almost never build speed. It is source access, data quality and how long it takes your organisation to agree a KPI definition. We front-load both so the surprises happen in week two rather than week ten.

Say so on the call. A fair share of the conversations we have end with a recommendation that is not a project: a licensing change, a process fix, a report retirement, or hiring one internal analyst instead of engaging a consultancy. We would rather be the people who told you that than the people who sold you a platform.