Separate requirements from the purchasing procedure
Describe the work the software must support, the intended users and the deployment environment. Then identify the organization’s own purchasing process and deadlines. This page helps prepare a software brief; it does not assert that Orbislum holds a particular framework position or that any specific procurement route is available.
Write a comparable product schedule
List products, proposed editions, quantities and subscription periods on separate lines. Include required output or administration capabilities so an alternative can be assessed against the same need. Ask each proposal to identify exclusions and additional services. Avoid comparing offers that use different products or contract lengths without making those differences explicit.
Bring technical reviewers into the discussion
Document identity, deployment, access and other organizational requirements for review against the proposed software. A general product description does not establish compliance with a public body’s internal requirements. Identify which questions need confirmation from the manufacturer or the purchasing authority before an offer can be accepted.
Prepare the initial enquiry safely
Provide the organization, country, non-confidential product schedule and relevant response date. Mention any supplier documentation requirements so they can be reviewed. Do not upload confidential tender material, internal credentials or personal records through the public form. Submission of an enquiry is not a tender acceptance or a binding order.
Plan your purchase
- Organization and deployment country
- Products, editions, quantities and term
- Technical requirements and purchasing deadline
- Required supplier documentation