The prompt
Score 10 of 10, Excellent
Use it when You want a fair side-by-side comparison of competing products, based on their own current pages rather than the model's memory.
- {{competitor_pages}}
- {{our_product}}
- {{criteria}}
- {{use_case}}
Full prompt and why it works
Prompt
<sources> {{competitor_pages}} </sources> <our_product> {{our_product}} </our_product> <criteria> {{criteria}} </criteria> <constraints> - Use only the sources and our product description above. Do not use what you remember about these companies; it may be out of date or wrong. - Each source starts with the product name and the URL or date it was copied. After every fact in the table, give the source in brackets. - Where a source does not mention a criterion, write "Not stated" instead of guessing. "Not stated" is not the same as "No". - Copy prices, limits and plan names exactly as written, with the date of the source. </constraints> <format> 1. A Markdown table: one row per criterion and one column per product, ours first. 2. Below the table, 3 to 5 bullets on where we are clearly stronger, clearly weaker, or where the sources do not let us tell. 3. A list of the claims that most need checking by a person, such as anything that looks out of date. </format> <task> Based only on the sources above, write a comparison of these products against the criteria, for our {{use_case}}. It should be fair enough that each competitor's own staff would accept their column. If the sources conflict with each other, show both values and say so. </task>
Variables
- {{competitor_pages}}
- Text copied from each competitor's own pages (pricing, features, docs), each starting with the product name, URL and date copied.
- {{our_product}}
- The same facts about your product.
- {{criteria}}
- What to compare, one per line, for example pricing model, single sign-on, API access, data residency.
- {{use_case}}
- What the comparison is for, for example "sales battlecard" or "positioning review".
Why it works
- Background facts. It works only from pages you paste, with dates, so the comparison reflects what competitors say today, not what the model remembers.
- What to avoid. "Not stated" is kept separate from "No", the mistake that makes most comparison tables unfair.
- What good looks like. The fairness test, that a competitor's own staff would accept their column, sets a clear bar for tone and accuracy.