本文へ移動
cccskills
無料GitHub で公開

positioning

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Positioning

Decide what you are, who it's for, what they'd use instead, and why you're the better choice, in words a buyer understands in five seconds. The method follows the public April Dunford school: start from the competitive alternatives buyers actually consider, and build out from there.

When to use it

  • The homepage doesn't explain what you do, or demos start with "so what is it exactly?".
  • You're choosing between going broad and niching down.
  • A new product, a new segment, or a competitor that moved.

Don't use it for taglines, value props or a full messaging library (/messaging, which runs after this), or for research you haven't done yet.

Inputs

Required: company name, a short description and the website URL.

Recommended: context/icp/, context/competitors/, context/win-loss/ and context/expert-pov/. Positioning without ICP and competitor evidence is opinion. If those are missing, say so, run what you can, and offer /icp-research and /competitor-research first.

Paths. Write to context/positioning/MMYY-positioning.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Steps

  1. Read the current state. Fetch the homepage, pricing and about pages. Run the five-second test: do the headline and sub-headline say what it is and who it's for? Note the category, differentiation and ICP the site claims today.

  2. Map the alternatives. What would a buyer do if you didn't exist?

    • do it manually
    • keep a legacy tool
    • buy a direct competitor
    • stretch an adjacent tool
    • do nothing
    • build it with a general AI assistant

    Rank them by how often they show up in deals.

  3. Map the anchors. What could the positioning hang on?

    • an activity
    • a product category
    • a use case
    • a problem
    • a persona
    • a competitive alternative ("the X alternative for Y")

    Score the promising combinations on clarity, differentiation and relevance to the ICP.

  4. Make the binary choice. Category-led (buyers already know the category and you win inside it) or problem-led (the category is new, crowded or wrong, so you lead with the pain). Use an activity anchor only when no software category fits.

  5. Lay out the options. Take the top 2 to 4 combinations (3 by default) and work each one up:

    • primary and secondary anchor
    • a hero headline and sub-headline
    • the value in three parts: category, problem, differentiation
    • who it's for
    • the bet it makes
    • the risks

    Each option must change the anchor or the binary choice. No rewording of the same bet.

  6. Build the comparison canvas. One column per option, rows for clarity, differentiation, ICP relevance, proof available, competitive exposure and risk. Mark each cell's confidence: verified, inferred, estimated or unknown. Recommend one and name the trade-off each option forces. The user decides.

  7. Lock the chosen option. Up to three differentiators, each one a thing you'd guarantee with money on the line (pass, partial or fail). Name the primary competitive alternative and the market focus, with simple TAM maths (average deal size × customers needed).

  8. Run the clarity ladder. Compress the position to one word, one phrase, one sentence and one paragraph. If a level fails, go back to the anchors.

  9. Write the positioning statement in the form that fits the anchor:

    • Use case: "We help [persona] [do the job] without [friction], by [approach]."
    • Category: "We are a [category] that [differentiator], unlike [alternative] which [weakness]."
    • Alternative: "We're the [leader] alternative that [upgrade], for [persona] who [unmet need]."
    • Activity: "We help [persona] [do activity], replacing [manual process] with [mechanism]."
  10. Map the implications. What changes for messaging, for the ICP, and which channel leads with which facet (homepage: primary anchor; comparison pages: the alternative; case studies: proof that matches the anchor).

  11. Hand off to /messaging.

Output shape

Open with a TLDR (the one-sentence position) and one block of open decisions. Then: current state, alternatives, the options with the canvas, the committed position (anchors, differentiators with guarantee verdicts, statement, clarity ladder), implications, and sources. Each caveat is stated once.

What good looks like

  • A stranger reads the hero and knows what it is and who it's for in five seconds.
  • No more than three differentiators, each one provable.
  • The comparison set matches the buyer. Compare to other vendors only when buyers already use the category.
  • The options are real choices, not three phrasings of one idea.
  • The TAM maths is realistic, not hopeful.

Mistakes to avoid

  • "The platform for X" with nothing else.
  • "AI-powered" as the main differentiator.
  • Inventing a category nobody searches for.
  • Choosing the position before mapping the alternatives.
  • Differentiators you couldn't prove to a sceptical buyer.

Chain

Step 8 of the suggested chain: /company-context → /icp-research → /competitor-research → /win-loss → /expert-pov → /tov-guidelines → /brand-kit → positioning → /messaging → /funnel-strategy → /goals.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

brand-kit

無料

Extracts a company's visual identity from screenshots (best) or its website (fallback) and writes a DESIGN.md brand file: machine-readable tokens for colours, typography, spacing, corner radius and logo usage, plus short prose explaining how and when to use each, and a list of do's and don'ts. Any later page, deck, carousel or ad can read the tokens instead of guessing. Triggers: "brand kit", "brand guidelines", "extract our brand", "design tokens", "colours and fonts from", "visual identity", "DESIGN.md". Not for tone of voice (use /tov-guidelines) or messaging (use /messaging).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches a company from its website and public sources and writes a company profile: what it sells, who buys it, traction, funding, team, hiring, tech stack, key people, red flags and the gaps you still need to fill, every claim tagged with a source and a confidence level. Use it as the first file in a marketing context folder, or to prep a discovery call or qualify a prospect. Triggers: "company research", "company background", "company context for", "qualify this prospect", "discovery call prep", "account brief", or a company URL handed over for research. Not for competitor analysis (use /competitor-research) or customer profiles (use /icp-research).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Works out a company's go-to-market motion (product-led, sales-led or hybrid) from its website and pricing, then maps the funnel stage by stage: a definition, strategy, leading inputs the team controls, lagging outputs with targets, cadence and owner for each stage, MQL, SQL and PQL criteria, post-sale stages, closed-lost re-entry paths and backward funnel maths from a revenue target. Triggers: "funnel strategy", "funnel stages", "pipeline stages", "PLG vs SLG", "lead qualification criteria", "map our sales process", "how do leads flow". Feeds /goals. Not for setting the target itself (use /goals).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

goals

無料

Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

matteotitta のスキルをすべて見る

このスキルの問題を報告する