본문으로 건너뛰기
cccskills
무료GitHub에 공개

competitive-battlecard

Create a concise sales reference comparing your product with a specific competitor. Organize product and pricing differences, strengths on both sides, responses to common objections, and win/loss patterns into a Markdown document for use during sales conversations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

설치 방법 보기

이럴 때 유용합니다

  • Preparing sales teams for competitive deals
  • Answering questions about a cheaper competitor
  • Creating a feature and pricing comparison
  • Organizing win/loss patterns

포함된 파일(1)

  • SKILL.md2.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Competitive Battlecard

Create a concise, sales-ready battlecard for use against a specific competitor.

Context

You are creating a competitive battlecard for $ARGUMENTS.

Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.

Instructions

  1. Research the competitor (use web search):

    • Current product offerings and features
    • Pricing tiers and model
    • Target market and positioning
    • Recent product launches or changes
    • Known strengths and weaknesses
    • Customer reviews and sentiment (G2, Capterra, Reddit)
  2. Create the battlecard with these sections:

    Company Overview

    • Founded, HQ, funding/revenue (if public)
    • Target market and ICP
    • Positioning in one sentence

    Quick Comparison

    CapabilityUsThemWinner
    [Feature area 1][Our approach][Their approach][Us/Them/Tie]
    [Feature area 2].........
    Pricing.........
    Support.........

    Where We Win

    • [Advantage 1]: [Proof point or customer quote]
    • [Advantage 2]: [Specific capability they lack]
    • [Advantage 3]: [Better approach with reasoning]

    Where They Win

    • [Their strength 1]: [Our counter-positioning]
    • [Their strength 2]: [How we mitigate this gap]

    Common Objections & Responses

    Prospect SaysRespond With
    "Competitor X has [feature]""[Our alternative approach and why it's better for them]"
    "They're cheaper""[Value framing: total cost of ownership, ROI, hidden costs]"
    "They're more established""[Our advantages: speed, innovation, focus, support]"

    Landmines to Plant

    Questions to ask the prospect that highlight competitor weaknesses:

    • "How important is [area where we excel] to your team?"
    • "Have you evaluated [specific capability they lack]?"

    Win/Loss Patterns

    • We tend to win when: [pattern]
    • We tend to lose when: [pattern]
    • Key differentiator in competitive deals: [what tips the scale]
  3. Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.

Save as markdown. Format for easy printing or sharing in Notion/Confluence.


Further Reading

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

phuryn의 스킬 모두 보기

이 스킬의 문제 신고