eighty-twenty-funnel-economics
Diagnose and prioritize sales funnel improvements by economics, conversion, split testing, and high-value customer potential. Use when optimizing funnels, deciding what to test, improving CAC or profit, evaluating upsells, or choosing the few metrics that matter now.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- eighty-twenty-funnel-economics
- license
- MIT
- metadata
- { "tags": "eighty-twenty,funnels,economics,experiments,marketing", "version": "0.1.0", "category": "Marketing", "displayName": "80/20 Funnel Economics" }
- description
- Diagnose and prioritize sales funnel improvements by economics, conversion, split testing, and high-value customer potential. Use when optimizing funnels, deciding what to test, improving CAC or profit, evaluating upsells, or choosing the few metrics that matter now.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
03 SKILL.md 正文
80/20 Funnel Economics
Use this skill to find the few funnel improvements that multiply economic results. It is based on 80/20 Sales and Marketing by Perry Marshall.
Source Traceability
Primary source: 80/20 Sales and Marketing, chapters 6, 9, 12, and 22.
- Chapter 6 introduces traffic, conversion, economics as a linked system.
- Chapter 9 covers split testing and fixing funnels in pieces.
- Chapter 12 covers higher customer value and premium buying behavior.
- Chapter 22 covers identifying the few measurements that matter now.
Workflow
1. Map The Funnel Economics
Capture each step:
- Traffic source.
- Lead capture.
- Qualification.
- Offer.
- Purchase.
- Upsell or expansion.
- Retention or repeat purchase.
For each step, capture volume, conversion rate, revenue, gross margin, and customer quality where available.
2. Work Backwards From Economics
Before increasing traffic, answer:
- What customer value can the funnel support?
- What acquisition cost is acceptable?
- Which customers are worth much more than the median?
- Where is premium demand hidden?
- What offer or upsell could capture more value?
3. Find The Multiplying Constraint
Identify the smallest number of steps where improvement multiplies downstream results.
Prefer tests that affect:
- Qualified conversion.
- Average order value or expansion.
- Gross margin.
- Sales cycle speed.
- High-value customer capture.
4. Design The Next Test
Choose one test at a time. Define:
- Hypothesis.
- Funnel step.
- Variant.
- Primary metric.
- Secondary guardrail.
- Run time or sample size.
- Decision rule.
Output Format
# Funnel Economics Diagnosis
## Funnel Map
| Step | Volume | Conversion | Revenue/Value | Constraint |
|------|--------|------------|---------------|------------|
## Economic Leverage
- Allowable CAC:
- Highest-value segment:
- Hidden premium opportunity:
- Main constraint:
## Test Priority
| Rank | Test | Step | Expected Economic Effect | Decision Rule |
|------|------|------|--------------------------|---------------|
## Recommendation
- Run next:
- Do not optimize yet:
- Data needed:
Quality Bar
- Do not increase traffic before checking economics.
- Do not optimize vanity metrics.
- Do not run multiple ambiguous tests at once.
- Treat funnel improvements as multiplicative, not isolated.
- Include a decision rule before recommending a test.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.