Inference Public

Public sector

Build around the service
and the people behind it.

AWS infrastructure and software engineering for government departments, agencies and local public services, working within real organisational constraints.

Central government and agencies

Departmental services
at national scale.

Work directly with a department or agency, or as a specialist alongside its existing delivery partner. Earlier central-government work includes enterprise architecture within a complex transformation programme. See anonymised experience

Multidisciplinary digital team reviewing a service map in a government office.

Government departments

Multidisciplinary teams, policy-to-delivery services and the platforms departments share across programmes.

Team leader and caseworker reviewing work on a large government operations floor.

Departments and agencies at scale

High-volume casework, legacy estates and services that cannot pause while they are modernised.

Evidence for assessment and assurance

Plan the delivery so that it produces the records departments are assessed against: the Service Standard, the Technology Code of Practice, Secure by Design and the Cyber Assessment Framework. Architecture decisions, pipeline evidence, recovery tests and runbooks then support an assessment instead of being assembled for it.

Local and regional services

Councils, combined authorities
and the services around them.

Council officer helping residents at a digitally equipped civic service desk.

Councils and combined authorities

Resident services, casework and the systems behind the front desk.

Transport staff checking digital information at a regional bus interchange.

Transport

Operational systems, passenger information and the integrations between operators.

Engineers checking digital information beside a river sluice and monitoring equipment.

Environment and resilience

Monitoring, field data and services that must keep running through an incident.

Lecturer and adult students discussing an engineering prototype alongside digital design tools.

Education and skills

Learning platforms, student services and the data that connects them.

Highways inspectors recording a bridge inspection on a rugged tablet beside a rural road.

Roads and highways

Inspections, asset records and mobile field services.

Librarian helping an older visitor use a public-access computer.

Libraries and digital inclusion

Public-access technology and support for people getting online.

Healthcare colleagues reviewing information together on a tablet in a community health centre.

Our sister R&D arm

Inference Clinical

Researching safer, more connected healthcare and community services.

Inference Clinical is our sister healthcare and community technology R&D arm, exploring how software, AI and better governance can improve coordination between organisations, professionals and the people they serve.

Its work includes SafeMesh, an emerging infrastructure platform designed to make responsibility visible and accountable as care moves between NHS providers, local services, private healthcare and community settings.

By combining applied research, clinical safety engineering and distributed systems expertise, Inference Clinical is developing new approaches to longstanding problems in healthcare: fragmented pathways, uncertain handovers and gaps in accountability.

Inference Public and Inference Clinical are both part of Inference Clinical Ltd.

Explore Inference Clinical →

Keep the service in view

Understand the tasks people depend on, the consequences of an outage and the constraints under which staff operate. Use those needs to shape engineering priorities.

Work with the estate you have

Map legacy systems, data, interfaces and supplier responsibilities before deciding how to change them. Plan transitions that the organisation can carry out.

Make responsibilities explicit

Agree ownership across delivery teams, operational teams and suppliers. Record the decisions and acceptance responsibilities at each interface.

Make costs and trade-offs visible

Explain the build scope, ongoing operating costs and consequences of architectural choices so that the organisation can make informed decisions.

Build internal capability

Work with the client’s engineers, document decisions and practise the operational procedures together. Plan knowledge transfer throughout delivery.

Connect transformation to a service improvement

Choose a concrete outcome, such as making a change easier to release or a priority service easier to recover. Agree how that outcome will be demonstrated.

Adopt AI where it improves the service

Start from a task that staff or the public find slow or difficult. Test whether AI improves it against simpler alternatives, and stop when the evidence does not support it.

Keep AI accountable

Name an owner for each AI-assisted decision, keep people involved where the outcome matters and publish transparency records where required. Work within the government AI Playbook and your own information governance.

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss a project