artifacts/bundle/skills/marketing-skill/marketing-strategy-pmm/SKILL.md
# Marketing Strategy & PMM Product marketing patterns for positioning, GTM strategy, and competitive intelligence. --- ## Table of Contents - [ICP Definition Workflow](#icp-definition-workflow) - [Positioning Development](#positioning-development) - [Competitive Intelligence](#competitive-intelligence) - [Product Launch Planning](#product-launch-planning) - [Sales Enablement](#sales-enablement) - [International Expansion](#international-expansion) - [Reference Documentation](#reference-docum
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/marketing-skill/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.
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 |
| Persona | Title | Goals | Messaging | | --------------- | ---------------------------------- | -------------------------------------- | ------------------------------------- | | Economic Buyer | VP, Director, Head of [Department] | ROI, team productivity, cost reduction | Business outcomes, ROI, case studies | | Technical Buyer | Engineer, Architect, Tech Lead | Technical fit, easy integration | Architecture, security, documentation | | User/Champion | Manager, Team Lead, Power User | Makes job easier, quick wins | UX, ease of use, time savings |
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 |
| When you ask for... | You get... | | ------------------------- | -------------------------------------------------------- | | "Position my product" | Positioning framework (April Dunford method) with output | | "GTM strategy" | Go-to-market plan with channels, messaging, and timeline | | "Competitive positioning" | Positioning map with competitive gaps and opportunities |
All output passes quality verification:
Creator: Marketing Skill License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:marketing-skillOriginal Path:marketing-skill/marketing-strategy-pmm
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski