agent-orchestration-ad…
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as…
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Claude Code
$ npx -y skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor --agent claude-code
Codex
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a codex -y
Cursor
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a cursor -y
Gemini CLI
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a gemini-cli -y
GitHub Copilot
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a github-copilot -y
OpenCode
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a opencode -y
Windsurf
$ npx skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor -a windsurf -y
name: acquisition-channel-advisor argument-hint: "[channel to evaluate]" description: Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel. intent: >- Guide product managers through evaluating whether to scale, test, or kill an acquisition channel based on unit economics (CAC, LTV, payback), customer quality (retention, NRR), and scalability (magic number, volume potential). Use this to make data-driven go-to-market decisions and optimize channel mix for sustainable growth. type: interactive best_for: - "Deciding whether a paid or outbound channel deserves more budget" - "Comparing channel quality, payback, and scalability side by side" - "Making scale, test, or kill decisions with finance-backed reasoning" scenarios: - "Should we keep investing in paid LinkedIn ads for enterprise leads?" - "Compare content marketing, outbound email, and partner referrals as acquisition channels" - "Help me decide whether to scale or kill our webinar acquisition channel" theme: finance-metrics estimated_time: "15-25 min"
Guide product managers through evaluating whether to scale, test, or kill an acquisition channel based on unit economics (CAC, LTV, payback), customer quality (retention, NRR), and scalability (magic number, volume potential). Use this to make data-driven go-to-market decisions and optimize channel mix for sustainable growth.
This is not a channel strategy framework—it's a financial lens for channel evaluation that helps you avoid scaling unprofitable channels or killing channels with fixable problems. Use when deciding how to allocate marketing budget across channels.
**Works best with:** The acquisition channel you're evaluating (e.g., paid search, outbound SDR, partner referrals). **Also useful:** Any metrics you already have — CAC, LTV, payback period, retention/NRR by channel — plus company stage and the decision on the table (scale, test, or kill).
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
**Arriving empty-handed? That works too.** The advisor opens by asking which channel you're evaluating and what data you have.
**Example invocation:** `Evaluate our paid LinkedIn channel: CAC $2,400, LTV $9,000, 14-month payback, flat retention vs. organic.`
A systematic approach to evaluate acquisition channels:
1. **Unit Economics** — What does it cost to acquire, and what's the return?
2. **Customer Quality** — Do customers from this channel stick around and expand?
3. **Scalability** — Can this channel sustain growth at the volume you need?
4. **Strategic Fit** — Does this channel align with your go-to-market strategy?
| LTV:CAC | Payback | Customer Quality | Scalability | Decision | |---------|---------|------------------|-------------|----------| | >3:1 | <12mo | Good retention | High volume | **Scale aggressively** | | 2-3:1 | 12-18mo | Average retention | Medium volume | **Test & optimize** | | <2:1 | >18mo | Poor retention | Low volume | **Kill or fix** |
**Use this when:**
**Don't use this when:**
---
Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.
**Default entry mode:** Guided · set in `pm-skills.config.yaml` (library-wide default or a per-skill override); the user's own choice in the session always wins. On the first turn, offer all three modes, then open in the default without waiting for a pick: Guided asks the first question, Context dump invites the paste, Best guess asks for a one-sentence minimum and drafts with every assumption labeled.
It defines:
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This
77 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as…
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability…
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or…
Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next…
The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate,…
Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a…
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…