The 5-dimension vendor scorecard
| Dimension | What you're measuring | What to ask for |
|---|---|---|
| Technical bar | What % of contacted candidates does the vendor accept? | Sourcing funnel data + sample vetting rubric |
| Working model | How the vendor works with your team and tools | Sample engagement letter + access list |
| Security posture | SOC 2 status, IP assignment, NDA flow | Latest SOC 2 report + IP clause |
| Commercial terms | Pricing model, minimums, termination terms | MSA + SOW + termination clause |
| Founder credibility | Track record, references, exit history | Founder bios + 3 client references at your stage |
The scorecard is multiplicative. A vendor that scores 9/10 on technical bar but 3/10 on commercial terms is a 3, not a 6. Optimize for the floor, not the ceiling.
Procurement timeline. What to expect
Day 0: Initial intro call (30 min). Vendor sends sample work + an overview of how they work.
Day 1 to 3: NDA exchange. Security questionnaire issued (SIG-Lite, CAIQ, or custom).
Day 4 to 7: Vendor returns questionnaire. Schedule technical reference call with a current client at your stage.
Day 7 to 10: MSA + SOW redline. IP assignment and termination terms reviewed by legal.
Day 10 to 14: Contract execution. Onboarding begins.
Day 14 to 21: First work lands.
Vendors that compress this timeline by skipping steps (e.g., signing without security review) are flagging that they don't have the maturity for enterprise procurement. Slow down.
Red flags. Vendors to drop
- Claims SOC 2 Type II but can't produce the report.
- IP clause uses 'work for hire' without explicit assignment language. Audit by your IP attorney.
- Minimum engagement >6 months. Lock-in protects the vendor, not you.
- Vetting funnel data they 'can't share for confidentiality reasons.' This is non-confidential information.
- Founders who won't take a reference call directly with your CTO.
Collection · Enterprise AI Talent Strategy (landing)
