Why we deliver analytics in fixed, outcome-based phases (and what that protects you from).

Most analytics projects fail commercially before they fail technically. Here is the phased, fixed-scope delivery model we use — assessment to optimisation — and the questions to ask any consultancy before you sign.

Most failed analytics projects did not fail because someone could not write the DAX. They failed commercially: scope drifted, the budget became a meter running on someone else’s clock, the sponsor lost confidence around month four, and the thing quietly stalled with a half-built dashboard nobody trusted. The technology was never the problem.

That is why the delivery model matters as much as the engineering. Here is how we structure analytics work so it produces outcomes on a predictable budget — and how to judge any consultancy’s approach, including ours.

Analytics fails commercially before it fails technically

Open-ended, time-and-materials analytics engagements put every incentive in the wrong place. The consultancy is paid for hours, so more hours is more revenue. The client carries all the risk of overrun. Scope is a conversation, not a commitment. Plenty of good people work this way honestly, but the structure quietly works against the outcome. Structured, outcome-based delivery flips it: fixed scope, defined outcomes, predictable budget, and the delivery risk sitting with the people best placed to manage it — us.

The phased model: assessment to optimisation

We deliver in sequential phases, each with explicit outcomes, a governance checkpoint, and an adoption goal — not one giant implementation you can only judge at the end. This is the backbone of our Analytics Acceleration Programme.

• Assessment. Understand the data estate, the reporting pain, the priority use cases and the readiness gaps. Output: a prioritised roadmap with sequencing, risks and a clear definition of done. A short, fixed phase that de-risks everything after it.
• Foundation. Stand up the governed platform — the pipelines, the lakehouse or warehouse, the security model and the semantic layer — so what follows is built on something solid.
• Pilot delivery. Ship one high-value use case end to end, into real users’ hands. This proves the platform and earns the trust that funds the rest.
• Scaling. Expand across subject areas in iterative releases, each shipping working reporting rather than promising it.
• Optimisation. Tune performance and cost, deepen adoption, and hand over capability so the client’s own team can run and extend the estate.

Each phase tracks against KPIs — adoption, freshness, reporting cycle time, decisions the data now supports — so progress is measured in business value, not story points. And because value ships every phase, the programme can be paused, re-prioritised or stopped with something usable already in production.

Fixed scope vs time-and-materials: who carries the risk

The core commercial question is who carries the risk of the unknown. Time-and-materials places it entirely on the client: flexible, yes, but every surprise is billable. Fixed-scope places it on the consultancy, which is why fixed-scope done well is defined precisely, with:

• clear deliverables and milestones,
• explicit success criteria for each,
• sensible revision limits so “one more tweak” does not become infinite,
• and a straightforward change-control process for genuinely new scope.

That precision is not bureaucracy — it is what makes a fixed price safe for both sides. We package analytics around business outcomes and predictable budgets rather than hourly utilisation because it aligns our incentives with yours: we are paid to deliver the result, so delivering it efficiently is our problem, not your invoice.

How to evaluate a consultancy’s methodology

Whether you work with us or not, press hard on delivery method before you sign. Good questions:

• Governance and escalation. How is the project governed? Who is accountable, how are decisions made, and what is the escalation path when something slips?
• Scope management. How is scope defined and change controlled? Ask to see an actual change-control process, not a reassurance.
• Discovery. What happens in discovery, and what tangible artefact comes out of it?
• Quality assurance. How is quality assured — testing, reconciliation, review — before anything reaches users?
• Evidence of maturity. Ask for the artefacts a mature delivery team already has: project plans, governance templates, a RAID log, and an honest walkthrough of a prior engagement including something that went wrong and how they handled it.

Mature firms answer with specifics and can show you the paperwork. If the answers are vague or the only evidence is a logo wall, that is your signal.

Beyond the project: the operating model

A programme that ends with a great dashboard and no way to sustain it has half-succeeded. Real analytics transformation spans strategy, governance, the operating model, architecture and adoption together. That means executive sponsorship that survives the first setback, a maturity assessment that tells you where you actually are, a prioritised portfolio of use cases rather than a wish list, capability building so the client’s team can carry the work, and continuous value-realisation tracking so the investment keeps proving itself. Optimisation is not the end of the engagement — it is the point at which the client no longer needs us for the day-to-day, which is exactly where a delivery partner should be trying to get you.