Value realisation, from the business case to year three.
On time and on budget is necessary. It is not the finish line: the benefits are. Value is not something that arrives after go-live, if anyone is still looking. We plan the benefits before the first package, build them into every package and keep tracking them long after go-live, under one management model, whoever does the work.
The short answer
How do you make sure the benefits are realised?
We treat the benefits as part of the delivery, not as a report at the end. Before the first package we agree the business objectives, measure the baseline and name an owner in your business for each benefit. During delivery every work package is traced to a benefit, which is tracked and reforecast, and changes are weighed by what they do to it. After go-live we keep tracking it, from your own systems wherever we can, review it at agreed points and choose the next package by the value still to be realised. We do not guarantee business results: we answer for the delivery and for showing the value honestly.
- Who it is for
- Consultancies, integrators and companies running a software or AI programme with a business case to meet.
- What you get
- A benefits plan with baselines and owners, every package traced to it, and a value report every period.
- When it starts
- Before the first package, with the business objectives. Already under way? From where the benefits stand today.
- What it is not
- A promise of business results, or a report written once the project has closed.
Continuity of value, from the roadmap to the long run.
Technology is handed over at every stage. One party writes the roadmap and the business case, another designs it, another builds it, and a maintenance contract runs it. Inside each stage, people move on: the architect rolls onto the next project, the vendor rotates the team, the programme director leaves halfway.
Every handover leaks value. The business case survives as a document. The baseline, the owners and the tracking behind it do not.
Value realised against the business case
Tap a number or a layer to see why.
Handover 1, roadmap to design
Intent lost
Why it is lost. The roadmap and the business case are signed off and the strategy team moves on. The reasons behind each choice stay in their workshops and slides, so the design team receives what to build, not the value it is for.
What it costs. The design drifts from the business case, and nobody notices until the benefits fail to show.
With Nessoris. The objectives, the benefits case and the baseline are written into the delivery record before design starts, and every design decision is checked against them.
Handover 2, design to delivery
Context lost
Why it is lost. Designers hand over specifications. The assumptions, constraints and options they rejected rarely travel with them, so the build team rediscovers them, or misses them.
What it costs. Rework and late surprises push the benefits back, and every week of delay is value not realised.
With Nessoris. Assumptions, constraints and rejected options are logged as decisions are made, so the build team starts with them, and each work package is traced to the objective it serves.
Handover 3, delivery to run
Ownership lost
Why it is lost. At go-live the project team disbands and a support contract takes over a system it did not build. The business case belonged to the project, so nobody is left to measure it, and the benefits go untracked.
What it costs. This is where most value is lost: the system runs, but nobody can show what it returns.
With Nessoris. Every benefit has a named owner in your business before go-live. We keep tracking it, from your own systems wherever we can, and review it at agreed points after go-live.
Handover 4, run to evolve
Momentum lost
Why it is lost. People rotate and contracts are re-tendered. Every newcomer ramps up from documents, relearning what the last team knew before they can improve anything.
What it costs. Improvements stall and the benefits level off, so the return of year three never comes.
With Nessoris. A newcomer starts from the record of what was built, decided and learned. Benefits roll up from each package to the programme, and each phase builds the case for the next.
Value realisation pillar
Benefits agreed with a named owner, baselined before work starts, and measured into run.
How it keeps the value. The baseline, the benefit owners and the benefits case travel with the work from stage to stage, and every change is weighed against them, so the value is protected through every handover.
Delivery pillar
Work packages with scope, brief, acceptance test and a stop point.
How it keeps the value. Every package is briefed, accepted and recorded the same way, and traced to the objective it serves. When a team changes, the next one inherits the brief, the acceptance test and the benefit it is for, not a blank page.
Governance pillar
Decision rights, quality gates and authority levels for people and agents.
How it keeps the value. Decisions and benefits are logged with who owns them and why, and reported in one view against the baseline, so value stays visible, and authority does not leave with a person.
Commercial pillar
Priced by certainty, and paid on accepted work.
How it keeps the value. Scope, price and risk are written per package, and the next package is chosen by the value still to be realised, so a handover does not reopen the deal or blur who is accountable.
Intelligence pillar
A running record of decisions, evidence and lessons, with early warning.
How it keeps the value, and compounds. It captures decisions, patterns and lessons as the work happens and makes them available to people and AI agents. Each stage starts from everything learned so far, so the value compounds.
- Intent lost. The design drifts from the business case, and nobody notices until the benefits fail to show.
- Context lost. Rework and late surprises push the benefits back, and every week of delay is value not realised.
- Ownership lost. This is where most value is lost: the system runs, but nobody can show what it returns.
- Momentum lost. Improvements stall and the benefits level off, so the return of year three never comes.
One delivery record runs through every stage. It keeps the intent, the decisions, the context and the benefits case as the work happens, so someone new can pick up where the last person stopped. People, partners and tools can change; the programme does not forget. Bring us in at any stage, and keep the parts you want to own.
Before, during and after go-live.
Value realisation is not a phase at the end. It starts with the business case, runs through every work package and carries on after go-live. Move over a stage or a step, or tap it, to explore.
Before the first package
Agree what the work is for, and measure where you start.
The business objectives the programme serves, the benefits each should bring, the cost of doing nothing and the alternatives weighed.
For each benefit, the problem it solves, its category, how it is measured, in numbers or in words where numbers do not fit, and the business change it needs.
An owner in your business who signs each benefit off, and a second person who checks the figures.
The baseline measured before the first package, so the gain can be shown, not claimed. Targets, the cost of reaching them, and the risks and dependencies, checked against the business case.
During delivery
Build the benefits in, package by package.
Every work package traced to the objective and the benefit it serves.
Planned, forecast and actual for each benefit, every period, starting during delivery, not after it.
When a risk or a change moves a benefit, the forecast moves with it, and you see why.
Every change request is assessed for its impact on budget, schedule and the benefits case, and ranked by what it contributes, so the team can say no to changes the benefits do not need.
The business change each benefit needs, training, process and communication, prepared from design: led by you, your partner, or by us with specialist partners.
After go-live
Keep each benefit owned until it lands, and beyond.
The actual figures from your own finance, ERP or operations systems wherever we can, by export or a connection your team agrees.
For example at 6, 12 and 18 months. A benefit that falls behind is challenged, with its cause and a recovery action.
Each realised benefit stays with its owner and, where it is a saving or a gain, can be written into your budgets, so it is banked, not just reported.
Benefits roll up from each package to the programme, new ones can be added at any time, and the next package is chosen by the value still to be realised.
What worked and what did not goes into the delivery record, so the next phase starts from it.
Value you can see, every period.
Every benefit carries the same record, and you follow it in one view, beside the milestones and the risks of the package that serves it. Benefits roll up from each package to the programme.
- Objective
- The business objective it serves.
- Category
- Financial, customer and stakeholder, productivity, people and culture, safety and compliance, or risk reduction.
- Owner
- Someone in your business who signs it off.
- Checked by
- A second person who validates the figures.
- Baseline and target
- Measured before the first package, and the target with its date.
- Measure and source
- How it is measured, and which of your systems the actual comes from.
- Plan, forecast, actual
- Every period, from delivery until it lands.
Work package 3 · Week 6 of 10
Claims intake automation
Traced to Objective 2 · Faster claims intake
Milestones
Tap a milestone or a risk to see how they connect.
Status and trend
The trend turns before the status does: late test data shows in the delivery signals first.
Benefits against objective 2
PlannedRealised
41% of the target realised so far, against 45% planned.
PlannedRealisedForecast
Now, Q2: 41% realised, against 45% planned.
Focus on the reds
Six stages, each priced to what is known.
The package loop runs inside every work package. The lifecycle is the longer arc around them: six stages, from what exists today to a system that is run and improved, or handed over. The benefits are tracked through every stage, each part is priced to what is known, and the next is chosen by the value still to be realised.
- AssessWhat exists today: the code, the costs and the team.
- SizeThe work cut into packages, each with a price and an acceptance test.
- BuildThe packages delivered under your name.
- HardenSecurity, performance and the evidence your client signs off.
- RunKept live and measured against what was agreed.
- EvolveImproved as the business changes, or handed over.
- Assess and sizeA fixed price for each first step.
- Build and hardenA fixed price where the scope and technology are known. Capped time and materials, with milestone reporting, where they are new.
- Run and evolveA monthly fee, tied to agreed measures.
Delivery that compounds.
Most delivery resets to zero when the project ends. Ours carries forward, so each cycle starts where the last one finished.
Every engagement closes with a delivery record: what was built, decided and learned, written so a successor can act on it.
Typical delivery
Starts from zero every time.
Delivery with Nessoris
Starts from what the last one built.
Questions about value realisation.
Straight answers. Ask us anything else on a call.
Do you guarantee the benefits?
No. Business results depend on decisions, markets and adoption in your business, so we never guarantee them. We answer for the delivery against the acceptance test agreed for each package, and for measuring and reporting the benefits honestly against the baseline, including when they fall short, with the cause and a recovery action.
Who owns each benefit?
Someone in your business, named before the first package, who signs the benefit off. A second person checks the figures. We deliver the change, and track and report the benefit; the business result stays yours. When we work behind a consulting firm, your client gets the value report under your name.
Where do the actual figures come from?
From your own systems wherever we can: finance, ERP, operations or product analytics, by export or a connection your team agrees. Where a figure cannot come from a system, the report says how it was estimated and who confirmed it.
What happens when a benefit falls behind?
It shows in the next report, against plan and forecast, with the cause. At the agreed review its owner and we decide on a recovery action, a change to the plan or stopping, and the next package is chosen by the value still to be realised.
Can you start when a programme is already under way?
Yes. We start by measuring where the benefits stand today, set the baseline from that point and name the owners, then trace the remaining work to the objectives. Bring us in at any stage, and keep the parts you want to own.
More on how it works
- A work package, week by weekThe package loop, from brief to accepted, and what working with us feels like each week.
- Inside the five pillarsWhat each pillar covers and gives you, and how people and AI agents share the work.
- Team and costWhere the team sits, how a steady core forms, and the indicative input cost.
- How it works, in shortThe Unified Management Model™, your method or ours, and the seven commitments.