Quick answer
The NHS App was built by multiple suppliers across seven capability layers. It has become the front door for accessing NHS services, and NHS Login is the security layer that makes it work at a national scale. Using public procurement notices that explicitly reference the NHS App and NHS Login, we can identify over £200m in contract value committed between 2018 and 2025. This project wasn’t delivered by a single supplier or under a single contract. The NHS App relied on different suppliers to provide leadership, core engineering, service operations, identity and verification, comms, and continuous improvement.
For suppliers selling into government, it’s a clear case study: winning isn’t just about showing up when a tender drops, it’s about tracking early signals, mapping the supplier chain, and engaging early enough to shape what gets bought.
Why the government is investing in a digital front door in healthcare
The NHS App isn’t just “an app project”. It is the front door for how citizens access services, and it is the delivery vehicle for system-wide change.
NHS England framed the NHS App as a digital front door as far back as the public rollout in 2019. More recently, the government’s 10 Year Health Plan messaging (July 2025) positioned the app as the place patients manage appointments, get advice, and interact with services, with AI-enabled support and wider self-service pathways. NHS England also set a goal of making the app an accessible front door to the whole NHS by 2028. Actionable opportunity areas this creates for suppliers include:
- Appointment, referral, and waiting list workflow products that reduce admin load and no-shows
- Identity, access, verification, and fraud controls that scale safely with adoption
- Messaging and outbound communications at a national scale, including multi-channel journeys
- Research, UX, and navigation work that reduces failure demand and improves completion
Early buying signals before the big contracts appeared
Suppliers who tracked early NHS App signals had a head start on the market. The intent was public before the major procurement value appeared.
These are the signals suppliers can use to create a strategy before notices hit the market.
The NHS App supplier chain broken down into seven capability stages.
The NHS and wider public sector are investing in large, joined-up digital programmes to cut duplication, standardise processes, and improve efficiency. The NHS App is a strong case study for suppliers because it shows what the government actually buys to launch and run a national service.
It is not a single contract, and it is not a single supplier. It is a set of capability layers, from leadership and core engineering to operations, identity and verification, comms, UX, and tooling. Understanding the supply chain helps you identify where demand sits today, where it will re-procure next, and where you can build a pipeline early.
1. Programme leadership and delivery management
This stage is about buying the leadership and control to run a national product and coordinate delivery across teams and suppliers.
- NHS App Head of Product: Senior product leadership to set the NHS App’s vision, priorities, roadmap, and delivery approach in the early build phase. | £296k | Supplier not disclosed | Award date: 22/11/2018
- Wayfinder Programme Team: Programme oversight and coordination for the Wayfinder workstream, keeping delivery on track across teams, suppliers, and stakeholders. | £320k | Mason Advisory Limited | Award date: 03/01/2023
2. Core build, engineering, and platform delivery
This is the backbone: the big build contracts, live development, DevOps delivery, and platform upgrades.
- NHS App Development (core build and maintenance): Core contract for building, expanding, and maintaining the NHS App, including ongoing feature delivery and live service development. | £78.6m (includes uplift) | IBM UK | Award date: 30/06/2022
- Live Development and DevOps Delivery (prj_3372): Agile delivery and DevOps capability to support live development, release management, and continuous improvement of the NHS App. | £13.0m | Kainos Software Limited | Award date: 09/12/2019
- NHS Login Transform 2: Major upgrade programme to improve NHS Login’s performance and resilience, and extend the platform for future demand.| £16.25m | BJSS Limited | Award date: 23/06/2025
3. Citizen support and service management
Once the app is citizen-facing at scale, procurement shifts toward support operations, service continuity, and run-and-improve delivery.
- NHS.UK Support Delivery (covers NHS App and NHS.UK): Ongoing support and enhancement delivery for NHS.UK and the NHS App, focused on stability, improvements, and operational responsiveness.| £37.5m | BJSS Limited | Award date: 01/01/2025
- NHS App Contact Centre Services: Citizen-facing contact centre to handle NHS App user support, service queries, and resolution of access or usage issues. | £7.0m | Teleperformance Limited | Award date: 07/05/2021
4. Identity, verification, and fraud controls
This stage secures access. As adoption grows, the NHS buys stronger verification and identity controls.
- Identity Check and Validation Solution: Identity verification capability to confirm users securely during onboarding, reducing fraud risk and enabling trusted access. (NHS Login) | £3.87m | iProov Limited | Award date: 02/02/2024
- NHS Login Transform: Platform improvement work to stabilise and scale NHS Login, strengthening how authentication and access services run day-to-day. | £7.6m | Accenture (UK) | Award date: 03/05/2022
5. UX, navigation, and research
This stage keeps the product usable. It includes navigation, service design, and user research that drives adoption and reduces failure demand.
6. Channels and communications
This stage covers how the NHS reaches people: outbound campaigns, authentication codes, and channel capacity that supports millions of users.
7. Tooling, environments, and development
This is the “keep shipping safely” layer. It includes test environments, design tooling, and software supply-chain hygiene.
What the NHS App supplier chain means for government suppliers
When you sell into government digital programmes, the biggest advantage is not reacting faster to tenders; it’s turning signals into a plan.
1. Create a strategy earlier than the market.
Procurement notices arrive late. By the time a tender is published, the buyer has usually already decided what they are building, how they will deliver it, and what “good” looks like. The NHS App is a clear example: the direction, scope, and delivery model were set before the major contracts came in.
What to do:
- Track early signals like policy announcements, programme updates, product roadmaps, and platform decisions.
- Turn those signals into a point of view on where you can win: build, run, identity and verification, comms, UX, or tooling.
- Use that focus to decide which buyers to target, which partners you need, and what proof you must build before the tender drops.
- Show up early with a clear outcome-led offer so you can influence requirements, not just respond to them.
2. Build a pipeline using buyer and incumbent supplier intelligence
Large programmes leave a trail. You can see who is already embedded, what they are responsible for, and which parts of the work are likely to come back to market next. If you treat that information as pipeline fuel, you stop guessing and start targeting with intent.
What to do:
- Map the buyer’s delivery chain: the prime suppliers, specialist partners, and the operational teams keeping services live.
- Identify which layers are sticky (long-term build and run) and which are re-procured often (operations, identity, comms, UX, tooling).
- Decide where you will compete and where you will partner. Build a partner plan around the suppliers already delivering the core work.
- Build your pipeline from renewals and adjacent workstreams, not just new tenders. Track what expires, what gets extended, and what keeps getting bought in smaller chunks.
3. Pre-engage with buyers to shape the tender
If you wait for the tender, you inherit someone else’s definition of the problem. Pre-engagement is how you influence what gets bought, how it is evaluated, and what evidence the buyer values. On programmes like the NHS App, that early shaping often matters more than the final written bid.
What to do:
- Engage while the buyer is still forming requirements: share a clear point of view on outcomes, risks, and what delivery needs to look like.
- Bring practical evidence early: comparable delivery, credible resourcing, transition approach, and how you will keep the service stable while it changes.
- Help the buyer write a better tender by suggesting measurable outcomes, realistic timelines, and evaluation criteria that reflect what will actually make the service succeed.
- Stay close throughout the market engagement and discovery phases so you are present when scope shifts and decisions are locked in.
Next steps
Use this supplier trail to spark inspiration and begin to turn buyer signals into a pipeline.
- Create your plan: You can use Stotles to track early signals and decide which layer you want to win in (build, run, identity, comms, UX, tooling).
- Build pipeline: Map incumbents, partners, and renewal cycles in Stotles so you target the work that comes back to market, not just new tenders.
- Pre-engage: Use what you learn to approach buyers early with a clear point of view on outcomes, risks, and what “good” looks like, before requirements get locked in.
If you want a taste of Stotles, here is a guest pass for NHS England that showcases awards, expiries, and pipeline signals to help you start your journey. If you want to explore the full supplier chain, then sign up for a free account.
Guest pass link
