agentleFS
UsermuseUsermuse/em-plugin/skills/gtm-strategy/SKILL.md

gtm-strategy

Skill0 starsChanged 3 months agoMITView on GitHub

Build a go-to-market strategy — messaging, channels, segment focus, GTM motions, metrics, and a launch timeline — where every choice is anchored in real customer evidence, not guesswork. Use when the user says 'plan the launch', 'build a GTM plan', 'how do we take this to market', 'what channels should we use', 'inbound or outbound', 'go-to-market strategy', or 'launch strategy'. Trigger terms: go-to-market, GTM, launch plan, GTM motions, marketing channels, launch strategy, distribution. Not for a single feature spec or an internal roadmap — this is how the product reaches its market.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Required — one parallel batch of searches: Verify the product (Rule 1), then fire in a single parallel batch:

    line 29
  2. Very specific:

    After saving, offer next steps: "Lock the beachhead?" (/evermuse:beachhead-segment), "Sharpen positioning & campaigns?" …

    line 94

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GTM Strategy

Produce a go-to-market strategy — target segment, messaging, channel/motion mix, success metrics, and a phased launch plan — where the segment choice, each message, and each channel is justified by what customers actually said and the market context around them. Grounding turns a plausible launch deck into one you can defend with quotes.

Step 0 — Relevance & availability

Confirm this is a launch / go-to-market task and Evermuse is connected. If the tools aren't present, produce a framework-only GTM plan labeled ⚠ ungrounded — Evermuse not connected and tell the user to authorize the MCP. See ${CLAUDE_PLUGIN_ROOT}/skills/using-evermuse/SKILL.md Step 0.

Evermuse Grounding (required)

Follow ${CLAUDE_PLUGIN_ROOT}/skills/using-evermuse/SKILL.md.

Required — one parallel batch of searches. Verify the product (Rule 1), then fire in a single parallel batch:

  • 3–4 evidence searches, each worded from a different angle (limit up to 50). Evidence comes back rich and varied — expect large, useful result sets.
  • one guidance search and one context search (limit up to 50). These are usually sparse or empty; run them anyway and note when they're thin.

Read each response's digest — it reports how many more results exist. Use judgment on whether a query is worth pulling deeper (raise limit toward the 100 max and/or page with next_offset to avoid repeats), weighing payload size, remaining context, task complexity, and the value of the data. For deep pulls, consider spawning sub-agents — instruct them to return every citation with the same metadata the tools return (url, who_said_it, meeting_name, created_at) so you can still cite.

Optional — considered use. Once grounded, reach for the other tools only when they add value: a quote-angled search for verbatim voice, read_source for a single deep dive, inline citations (references/citations.md), and add_source to save the deliverable. Sources, citations, and saving are optional — not required.

Instructions

You are planning the go-to-market for $ARGUMENTS. Where the source method reaches for "web search / user-provided data," use Evermuse evidence (customer voice) as the primary source and context (market) as secondary.

1. Target segment & positioning

Name the segment you launch into and why — the strongest, most-cited burning pain wins. Anchor it in an evidence quote. (If the beachhead is genuinely undecided, run /evermuse:beachhead-segment first and feed its result here.) State the one-line value proposition in the customer's language.

2. Messaging — mined, not invented

Develop messaging where every message maps to a verbatim quote that proves it resonates:

  • Core value proposition for the segment (the "what after" they described).
  • 3–5 key differentiators — each tied to a pain quote (evidence) or a gap in an alternative (context).
  • Proof points: the sharpest customer quotes, reusable as social proof.
  • Channel-specific variations only where the audience differs. Reject any message you can't back with a quote — that is the tell of a generic deck.

3. Channels & GTM motions

Choose the acquisition mix. Score the 7 GTM motions for this product (below), ground the top choices in where evidence shows customers actually found tools like ours, then commit to a motion stack of 2–4: one primary, the rest complementary, in a sequence.

The 7 GTM motions (pick the fit, don't run all seven):

  • Inbound — content, SEO, webinars, thought leadership. Best for B2B SaaS, technical buyers, long cycles. Slow to compound but builds authority.
  • Outbound — cold email, LinkedIn, ABM-style prospecting. Best for enterprise, high ACV, niche lists. Predictable but resource-heavy.
  • Paid digital — search/social/display ads, retargeting. Fast and measurable; expensive and needs constant tuning.
  • Community — forums, Slack/Discord, user groups, ambassadors. Low CAC, high loyalty; slow to reach critical mass.
  • Partners — integrations, co-marketing, marketplaces, resellers. Borrowed reach and credibility; alignment overhead.
  • ABM — high-value accounts treated as individual markets. Higher conversion and deal size; not SMB-scalable.
  • PLG — free trial/freemium, in-app onboarding, self-serve. Low CAC and strong PMF signal; demands an excellent product experience.

Match to product reality: ACV, sales-cycle length, buyer type, complexity, and where the evidence shows these customers already hang out. Most launches win with 2–4 complementary motions (e.g. inbound for brand + outbound for pipeline; PLG to lower CAC + paid to accelerate a proven channel).

4. Success metrics

Define KPIs across the funnel: awareness (reach), engagement (CTR, activation), conversion (signups, demos, trials), revenue (MRR, CAC, LTV), and market (segment penetration). Establish baselines before launch. For a formal North Star + input-metric tree, hand off to /evermuse:north-star-metric.

5. Launch plan (90 days)

Phase it: pre-launch (assets, channel setup, baseline metrics) → launch (announcement, activities) → post-launch momentum (content, partnerships, community) → measure & optimize cadence, with go/no-go criteria.

Deliverable format

# GTM Strategy — [product]

**Target segment:** [segment] — burning pain: > "[quote]" — [attribution] [`1`](URL). Why now: [context, cited [`2`](URL)].

**Positioning (one line):** [value prop in customer language]

**Messaging**
| Message | Proof quote (evidence) | Maps to differentiator |
|---|---|---|
| [message] | > "[verbatim]" — [attribution] [`3`](URL) | [diff] |

**Motion stack:** Primary — [motion] ([why, grounded [`4`](URL)]); Secondary — [motion(s)]. Sequence: [order].

**Success metrics:** North Star [metric] · Funnel KPIs [awareness → revenue] · Baselines [values].

**90-day launch plan:** Pre-launch → Launch → Post-launch → Optimize. Go/no-go: [criteria].

Save & hand off

After saving, offer next steps: "Lock the beachhead?" (/evermuse:beachhead-segment), "Sharpen positioning & campaigns?" (/evermuse:positioning-and-messaging), "Define the North Star?" (/evermuse:north-star-metric), or "Build a battlecard for the top competitor?" (/evermuse:competitive-battlecard).


Further reading

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.