Measure whether the value youapproved actually appears.
The business case already carries a baseline and a set of benefit measures. We confirm them before implementation changes the business, then establish the framework that tracks them. We follow them through the build and after go-live. You get evidence of what the investment is returning, and where it is not.
£5,000 a month unless separately scoped. We measure and we bring you the evidence. Acting on it, and the business result itself, stay with your management team.
“It went live. We cannot tell what it returned.”
A build can succeed technically and still leave the board unable to show what the investment returned. The partner delivers what was asked for. It passes testing. It goes live on time.
Later, the question is a different one. Answering it needs evidence that had to be collected before anything changed. Once the new way of working is live, the old performance may no longer be measurable reliably.
The board question is: are we getting the value we approved? This service exists to answer it with evidence.
The baseline was not confirmed before the change. Once the new system is live, the old performance may no longer be measurable reliably.
The benefit measures were never instrumented. Nobody asked for the data during the build, so the evidence to show the return does not exist.
Technical decisions moved the commercial case. Reasonable choices, made one at a time, can add up to something different from what was approved.
Adoption or process change was weaker than assumed. The technology works. The way of working did not move as far as the case expected.
The evidence is fragmented. Leadership sees activity, but cannot connect it to a business result.
Not every programme meets all of these. Any one of them can make the return harder to evidence reliably.
It starts before the build, not after it.
The baseline comes out of AI Business Case & Process Redesign and is approved with the case. We confirm it before implementation changes anything, then track the benefit measures through the build and after go-live.
A baseline agreed before the business changes is evidence. One reconstructed afterwards is an argument. That is why this service begins at board approval rather than at handover, and why the last two bands overlap.
Through the build, and after it.
One service, because the commercial thinking should not disappear while the technology is being built.
Is the expected value still intact as the solution is designed and built?
We start at the approved baseline, before implementation changes the business. We do not manage the technical programme. Your partner remains fully responsible for delivery. We check the commercial position at four defined points and keep the benefit measures in view.
Are the expected benefits appearing against the approved baseline?
The question changes. We measure what actually happened against the case. We identify where value is not appearing, and bring the evidence to your leadership team so they can decide what to do.
Four checkpoints. Not open-ended project management.
Defined points, not a standing seat in every meeting. The checkpoints keep the scope bounded and avoid duplicating your partner’s project-management role.
Baseline and measures confirmed
Are the approved baseline, the expected benefits, the assumptions behind them and the benefit measures clear before implementation changes the business?
Mobilisation
Has your technology partner understood the redesigned process, the commercial case, the controls and the measurement requirements?
Design integrity
Are technical decisions changing the commercial assumptions or the expected benefits the board approved?
Measurement readiness
Will the data and the measurement mechanisms be available when the solution goes live? Without them, later evidence is weaker and may be impossible to establish reliably.
Three kinds of evidence, joined up.
The point is not another dashboard. It is the chain between the three: what the technology did, what changed in the work, and what that was worth.
Technology and AI activity
Usage, activity, adoption, and relevant model or agent performance. Your technology partner owns technical performance. We use the evidence, we do not own it.
Operational performance
Cycle time, throughput, quality, exceptions, how often a person still has to step in, and capacity.
Business performance
Cost, capacity, revenue, margin, risk, or whichever benefit measures the approved case defined.
Technology activity → operational effect → business outcome. Measured against the baseline agreed before the business changed.
Not every engagement measures all of these. The measures are the ones the approved business case defined, and no others are added without agreement.
Your management team owns the rest: the business process change, adoption, resourcing, management action, and the business result itself.
We are not a software company. The tracking framework is a measurement method and a commercial data model. It is set up where practical in the systems that already hold the evidence. We do not sell software, licences or implementation. The economic assumptions belong to the approved business case, not to us. Where they need to change, that is a decision for your board.
Governance, risk, privacy, security and responsible-AI requirements may be carried into the tracking framework where they affect the approved business case. AI Governance & Assurance remains a separate cross-cutting capability, not another stage in the service progression.
This is where the evidence can become measured.
Everything we tell you carries an evidence status. In the Formalus service ladder, three of the four can be reached before anything is built. The fourth cannot.
The business case is modelled until actual results are compared with the baseline. Only then is the benefit measured rather than expected.
A commercial measurement loop that runs alongside the build.
This is not a delivery lifecycle. It follows the commercial case while your technology partner delivers the technical solution.
Through implementation · protecting what was approved
After go-live · showing what it returned
Back to the start — the evidence informs the next decision, and the loop runs again.
Evidence of what the investment is returning.
A benefit dashboard
The agreed benefit measures in one place, tracked against the approved baseline.
Variance analysis
Expected against actual, in business terms rather than usage statistics.
Evidence of realised results
What has actually been observed against the baseline, and what remains modelled.
Executive value reviews
A working session with the relevant leadership team. A decision session, not a status update.
Benefit-capture actions
Where value is not appearing, what could be done about it, and what each option depends on. Your management team decides what to do.
Remeasurement where agreed
Post-implementation review, and remeasurement at six and twelve months where that is agreed in scope.
The review cadence is set in scope rather than fixed here. £5,000 a month unless separately scoped.
This is not a second project manager.
Not technical programme or project management. Not development or sprint management. Not detailed solution architecture. Not tenant administration. Not technical testing or security implementation. Not support or managed technical services.
Nor does £5,000 a month buy unlimited access to consultants. It buys four defined checkpoints, a measurement model, a tracking framework, executive value reviews and the evidence behind them.
Your technology partner remains responsible for technical delivery, support and operation.
Formalus. The integrity of the value model, the measurement design, the evidence, identifying variance, the commercial review, and decision support.
Your management team. Changing the business, allocating resources, acting on the evidence, and achieving the business result.
Your technology partner. Technical architecture, build, configuration, integration, security, deployment and technical operation.
We measure and bring you the evidence. Your management team owns the business result.
Confirm the baseline before implementation changes the business.
AI Business Case & Process Redesign establishes the baseline and the benefit measures, and your board approves them with the case. We confirm them before anything changes, then follow the benefits through the build and after go-live. A baseline agreed beforehand is evidence. One reconstructed afterwards is an argument.
Book a complimentary AI Opportunity Assessment