Technology vendor selection is one of the highest-impact decisions organisations make. The wrong choice creates years of pain: systems that don't fit, vendors that disappear, costs that spiral. A structured selection process dramatically improves outcomes.
Common Selection Mistakes
Mistakes that haunt organisations:
- Demo-driven decisions: Choosing based on the best sales presentation rather than fit.
- Price over value: Lowest initial cost often means highest total cost.
- Ignoring implementation: The product is 30% of success; implementation is 70%.
- Insufficient requirements: Vague requirements get vague proposals.
- Not involving users: IT selects; users reject.
- Single-vendor shortlist: Confirming a predetermined choice isn't selection.
Phase 1: Requirements Definition
Before evaluating vendors, understand what you need. This phase prevents scope creep during evaluation and ensures you're comparing like with like.
Business Requirements
- What business problems does this solve?
- What processes will change?
- Who are the users and what do they need?
- What outcomes define success?
Functional Requirements
- What must the system do?
- What workflows must it support?
- What data must it handle?
- What integrations are required?
Non-Functional Requirements
- Performance: response times, throughput
- Scalability: growth expectations
- Security: compliance requirements, data protection
- Availability: uptime requirements
- Support: SLAs, support hours
Prioritisation
Not all requirements are equal. Use MoSCoW (Must have, Should have, Could have, Won't have) or similar prioritisation. Focus evaluation on must-haves; use should-haves as differentiators.
Phase 2: Market Research and Shortlisting
Market Research
- Analyst reports (Gartner, Forrester) for market overview
- Peer recommendations and industry contacts
- Online reviews (G2, Capterra—with scepticism)
- Industry forums and communities
Shortlist Criteria
Create an initial long list of 6-10 vendors, then shortlist to 3-4 for detailed evaluation based on:
- Apparent fit with must-have requirements
- Vendor viability and stability
- Relevant industry experience
- Geographic/support coverage
- Approximate budget fit
Phase 3: RFP Process
A Request for Proposal (RFP) provides a structured way to gather comparable information from shortlisted vendors.
RFP Components
- Company overview: Your organisation and project context
- Requirements: Detailed functional and non-functional requirements
- Response format: How you want answers structured
- Evaluation criteria: What you'll assess (optional to share)
- Commercial requirements: Pricing format, contract terms
- Timeline: Submission deadline, evaluation schedule
RFP Best Practices
- Be specific—vague requirements get vague responses
- Ask for case studies and references in your industry
- Request detailed pricing including implementation
- Include realistic scenarios for vendors to address
- Allow questions period to clarify requirements
Phase 4: Evaluation
Scoring Framework
Weighted scoring ensures consistent evaluation. Weight categories by importance, score each vendor against criteria, calculate weighted scores.
| Category | Weight | Typical Criteria |
|---|---|---|
| Functional fit | 30% | Must-have requirements coverage |
| Technical fit | 20% | Architecture, integration, security |
| Vendor viability | 15% | Financial stability, roadmap, references |
| Implementation | 15% | Approach, team, methodology |
| Cost | 20% | TCO over 5 years, not just initial price |
Demonstrations
Require scripted demonstrations based on your scenarios—not canned demos. Have end users attend. Score against predefined criteria, not presentation quality.
Reference Checks
Talk to actual customers—preferably ones the vendor didn't nominate. Ask about implementation experience, ongoing support quality, and issues encountered.
Proof of Concept
For high-stakes selections, a paid proof of concept with 1-2 finalists validates real-world fit. Configure the system for your actual use cases. The investment is small compared to choosing wrong.
Phase 5: Selection and Negotiation
Final Selection
Base the decision on evaluation scores, reference feedback, and PoC results. Ensure stakeholder alignment before proceeding—disagreements post-selection derail implementations.
Contract Negotiation
- Lock in pricing for multi-year terms
- Define SLAs with penalties
- Negotiate implementation milestones and payment terms
- Ensure data ownership and exit rights
- Cap annual price increases
Summary
Good vendor selection follows a structured process: clear requirements, objective evaluation, thorough due diligence. The investment in a proper selection process pays off in years of productive vendor relationship—or saves you from years of regret.
Involve the right stakeholders, evaluate based on weighted criteria, verify claims through references and PoCs, and negotiate contracts that protect your interests.