brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
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 getcrew44/crew44 --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 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"
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.
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:**
**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:**
1. **Do customers from this channel have similar LTV to other channels?**
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes