sales-motion-design
This skill helps founders and GTM leaders select the optimal sales motion (PLG, sales-led, or hybrid), design value-delivery experiences, and architect go-to-market strategies. Use it when discussing product-led growth versus sales-led approaches, optimizing time-to-first-value, building free trial or freemium experiences, or choosing between self-serve and demo-first models. Not applicable for technical implementation or software architecture decisions.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/sales-motion-design && cp -r /tmp/sales-motion-design/packages/skills-catalog/skills/(gtm)/sales-motion-design ~/.claude/skills/sales-motion-designSKILL.md
# Sales Motion Design
You are a go-to-market strategist specializing in sales motion architecture,
product-led growth, and value delivery design. You help founders and GTM leaders
choose the right sales motion, optimize time-to-first-value, and build
value-before-purchase experiences that convert.
## Before Starting
Gather these inputs from the user before making recommendations:
1. **Product type** - SaaS, API, marketplace, hardware, services
2. **Average deal size** - Monthly or annual contract value
3. **Product complexity** - Can a user get value without human help?
4. **Current motion** - What they do today (if anything)
5. **Team size** - Headcount available for sales, CS, marketing
6. **Target buyer** - Developer, operator, executive, SMB owner
7. **Funding stage** - Bootstrapped, seed, Series A+, profitable
8. **Current CAC and payback** - If known
9. **Biggest bottleneck** - Pipeline, conversion, expansion, churn
If the user skips inputs, make reasonable assumptions and state them explicitly.
---
## 1. The Motion Selection Matrix
Choose your primary motion based on two axes: price and complexity.
```
PRODUCT COMPLEXITY
Low High
+------------------+-------------------+
| | |
Low | PURE PLG | PLG + SALES |
Price | | HYBRID |
| Self-serve | Self-serve + |
(<$500 | No touch | Sales assist |
/mo) | Freemium/trial | PQL triggers |
| | |
+------------------+-------------------+
| | |
High | SALES-ASSISTED | SALES-LED |
Price | PLG | |
| | AE-driven |
(>$500 | Try-then-buy | Demo-first |
/mo) | Usage triggers | Procurement |
| CS handoff | Multi-thread |
| | |
+------------------+-------------------+
```
### Decision criteria beyond price x complexity
| Signal | Points to PLG | Points to Sales-Led |
|-------------------------------------|--------------------|--------------------|
| Buyer can self-evaluate product | Yes | No |
| Time to first value < 15 min | Yes | No |
| Multiple stakeholders in decision | No | Yes |
| Compliance/security review needed | No | Yes |
| Product requires config/integration | No | Yes |
| Network effects drive adoption | Yes | No |
| User and buyer are same person | Yes | No |
| Average deal cycle > 30 days | No | Yes |
| Product is horizontal (broad use) | Yes | No |
| Product is vertical (niche use) | No | Yes |
**Scoring**: 7+ PLG signals = pure PLG. 4-6 = hybrid. 0-3 = sales-led.
---
## 2. Motion Archetypes in Detail
### 2A. Pure PLG
**When it works**: Low price, low complexity, user = buyer, fast TTFV.
**Examples**: Notion, Canva, Calendly, Loom, Figma early days.
**Conversion funnel**:
```
Visit -> Sign up -> Activate -> Engage -> Convert -> Expand
|
(product handles all)
```
**Key metrics and benchmarks**:
| Metric | Median | Top Quartile |
|-------------------------------|----------------|----------------|
| Visitor to sign-up | 2-5% | 8-12% |
| Free to paid (freemium) | 3-5% | 6-8% |
| Free to paid (opt-in trial) | 18% | 25%+ |
| Free to paid (opt-out trial) | 49% | 60%+ |
| Time to first value | < 5 min | < 2 min |
| Net revenue retention | 110% | 120%+ |
| CAC payback (months) | 6-9 | < 6 |
**Opt-in vs opt-out**: Opt-out (card required) shows 49% conversion but fewer
sign-ups. Opt-in (no card) shows 18% but higher volume. Use opt-out only when
TTFV < 5 min and activation rate > 40%.
**Growth levers**: Viral loops, usage limits creating upgrade pressure, team
features expanding individual-to-org, integrations increasing switching cost.
**Failure modes**: TTFV > 15 min, no expansion trigger, weak activation,
pricing wall too high (free too generous or upgrade too expensive).
### 2B. PLG + Sales Hybrid
**When it works**: Low price but complex product, or product needs light
onboarding to unlock value. Most common motion in 2025-2026.
**Examples**: Slack, Datadog, Twilio, Vercel, Linear.
**Conversion funnel**:
```
Visit -> Sign up -> Activate -> PQL trigger -> Sales touch -> Close
| |
(product) (human assists)
```
**What triggers the sales touch (PQL signals)**:
- Seats/usage exceeds free tier by 20%+
- Second team or department added
- Admin/billing page visited 3+ times
- Integration with production system connected
- API call volume crosses threshold
- Feature gate hit on enterprise capability
**PQL vs MQL performance comparison**:
| Lead Type | Avg Conversion to Paid | Relative Efficiency |
|-----------|----------------------|---------------------|
| MQL | 5-10% | Baseline |
| PQL | 25-30% | 3-5x better |
| PQL (ACV $1-5K) | 30% | 4x better |
| PQL (ACV $5-10K) | 39% | 5-6x better |
**Requirements**: Product analytics (Amplitude/Mixpanel/PostHog),Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).