Compare options and recommend one

Weigh two or more options against your criteria and hard limits, see the trade-offs side by side, and get a recommendation when the facts support one.

Task: Compare options and recommend one · Other tasks

Fill in the details

Give each option a name and the facts you have: prices, features, limits, your experience with it.

Optional. List criteria in order of importance. If you leave this empty, the prompt asks Claude to suggest criteria for your confirmation before comparing.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

2 required fields are empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • You have a short list of options and need a clear, defensible choice rather than an open discussion.
  • You want the trade-offs laid out against criteria you set, so the reasoning can be shared with others.
  • You suspect you are missing information and want a list of what to find out before deciding.

When not to use it

  • You have not gathered any facts about the options yet. Collect the basics first; a comparison built on guesses only looks precise.
  • The decision depends on current prices, reviews or availability that you have not provided. Claude here works only with the facts you paste.
  • The choice is personal or values-based with no criteria to weigh. A conversation about what you care about is a better starting point.

Why this structure

  • The option descriptions come first inside <options> tags, followed by the decision and your criteria, which helps Claude keep your facts apart from the task.
  • Hard limits work as a filter: the prompt asks Claude to drop options that break them before comparing the rest, to mark unclear cases as unresolved, and to say so if nothing qualifies.
  • Criteria are ordered by importance, which tells Claude how to weigh them. If you leave them out, the first step asks Claude to suggest criteria and wait for your confirmation, so the comparison uses criteria you agreed to.
  • The table with "unknown" cells makes gaps visible, and the closing paragraph tells Claude not to fill them with assumptions.
  • A recommendation is requested only when the facts support it, and asking what would change it gives you a decision you can revisit when the facts change.

Example input (fictional)

The decision
Which note-taking app our five-person design studio should use
The options
Option A: Inkwell (fictional). 6 per person per month, works offline, no shared folders.
Option B: Paperlane (fictional). 9 per person per month, shared folders, web only.
Option C: Keep using shared documents. Free, already familiar, hard to search.
What matters most
1. Sharing between team members 2. Search 3. Cost
Hard limits
Must cost under 60 per month in total

Follow-ups to send Claude

  • Assume cost matters more than search. Does the recommendation change?
  • Write a short note to my team explaining the choice and the main trade-off.
  • For each "unknown" cell, suggest the quickest way to find the answer.

Common mistakes

  • Listing options with very different amounts of detail. The option you know best tends to win; give each one comparable facts.
  • Treating the recommendation as final. It is only as good as the facts and criteria you supplied; check the table before the conclusion.
  • Mixing hard limits with preferences. Put deal-breakers in the hard limits field so they are applied as filters, not weighed.
  • Critique an argument: Test an argument before you rely on it: its main claim, hidden assumptions, weak links and the strongest objection, with fixes.
  • Analyze customer feedback: Group raw customer comments into themes, priorities or feature requests, with counts and quotes that show where each finding comes from.

See all templates

Sources