agent-orchestration-ad…
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead…
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
$ npx -y skills add deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/acquisition-channel-advisorContext preview
The summary Claude sees to decide when to auto-load this skill.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
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.
It defines:
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks **up to 4 adaptive questions**, offering **3-5 enumerated options** at decision points.
---
**Agent asks:**
"Let's evaluate this acquisition channel. Please provide:
**Channel details:**
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 parallel specialized agents instead…
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from,…
The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence…
Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research…