Pricing tailored to your organisation.

How procurement software is normally priced

Almost all modern procurement software is sold as a subscription rather than a perpetual licence, which shifts it from capital to revenue in most authorities' accounting. The recurring element is usually driven by one or more of a small number of variables: the number of named users or roles, the modules in scope, the size of the organisation by spend or population, or the volume of activity such as competitions run or contracts managed.

Each model has consequences worth thinking through before you choose. Per user pricing is predictable but discourages giving read access to service managers and finance colleagues, which is exactly the visibility most authorities say they want. Module pricing is transparent but invites a slow accumulation of additions. Volume pricing aligns cost to use but makes budgeting harder in a year with an unusually heavy pipeline.

The practical advice is to model your own three year shape rather than comparing headline figures. Ask each vendor to price the same defined scenario: your actual user population including occasional evaluators, your realistic module set, and your typical annual competition and contract volumes. Then ask what happens if each of those grows by a third, because at some point one of them will.

• Per user or per role, sometimes split between full users and lighter evaluator or viewer access.
• Per module, with sourcing, contract management, supplier assurance and analytics priced separately.
• By organisation size, using spend, population or headcount as the band.
• By volume, using competitions run, contracts under management or suppliers registered.

The cost lines beyond the licence

Implementation is the largest one off cost and the most variable. It covers configuration of your workflows, permissions and approval routes, rebuilding your document and question templates, setting up evaluation models, and configuring notices and reporting. The size depends far more on your own readiness than on the product. An authority with tidy current templates and clear governance implements quickly. One with fifteen years of accumulated variants does not.

Data migration is the second. Deciding what to migrate is a genuine decision rather than a technical detail: live contracts and current supplier records usually justify migration, while a decade of completed tenders usually does not, especially where retention obligations can be met by keeping the legacy archive read only. Cleaning data before migration is cheaper than cleaning it afterwards.

Integration, training and support complete the picture. Integration effort depends on your finance system and on how many flows you genuinely need. Training costs are often underestimated because they must cover occasional users, particularly evaluators who may only score once a year and will have forgotten everything by the next time. Support tiers vary widely in response times, named contacts and whether configuration changes are included, and the difference between tiers can be significant over a contract term.

Buying through frameworks, including G-Cloud 15

Most public buyers reach procurement software through a framework, because the terms, conditions and supplier assessment are already settled and the route from decision to contract is far shorter than a bespoke competition. Framework purchases are made as call off contracts, and the framework's own rules govern how you select: some allow direct award against defined criteria, others require a further competition among suitable suppliers.

eSourcing Data software is available to public buyers through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace alongside cloud support services. The Digital Marketplace publishes service definitions, pricing documents and terms for each listed service, which makes early cost estimation for a business case straightforward without needing to open a sales conversation first.

One caution. A framework listing is a route to market. It is not approval, accreditation or endorsement of any supplier, and it does not remove your obligation to assess whether a service meets your requirements and delivers value for money. Record your selection rationale in the same way you would for any other award, because internal audit will ask.

Building the business case

A business case that rests only on efficiency savings tends to struggle, because the savings are real but diffuse and the finance director has heard the claim before. Stronger cases combine three strands: risk reduction, capacity release and commercial improvement. Risk reduction is the easiest to evidence, because the cost of a single successful challenge, a failed audit or an emergency direct award following a missed contract expiry is usually concrete and locally memorable.

Capacity release should be expressed in what the team will do with the time rather than as a notional cash saving, unless you genuinely intend to remove posts. Redirecting officer time from administration to category work, contract management and market engagement is a credible claim that stands up under questioning. Claiming a headcount saving you will not make damages your credibility for the next case.

Commercial improvement covers better competition, better contract oversight and better renewal planning. Be careful with savings percentages: they are easy to assert and hard to defend, and a challenged benefits claim can sink an otherwise sound case. It is safer to describe the mechanism, such as fewer expired contracts rolling on at unreviewed rates, than to attach a figure you cannot evidence.

Set out the whole life cost over the full term including one off and recurring elements, exit costs and any planned growth, alongside the do nothing option costed honestly. The do nothing comparison is usually the most persuasive section, because it forces the current manual effort and risk exposure into the open.

Budget mechanics in the public sector

Subscription software is normally revenue expenditure, while implementation may be treated differently depending on your accounting policies and the nature of the work. Confirm the treatment with finance before drafting the case rather than after, because a case built on the wrong assumption will come back. If capital funding is available for transformation, the split between capital implementation and revenue subscription is often the deciding factor in whether a case can proceed this year.

Financial year boundaries drive more procurement software decisions than anyone admits. A contract starting in month eleven of the year consumes only two months of revenue budget in year one but commits the full amount thereafter, so make sure the medium term financial plan carries the recurring figure rather than the part year one. Multi year contracts also need the commitment recorded in the forward plan, not just approved once.

Approval routes vary. Depending on value and constitution you may need service level sign off, a corporate digital or technology board, information governance clearance, a data protection impact assessment, legal review of terms and, above certain thresholds, cabinet or committee approval. Map every gate at the start with its meeting date. Committee cycles, not vendor timescales, determine when you go live.

• Confirm capital and revenue treatment with finance before writing the case.
• Carry the full year recurring cost into the medium term financial plan.
• Map every approval gate and its meeting date before agreeing an implementation timetable.
• Include information governance review and a data protection impact assessment in the plan.

Contract terms that affect real cost

The term and any uplift mechanism matter as much as the starting figure. Understand how increases are calculated and capped, what notice you receive, and whether any cap applies to the whole contract or only to the base subscription. A contract with an uncapped annual uplift can look competitive at signature and uncomfortable by year four.

Check what triggers additional charges. Extra users, additional modules, extra environments, integration endpoints, professional services days for configuration changes, and increased storage are all common charge points. Ask specifically who can make configuration changes after go live, because if every change requires paid vendor days, your running cost is higher than the quote suggests.

Exit terms deserve as much attention as entry. Establish what data you get back, in what format, within what period and at what cost, and whether you retain access for a transition window. Procurement records carry retention obligations that outlive most software contracts, so an exit that leaves you unable to produce evidence for an old competition is a governance problem, not just an inconvenience.

Sector considerations

Councils typically need the widest user population because buying is devolved across directorates, which makes the treatment of light touch users a significant cost variable. NHS organisations often sit inside collaborative arrangements where some capability is already provided regionally, so the first question is what gap actually needs filling rather than what a full estate would cost.

Housing associations increasingly run procurement to public sector standards under regulatory expectation, building safety obligations and lender scrutiny, with spend concentrated in repairs, maintenance and development. Their business cases often lead on assurance and contract oversight rather than on tendering volume. Smaller associations frequently find that combining software with outsourced procurement support is better value than software alone.

Education buyers, particularly academy trusts and colleges, are cost sensitive and framework reliant, and often benefit from scope discipline: a modest module set used properly beats a full estate used partially. Charities and third sector bodies handling public money face similar constraints with even smaller teams, and usually need the lightest configuration that still satisfies funder scrutiny.

Dynamic Markets and the running cost nobody budgets for

Dynamic Markets replaced the Dynamic Purchasing System when the Procurement Act 2023 came into force on 24 February 2025, and they carry a running cost that authorities routinely omit from their planning. Because a dynamic market is permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and pending applications must be considered before a competition concludes, the administrative load is continuous rather than periodic.

That ongoing load is officer time. Assessing a steady flow of applications, chasing expiring insurance and certification evidence, and checking pending applications before every award is exactly the sort of work that consumes a small team without ever appearing in a business case. Automating assessment workflows and evidence expiry prompts is where a large part of the value of the software actually lands, so it belongs in the benefits section explicitly.

There is a revenue difference by sector. Utilities in water, energy and transport may charge suppliers membership and award fees and may run member only tenders. General contracting authorities may not charge membership fees, so for councils, NHS bodies and similar organisations a dynamic market is a cost to run rather than a cost to recover.

How eSourcing Data approaches pricing

eSourcing Data covers source to contract in one platform: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows, with UK data residency and GDPR compliance. Scope is agreed against what an organisation actually needs rather than sold as an all or nothing estate, because a module bought and never configured is pure cost.

Public buyers can access the software through RM1557.15 G-Cloud 15, where 28 software services are listed on the Digital Marketplace with published service definitions and pricing documents, alongside cloud support services. Purchases are made as call off contracts. That published detail is usually the fastest way to get indicative figures into a draft business case before any commercial conversation begins.

Where an authority needs delivery capacity as well as tooling, consulting and outsourced procurement support can be scoped alongside the software, which lets a business case balance software cost against the interim or agency spend it displaces. For an indicative view of the benefit side of the case, the ROI calculator is a reasonable starting point, and a demonstration configured against one of your own recent procurements is the most reliable way to test whether the scope you are budgeting for is the scope you need.