Skip to content

Sector · Software

Find your software behind the specification.

Buyers describe uses, not your product. VIGLIA maps functions, users, interfaces and maintenance to your modules, then exposes the gaps your team needs to check.

Your catalogue is the reference. You keep the decision.

Software and SaaS
VIGLIA Sector qualification

A requirement. Your offer. The checks that remain.

  • Functional coverage and gaps against the specification
  • Hosting, security and data location
  • Interoperability, APIs and legacy migration
An illustration of the workflow, not a published notice or customer result.

01 · Trade signal

Read the signal, not just the title

Three archetypes written by VIGLIA to illustrate the sector. They are not published notices: no named buyer, value or date.

  1. 01

    Illustrative example

    Typical buyer Urban community authority

    SaaS financial management software with data migration

    Check before committing Demonstration or prototype requested, interfaces with existing tools

  2. 02

    Illustrative example

    Typical buyer University

    Application maintenance of a business information system

    Check before committing Reversibility phase, knowledge transfer and service levels

  3. 03

    Illustrative example

    Typical buyer Government agency

    Agile development and enhancement of a business application

    Check before committing Work units, required profiles and imposed hosting constraints

02 · Market reading

The opportunity families

  • 01 Licences and SaaS subscriptions
  • 02 Integration, configuration and data migration
  • 03 Application maintenance and support
  • 04 Custom development and enhancements

03 · Qualification

Before committing the team

A match with your product is not proof of functional compliance: the response grid and any demonstration still have to be prepared.

  • Functional coverage and gaps against the specification
  • Hosting, security and data location
  • Interoperability, APIs and legacy migration
  • Licensing model, term and reversibility

04 · Method

From catalogue to decision

  1. 01

    Your catalogue

    Describe your product by modules, functions, users and deployment models, and list integration or maintenance services separately.

  2. 02

    The documents

    VIGLIA maps requested functions to your modules and flags the security, interoperability and migration requirements cited in the documents.

  3. 03

    Your decision

    Bidding alone, in a consortium or through an integrator remains your call; VIGLIA makes the facts visible first.

05 · CPV 2008

CPV codes worth knowing

Official labels from the Common Procurement Vocabulary (CPV 2008, Regulation (EC) No 213/2008). A code helps you explore a portal, not decide: VIGLIA also qualifies notice text and documents.

Find more CPV codes
  • 48000000-8 Software package and information systems
  • 72200000-7 Software programming and consultancy services
  • 72263000-6 Software implementation services
  • 72267000-4 Software maintenance and repair services
  • 72416000-9 Application service providers

06 · Honest boundary

Scope and limits

A match with your product is not proof of functional compliance: the response grid and any demonstration still have to be prepared.

VIGLIA compares notices from active sources with your private catalogue. The buyer portal, current procurement documents and your company evidence remain authoritative for eligibility and response decisions.

07 · Resources

Further reading

Free digest · France · in French

Explore the Software and SaaS digest

A generic sector selection of tenders published in France on BOAMP, PLACE and TED France on Mondays when at least one notice was selected. It does not match your private catalogue or goals; the free digest is in French.

View the free French digest