Digital service delivery through alpha, beta and live

Add engineering capacity around the service phase

Government digital services need software delivery that follows the evidence about users and the service as a whole. The work required in alpha is different from the work needed to operate a live application.

We work alongside product owners, service managers, researchers, designers and technical specialists. We agree the contribution needed from our team, the decisions it supports and how it fits your governance and procurement arrangements. The engagement can cover a defined stage or an agreed part of a wider delivery programme.

Alpha: investigate the difficult assumptions

During alpha, prototypes and technical exploration help test whether a proposed approach is feasible and useful. We can investigate integrations, data availability, architecture options and other constraints that could change the delivery decision.

The aim is to produce evidence and reduce uncertainty. Prototype code may need to be replaced or substantially developed before production; we make that distinction clear when agreeing scope and evaluating results.

Beta: build and test the service people will use

As a service moves towards production, the work includes implementing user journeys, connecting systems and checking the behaviour that matters. We collaborate with your team on prioritisation, testing, accessibility and release planning.

We help record technical decisions, risks and the evidence of delivery for your team’s review. We can support preparation for the relevant service assessment, but the assessment decision belongs to the responsible assessors; an engineering engagement does not guarantee a pass.

Live: establish ownership and keep improving

A live service needs named responsibility for maintenance, incidents, dependencies and changes. We agree coverage, escalation, release decisions and how user feedback reaches the backlog. Technical improvements are considered alongside service priorities, rather than postponing maintenance until a failure occurs.

Our support and maintenance service explains how we establish those operational arrangements. For a specific shortfall within an existing delivery team, see team augmentation.

Experience with the GOV.UK Trade Tariff

On the GOV.UK Trade Tariff, we worked with HMRC and GDS colleagues including the product owner, service manager, technical architect and designers. During alpha we developed a prototype to help stakeholders evaluate the approach; beta work prioritised user needs for the production service.

The wider project involved replacing a complex legacy application, migrating data and continuing support after launch. That experience informs the questions we ask about dependencies, assurance and ownership at each stage.

What should an initial discussion cover?

Share the current phase, available research, delivery team and any assessment or release milestones. We can establish the technical work required, what depends on other suppliers and which decisions need further investigation before estimating the engagement.