Compare Options + Pick a Winner (With Criteria)
This prompt structures comparison decisions through explicit criteria, scored evaluation, and clear recommendations. It moves beyond feature lists to examine how options perform against your specific use case. The output acknowledges that the 'right' choice depends on context, not universal superiority.
GPT / Claude / Gemini3 variables
Prompt
Compare {OPTION_A} vs {OPTION_B} for {USE_CASE}.
Rules:
- If USE_CASE is vague, ask 1 clarifying question first.
- Score each criterion 1–10 with 1-line justification.
- End with a clear recommendation and who should pick the other option.
Output format:
1) Assumptions (if any)
2) Criteria table (Criterion | A score | B score | Why)
3) Key tradeoffs (bullets)
4) Recommendation (winner + why)
5) If you choose the other one (when that makes sense)
Option A: {OPTION_A}
Option B: {OPTION_B}
Use case: {USE_CASE}Quick brief
Purpose
Turn 'which is better?' into a clear decision with tradeoffs and a final pick.
Expected output
A decision framework containing any necessary assumptions, a criteria table with 1-10 scores and justifications for both options, key tradeoffs in bullet form, a clear winner recommendation with reasoning, and scenarios where choosing the alternative makes sense.
Customize before copying
Replace these placeholders with your own context before you run the prompt.
{OPTION_A}{OPTION_B}{USE_CASE}
Works well with
GPT
Claude
Gemini
Variations
Add a 'budget pick' and 'power-user pick' if relevant.
Make it one-screen short (no table, just bullets).
Add a 30-second summary I can read out loud.
What this prompt helps you do
This prompt structures comparison decisions through explicit criteria, scored evaluation, and clear recommendations. It moves beyond feature lists to examine how options perform against your specific use case. The output acknowledges that the 'right' choice depends on context, not universal superiority.
When to use it
Apply this when choosing between tools, services, technologies, or approaches where both options have merit. Most valuable when you understand the choices superficially but need deeper analysis of tradeoffs. Essential when explaining decisions to stakeholders or teams.
How it works
The prompt evaluates options across consistent criteria, scores each 1-10 with justification, identifies key tradeoffs, recommends a winner for the stated use case, then describes scenarios where the other option makes sense. This structure prevents false dichotomy thinking.
Best practices
Define your use case specifically—'e-commerce site with 100k monthly visitors' not just 'website'. If comparing tools you haven't used, state this and rely on documented capabilities. Let the AI ask clarifying questions if your use case is vague. Focus on criteria that matter to your decision, not exhaustive feature lists.
Common mistakes
Comparing options at different price points without considering budget as a criterion. Treating scores as objective when they're contextual to the use case. Ignoring the 'when to pick the other option' section—it often reveals the decision is closer than it seems. Making criteria too generic to be useful.
What you should expect back
A decision framework containing any necessary assumptions, a criteria table with 1-10 scores and justifications for both options, key tradeoffs in bullet form, a clear winner recommendation with reasoning, and scenarios where choosing the alternative makes sense.
Limitations
Quality depends on the specificity of your use case—vague needs produce vague comparisons. Can't account for future changes in the options. Scores are somewhat arbitrary; focus on the justifications instead. Works best comparing similar categories, not apples-to-oranges comparisons.
Model notes
Compatible with all major models. Claude excels at nuanced tradeoff analysis. GPT-4 tends to generate more systematic scoring. Gemini sometimes surfaces less obvious comparison angles. Works for any domain: software, services, methodologies, approaches.
Real-world applications
Engineering teams use this to evaluate technology choices. Product managers use it to prioritize features or approaches. Individuals use it for major purchases. Consultants use it to structure recommendations. Teams use it to document why decisions were made.
How to tell if it worked
Effective comparisons mean you can defend the decision to skeptics, understand when to revisit the choice, and know what you're sacrificing. If team members disagree after seeing the analysis, the criteria likely need refinement. If the decision feels obvious, you might not have needed the comparison.
Where to go next
Follow up with Product Review Brief to deep-dive on the winner. Use Bug Hunter if comparing debugging approaches. Pair with SQL Query Builder when comparing database solutions.
Appears in collections
Decision Framework (Compare Options, Pick Confidently)
Stop overthinking. Structure your options, evaluate systematically, and make defendable decisions.
Competitive Research & Analysis (Know Your Landscape)
Understand what competitors are doing, why it works, and where opportunities hide.
User Research Synthesis (Insights to Action)
Turn user interviews and feedback into clear insights and product decisions.
Related prompts
Meeting Agenda (Clear Outcomes, Not Generic Lists)
Create agendas that make meetings actually productive.
Meeting Notes with Action Items (Clarity & Accountability)
Document meetings so everyone knows what was decided and what happens next.
Daily Schedule Fixer
Rescue a messy day by turning too many loose tasks into a workable plan.
Period Week Planner
Adjust your week more realistically around low energy, discomfort, or heavier mental load during your period.