Digital Services Procurement

Digital services procurement encompasses the sourcing of people-delivered technology services: the teams and individuals who design, build, test, and maintain digital systems for public sector organisations. It is distinct from purchasing software products or cloud infrastructure. Across Europe, public bodies spend billions annually on digital services as they modernise legacy systems, build citizen-facing platforms, and transform internal operations. Getting digital services procurement right, in terms of specification, market engagement, and commercial model, is critical to delivery success.

What is digital services procurement?

Digital services procurement includes a broad range of services: agile software development, user experience research and design, data engineering and analytics, cybersecurity consultancy, enterprise architecture, digital transformation programme management, and platform engineering. These services are typically provided by specialist firms or individual contractors rather than commodity suppliers.

In the UK, the primary framework routes are the Digital Outcomes and Specialists (DOS) framework (and its successor DTO) and, for some service types, the G-Cloud framework. EU member states procure digital services under Directive 2014/24/EU, using open or restricted procedures for high-value contracts, or dynamic purchasing systems for lower-value or more frequent needs. Some EU national central purchasing bodies operate their own digital services frameworks.

For complex or novel digital requirements where the solution is not fully defined, buyers may use competitive dialogue or innovation partnerships under Directive 2014/24/EU. These procedures allow structured engagement with the market to refine requirements before final bids are submitted, which is particularly appropriate when buying outcomes rather than defined deliverables.

The technology code of practice sets the UK government's expectations for digital services delivery, including requirements to follow open standards, design for interoperability, and make source code open by default. Buyers should embed these expectations in their specifications.

Why it matters for bidders

Digital services suppliers compete in a market where the procurement process itself signals the buyer's maturity and expectations. Well-run digital services procurements specify outcomes rather than inputs, use agile commercial models (time-and-materials or capped-and-managed), and include provisions for iterative delivery rather than waterfall fixed-price contracts.

Suppliers should understand the buyer's preferred procurement route and tailor their approach accordingly. For DOS mini-competitions, written responses must demonstrate team capability, delivery methodology, and relevant experience within strict word limits. For open procedure contracts, full technical bids are required. In both cases, demonstrating open standards in procurement compliance and interoperability requirements adherence is increasingly expected.

Security capability is a consistent selection requirement. Cyber Essentials (procurement requirement) certification is baseline in the UK; equivalent national certifications apply across EU member states.

Example

A Dutch municipality needs a team to redesign its online permit application service. It runs an open procedure under Directive 2014/24/EU, specifying a multidisciplinary team covering UX design, front-end development, and user research. The specification requires delivery using agile methods, open source code published on a public repository, and compliance with Dutch government API standards and accessibility requirements.

Frequently Asked Questions

How should a buyer specify digital services to avoid lock-in?

Buyers should specify outcomes (the service to be delivered and the user needs it must meet) rather than prescribing how the team should work or what technologies to use. Ownership of code, data, and documentation should rest with the contracting authority. Exit clauses should require a knowledge transfer period and provision of all source code and deployment scripts.

What commercial model works best for digital services?

For discovery and alpha phases, time-and-materials within a capped budget is typical. For larger build phases, buyers can use either time-and-materials (more flexible, higher cost risk) or outcome-based pricing with milestone payments (more defined scope, risk of waterfall creep). Fixed-price contracts are generally unsuitable for services requiring iterative delivery.

Is IR35 relevant for digital services procurement in the UK?

IR35 (off-payroll working rules) applies when public sector bodies engage individual contractors through intermediary companies. Since April 2017, UK public sector organisations are responsible for determining a contractor's employment status for tax purposes. This affects how individual specialist engagements through DOS are structured and priced, and buyers should confirm their IR35 status determination process before running a specialist procurement.