Introducing Our Delivery Lifecycle

We have published the delivery lifecycle we run every engagement through. It is now on our capabilities page, and it is the same four stages whether the work is a field services rollout, a customer portal, or a platform modernisation that touches everything.

None of this is new to the teams who have been working this way for years. What is new is that it is written down, in public, in the same words we use internally — so a prospective client can see how we work before they talk to us, and so nobody on either side has to guess what happens next.

The four stages

Discover — understand business goals, challenges, and opportunities. This is where we establish what the organisation is actually trying to achieve, as distinct from the solution someone has already decided on.

Design — develop the strategy, architecture, and implementation roadmap. Sequencing matters as much as architecture here. The order in which capability arrives decides whether people can absorb it.

Deliver — build, implement, and integrate modern digital solutions. Work goes live in increments that stand on their own, rather than in one release that carries every risk in the programme.

Evolve — optimise, support, and continuously improve over time.

Why the fourth stage is the point

Most delivery frameworks are three stages with a support contract bolted to the end. Ours is a loop, and that is deliberate.

The pattern we see repeatedly is a programme that hits its go-live date, gets signed off, and then slowly degrades — not because the software was wrong, but because nothing was funded to keep it matched to a business that kept changing. Reports drift out of use. Workarounds accumulate. Two years later the modernisation itself is the legacy system.

Treating Evolve as a stage rather than an afterthought changes what gets budgeted, what gets measured, and who stays accountable after the launch. It is also the stage that produces the next Discover, which is why the diagram is a ring and not a line.

What this changes for clients

Practically, three things. Every proposal we write now maps to these stages, so the shape of the work is legible before it starts. Every engagement has a named owner per stage. And the handover conversation happens during Design, not in the last fortnight before go-live.

Where to start

The lifecycle sits alongside our capabilities, and each stage links through to the practices behind it. If you are weighing up a programme and want a second opinion on how it is sequenced, that is a conversation worth having early — Discover is cheap, and re-sequencing after Deliver is not.