Build a comparison table assistants can lift

Use when you want a comparison page that assistants summarise accurately rather than mangle.

You are building a comparison table for a page comparing {{ITEM_A}} and {{ITEM_B}} (and optionally {{ITEM_C}}).

Audience and their decision: {{AUDIENCE_AND_DECISION}}
Facts I can verify: {{KNOWN_FACTS}}

Produce:
1. A table with one row per decision criterion and one column per item. Choose 8 to 12 criteria that actually change the decision, not feature counts. Every cell must be a short factual statement, under 15 words, no marketing adjectives.
2. A "verdict by use case" section: 4 to 6 short paragraphs, each starting "Choose X if you ...".
3. A one-paragraph summary of 50 to 70 words that a reader could quote as the answer to "which should I pick".

Constraints:
- Any cell you cannot verify from {{KNOWN_FACTS}} must read "not verified" rather than a guess. Do not invent pricing, limits or dates.
- Do not declare an overall winner. Verdicts are per use case.
- Criteria must be phrased as neutral nouns, not as leading questions.
- No em dashes, no superlatives, no "the clear winner".

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

• {{ITEM_A}}
• {{ITEM_B}}
• {{ITEM_C}}
• {{AUDIENCE_AND_DECISION}}
• {{KNOWN_FACTS}}

Getting a better result

1. 1 Assistants lift row labels as much as cell values, so make criteria names literal and searchable.
2. 2 Mark verified pricing with the date you checked it; stale numbers get cited for years.
3. 3 Publishing the table as real HTML rather than an image is what makes it liftable.