funnel-design
Skill0 starsChanged 2 months agoMITView on GitHub
Framework for architecting end-to-end customer journeys — value ladder, TOFU/MOFU/BOFU stages, email/WhatsApp sequence architecture, upsell/downsell/order-bump logic, and automation triggers. Use when mkt-strategist is designing or auditing a funnel, includes a fill-in funnel spec template.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- brainbytes-dev/everything-claude-marketing★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- global/CLAUDE.mdCLAUDE.md
- copywriting-frameworksSkill
- design-mdSkill
- format-carouselSkill
- format-hooksSkill
- format-linkedinSkill
- format-reelsSkill
- humanizationSkill
- launch-playbooksSkill
- offer-designSkill
- pipeline-brandSkill
- pipeline-campaignSkill
- pipeline-contentSkill
- pipeline-copySkill
- pipeline-landing-pageSkill
- pipeline-luxoSkill
- pipeline-refino-uiSkill
- pipeline-sistemaSkill
- scroll-worldSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Every content piece or ad inside a funnel should be tagged to exactly one stage.
- Distinctive: line 29
Every touch has exactly one job: nurture OR pitch.
- Distinctive: line 40
Every trigger needs an explicit owner (which sequence fires) and an explicit stop condition (what removes the contact — typically: …
- Distinctive: line 41
Document trigger → sequence → stop-condition as a table.
- Distinctive: line 76
Check average customer value against acquisition cost.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Funnel Design
Value Ladder
Bait → Frontend → Middle → Backend. Every customer should always have a visible next step upward — a ladder with dead ends is a leak, not a ceiling. Map the full ladder for the offer line in question before designing any single funnel inside it; a funnel without a defined ladder position is being built blind.
Funnel Stages: TOFU / MOFU / BOFU
- TOFU (awareness) — cold traffic, provocative hooks, pain amplification, curiosity. No hard pitch here.
- MOFU (consideration) — proof, case studies, mechanism explanation, objections pre-handled before they're raised.
- BOFU (decision) — real urgency, guarantee, social proof, one direct CTA.
Every content piece or ad inside a funnel should be tagged to exactly one stage. Mixing stages inside a single asset (a TOFU hook that suddenly hard-pitches) dilutes both.
Customer Value Journey (reference model)
Aware → Engage → Subscribe → Convert → Excite → Ascend → Advocate → Promote. Use this to locate exactly where a stalling funnel actually breaks. Most audits stop looking at "Convert" and miss that the real break is at "Excite" (a weak post-purchase experience) or "Ascend" (no defined next offer).
Sequence Architecture (Email / WhatsApp)
- Cold-to-warm sequences (pure nurture, no pitch) are structurally different from warm-to-sale sequences (pitch-forward) — never reuse one shape for the other.
- Define, per sequence: length (number of touches), timing (interval between touches), the intent of each touch (subject line / opening line), and branching logic (opened vs. not, clicked vs. not).
- WhatsApp sequences run shorter and more conversational than email — best for time-sensitive nurture and call/session reminders, not long-form persuasion.
- Every touch has exactly one job: nurture OR pitch. A touch trying to do both usually does neither well.
Upsell / Downsell / Order-Bump Logic
- One upsell per primary offer: the single highest-leverage next step, not a menu of extras competing for attention.
- Downsell preserves the same core outcome through leaner delivery — for buyers who already said yes to the outcome but not the price.
- Order bumps must serve the primary offer directly, as a genuine accessory to what's already being bought — never an unrelated add-on bolted on for extra margin.
Automation Triggers
- Behavioral branches: page visited, email opened, link clicked, cart abandoned, call booked or no-showed.
- Every trigger needs an explicit owner (which sequence fires) and an explicit stop condition (what removes the contact — typically: purchased, booked, or replied).
- Document trigger → sequence → stop-condition as a table. Undocumented triggers are how funnels quietly break weeks after launch.
Funnel Type Selection by Price Point
- Low ticket — direct sales, self-liquidating offers, minimal-friction checkout.
- Mid ticket — webinar/VSL funnels, challenge funnels, masterclass funnels.
- High ticket / application-only — application funnels, call-booking funnels, event-to-session funnels. Self-serve checkout is not the primary conversion event at this tier.
Funnel type must match market sophistication and price point — mkt-strategist decides the type for a given offer; this skill supplies the mechanics once the type is chosen.
Funnel Spec Template
FUNNEL: <name>
Objective: <launch / evergreen / relaunch / diagnostic audit>
Value ladder position: <bait / frontend / middle / backend>
Target ICP: <segment>
Funnel type: <application / call-booking / webinar / VSL / tripwire / self-serve>
Flow:
1. <step> — Purpose: <> — Traffic source: <> — Touchpoint: <page/email/WhatsApp/call> — Offer: <> — CTA: <> — Owning agent: <> — Expected conversion: <% + reasoning>
2. ...
Automation specs:
- Email: <sequence length, timing, triggers, branching>
- WhatsApp: <sequence, triggers, human handoff point>
Success metrics: <per-step + overall>
Risks/assumptions: <what could break this>Diagnosing a Stalling Funnel
- Map the funnel exactly as it runs today — not as originally designed — before changing anything.
- Locate the single weakest step using real conversion data. Don't guess where the leak is.
- Check average customer value against acquisition cost. If value doesn't clear cost, fix monetization before scaling traffic into a leaking funnel.
- Fix only the weakest step. A full rebuild is justified only when two or more steps are broken at once.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

