Claude prompt for business: Vendor Evaluation (Advanced)
Claude · Business · Advanced
You are a exacting editor using Claude for business, specifically vendor evaluation.
Job: compare tools fairly.
Audience: procurement. Constraint: weighted scorecard.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Claude users in business use this vendor evaluation prompt to ship faster drafts that respect "weighted scorecard". Teams report saving 15–30 minutes per task when prompts include constraints up front. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
Picture a procurement professional opening Claude with one job: vendor evaluation. Without "weighted scorecard", answers drift. This page prevents that drift. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Repeats the hard constraint: weighted scorecard.
- Forces an output contract: headings, examples, and a final version.
- Centers compare tools fairly so success is observable.
- Uses precise and demanding language that matches how practitioners actually brief work.
- Names a clear job so Claude does not wander into generic advice.
How to use it in Claude
Ask for a shorter version after the long one; compression reveals weak claims. Plans, memos, research, and operating documents. Keep that context in the thread when you iterate. If the first answer is vague, reply with the constraint again: weighted scorecard. Add one real example from your last week of work so the model mirrors your domain. Paste the prompt into Claude and replace bracketed details with your facts.
Run a constrained version and a wild version of vendor evaluation. Keep structure from one and energy from the other. For vendor evaluation in business, the failure mode is usually vague audience. This prompt blocks that by design — especially "weighted scorecard". Expect two minutes customizing and two minutes editing for Advanced output. Anthropic models still need your facts for vendor evaluation; they cannot invent metrics or brand rules. operators and founders teams bookmark slug vendor-evaluation-advanced when constraints, evaluation, and edge cases matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (procurement, offer, timeline).
- Confirm the constraint is still visible: weighted scorecard.
- For business work, paste a rubric and ask for a self-score.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Vendor Evaluation, 3 short sections, bullet list of recommendations, closing line that states weighted scorecard. Facts you supply appear; nothing invented.
Common mistakes
- Accepting the first draft without checking compare tools fairly.
- Asking for vendor evaluation plus three other jobs in one message.
- Skipping the audience (procurement) and hoping Claude infers it.
Expert notes
Slug vendor-evaluation-advanced: a operators and founders-oriented business brief. Plans, memos, research, and operating documents. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if weighted scorecard no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a vendor evaluation piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Keep weighted scorecard visible in the prompt, not only in your head.
- Claude improves when you paste a real snippet or reference still.
- If text output drifts, re-anchor with weighted scorecard.
- State the job (compare tools fairly) in one line before any style talk.
- Document what changed when you customized slug vendor-evaluation-advanced.
FAQ
- What is a Claude prompt for vendor evaluation?
- It is a structured brief that tells Claude how to produce business output for procurement. This advanced version stresses constraints, evaluation, and edge cases and keeps "weighted scorecard" in the instructions.
- How do I customize this Claude business prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "weighted scorecard" should stay unless your brief truly changed.
- Why use the advanced angle for vendor evaluation?
- Different angles solve different failures. Advanced helps when procurement need constraints, evaluation, and edge cases. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.