The Revenue AI Report

Compare Your Product with a Competitor

AnalyzeSalesLeadership

A side-by-side feature table of your product and one competitor, built from the material you provide, so reps and buyers can see the real differences in one view.

This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.

The file

---
name: choosing-between-2-products
description: >-
  A side-by-side feature table of your product and one competitor, built from the material you provide, so reps and buyers can see the real differences in one view.
  Task type: Analyze. Built for Sales, Leadership.
  Use when the request sounds like "Compare Your Product with a Competitor".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Deal Strategy and Negotiation
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/choosing-between-2-products
---

# Compare Your Product with a Competitor

A side-by-side feature table of your product and one competitor, built from the material you provide, so reps and buyers can see the real differences in one view.

One job only: a side-by-side feature table of your product and one competitor, built from the material you provide, so reps and buyers can see the real differences in one view. Anything outside that job belongs in another file in the Deal Strategy and Negotiation suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- company name
- competitor name
- folder url
- document url 1
- document url 2
- comparison table

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You will be helping me compare two products - one from {$COMPANY_NAME} and one from {$COMPETITOR_NAME} - by creating a feature comparison table. To do this, you will need to carefully review the resources I provide and ask me clarifying questions if needed.

First, review the following resources I have provided:
- A folder containing product information: {$FOLDER_URL}
- A document about {$COMPANY_NAME}'s product: {$DOCUMENT_URL_1} 
- A document about {$COMPETITOR_NAME}'s product: {$DOCUMENT_URL_2}

Thoroughly read through each of these resources, taking notes on the key features of each product. Look for details on functionality, technical specifications, pricing, and any other relevant information that could be used to compare the two products.

Once you have a good understanding of both products from the provided resources, create a draft feature comparison table with the following columns:

- Feature 
- {$COMPANY_NAME} Product
- {$COMPETITOR_NAME} Product

In the "Feature" column, list out all the major features and capabilities you identified across both products. Then, in the corresponding product columns, use checkmarks (✓) to indicate if that feature is available for the product, and X marks to indicate if the feature is not available.

If you need any clarification or have questions about specific features or product details, write out your questions starting with <question> tags, like this:

<question>Your clarifying question here?</question>

I will do my best to provide additional context to help you accurately fill out the comparison table.

Once you have completed the draft comparison table to the best of your ability using the provided resources and any clarifications from me, provide your final comparison table within <comparison_table> tags, like this:

<comparison_table>
[Your final feature comparison table here]
</comparison_table>

If certain features are unclear or unable to be compared due to lack of information in the provided resources, make a note of that in your comparison table.

The key is to create an organized, accurate, and insightful comparison that will allow me to understand the major differences between the two products across all important features and capabilities. Take your time, think it through carefully, and don't hesitate to ask any clarifying questions you may have.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/choosing-between-2-products
- Suite: https://www.therevenueaireport.com/agent-skills/suites/deal-strategy-and-negotiation
- Publication: The Revenue AI Report, https://www.therevenueaireport.com

Install this skill

  1. For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
  2. For another assistant that supports skills, download the file above and place it in a folder named choosing-between-2-products inside that assistant's skills directory.
  3. Start a new conversation and ask for the job named on this page. Review the result before using it.

For the supporting files, download the full Deal Strategy and Negotiation package too. The single-file command only installs SKILL.md.

mkdir -p "$HOME/.claude/skills/choosing-between-2-products" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/choosing-between-2-products/SKILL.md" -o "$HOME/.claude/skills/choosing-between-2-products/SKILL.md"

Get the Report

The research behind these skills, weekly.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.