openclaw-skills/marketing-strategy-pmm/SKILL.md
Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry.
npx skillsauth add seaworld008/commonly-used-high-value-skills marketing-strategy-pmmInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Product marketing patterns for positioning, GTM strategy, and competitive intelligence.
Use this skill when the user wants to:
Recommended flow:
define target customer
-> shape positioning
-> assess competition
-> build launch and enablement materials
-> adapt for market or segment expansion
Define ideal customer profile for targeting:
| Dimension | Target Range | Rationale | |-----------|--------------|-----------| | Employees | 50-5000 | Series A sweet spot | | Revenue | $5M-$500M | Budget available | | Industry | SaaS, Tech, Services | Product fit | | Geography | US, UK, DACH | Market priority | | Funding | Seed to Growth | Willing to adopt |
Economic Buyer (signs contract):
Technical Buyer (evaluates product):
User/Champion (advocates internally):
Develop positioning using April Dunford methodology:
FOR [target customer]
WHO [statement of need]
THE [product] IS A [category]
THAT [key benefit]
UNLIKE [competitive alternative]
OUR PRODUCT [primary differentiation]
Template: [Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]
Example: "Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI"
| Level | Content | Example | |-------|---------|---------| | Headline | 5-7 words | "Ship faster with AI automation" | | Subhead | 1 sentence | "Automate workflows so teams focus on what matters" | | Benefits | 3-4 bullets | Speed, quality, collaboration, cost | | Features | Supporting evidence | AI automation → 10 hrs/week saved | | Proof | Social proof | Customer logos, stats, case studies |
Build competitive knowledge base:
| Tier | Definition | Examples | |------|------------|----------| | 1 | Direct competitor, same category | [Competitor A, B] | | 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] | | 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |
COMPETITOR: [Name]
OVERVIEW: Founded [year], Funding [stage], Size [employees]
POSITIONING:
- They say: "[Their claim]"
- Reality: [Your assessment]
STRENGTHS:
1. [What they do well]
2. [What they do well]
WEAKNESSES:
1. [Where they fall short]
2. [Where they fall short]
OUR ADVANTAGES:
1. [Your advantage + evidence]
2. [Your advantage + evidence]
WHEN WE WIN:
- [Scenario where you win]
WHEN WE LOSE:
- [Scenario where they win]
TALK TRACK:
Objection: "[Common objection]"
Response: "[Your response]"
Track monthly:
Plan launches by tier:
| Tier | Scope | Prep Time | Budget | |------|-------|-----------|--------| | 1 | New product, major feature | 6-8 weeks | $50-100k | | 2 | Significant feature, integration | 3-4 weeks | $10-25k | | 3 | Small improvement | 1 week | <$5k |
Execute major product launch:
| Metric | Leading (Daily) | Lagging (Weekly) | |--------|-----------------|------------------| | Traffic | Landing page visitors | - | | Engagement | Demo requests, signups | Feature adoption % | | Pipeline | MQLs generated | SQLs, pipeline $ | | Revenue | - | Deals closed, revenue |
Equip sales team with PMM assets:
| Slide | Content | |-------|---------| | 1-2 | Title, agenda | | 3-4 | Company intro, problem statement | | 5-7 | Solution, key benefits, demo | | 8-10 | Differentiation, case study, pricing | | 11-12 | Implementation, support, next steps |
1. Intro (2 min): Who we are, agenda
2. Discovery (5 min): Their needs, pain points
3. Demo (20 min): Product focused on their use case
4. Q&A (10 min): Objection handling
5. Next steps (3 min): Trial, POC, proposal
| Handoff | Frequency | Content | |---------|-----------|---------| | Weekly sync | 30 min | Win/loss, competitive, new assets | | Monthly enablement | 60 min | Product updates, training | | Quarterly review | Half-day | Results, strategy, planning |
Enter new markets systematically:
| Market | Timeline | Budget % | Target ARR | |--------|----------|----------|------------| | US | Months 1-6 | 50% | $1M | | UK | Months 4-9 | 20% | $500k | | DACH | Months 7-12 | 15% | $300k | | France | Months 10-15 | 10% | $200k | | Canada | Months 7-12 | 5% | $100k |
references/positioning-frameworks.md contains:
references/launch-checklists.md contains:
references/international-gtm.md contains:
references/messaging-templates.md contains:
| Metric | Target | Measurement | |--------|--------|-------------| | Product adoption | >40% in 90 days | Feature usage after launch | | Win rate | >30% competitive | Deals won vs. competitors | | Sales velocity | -20% YoY | Days from SQL to close | | Deal size | +25% YoY | Average contract value | | Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |
| Week | Focus | |------|-------| | 1 | Review metrics, update battlecards | | 2 | Create assets, publish content | | 3 | Support launches, optimize campaigns | | 4 | Monthly report, plan next month |
tools
飞书审批:查询和处理审批待办/已办/实例,搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务;非审批类待办走 lark-task。不负责创建审批定义;三方审批定义不走原生提单。
development
Use when a user needs reproducible repository sizing, language composition, file counts, or code-versus-comment ratios with pygount; record exclusions and verify measurement scope before interpreting results.
development
Route a development task to the official Hermes Agent skill, Graphify Codex artifact set, Open GSD Core bundle, or optional GSD Pi bundle without duplicating their installers or state machines.
development
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。