CRAFT GTM report
Competitive Intel: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Competitive Intel
Build a battle card for each competitor
For sales and product marketing leads. The decision: how do we win against each competitor?
Give it your product and competitors, plus any wins, losses or objections. You get a battle card for each competitor, objection handlers, a win and loss analysis and a quick reference card.
What you get
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Against your first competitor
Against your first competitor, lead with: works offline on low-end phones; order suggestions for every outlet.
Questions to ask the buyer about your first competitor:
- How well does your current setup work for you today, measured by adoption by role over the last quarter?
- Walk me through how a typical piece of work goes from start to finish today, and which tools touch it.
- Which part of that work takes the most manual effort or goes wrong most often?
Why not stay with the current approach? What to say:
See the full example answer or run it with your own details.
Result
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Example answer
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
CRAFT GTM report
Example: Competitive Intel
Show the full result
Battle cards: our product
Sector: read from your inputs as vertical SaaS. Business model: not stated. Tell us how you charge and the plan will adjust.
Billing dependent steps are conditional: trials, seats and recurring renewals require a subscription; a statement of work requires a services contract; site or link commitments require connectivity billing. Confirm the applicable choice before using those steps.
Where you stand
The alternatives you named: your first competitor; your second competitor.
Seller claims to test: works offline on low-end phones; order suggestions for every outlet.
Comparison evidence to confirm
| Named alternative | Buyer criterion | Your supplied evidence | Alternative supplied evidence | Conclusion |
|---|---|---|---|---|
| your first competitor | Unknown; agree the buyer's criterion | Seller claim, unverified: works offline on low-end phones; order suggestions for every outlet | Unknown | Not established; compare both options on the same buyer task and retain the source |
| your second competitor | Unknown; agree the buyer's criterion | Seller claim, unverified: works offline on low-end phones; order suggestions for every outlet | Unknown | Not established; compare both options on the same buyer task and retain the source |
Recent wins: offline order capture; faster rollout.
You lose when: no built-in distributor billing yet.
Recent losses: wanted billing and sales in one system.
Against your first competitor
Against your first competitor, lead with: works offline on low-end phones; order suggestions for every outlet.
Questions to ask the buyer about your first competitor:
- How well does your current setup work for you today, measured by adoption by role over the last quarter?
- Walk me through how a typical piece of work goes from start to finish today, and which tools touch it.
- Which part of that work takes the most manual effort or goes wrong most often?
Why not stay with the current approach? What to say:
"Comparing us with your first competitor is fair, and I would rather answer it than dodge it. Against your first competitor, our unverified seller claim is: works offline on low-end phones; order suggestions for every outlet. Which of that would you want to check first against your first competitor?"
Against your second competitor
Questions to ask the buyer about your second competitor:
- How well does your current setup work for you today, measured by time to onboard a new team over the last quarter?
- Who uses the software every day, and how do they feel about their current tools?
- Which systems (accounting, ERP, other tools) must it connect to, and who owns that integration?
Objection handlers
"our distributor system has a free sales app"
Approach: The proof that settles this in vertical SaaS: one team or site before and after on the work the software changes, measured by the buyer's own staff over a full working cycle.
What to say:
"Thank you for raising that. On "our distributor system has a free sales app" I would rather give you an accurate answer than a guess, so I will confirm the specifics and come back to you. Can you tell me more about why that matters in your situation?"
"reps will not use another app"
Approach: Agree a small pilot with the people who will use it, and decide up front how adoption is measured.
What to say:
"I am glad you said that. On "reps will not use another app" I would rather give you an accurate answer than a guess, so I will confirm the specifics and come back to you. Until then, I would suggest we agree a small pilot with the people who will use it, and decide up front how adoption is measured. What is behind that for you?"
Objections vertical SaaS buyers often raise that you did not list
- We run on spreadsheets and it works: Map one real week of work in their spreadsheets, show where time and errors go, and let them judge the product against their own process.
- Our people will not change how they work: Offer a rollout with one team first, training in their own words, and an adoption measure agreed before the start.
- It will not fit how our industry works: Walk through the few workflows that are particular to the trade, using their own documents and forms, and say what is configured and what is built.
Who decides in vertical SaaS
The owner, managing director or head of operations signs; the department head who feels the daily problem champions it; the people who work in it every day decide whether it sticks; finance checks cost and payback; IT checks the fit with the systems already in place. A proof point that lands: one team or site before and after on the work the software changes, measured by the buyer's own staff over a full working cycle.
To sharpen this, give:
- competitor details: a price, a segment or a known weak point for each alternative (it would change the weak points, the questions and the "why not" line on each card)
- a fact that answers "our distributor system has a free sales app": the specific fact that settles it (it would change this answer, which now gives a pattern of answer instead of a fact)
- a fact that answers "reps will not use another app": the specific fact that settles it (it would change this answer, which now gives a pattern of answer instead of a fact)
- the deals you met and won against each alternative (it would change a win rate for each alternative)
- how you charge; the charging model is unknown until you confirm it (it would change the wording on price, trials and contracts)
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
How to read the answer
The tool does not look up live competitor data; it organizes what you typed into Where you stand, a Comparison evidence to confirm table, per-competitor battle cards (lead with, discovery questions, and Why not stay with the current approach?), and Objection handlers. Every strength or weakness you entered is marked Seller claim, unverified and Not established until you and the buyer test both options on the same buyer task with a dated source. Use the battle cards as questions to ask the buyer and tests to run in a live evaluation, not as claims to read out as settled facts.
What to do next
- Founder: Review the Comparison evidence to confirm table and pick one buyer criterion where you can prove your advantage on the buyer's own data or workflow.
- CEO: Check Where you stand and Why not stay with the current approach? to ensure your positioning addresses the status quo and manual work, not just named software rivals.
- CMO: Add the missing inputs listed under To sharpen this (competitor details, recent wins, and recent losses with reasons) so the battle cards reflect real deal evidence.
- CRO: Coach reps to ask the neutral discovery questions under each competitor card instead of disparaging rivals, and require a live proof on the buyer's task.
- Demand generation head: Use the Objections <sector> buyers often raise that you did not list to build comparison guides and mid-funnel content that answer those concerns early.
Why come back
Come back after every quarterly win/loss review or whenever a new competitor appears in your pipeline, and re-run the tool with your latest won and lost deal notes to update your battle cards. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Who is the Competitive Intel tool not ideal for?
- Anyone who cannot give the inputs listed above, because the answer is built only from them.
- Teams that want finished plans ready to publish: each tool returns a structured draft, with placeholders where your inputs gave no fact.
- Anyone who needs live market or competitor data: the tools do not look anything up. They work from what you type, and anything they add themselves is marked as an example, a suggestion or a placeholder.
How do I use the Competitive Intel tool with an AI assistant?
Add CRAFT GTM to your assistant once (the steps are on Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use CRAFT GTM's Competitive Intel tool. your product: our product; competitors: your first competitor, your second competitor; your strengths: works offline on low-end phones, order suggestions for every outlet; your weaknesses: no built-in distributor billing yet; common objections: our distributor system has a free sales app, reps will not use another app; recent wins: offline order capture, faster rollout; recent losses: wanted billing and sales in one system. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
How does the Competitive Intel tool work?
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
- Fill in the form above, or press Fill in an example.
- Press Run Competitive Intel.
- Read the result on this page, then copy it and edit it before you use it.
It applies fixed rules in the CRAFT GTM code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
For developers
MCP tool name: competitive_intel. REST: POST https://craft-gtm.gtmhelix.com/api/tools/competitive_intel with this JSON body (see How it works):
{
"input": {
"your_product": "our product",
"competitors": "your first competitor, your second competitor",
"your_strengths": "works offline on low-end phones, order suggestions for every outlet",
"your_weaknesses": "no built-in distributor billing yet",
"common_objections": "our distributor system has a free sales app, reps will not use another app",
"recent_wins": "offline order capture, faster rollout",
"recent_losses": "wanted billing and sales in one system"
}
}
Choose your app
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh