UK procurement routes for productivity software suppliers

What to take away

How Crown Commercial Service became the Government Commercial Agency

Crown Commercial Service was the UK government's central buying organisation. It negotiated frameworks, ran the Digital Marketplace and published spend data. Its remit covered everything from laptops to legal services.

Crown Commercial Service is now known as the Government Commercial Agency (GCA). For suppliers, the important point is to check the current agreement documents and identify the contracting authority for the framework or contract in question.

Existing agreements remain governed by their published terms. A change in organisational name does not itself change an agreement's terms or call-off process, so suppliers and buyers should check the current agreement documents for the relevant guidance and contact details.

The GCA is a source of guidance on its frameworks and routes to market. Buyers should check the relevant agreement's customer guide and current documents, including who to contact with clarification questions.

The Crown Commercial Service role and its frameworks for software supply remain the anchor for public sector productivity software. If you sell tools for HR, finance, case management or workflow, this is the market you are entering.

CCS and GCA frameworks versus direct and partner purchases

A framework is a pre-competed agreement. The GCA has already run the competition, checked the suppliers and fixed the terms. A buyer then runs a smaller competition or calls off directly, depending on the lot.

A direct purchase is what it sounds like. The buyer contracts with the supplier on the supplier's paper. It is fast and flexible, but the buyer carries the full burden of due diligence, subsidy control checks and transparency.

A partner purchase runs through a reseller, systems integrator or managed service provider. The partner holds the contract and subcontracts the software. This suits complex deployments where implementation matters more than licences.

Each route has a different cost and risk profile. Framework documents set the applicable pricing structure and call-off terms, so buyers should check the current documents before comparing offers. Direct deals can offer flexibility but leave the buyer responsible for its procurement and due diligence. Partner deals may bundle services, making it important to understand what is included and who holds the contract.

If you are weighing these options for a rollout, the trade-offs are set out in our guide to choosing a direct, partner or framework route. The short version: frameworks win on auditability, direct wins on speed, partners win on delivery capacity.

Named software and cloud agreements

Back Office Software 2, agreement number RM6285, is one route for public sector productivity software. It covers finance, HR, payroll, document management and similar back office tools. It replaced the earlier Back Office Software agreement.

RM6285 is split into lots. Separate lots cover software licences, associated services and, in some structures, sector-specific needs. A buyer picks the lot that matches the requirement, then runs the competition within it.

The Back Office Software 2 framework for public sector productivity software is the one most suppliers ask about. It is where a mid-sized vendor of finance workflow or records management can realistically win public work without a full OJEU-style procurement of its own.

Cloud Compute 2, RM6292, covers cloud infrastructure and platform services. It matters to productivity software suppliers because many products are delivered as SaaS. If your tool runs on hyperscale cloud, your buyer may source the compute through RM6292 and the application through RM6285.

G-Cloud is another common route for public sector buyers procuring cloud-hosted software and SaaS. Suppliers should check the current G-Cloud agreement and lot documents for eligibility, service definitions, pricing and the call-off process. This is separate from Cloud Compute 2, which covers cloud infrastructure and platform services.

Artificial intelligence is handled through a mix of routes rather than one single agreement. Some AI tools sit under existing software lots, others under specialist agreements or the Digital Marketplace. Buyers should check which agreement actually covers the specific AI capability before assuming a call-off is valid.

The Automation Marketplace DPS for operations automation

The Automation Marketplace is a dynamic purchasing system. A DPS is a two-stage route: suppliers qualify once, then compete for individual call-offs as they arise.

That structure suits automation because requirements vary so much. One council wants invoice processing automated. Another wants case triage. A single fixed framework cannot price both well, so the DPS lets buyers define each competition.

Suppliers join by passing a selection questionnaire. Once admitted, they stay on the DPS and bid for work when it appears. There is no single award date and no fixed list of winners.

For operations teams, this is often the fastest compliant route to buy process automation. It avoids a full tender while keeping the competition auditable.

Buyers should confirm the DPS remains open to new entrants and check the current scope before going to market. Scope changes are published on the agreement page.

Buyer duties under the Procurement Act 2023

The Procurement Act 2023 governs most covered public procurement in England, Wales and Northern Ireland. Devolved Scottish procurement continues under separate rules.

The Act's effect on public sector software buying includes new transparency requirements. Buyers must publish the notices required for their procurement on the central digital platform, accessed through the Find a Tender service, and have regard to the National Procurement Policy Statement.

Framework call-offs are not automatically exempt from the Act's requirements. Buyers should check which notices and records apply, including any transitional rules for frameworks established under earlier legislation.

There is more discretion than before. Buyers can design their own procedures rather than picking from a fixed menu. That flexibility helps software procurement, where requirements are hard to specify in advance.

It also raises the bar on record keeping. If a buyer departs from the framework terms or runs a bespoke competition, the reasoning must be documented. Suppliers should expect more questions about how value was assessed.

Scottish procurement runs on its own rules through Public Contracts Scotland. A supplier selling across the UK needs to know both regimes, because a Scottish public body will not use the same notices or thresholds.

Social value requirements in public sector software procurement

For relevant public service contracts, the Public Services (Social Value) Act requires authorities to consider social value. Central government buyers may also apply the Social Value Model; suppliers should check the procurement documents to see what applies to their bid.

Social value requirements in UK public sector software procurement typically cover areas such as skills, regional employment, environmental impact and support for small businesses in the supply chain. A software contract can score well here through apprenticeships, local hiring or carbon reporting.

The Social Value Model sets out themes including tackling economic inequality, fighting climate change, equal opportunity and wellbeing. The procurement documents set the applicable criteria and weighting, which can vary between agreements and call-offs.

For a software supplier the practical tasks are unglamorous. Measure your baseline. Commit to something you can evidence. Report on it during the contract, because the buyer will ask.

Weak social value responses are a common reason bids lose. Generic statements about being a responsible employer score poorly against a measured commitment tied to the contract's location and duration.

How suppliers get onto a framework

Getting onto a GCA framework is a project in itself. The sequence below is the standard path for a software agreement.

A typical sequence is:

Before you start, run a supplier comparison against the incumbents already on the agreement. If a lot is crowded with established names, a different lot or a partner route may serve you better.

Accreditations matter. Cyber Essentials, ISO 27001 and UK GDPR compliance are commonly required, and the Information Commissioner's Office enforces the data protection side. Missing evidence at selection stage ends the bid.

Framework places are not permanent. Agreements have terms and may be extended or replaced. Suppliers should plan for re-competition and keep their evidence pack warm.

What a buyer must check before calling off

A call-off looks simple. It is still a contract award, and the buyer owns the risk. The GCA publishes guidance on how to buy through its frameworks, which sets out the steps below in more detail.

Scope is the most common failure. A buyer who calls off a workflow tool under a lot written for licences alone creates an unauditable contract. Read the lot description before you shortlist.

Exit terms deserve attention too. Productivity software holds records, so the buyer needs a clear route to extract data if the contract ends or the supplier changes ownership. This is where vendor due diligence pays for itself.

Pricing discipline matters. Framework rates are ceilings in many agreements, so a buyer can negotiate below them. A short competition between listed suppliers usually improves the price and the service commitments.

Finally, check the supplier's wider footprint. Companies House filings, financial standing and any regulatory action are all fair game. A supplier in distress is a risk to a multi-year software contract.

For context on how these routes compare with the wider commercial market, our work on England's productivity software market looks at demand by job rather than by product category.

Common questions