Run vendor compares in Claude, then verify every claim

What you will be able to do

You will run a vendor or tool comparison in Claude that stress-tests options, marks unknowns as [NEED], and forces you to verify every price and feature on primary sources before you decide.

Claude’s job vs your job

Claude is good at structuring criteria, listing failure modes, and arguing against the leading option.

You are responsible for every price, contract term, and “supports X” claim. Treat the chat as a draft brief, not a purchase order.

Try this job: 45-minute vendor compare

Goal: Keep current vendor vs trial alternative—for supplies, software, or a contractor.

1. Write the decision question in one line.
2. Paste hard constraints (delivery needs, must-have features, monthly budget labeled estimate).
3. Paste facts you gathered from each vendor’s current site or quote (note the date you checked).
4. Prompt: “Build a decision brief: three options max, criteria, risks, unknowns as [NEED], recommend-or-kill line. Do not invent facts.”
5. Prompt: “Argue against the leading option in five bullets.”
6. Verify every number and feature on the vendor’s current page or signed quote.
7. Decide in the same sitting or schedule the decision within 48 hours.

Same skeleton as hire-vs-tool briefs.

Stress-test prompts worth keeping

• “What would make the recommended option fail in our busy season?”
• “Which constraints did I state that you ignored?”
• “List claims in your brief that are not in my facts—rewrite them as [NEED].”

Research modes

If your plan includes web research features, still open the cited pages yourself. Snippets go stale. Feature matrices in a chat go stale faster.

Where Claude is weak

• Live promotional pricing
• Contractual fine print
• Regulated advice (legal, clinical, tax)
• “Who is best” questions with no criteria

Short close

Claude structures the compare—you verify every price and feature, then decide.