What Anthropic's GOV.UK partnership means for public sector suppliers

In January 2026, DSIT selected Anthropic to build an AI-powered assistant for GOV.UK. The first use case is employment: helping people find work, access training, and figure out what support they're eligible for.

Worth paying attention to how this thing actually works. It remembers context between sessions, walks people through multi-step processes, and gives tailored advice based on individual circumstances. Users can opt out and control their data at any point. This builds on a Memorandum of Understanding the two parties signed back in February 2025.

The bit that caught our eye: Anthropic's engineers are embedding directly inside the Government Digital Service team. They're not delivering from a distance. And the stated goal is for government to be able to run the system on its own once the engagement ends.

What this signals for suppliers

If you build software for government, this tells you where things are heading.

DSIT is using what they call "Scan, Pilot, Scale" for procurement. Test something small, learn from it, then decide whether to roll it out wider. That's good for smaller agencies who can actually ship working software quickly. Less good for the kind of supplier that produces a 200-page requirements document before writing any code.

The technical expectations are shifting too. Government is going to want systems that hold state across sessions, handle personal data properly under UK law, and plug into existing government services. Building a simple FAQ chatbot won't cut it.

And then there's the embedded model. Anthropic's people are sitting inside GDS, working alongside civil servants. We think this will become more common. Government bringing vendor engineers onto the team directly, rather than managing them at arm's length through a contract.

So what do you actually do with this

You don't need to add AI to everything you build. But you should understand where an agentic approach genuinely helps: navigating complex eligibility rules, personalising guidance across services, keeping context so people aren't repeating themselves every time they come back.

The projects that follow from this partnership will need teams comfortable with government platforms and serious about data governance. Teams that can ship in short cycles rather than long procurement arcs. We've worked this way for years. If you haven't, now's a reasonable time to start.