Workflow · Moderate effort
Evaluate a tool
Compare credible software options against actual requirements and produce a defensible recommendation.
Opens the tool in a new tab. Sign-in or a plan may be required there. Follow the steps below and return to check your result.
Step by step
Here’s how to do it
Work through these steps in order. Your notes stay on this page until you copy them; nothing runs automatically.
What you’ll need
- The user need, material constraints and decision criteria.
- A bounded shortlist and current official product sources.
List what the software must do
- Write the user need and the requirements that would change your choice.
- Separate essential requirements from preferences, then agree their importance with the decision-maker.
- In Claude, paste the prompt below with this step’s source material, then send it. Review the answer before carrying it forward.
Prepare your prompt
Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.
View prepared prompt
Turn this software need into a short decision checklist. Separate essential requirements from preferences. Suggest measurable acceptance checks and flag missing constraints. Do not select a product yet. Requested output format: Requirement | Candidate | Evidence | Limitation
- Start with
- Problem plus constraints.
- You’ll have
- Prioritised criteria.
Claude’s file guide (opens in a new tab) · Checked
Make a shortlist
- Choose a manageable set of candidates that could meet the need.
- Record why each candidate is included. Do not treat popularity as proof that it fits.
- In Claude, paste the prompt below with this step’s source material, then send it. Review the answer before carrying it forward.
Prepare your prompt
Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.
View prepared prompt
Create a bounded shortlist from the supplied candidates and agreed requirements. Explain the reason for including each. Mark unsupported product capabilities Unknown; do not rank by popularity or commercial relationships. Requested output format: Requirement | Candidate | Evidence | Limitation
- Start with
- Criteria plus known options.
- You’ll have
- Shortlist.
Claude’s file guide (opens in a new tab) · Checked
Check the evidence for each candidate
- Open current official product and plan information for each important requirement.
- Record the link, date and relevant evidence. Mark missing or unclear support as “Unknown”.
- Start with
- Shortlist.
- You’ll have
- Evidence by candidate and criterion.
Compare one requirement at a time
- Create a table with requirements as rows and candidates as columns.
- Fill each cell with the supporting evidence, a limitation or “Unknown”. Keep pricing separate from suitability.
- In ChatGPT, paste the prompt below with this step’s source material, then send it. Review the answer before carrying it forward.
Prepare your prompt
Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.
View prepared prompt
Compare these candidates against the agreed requirements using only the supplied evidence. Use the same rows for each candidate. Put Unknown in unsupported cells and retain the source references. Keep price separate from task suitability. Requested output format: Requirement | Candidate | Evidence | Limitation
- Start with
- Criteria plus evidence.
- You’ll have
- Comparison matrix.
Explain the trade-offs
- Use the agreed requirements to describe which candidate fits best and why.
- List the compromises, missing evidence and conditions that could change the recommendation.
- In ChatGPT, paste the prompt below with this step’s source material, then send it. Review the answer before carrying it forward.
Prepare your prompt
Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.
View prepared prompt
Explain the trade-offs in this checked comparison. Identify the best fit against the agreed criteria, the compromises and what missing evidence could change the recommendation. Do not treat Unknown as a pass. Requested output format: Requirement | Candidate | Evidence | Limitation
- Start with
- Comparison matrix.
- You’ll have
- Recommendation rationale.
Choose a small validation task
- Pick a trial, demo or review that tests the most important uncertainty.
- Define what would count as a useful result before spending money or using sensitive information.
- Start with
- Recommendation.
- You’ll have
- Validation step.
Write the recommendation
- Summarise the need, comparison, proposed choice and trade-offs in one document.
- Include the evidence, unresolved questions and proposed validation step. Ask the decision-maker to review it before committing.
- In Claude, paste the prompt below with this step’s source material, then send it. Review the answer before carrying it forward.
Prepare your prompt
Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.
View prepared prompt
Draft an internal software recommendation from this reviewed comparison. Include the need, criteria, evidence, proposed choice, trade-offs, unknowns and next validation step. Do not claim that a purchase or trial has been approved. Requested output format: Requirement | Candidate | Evidence | Limitation
- Start with
- All prior outputs.
- You’ll have
- Final recommendation.
Claude’s file guide (opens in a new tab) · Checked
0 of 7 step checks complete. The decision-maker can see why the preferred option fits, what remains uncertain and what should happen before commitment.
Before you share or switch it on
- Verify material features and plan entitlements.
- Check the conclusion against weighted criteria.
- Trial sensitive or costly choices before committing.
03 · Tools used
Tool roles, with choice kept visible
Primary Tools
Optional
No optional tool is included in this setup.
01 · What this workflow helps you do
Requirements, shortlisted options, evidence, trade-offs, preferred option, risks/conditions and next validation step.
Turn a software need into a bounded, evidence-backed internal recommendation.
Requirements, shortlisted options, evidence, trade-offs, preferred option, risks/conditions and next validation step.
Complete when: The decision-maker can see why the preferred option fits, what remains uncertain and what should happen before commitment.02 · What you need
Start with the available source material
- Problem/Job
- Must-Have Requirements
- Constraints
- Known Candidate Tools
- Decision Owner/Deadline Where Relevant
05 · Human checks
Keep judgement with the person doing the work
- Criteria come from need, not marketing.
- Keep candidate set bounded.
- Prefer primary evidence for capability/pricing claims.
- Unknowns stay visible.
- Human owns procurement decision.
- Match validation to uncertainty.
- State assumptions and unknowns.
06 · Limitations
Where this workflow needs care
- Pricing and capabilities change.
- Vendor marketing is not neutral evidence.
- No universal score should replace requirements.
- Security/compliance needs authoritative evidence.
07 · Related workflows