Choosing software licences for your needs
Clarify users, devices, licence term and support requirements before comparing software licences or requesting a quotation.
Who is this for? Purchasing and IT managers who prepare software procurement professionally and commercially.
Use cases and context
Licenses don't just differ in the product name. The benchmark can be user, device, instance, or other entity. Duration, included features, support, and renewal will all affect the actual scope.
A displayed article is therefore only comparable if the required variant is clearly determined. Existing contracts, migration rights and technical requirements can play a role. The applicable manufacturer's terms and conditions and the specific offer determine the binding framework.
The approach in detail
- Describe the use: product, existing environment, number of relevant units and desired time period.
- Compare license model and scope of services. Consider features, support, deployment, and renewal separately.
- Check the offer for clear article description, quantity, delivery time, recipient and references. Clarify open variants before placing a binding order.
Expected outcomes
- Clearly described license requirements
- Comparable product variants
- Recorded maturities and renewal issues
- Comprehensible basis for a concrete offer
Prepare for an informed decision
Existing article numbers, contract ends and the required functions are helpful. Please do not submit secret license keys via public forms.
A general product text does not contain any promise of availability, discount or right of use. These points are confirmed in the actual procurement process.
Questions and answers
Is the same product family always the same license?
No. Edition, reference value, duration and included services may differ.
When should an extension be considered?
In good time before the contractually relevant deadlines. The specific term and termination rule result from the respective agreement.