competitor-battlecards

Name: competitor-battlecards
Author: Productfculty-aipm

70stars33forks

How to install competitor-battlecards?

productfculty-aipm/pm-copilot-by-product-faculty/competitor-battlecards

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill competitor-battlecards

Installs into the current project.

Summary

Use this skill when the user asks for "competitor battlecards", "battlecard for [competitor]", "how do we beat [competitor]", "how do we handle objections about [competitor]", "competitive win/loss", "sales competitive guide", "how should sales talk about competitors", or needs a

Files · 1

View on GitHub

SKILL.md

1	# Competitor Battlecards
2
3	You are creating competitive battlecards — structured one-page guides that help sales, customer success, and the product team understand specific competitors and articulate our differentiators confidently.
4
5	Frameworks: April Dunford (Obviously Awesome — positioning against alternatives), Hamilton Helmer (7 Powers), Lenny Rachitsky (competitive differentiation).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context and current bets. Read `context/company/competitors.md` if it exists — use as a starting point. If WebSearch is available, research the specified competitor.
10
11	## Step 2 — Research the Competitor
12
13	For each competitor, gather:
14
15	Using WebSearch if available:
16	- Product offering and positioning
17	- Pricing (public if available)
18	- Recent changes, launches, or news
19	- Customer reviews (G2, Capterra, Product Hunt, Reddit, App Store)
20	- Target segment
21	- Key strengths based on reviews
22	- Key weaknesses based on reviews
23
24	## Step 3 — Battlecard Structure
25
26	For each competitor, produce a one-page battlecard:
27
28	---
29
30	[Competitor Name] Battlecard
31
32	Who they are: [One sentence description — what they build and who they serve]
33	Best for: [The customer profile they're ideal for — be honest]
34	Price: [If public]
35	Key differentiators: [Their 3 strongest genuine advantages]
36
37	Where we win:
38	\| Dimension \| Us \| [Competitor] \| Why We Win \|
39	\|---\|---\|---\|---\|
40	\| [Dimension 1] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
41	\| [Dimension 2] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
42	\| [Dimension 3] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
43
44	Where they win:
45	(Be honest — your team needs to know where competitors are stronger to have credible conversations)
46	- [Area 1]: They are better at [X] for [Y type of customer]
47	- [Area 2]: They are better at [X] for [Y type of customer]
48
49	When we lose and why:
50	- [Loss scenario 1]: We tend to lose when the prospect [situation]. Handle by: [approach]
51	- [Loss scenario 2]: We tend to lose when the prospect [situation]. Handle by: [approach]
52
53	Common objections and responses:
54
55	"[Competitor] has more integrations"
56	> "[Honest, confident response that acknowledges the point and reframes toward our strength]"
57
58	"[Competitor] is cheaper"
59	> "[Response]"
60
61	"[Competitor] is more established"
62	> "[Response]"
63
64	Trap to avoid:
65	[The one thing to never say when this competitor comes up — often a claim we can't back up or a dismissal that makes us look defensive]
66
67	How to qualify:
68	Ask: "[Question that helps determine whether this prospect is better served by us or by [Competitor]"
69
70	---
71
72	## Step 4 — Competitive Response Principles
73
74	Add a section of general principles for competitive conversations:
75
76	1. Lead with the customer's problem, not our features. Ask: "What's most important to you?" before positioning.
77	2. Acknowledge genuine competitor strengths. Dismissing them loses credibility. "They're strong at X, and if X is your priority, they might be the right choice. Here's what we're strong at..."
78	3. Use specifics. "We have better memory" is weak. "We maintain context across sessions so you never re-brief — here's what that looks like..." is strong.
79	4. Know when to walk away. If a prospect's primary need is X and a competitor genuinely does X better, say so. Referrals come back.
80
81	## Step 5 — Output
82
83	Produce battlecard(s) for each competitor specified. Offer to:
84	- Save to `context/company/competitors.md`
85	- Save each card to `outputs/battlecard-[competitor]-[date].md`

People who liked this also viewed

6 picks

Type

competitor-battlecards

70stars33forks

View on GitHub

How to install competitor-battlecards?

productfculty-aipm/pm-copilot-by-product-faculty/competitor-battlecards

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill competitor-battlecards

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Competitor Battlecards
2
3	You are creating competitive battlecards — structured one-page guides that help sales, customer success, and the product team understand specific competitors and articulate our differentiators confidently.
4
5	Frameworks: April Dunford (Obviously Awesome — positioning against alternatives), Hamilton Helmer (7 Powers), Lenny Rachitsky (competitive differentiation).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context and current bets. Read `context/company/competitors.md` if it exists — use as a starting point. If WebSearch is available, research the specified competitor.
10
11	## Step 2 — Research the Competitor
12
13	For each competitor, gather:
14
15	Using WebSearch if available:
16	- Product offering and positioning
17	- Pricing (public if available)
18	- Recent changes, launches, or news
19	- Customer reviews (G2, Capterra, Product Hunt, Reddit, App Store)
20	- Target segment
21	- Key strengths based on reviews
22	- Key weaknesses based on reviews
23
24	## Step 3 — Battlecard Structure
25
26	For each competitor, produce a one-page battlecard:
27
28	---
29
30	[Competitor Name] Battlecard
31
32	Who they are: [One sentence description — what they build and who they serve]
33	Best for: [The customer profile they're ideal for — be honest]
34	Price: [If public]
35	Key differentiators: [Their 3 strongest genuine advantages]
36
37	Where we win:
38	\| Dimension \| Us \| [Competitor] \| Why We Win \|
39	\|---\|---\|---\|---\|
40	\| [Dimension 1] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
41	\| [Dimension 2] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
42	\| [Dimension 3] \| [Our capability] \| [Their capability] \| [Honest differentiator] \|
43
44	Where they win:
45	(Be honest — your team needs to know where competitors are stronger to have credible conversations)
46	- [Area 1]: They are better at [X] for [Y type of customer]
47	- [Area 2]: They are better at [X] for [Y type of customer]
48
49	When we lose and why:
50	- [Loss scenario 1]: We tend to lose when the prospect [situation]. Handle by: [approach]
51	- [Loss scenario 2]: We tend to lose when the prospect [situation]. Handle by: [approach]
52
53	Common objections and responses:
54
55	"[Competitor] has more integrations"
56	> "[Honest, confident response that acknowledges the point and reframes toward our strength]"
57
58	"[Competitor] is cheaper"
59	> "[Response]"
60
61	"[Competitor] is more established"
62	> "[Response]"
63
64	Trap to avoid:
65	[The one thing to never say when this competitor comes up — often a claim we can't back up or a dismissal that makes us look defensive]
66
67	How to qualify:
68	Ask: "[Question that helps determine whether this prospect is better served by us or by [Competitor]"
69
70	---
71
72	## Step 4 — Competitive Response Principles
73
74	Add a section of general principles for competitive conversations:
75
76	1. Lead with the customer's problem, not our features. Ask: "What's most important to you?" before positioning.
77	2. Acknowledge genuine competitor strengths. Dismissing them loses credibility. "They're strong at X, and if X is your priority, they might be the right choice. Here's what we're strong at..."
78	3. Use specifics. "We have better memory" is weak. "We maintain context across sessions so you never re-brief — here's what that looks like..." is strong.
79	4. Know when to walk away. If a prospect's primary need is X and a competitor genuinely does X better, say so. Referrals come back.
80
81	## Step 5 — Output
82
83	Produce battlecard(s) for each competitor specified. Offer to:
84	- Save to `context/company/competitors.md`
85	- Save each card to `outputs/battlecard-[competitor]-[date].md`

People who liked this also viewed

6 picks

Type