Public Procurement Software for Local Councils: 2026 Comparison

1. Why a council needs specialised software (not just PLACSP)

There is a frequent confusion in smaller councils: believing that the Public Sector Procurement Platform (PLACSP) is enough. PLACSP is essential (and mandatory under the LCSP itself), but it is only the channel for publication and receipt of bids. It does not process the internal file, manage approval workflows, electronically sign documents, and certainly does not draft specifications.

Everything that happens before publication on PLACSP (need report, justificatory report, technical specification, administrative clauses, audit, approval) and after (award, formalisation, execution, payments, amendments) requires additional infrastructure. In large councils this is covered by an electronic-file ERP; in small ones it is often improvised with office software and signed PDFs.

2. The three software categories: ERP, platform, AI

To organise the market it helps to clearly distinguish three layers, each with its function and economic model:

• Electronic-file ERP: full administrative processing (registration, workflows, signature, archiving). Examples: Plyca, Vortal, Pixelware, Gestiona, absis. Contracted by annual licence or SaaS.
• Tender platforms: official channel to publish notices, receive bids and communicate with tenderers. In Spain, PLACSP as the central state platform, plus approved regional platforms.
• AI layer for drafting: generates and validates documentary content (specifications, reports) from file data. Emerging category. Examples: LicitadIA as a tool specialised in the LCSP; ChatGPT and similar as generic alternatives.

Confusing these three categories leads to expensive mistakes. Contracting a full ERP when what is needed is to reduce drafting time is over-engineering. Expecting ChatGPT to do the work of an ERP is ignoring everything around drafting.

3. ERP / electronic file: Plyca, Vortal, Gestiona, Pixelware

The major names in electronic-file processing in Spain are these four, although regional alternatives dominate in some communities:

• Plyca: public sector procurement processing platform widely deployed in regional and local government. Strength: complete file traceability and robust validation workflows.
• Vortal: Portuguese multinational with growing presence in Spain, especially in local authorities and the public health sector. Strength: modern interface and analytics module for tenderers.
• Gestiona: electronic administration suite by aytos.es widely used in medium-sized councils. Strength: integration with the full set of municipal management (census, treasury, planning).
• Pixelware: specialist procurement solution focused on councils and dependent entities. Strength: specific modules for minor contracts and framework-based contracts.

4. Tender platforms: PLACSP and regional platforms

The Public Sector Procurement Platform (contrataciondelestado.es) is the mandatory channel for the contractor profile in the general state administration and for local and regional entities that do not have their own approved platform. It is free and managed by the Ministry of Finance.

Several autonomous regions operate their own platform (Catalonia, the Basque Country and Navarre, among others) that replaces PLACSP as the main channel for entities in their territory, but replicates information to the state platform to maintain transparency at national level. The open-information requirement is identical across all of them.

5. The AI layer: assisted drafting vs automatic validation

The most recent layer in the procurement stack is generative artificial intelligence applied to documentary drafting. It is worth distinguishing two different approaches:

• Generic AI (ChatGPT, Copilot, Gemini): powerful models but without specific knowledge of Spanish procurement law. Useful as writing aid but with real risk of hallucinating regulatory references, citing repealed articles or mixing European directives with national regulation. Its use for official documentation requires exhaustive manual review.
• Specialised AI (LicitadIA and similar): models adapted to the Spanish regulatory corpus (LCSP, directives, TACRC case law, Advisory Committees), with built-in validation that flags inconsistencies before saving the document. More predictable, more auditable and hosted on ENS-compliant infrastructure.

A reasonable use of generic AI is as a style assistant or to summarise rulings. For production work (drafting specifications and reports that will be signed and published), specialised AI avoids the audit problems generated by an open tool not controlled by the administration.

6. Selection criteria: budget, integration, ENS, support

Regardless of council size, four criteria dominate when evaluating any piece of procurement software:

• Total cost of ownership (TCO): not only the annual licence, also implementation, training, historical data migration and support hours.
• Integration capability: can it connect with the existing ERP, the regional tender platform, the electronic registry, the eIDAS signature infrastructure?
• ENS compliance: the National Security Scheme is mandatory. Require ENS certification at the appropriate category, not just "declared compliance".
• Real support in Spanish: for smaller councils, the difference between phone support in business hours and asynchronous ticketing is huge when a specification is stuck 48 hours before the plenary.

7. Case 1 — Council under 5,000 inhabitants (limited resources)

The most common scenario: a secretary-auditor covering practically everything (procurement included), with little staff and tight budgets. Contracting a full ERP is not realistic in terms of cost and implementation complexity.

In this case, the biggest saving does not come from the ERP (which would be a disproportionate investment) but from automating the drafting of recurring specifications: cleaning services, park maintenance, electricity supply, etc.

8. Case 2 — Council 5,000-50,000 inhabitants (standard)

The council with a procurement department made up of one or two officers and several assistants, with regular volume of open procedures and minor contracts. Here an electronic-file ERP does make sense.

The key here is not to contract only the ERP expecting it to cover everything. The ERP processes files and manages workflows, but does not draft content: the officer still produces the documents within the flow. An AI layer on top turns that bottleneck into a reasonable time.

9. Case 3 — Provincial council or city over 100,000 inhabitants

Administrations with complete procurement departments, high volume and sophisticated procedures (framework agreements, call-off contracts, design competitions, harmonised procurement with OJEU publication). Here the stack is complete and integrations become the critical factor.

In this scenario, the cost of the ERP is justified by scale. What the AI layer adds is technical staff time freed for strategic tasks (negotiation, monitoring, evaluation) instead of routine drafting.

10. Common errors when choosing

• Contracting an over-sized ERP for the council's real size (licences that are never activated).
• Believing that the tender platform (PLACSP or regional) handles the internal file.
• Using open ChatGPT to draft specifications without controlling data hosting or regulatory validation.
• Not requiring ENS certification from the provider (mandatory, not optional).
• Ignoring the provincial or regional framework agreement that allows cheaper adhesions.
• Contracting software without a training programme: after implementation, staff revert to Word.

11. Why LicitadIA complements (not replaces) the ERP

LicitadIA is a generative AI layer specialised in the LCSP: it drafts the content of procurement documents (justificatory report, technical specification, administrative clauses, evaluation reports) and validates each draft against current regulation before handing it to the officer. It does not process the file, does not manage signature workflows, does not integrate with internal audit. That part is done by the ERP.

The integration between the two layers is natural: the ERP stores the file and its documents; LicitadIA produces the documents. When they are connected via API, the officer starts the draft from the ERP file itself, LicitadIA drafts it and returns it to the ERP flow for signature and publication.

To understand how this layer fits into a council's day-to-day, our article on digitalisation of public procurement in local councils details the complete flow from need to formalisation. If you want to see the concrete capabilities, the features and how it works pages cover the technical side.

The most efficient way to resolve the question "do I need LicitadIA in addition to the ERP I already have?" is to test it with your council's real contract types. In a 30-minute demo you can see whether the time savings justify the subscription. Book the demo here.

Frequently asked questions