Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill acquisition-channel-advisor
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:
| 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 as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)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:
Customer acquisition:
Business context:
You can provide estimates if you don't have exact numbers."
Agent calculates (if not provided):
CAC = Monthly Spend / Customers Acquired per Month
Agent asks:
"Now let's compare this channel's unit economics to your blended metrics.
Channel Unit Economics:
Questions:
Based on answers, agent calculates:
Agent flags:
Agent asks:
"How do customers from this channel perform compared to other channels?
Retention & Expansion:
Based on answers, agent evaluates:
Agent flags:
Agent asks:
"Can this channel scale to meet your growth targets?
Efficiency & Volume:
Based on answers, agent evaluates:
Agent synthesizes:
Agent offers 3-4 recommendations:
When:
Recommendation:
"Scale this channel aggressively — Excellent economics + scalability
Unit Economics:
Customer Quality:
Scalability:
Why this is a winner:
How to scale:
Expected impact:
Risk: Low. Strong unit economics support aggressive scaling."
When:
Recommendation:
"Test & optimize before scaling — Marginal economics, fixable
Current State:
Customer Quality:
Diagnosis:
[One of these:]
How to optimize:
If CAC is the problem:
If LTV is the problem:
If targeting is the problem:
Timeline:
Don't scale yet: Current economics are break-even at best. Fix first, then scale."
When:
Recommendation:
"Kill this channel (or pause) — Economics don't support investment
Why:
Problem:
Customer Quality:
What's broken:
[Specific diagnosis:]
Should you fix or kill?
Fix if:
Kill if:
Recommendation: Kill and reallocate budget
Reallocate to:
What to do with budget:
Exception: If this channel is <10% of total S&M spend, just pause it. Not worth fixing."
When:
Recommendation:
"Continue, but cap investment — Strategic value > short-term ROI
Financial Reality:
Why continue despite poor economics:
How to manage:
Timeline:
Risk: You're subsidizing growth. Make sure it's worth it."
If user has multiple channels, agent can generate:
| Channel | CAC | LTV | LTV:CAC | Payback | Magic Number | Quality | Recommendation |
|---------|-----|-----|---------|---------|--------------|---------|----------------|
| Google Ads | $500 | $2,000 | 4:1 | 8mo | 0.9 | High | Scale |
| Content | $200 | $1,500 | 7.5:1 | 4mo | 1.2 | High | Scale |
| Outbound | $10K | $50K | 5:1 | 18mo | 0.6 | Medium | Optimize |
| Events | $15K | $30K | 2:1 | 24mo | 0.3 | Low | Kill |
Budget allocation recommendation:
See examples/ folder for sample conversation flows. Mini examples below:
Channel: Organic content (blog, SEO)
Recommendation: Scale aggressively. Exceptional unit economics, fast payback, high-quality customers. Increase content spend 2-3x.
Channel: Google Ads
Recommendation: Test & optimize before scaling. CAC is high, onboarding is weak for this segment. Improve landing page, target higher-intent keywords, better onboarding for paid customers.
Channel: Industry events
Recommendation: Kill. CAC too high, payback too long, poor customer quality. Reallocate budget to content and paid search.
Symptom: "Let's 10x our Google Ads spend!" (LTV:CAC is 1.5:1)
Consequence: You accelerate cash burn without improving unit economics. Lose money faster.
Fix: Only scale channels with LTV:CAC >3:1 and payback <12 months. Fix broken channels before scaling.
Symptom: "CAC is only $100!" (but customers churn in 30 days)
Consequence: Low CAC means nothing if LTV is also low. You're acquiring churners, not customers.
Fix: Track cohort retention and NRR by channel. Low CAC + high churn = bad channel.
Symptom: "We got 10,000 signups from this campaign!" (5% convert to paid)
Consequence: Signups don't pay bills. CAC is calculated on paid customers, not signups.
Fix: Track CAC on paid customers only. Ignore vanity metrics like signups, impressions, clicks.
Symptom: "Blended CAC is $500" (but hiding that one channel is $10K CAC)
Consequence: Bad channels hide in blended metrics. You don't know which channels to kill.
Fix: Track CAC, LTV, payback by channel. Compare channels individually.
Symptom: "We reduced CAC 50%!" (by targeting low-intent, low-LTV customers)
Consequence: CAC dropped but so did LTV. Unit economics got worse, not better.
Fix: Optimize for LTV:CAC ratio, not CAC alone. Higher CAC with higher LTV is better.
Symptom: "LTV:CAC is 6:1, this channel is amazing!" (payback is 48 months)
Consequence: You run out of cash before recovering CAC. Great ratio, terrible cash flow.
Fix: Pair LTV:CAC with payback period. 3:1 with 8-month payback beats 6:1 with 36-month payback.
Symptom: "This channel didn't work after 2 weeks"
Consequence: Channels need time to optimize. Killing too early wastes learning.
Fix: Give channels 3-6 months and 100+ customers before evaluating. Track trends, not snapshots.
Symptom: "90% of our customers come from Google Ads"
Consequence: Algorithm change, competitor outbids you, channel saturates = business grinds to halt.
Fix: Diversify channels. No single channel should be >50% of new customer acquisition.
Symptom: "This retargeting campaign has great ROI!" (but customers would've converted anyway)
Consequence: You're paying for conversions that would happen organically. Inflated ROI.
Fix: Test incrementality with holdout groups. Only count truly incremental conversions.
Symptom: "Enterprise events are strategic, we can't stop!" (losing $500K/year)
Consequence: "Strategic" becomes an excuse for burning cash indefinitely.
Fix: Cap spend on strategic channels. Set timeline for improvement (6-12 months). If no progress, kill.
saas-economics-efficiency-metrics — CAC, LTV, payback, magic number calculationssaas-revenue-growth-metrics — NRR, churn, cohort analysis by channelfinance-metrics-quickref — Fast lookup for channel evaluation metricsfeature-investment-advisor — Similar ROI framework for feature decisionsbusiness-health-diagnostic — Broader business health assessmentresearch/finance/Finance_For_PMs.Putting_It_Together_Synthesis.md (Decision Framework #2)research/finance/Finance for Product Managers.mdA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
Take deanpeters/acquisition-channel-advisor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.