funnel-flow-architecture
Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when a
Profile →npx skills add rampstackco/claude-skills --skill funnel-flow-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Architects cross-tool funnel flows that match audience and stage. It focuses on mapping entry points, segments, and stages to appropriate tools (lead magnets, calculators, quizzes, multi-step forms, chatbots) and designing corresponding nurture sequences and cross-tool data flows. The goal is to create a cohesive funnel architecture where tools work together rather than in isolation, distinguishing silo-funnels, kitchen-sink-funnels, and matched-funnels patterns.
How it works
The skill describes audience and stage segmentation, then defines entry-point architecture and how each tool maps to specific segments and stages. It specifies cross-tool data flow principles (identity threading, context capture, segment tagging, sequence-tool integration) to maintain continuity across tools as visitors move through the funnel. It covers how nurture sequences should vary by stage (awareness, consideration, decision) and by audience (enterprise vs SMB, roles, industries). It includes how to map tools to funnel stages and entry points (lead magnets for awareness-to-consideration, calculators for consideration, quizzes for various stages, multi-step forms for decision/qualification, chatbots for cross-cutting routing). It also discusses measurement concepts at architecture and tool levels and outlines when to refine or redesign the funnel architecture, plus common anti-patterns to avoid.
When to use it
Use when architecting a funnel from scratch, auditing a growth program where tools operate independently but conversion is flat, designing cross-tool data flow, or deciding which segments warrant which funnel paths.
What it can touch
The skill references cross-tool data flow and mappings between tools and funnel entry points, segments, and nurture sequences. It implies coordination across five sister growth-tooling skills (lead-magnet-design, calculator-design, quiz-and-assessment-design, multi-step-form-design, chatbot-flow-design) and mentions content-distribution, experiment-design, and landing-page-copy as related areas.
Caveats
Out of scope: specific tool design details (handled by sister growth-tooling skills), content distribution mechanics, A/B testing methodology, and page-level copy.
# Funnel Flow Architecture A senior growth practitioner's playbook for architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. The discipline of building a funnel architecture, not just collecting tools. Most growth programs accumulate tools without architecture. A chatbot, a calculator, a quiz, a lead magnet, a newsletter signup, a demo CTA. Each tool works individually; none of them work together. Visitors hit one tool, leave, and never enter the broader nurture sequence. The funnel is a collection of orphans. The growth programs that compound do something different. They architect the funnel deliberately. Different entry points lead to different nurture sequences. Different stages get different CTAs. Different tools serve different segments. Each tool is part of a larger architecture, not a standalone artifact. This skill is the architecture skill that orchestrates the other 5 growth-tooling skills (lead-magnet-design, calculator-design, quiz-and-assessment-design, multi-step-form-design, chatbot-flow-design). Where those skills zoom into specific tool design, this skill zooms out to th
- What this skill covers
- Silo-funnels vs kitchen-sink-funnels vs matched-funnels
- Audience and stage segmentation
- Entry-point architecture
- Tool-to-funnel mapping
- Nurture sequence architecture
- Cross-tool data flow
- Funnel measurement
- Funnel iteration discipline
- Architecture anti-patterns
- The framework: 12 considerations for funnel flow architecture
- Reference files
- Closing: funnels are architecture, not collections
- Closing: funnels earn investment when they compose
What does the funnel-flow-architecture skill do?
Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when a
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill funnel-flow-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.