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

funnel-strategy

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).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.1 KB

SKILL.md(原文)

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

Funnel strategy

Map how a buyer moves from first touch to renewal, in the shape this company actually sells. The motion decides the stages: a product-led company and a sales-led company should not share a funnel. Every stage separates what the team does (inputs) from what it measures (outputs), and the maths runs backwards from the revenue target.

When to use it

  • Building the context folder, after positioning and messaging, before /goals.
  • Setting up or cleaning up CRM stages.
  • When marketing and sales disagree on what a qualified lead is.

Don't use it to set the revenue target (/goals takes a target someone has already committed to) or to design individual campaigns.

Inputs

Required: the company website URL.

Recommended: context/company/ (deal size, team size, funding sharpen the motion call), context/icp/ (buying triggers shape qualification), the real CRM stages if they exist (they override anything inferred), pricing or average deal size.

Paths. Write to context/goals/MMYY-funnel.md, next to the scope file /goals will write. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Tools. Page fetching and web search. Exa helps with company research if you have it.

Steps

  1. Read the signals. Homepage CTA ("Start free" vs "Book a demo"), pricing (self-serve checkout vs "Contact sales"), free trial or freemium, docs and API in the navigation, average deal size, sales team size.

  2. Call the motion.

    • Product-led: signals point to self-serve.
    • Sales-led: they point to demos and sales.
    • Hybrid: both are strong.
    • Unclear: ask the user.

    State it with your two or three strongest signals and a confidence level.

  3. Pick the stage set for that motion only. Don't mix product-led stages into a sales-led funnel. Hybrid runs two tracks with a rule for when a product user gets routed to sales.

  4. Define each pre-sale stage:

    • a definition for this company
    • the strategy
    • inputs: leading activities the team controls, with a frequency ("3 LinkedIn posts a week")
    • outputs: lagging results with a target ("500 visitors a month")
    • cadence and owner

    Never put a metric in the inputs.

  5. Set qualification criteria. 3 to 5 measurable signals each for MQL (marketing to sales), SQL (confirmed by sales) and, for product-led or hybrid, PQL (product usage). "Good fit" isn't a criterion; "50+ employees and visited pricing twice" is.

  6. Map closed-lost re-entry. Loss reason, which stage they re-enter, the trigger and the timing.

  7. Map post-sale stages in the same format: onboarding (the path to first value), retention, expansion, churn prevention. Match the motion: product-led is in-app, sales-led is account-manager driven.

  8. Run the backward maths if there's a revenue target. Revenue to deals, deals to opportunities, then SQLs, MQLs, leads and traffic, using real conversion rates where you have them and marked estimates where you don't. Check whether current volumes can get there.

  9. Draw the journey as a simple text diagram from first touch to expansion.

  10. List gaps and recommendations, then hand off to /goals.

Output shape

  1. Motion assessment table: signal, what you saw, what it points to.
  2. Pre-sale stages, each in the same format.
  3. Qualification criteria.
  4. Post-sale stages.
  5. Closed-lost re-entry table.
  6. Journey diagram.
  7. Backward maths (if a target exists).
  8. Gaps and recommendations.
  9. Sources with URLs and confidence.

What good looks like

  • The motion is backed by at least three signals.
  • Every input has a frequency, every output a target, every stage a cadence and an owner.
  • Inputs and outputs never swap places.
  • Qualification criteria are thresholds someone could put into a CRM.
  • Post-sale matches pre-sale. A product-led company doesn't suddenly get a customer-success-led renewal motion.

Mistakes to avoid

  • Inventing stages the company doesn't run, instead of asking for the real ones.
  • Assuming the motion from the category ("it's dev tools, so it's product-led").
  • Making up conversion rates or KPI targets without marking them as estimates.
  • One funnel template forced onto every company.

Chain

Step 10 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日 更新

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日 更新

Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).

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

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

matteotitta のスキルをすべて見る

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