Professional services: seeing which projects actually make money — in minutes, not quarters

This is an illustrative scenario modelled on typical mid-market deployments — not a specific customer.

The situation

Picture a mid-sized management-consulting firm in the Benelux region: around 85 consultants, roughly €12M in annual revenue, a strong reputation built on deep client relationships and pragmatic delivery. From the outside, the firm looks healthy. The pipeline is full, consultants are busy, and revenue keeps climbing.

And yet the partners share a quiet, nagging worry: for all the activity, the firm is less profitable than it should be. People are working flat out, but the money doesn't add up the way the effort suggests it should.

Underneath, three frictions are at work. Billable utilisation is uneven — some consultants are overallocated and heading for burnout, while others sit under-used, and nobody has a live picture of who is where. A handful of engagements quietly lose money: they begin at a fixed price and drift through scope creep into unbilled overruns, but the loss only becomes visible long after the invoice has gone out. And when a partner asks the obvious question — which clients and which types of work are actually most profitable for us? — there is no confident answer, only opinions.

The root cause isn't laziness or bad management. It's that the numbers needed to answer these questions live in four different places that don't talk to each other: hours in the time-tracking tool, tasks and milestones in the project-management system, costs and invoices in finance, and relationships in the CRM. Stitching them together means someone exporting spreadsheets, reconciling them by hand, and producing a view that is already weeks stale by the time it lands.

Why the existing tools fell short

The firm had reporting. What it didn't have was answers.

Each system had its own dashboards, but each told only its own slice of the story. Time-tracking showed hours logged, not whether those hours were profitable. Finance showed margins at the company level, not per project or per client, and never in time to change course. The CRM knew who the clients were but nothing about what each relationship actually earned. Nobody could see the whole board at once.

The conventional fix — commission a proper data-warehouse and semantic-modelling project — was a non-starter. That's a six-month build with an external consultancy, a five- or six-figure cost, and the irony of a consulting firm hiring consultants to tell it how profitable its own consulting is. Off-the-shelf BI tools carried their own tax: modelling layers that famously eat 40–60% of the total tool investment (Gartner's figure for LookML on Looker), recent price rises across the incumbents (Power BI raised prices ~40% in April 2025), and increasingly, per-query AI features metered on top. For a services firm whose data includes client-confidential engagement detail and employee records, there was also a hard line: that data could not simply be shipped off to a US-hosted AI cloud to be queried.

What changed with Adaptrix

The starting point was the part that usually takes months: unifying the data. Adaptrix connected to the firm's existing PostgreSQL-backed systems and auto-discovered a semantic layer — a knowledge graph of the entities that matter (consultants, projects, clients, hours, invoices, costs) and how they relate — built on PostgreSQL and Apache AGE, with high-confidence relationships auto-accepted and the ambiguous ones flagged for a quick human review. No six-month LookML or dbt modelling project; the shared vocabulary the firm had always lacked simply appeared, ready to question.

From there, the work became conversation. Instead of exporting and reconciling, a partner could open DirectorChat and ask, in plain language, "what was our billable utilisation by team last quarter, and where is it trending?" The platform mapped the intent, ran the analysis across the now-joined data, and streamed back an answer plus an interactive artifact — a KPI card and a chart — rather than a static slide someone had to build.

The more valuable questions were the why ones. Asking why project margins vary triggered key-driver root-cause analysis: automated exploratory analysis, group-by segmentation, correlation, and a SHAP key-driver breakdown that ranked what actually moves project profitability — engagement type, seniority mix on the team, degree of scope change, client, project duration — synthesised into a plain-language read rather than a wall of statistics. This is directional key-driver analysis, not a claim of proven causation; but for the first time the partners could see which factors travel with margin leakage instead of guessing.

Three more capabilities did steady work in the background. Forecasting — an ensemble of statistical forecasting models chosen per series, with confidence intervals — projected capacity and utilisation forward, turning "we're too busy to take that on" into a claim the firm could actually check against the numbers. RFM and clustering-based segmentation grouped clients and project types by the value they concentrate, making it obvious where the firm's best economics really sat — often not where intuition assumed. And anomaly detection watched engagements as they ran, flagging the ones trending over budget while there was still time to have the scope conversation, rather than discovering the overrun at close-out.

Crucially, all of this ran on Adaptrix's sovereign EU infrastructure with self-hosted models — EU data residency, GDPR-native, and no per-token or per-query fee for asking another question. Client-confidential data stayed inside the EU and never went to a US cloud or a third-party AI provider, and curiosity carried no marginal cost.

The outcome — thrive, efficiency, profit

The first thing that changed was where people's attention went. Instead of a monthly scramble to assemble a profitability view that was stale on arrival, the partners had a living picture they could interrogate the moment a question occurred to them. The reflex shifted from firefighting after the fact to steering while it still matters — catching a drifting engagement mid-flight, rebalancing an over-stretched team before someone burned out, steering the pipeline toward the work that genuinely paid.

The defensible, directional gains follow from that shift. Reconciliation that used to consume analyst-days each cycle collapses toward minutes, in line with Adaptrix's demonstrated ~4.2× analyst-productivity uplift. A margin-driver analysis that would have been a multi-week manual exercise — if it happened at all — becomes a question answered over a coffee. Fewer projects quietly bleed margin, because the ones heading that way surface early. And the firm can consciously reallocate its most senior, most expensive attention toward its most valuable clients and engagement types, because for the first time it can see clearly where that value concentrates.

These are modelled outcomes for a deployment like this one, not a verified customer result — teams with this shape typically see time-to-answer compress from weeks to minutes and decisions move from gut to grounded. What they don't get is a surprise bill for asking: the cost is a flat annual fee, a fraction of the total cost of ownership of a Tableau, Looker or Palantir stack, with no per-query AI charges bolted on.

Why this pattern generalises

Any firm whose profitability hides across four systems — services, agencies, professional practices — has the same problem in a different costume: plenty of dashboards showing what, almost nothing explaining why, and the answers arriving too late to act on. Unify the data once, then ask it questions in plain language, and the why stops being a quarterly archaeology project and becomes something a partner can settle before lunch.