Vendor and Procurement Management: RFPs, Contract Types and SLAs for IT Projects
Almost no modern IT project builds everything itself. Teams buy software licences, rent cloud capacity, hire contractors and outsource development or testing. Procurement management covers the processes of buying products, services or results from outside the project team, and managing the resulting relationships. Because a vendor’s failure becomes your failure in the eyes of the sponsor, this is a high-risk, high-reward area.
The Procurement Process
- Plan procurement: decide what to buy and what to build (make-or-buy analysis), the contract approach and the selection method.
- Conduct procurement: issue requests, receive proposals, evaluate and select vendors, negotiate and award the contract.
- Control procurement: manage the relationship, monitor performance, handle changes and disputes.
- Close procurement: verify delivery, settle payments and archive records.
Make-or-Buy Analysis
Compare building internally with buying a product, subscribing to a service or outsourcing. Consider cost over the full life (licences, customisation, support, upgrades), fit to requirements, time to deliver, control and flexibility, availability of skills, strategic importance (is this a differentiator or a commodity?), and risk including vendor lock-in and continuity. Commodity needs such as email or payroll are often better bought; unique capabilities that give a competitive edge may justify building.
RFI, RFQ and RFP
| Document | Stands for | Used when |
|---|---|---|
| RFI | Request for Information | You are exploring what the market offers and need general information |
| RFQ | Request for Quotation | Requirements are clear and well defined and you mainly want price |
| RFP | Request for Proposal | You need vendors to propose solutions, approach, team and price for a complex need |
A good RFP includes background and objectives, scope and requirements (separating mandatory from desirable), technical and security constraints, timeline, the evaluation criteria and weights, contract terms, the response format and a deadline. Giving all bidders the same information and the same chance to ask questions keeps the process fair.
Selecting a Vendor
Use a weighted scoring model like the one in Business Case and Project Selection. Typical criteria are understanding of the requirement, technical approach, relevant experience and references, team quality, price and total cost, financial stability, security and compliance posture, support arrangements and cultural fit. Agree the weights before opening proposals to avoid bias. Ask for demonstrations or a proof of concept for critical capabilities, and speak to reference customers about their actual experience, including what went wrong.
Contract Types
| Contract type | How price works | Risk sits mainly with | Best when |
|---|---|---|---|
| Fixed price (firm fixed price) | Agreed total price for defined scope | Seller | Scope is clear and stable |
| Fixed price with incentive | Fixed price with a bonus or penalty linked to performance | Shared | You want to reward early or better delivery |
| Time and materials (T&M) | Pay for hours or resources used at agreed rates | Buyer | Scope is unclear or evolving, or you need extra staff quickly |
| Cost-reimbursable (cost plus) | Pay actual costs plus a fee | Buyer | Work is uncertain and exploratory |
Fixed-price contracts give budget certainty, but they invite disputes when requirements change, because every change becomes a negotiation, and a vendor squeezed on price may cut corners. T&M gives flexibility but needs close monitoring and caps (“not to exceed” limits). For Agile work, organisations often use time-and-materials with a fixed team, or a fixed price per iteration or story, with a clear mechanism for reprioritising scope.
Key Contract Elements
- Scope and deliverables with acceptance criteria.
- Price, payment milestones tied to accepted deliverables, not just elapsed time.
- Schedule and consequences of delay.
- Change control procedure and rate card.
- Service levels (SLAs) and remedies.
- Intellectual property ownership and licensing.
- Confidentiality, data protection and security obligations.
- Key personnel commitments and substitution rules.
- Warranties, liability and indemnities.
- Termination and exit terms, including data return and transition support.
Have legal counsel review contracts. A project manager is not a lawyer, and this lesson is general guidance, not legal advice.
Service Level Agreements
An SLA is a measurable commitment about service quality. For example: “The service shall be available 99.9 per cent of the time each month, excluding agreed maintenance. Priority 1 incidents shall receive a response within 30 minutes and a resolution or workaround within four hours.” Good SLAs define how each metric is measured, reported and reviewed, and what happens if targets are missed, such as service credits. Note that 99.9 per cent availability still allows roughly 43 minutes of downtime in a 30-day month, so check whether that is acceptable for your business.
Managing the Vendor Relationship
- Name a single point of contact on each side.
- Hold regular governance meetings: weekly for delivery, monthly for commercial review.
- Treat the vendor as part of the team with shared goals, but verify deliverables independently.
- Track performance against milestones and SLAs, and keep records of instructions and decisions.
- Manage changes formally, since verbal agreements cause disputes.
- Pay on accepted milestones and reconcile invoices against progress.
- Escalate early using the contractual path; see RAID Logs, Issues and Dependencies.
Procurement Risks
- Vendor lock-in: proprietary formats or heavy customisation make switching costly. Mitigate with open standards, data export rights and exit clauses.
- Vendor failure: financial problems or loss of key staff. Mitigate with due diligence, escrow arrangements and step-in rights.
- Misunderstood scope: mitigate with clear requirements and joint walkthroughs.
- Security and data protection: assess the vendor’s controls and obligations, especially for personal data.
- Hidden costs: customisation, integration, extra environments, support tiers, training and renewal increases.
Include procurement risks in the project’s risk register; see Project Risk Management.
Closing Procurements
Before closing a contract, confirm all deliverables are accepted, warranties start, outstanding invoices are settled, documentation and knowledge transfer are complete, access credentials are revoked and the vendor’s performance is evaluated for future reference. Update the organisation’s vendor records with lessons learned.
Common Mistakes
- Choosing the lowest price without checking total cost of ownership.
- Writing vague contracts with no acceptance criteria.
- Paying for time instead of delivered results.
- Ignoring exit and transition terms until the relationship sours.
- Leaving vendor management to chance after contract signature.
- Run a make-or-buy analysis, then use RFI, RFQ or RFP to match the need.
- Fixed-price suits clear scope; T&M and cost-reimbursable suit uncertain work.
- Contracts should define deliverables, acceptance, change control, SLAs and exit terms.
- Manage vendors actively with governance meetings, milestone-based payment and early escalation.