IT procurement: requirements, comparison and total costs
An inexpensive purchase can become costly if setup, licences or exit are missing. Procurement advice establishes a common basis. It can assess requirements or quotes already received.
Define needs before selecting products
Describe the work and existing equipment. Separate essential requirements from useful extras. Retaining equipment may suit the need when support and compatibility fit.
Specify advice, quote comparison or support through ordering. Delivery and technical installation are not automatically part of consulting.
Make requirements testable
Write requirements that can be checked against quotes. Each feature should serve an identifiable use rather than favouring a provider without reason.
| Procurement area | Concrete information |
|---|---|
| Computers and accessories | Quantities, applications, known models and connections |
| Software | Users, roles, functions and interfaces |
| Cloud service | Billing model, data scope, operation and exit |
| IT service | Ownership, availability and agreed response |
Check integration and rights
New equipment and services must fit existing networks, applications and sign-in. For critical combinations, request relevant evidence or a limited test.
Review licence assignments, contract length and rights when circumstances change. Included software does not always explain who may use it and for how long. Existing contracts and renewals affect timing.
Evaluate on a common basis
Compare the same scope and usage period. Flag assumptions and missing items. A discount or low introductory price says little if essential services are excluded.
- Criteria. Set mandatory requirements and comparison criteria first.
- Requests. Provide the same defined needs to each supplier.
- Checks. Review exclusions, recurring costs and compatibility.
- Decision. Explain the selection and clarify open points before ordering.
Consider the full usage period
Include operation, support and later change alongside purchase price. Missing costs remain unknown, not free. Use the same quantities and a stated usage period for every option.
| Cost item | Comparison point |
|---|---|
| Purchase | Advice, equipment, delivery and setup |
| Use | Licences, consumption, maintenance and internal support |
| Changes | Expansion, additional users and integrations |
| End of use | Export, return, data handling and disposal |
Check service life and evidence
Ask about repairability, spare parts, updates and support for the intended period. Environmental or quality criteria should fit the purchase and have useful evidence.
Rules for public purchasers do not automatically bind private companies. Public procurement needs separate assessment of applicable procedures; ordinary purchasing advice does not replace it.
Hand over the decision clearly
A recommendation records reasons, cost assumptions, exclusions and remaining risks. Agree whether advice ends at comparison or also covers contracts and introduction.
- Result. Retain requirements and comparable quotations.
- Roles. Name the decision-maker, purchaser and setup owner.
- Control. Compare delivery and contract items with the selection.
Frequently asked questions
Is this only about computers?
No. It may cover hardware, software, cloud services or IT support contracts.
Must models already be known?
No. Tasks and environment support initial assessment; known models help check compatibility.
Can existing quotes be assessed?
Yes. Agree scope, number and a common evaluation basis.
Does the lowest purchase price decide?
It is one item. Setup, use, support and exit may change the overall comparison.
Must I state a budget?
Needs and scope matter most initially. A cost framework can help at selection stage.
Will the adviser place an order automatically?
Only with explicit assignment and approval. Advice, ordering and technical setup are separate tasks.
