Comparative Analysis Prompt

The Problem

When you ask AI to compare two options, it defaults to a balanced, non-committal response that lists pros and cons without making a decision. This is useless for real engineering choices where you need a clear recommendation based on your specific constraints. You need the model to weigh tradeoffs against your priorities and commit to a position.

The Prompt

Compare [OPTION A] vs [OPTION B] for my specific use case.

MY CONTEXT:
- Use case: [what you are building]
- Scale: [expected users/data/traffic]
- Team: [size, experience level, existing expertise]
- Timeline: [deadline or runway]
- Budget: [constraints]

COMPARE ON THESE DIMENSIONS:
1. [Dimension 1, e.g., Performance]
2. [Dimension 2, e.g., Developer Experience]
3. [Dimension 3, e.g., Long-term Maintenance]
4. [Dimension 4, e.g., Cost]

FOR EACH DIMENSION:
- Rate each option (1-5) with justification
- Identify the clear winner for this dimension
- Note any dealbreakers

THEN:
- Provide a weighted overall recommendation based on MY priorities
- State which option you would choose and why
- List the top 3 risks of your recommended choice

Example Output

COMPARISON: Astro vs Next.js for a multilingual brochure site (10 pages, 3 locales)

| Dimension           | Astro (score) | Next.js (score) | Winner |
|---------------------|---------------|-----------------|--------|
| Performance         | 5             | 3               | Astro  |
| Developer Experience| 4             | 4               | Tie    |
| i18n Support        | 4             | 5               | Next.js|
| Hosting Cost        | 5             | 3               | Astro  |

RECOMMENDATION: Astro
For a static brochure site with 30 total pages, Astro's zero-JS default produces
faster pages than Next.js SSG. The i18n gap is closeable with astro-i18next.

TOP 3 RISKS:
1. Astro's i18n ecosystem is less mature — custom routing may be needed
2. If the site later needs authentication, Astro requires more setup than Next.js
3. Smaller hiring pool for Astro vs Next.js developers

When to Use

Use comparative analysis prompts for technology selection, architecture decisions, vendor evaluation, or any choice where you need an evidence-based recommendation instead of a balanced list of pros and cons. It forces the model to commit to a position and defend it with reasoning specific to your context.

Pro Tips

• Weight your dimensions — tell the model which dimensions matter most; “performance is 3x more important than DX” produces sharper recommendations.
• Ask for dealbreakers — a single dealbreaker can override every other advantage; force the model to identify them explicitly.
• Request a dissenting opinion — after the recommendation, ask “now argue for the option you did not choose” to stress-test the analysis.
• Include real metrics — “our p95 latency budget is 200ms” is more useful than “performance matters” for generating actionable comparisons.