| name | vendor-eval |
| description | Vendor proposal evaluation. Analyze technical architecture, pricing, and market benchmarks from a proposal PDF/Doc. Output evaluation report + comparison. |
| argument-hint | [PDF/Doc file path] [--scope 'OCR only'] [--exclude-competitor 'CompanyX'] |
| allowed-tools | Read, Bash, Write, Glob, Grep, WebSearch, Agent |
| author | Maki |
| version | 1.0.0 |
| tags | ["business","procurement","vendor","evaluation","analysis"] |
| required_env | [] |
| required_bins | [] |
| platforms | ["macos","linux","windows"] |
| safety_level | safe |
/vendor-eval — Vendor Proposal Evaluation
Read a vendor proposal document and produce a comprehensive evaluation report with negotiation toolkit.
Output
- Markdown report — Full evaluation (tech analysis + pricing breakdown + risk matrix + negotiation strategy)
- Comparison table — Alternative solutions + PoC acceptance criteria + negotiation priorities
Not Applicable When
- Vendor gave only a verbal quote, no written proposal → ask for written document first
- Pure price comparison with no technical content → just use a spreadsheet
- Involves confidential internal pricing strategy → handle offline
Input
From $ARGUMENTS or conversation:
| Field | Required | Description |
|---|
| Proposal file | Yes | PDF path, or document URL |
| Evaluation scope | No | Default: all. Can limit to e.g., "OCR module only" |
| Excluded competitors | No | e.g., "CompanyX is our competitor, don't mention in report" |
| Audience / purpose | No | Affects report tone, e.g., "for exec negotiation" vs "internal tech review" |
| Industry context | No | Client's industry, size, IT maturity (helps judge solution fit) |
If missing the proposal file, ask user.
Decision Model
Phase 0: Read Proposal (Pre-flight)
-
Identify file type:
- Local PDF →
Read tool
- URL →
WebFetch to download then read
-
Extract key info, build a proposal summary card:
## Proposal Summary Card
- Vendor name: {name or "not specified"}
- Client: {client name}
- Module count: {N}
- Modules and pricing: {list}
- First-year total: {amount}
- Usage limits and overage fees: {list}
- Reference customers: {list}
- Timeline: {N weeks}
- Security/compliance terms: {yes/no}
- Confirm scope: if user specified (e.g., "OCR only"), focus only on that scope from here.
Phase 1: Technical Architecture Analysis
Analyze each module:
