sales-motion-design
When the user wants to choose between PLG and sales-led, design a sales motion, optimize time-to-first-value, or build a value-before-purchase experience. Also use when the user mentions 'PLG,' 'product-led growth,' 'sales-led,' 'sales motion,' 'free trial,' 'freemium,' 'self-serve,' 'demo-first,' 'time-to-first-value,' 'TTFV,' or 'agent-led sales.' This skill covers sales motion selection, value delivery design, and go-to-market motion architecture. Do NOT use for technical implementation, code review, or software architecture.
What this skill does
# 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), PQL scoring
model, CRM integration to surface PQLs, clear product-to-sales handoff.
**Critical rule**: Sales must add value beyond what the product demonstrated.
Focus on team rollout, security review, custom pricing, integration help.
### 2C. Sales-Assisted PLG
**When it works**: Higher price, simple enough for try-before-buy.
**Examples**: Figma Enterprise, GitHub Enterprise, Airtable Enterprise.
Bottom-up adoption triggers top-down sale. Free individual tier ($0-20/user/mo)
feeds adoption. Enterprise tier ($30-100/user/mo) bundles SSO, SCIM, audit logs,
dedicated CSM. The gap creates a natural sales conversation.
**Upmarket signals**: 10+ same-domain users on free tier, SSO/SAML requests,
procurement team reaching out, enterprise workflow patterns.
### 2D. Sales-Led
**When it works**: High price, high complexity, multi-stakeholder buying
committee, security/compliance review required.
**Examples**: Salesforce, Workday, Snowflake (enterprise), Palantir.
| Metric | Median | Top Quartile |
|--------------------------|-------------|--------------|
| Lead to opportunity | 13-15% | 20%+ |
| Opportunity to close | 20-25% | 30%+ |
| Average sales cycle | 90-180 days | 60-90 days |
| CAC payback (months) | 18-24 | 12-15 |
Even sales-led motions benefit from interactive demos, sandboxes, and POCs.
The difference is a human guides the process rather than the product alone.
### 2E. Agent-Led Discovery (Emerging, 2025-2026)
**What it is**: AI agents handle prospecting, qualification, initial outreach,
and meeting scheduling. Humans handle discovery calls, demos, negotiation, and
closing.
**Current reality check (2026 data)**:
| Metric | Current State |
|-------------------------------------|----------------------|
| Pipeline growth (well-implemented) | 3-8x |
| CAC reduction (best case) | 30-42% lower |
| Failure rRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".