Vendor selection decision tree
Evaluate options, score criteria, negotiate terms, and decide on a vendor.
Vendor selection is one of the biggest leverage moments in enterprise software — a bad choice costs thousands per year and takes months to unwind. Yet many teams skip rigorous evaluation and jump to the vendor with the flashiest demo. This template maps the full journey: from a final shortlist through objective scoring, side-by-side demo requests, term negotiation with a credible alternative standing by, legal review, and contract execution.
The decision points are the fault lines: clear scoring prevents the loudest stakeholder from picking a poor fit; keeping the runner-up option credible gives you leverage in negotiations; and separating the legal review from the scoring ensures you're not re-litigating "is this vendor right for us?" once you've shaken hands on terms.
When to use this template
- Procurement policy documentation — walk your organization through the decision process so every team (engineering, security, finance, legal) knows when they're consulted and what they're evaluating.
- Vendor evaluation kickoff — share this diagram with the shortlist of vendors and your evaluation committee so everyone knows the sequence: demo, scoring, negotiation, legal, execution.
- Incident postmortems — when a vendor fails to deliver or a contract dispute erupts, trace which decision point misfired (scoring was unclear, legal didn't catch a term, no alternative was ready).
How to adapt it
Customize the scoring and approval gates to your organization:
- Add a security checklist (SOC 2, HIPAA, data residency) after scoring if your industry has compliance mandates.
- Insert a CFO/budget sign-off between negotiation and legal if vendor pricing needs executive approval.
- Add a customer advisory board vote if your engineering team has strong opinions on vendor choice; layer it into the "revisit scoring" loop.
Visual edits regenerate clean Mermaid code, so you can extend the decision tree with your approval checkpoints without touching syntax.
Mermaid code
Copy it anywhere Mermaid is supported — GitHub, Notion, or your docs.
flowchart TD
A[Finalize RFP shortlist] --> B[Establish scoring criteria]
B --> C[Define weights by priority]
C --> D[Score each vendor response]
D --> E{Top vendor clear?}
E -->|No| F[Request follow-up demos]
F --> G[Revisit scoring]
G --> D
E -->|Yes| H[Invite top 2 to negotiate]
H --> I[Submit term sheet]
I --> J{Terms acceptable?}
J -->|No| K[Counter-propose]
K --> L{Agreement reached?}
L -->|No| M[Escalate to stakeholders]
M --> N{Proceed with this vendor?}
N -->|No| O[Move to #2 option]
O --> H
N -->|Yes| L
L -->|Yes| P[Internal legal review]
P --> Q{Contract approved?}
Q -->|No| R[Revise with vendor]
R --> I
Q -->|Yes| S[Execute contract]
S --> T[Handoff to implementation]
J -->|Yes| P
Frequently asked questions
- What is a vendor selection decision tree?
- It maps the journey from a final shortlist of vendors through evaluation, scoring, negotiation, legal review, and contract execution. It shows the decision points — is the top vendor clear, are terms acceptable, does legal approve — and the recovery loops when stakeholders want to re-score, negotiate harder, or pivot to the runner-up.
- Why score vendors before negotiating?
- Scoring forces objectivity. Without a scoring framework, negotiations often hinge on personality or the loudest stakeholder. A clear score (pricing, support SLA, feature coverage, security certifications, implementation time) gives both the buyer and vendor a shared baseline. It also documents the decision for audits and future reference.
- What happens if the top vendor's terms are unacceptable?
- You pivot to the runner-up. This diagram shows that path: if the top vendor won't budge on negotiation, you escalate internally, decide whether to walk away entirely, and if yes, loop back to vendor #2 with your full negotiating power. Many enterprise deals swing because a buyer kept a credible alternative open.
- When do legal and security reviews happen?
- After both sides agree on terms. Until then, legal review is wasted effort — vendors will change contract language during negotiation anyway. Once you have a term sheet both sides will sign, that's when legal, security, and compliance sign off. Visual edits regenerate clean code, so you can add security checkpoints or compliance gates without rewriting syntax.