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.
Install / Use
npx skills add rampstackco/claude-skills --skill funnel-flow-architectureInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of funnel-flow-architecture
funnel-flow-architecture scores 86/100 on our quality scale, 410th of 642 Marketing skills we index.
Its SKILL.md is 22 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so funnel-flow-architecture is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
funnel-flow-architecture compared with similar skills
All 4 of these similar skills score higher than funnel-flow-architecture; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| funnel-flow-architecture (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install funnel-flow-architecture?
- Run
npx skills add rampstackco/claude-skills --skill funnel-flow-architecture. The install tabs above show the steps for each supported agent. - Which AI agents does funnel-flow-architecture work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is funnel-flow-architecture safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is funnel-flow-architecture still maintained?
- The repository was last updated about 2 months ago, so funnel-flow-architecture is actively maintained.
Skill content
View source on GitHubname: funnel-flow-architecture description: "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 audience segments share one nurture path, or when a funnel is being architected from scratch." category: growth-tooling catalog_summary: "Architecting cross-tool conversion flows that match audience and stage. Distinguishes silo-funnels (every tool standalone) from kitchen-sink-funnels (every audience squeezed through one path) from matched-funnels (architecture matched to audience-and-stage)" display_order: 6
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 the cross-tool architecture that determines whether the tools compound.
The voice is the senior growth practitioner who has watched funnels architecture compound and watched siloed funnel collections produce engagement metrics with no business impact. Practical, opinionated about the difference between collecting tools and architecting funnels, willing to call out when a team's growth program needs architecture rather than another tool.
When to use this skill: architecting a funnel from scratch, auditing a growth program where tools work individually but conversion is flat, designing the cross-tool data flow that captures audience signal across touchpoints, or deciding which segments warrant which funnel paths.
What this skill covers
This skill spans cross-tool funnel architecture. The growth-tooling distinctions:
lead-magnet-design,calculator-design,quiz-and-assessment-design,multi-step-form-design,chatbot-flow-designare tools that LIVE INSIDE the funnel architecture this skill designs. They zoom into specific tool design.content-distributioncovers how content reaches audiences. This skill is what audiences DO once they reach content.experiment-designvalidates funnel changes. This skill designs the architecture; experiment-design tests it.landing-page-copycovers page-level copy. This skill is the cross-page architecture.funnel-flow-architecture(this skill) is audience-and-stage segmentation, entry-point architecture, tool-to-funnel mapping, nurture sequence architecture, cross-tool data flow.
The audience: growth marketing leads, product marketing leads, marketing directors at SMB and mid-market companies, agencies running funnel architecture for clients, founders architecting growth programs from scratch.
Out of scope: specific tool design (covered by the 5 sister growth-tooling skills); content distribution mechanics (covered by content-distribution); A/B testing methodology (covered by experiment-design); page-level copy (covered by landing-page-copy).
Silo-funnels vs kitchen-sink-funnels vs matched-funnels
The keystone framing.
Silo-funnels. Each tool (chatbot, calculator, lead magnet, quiz) lives independently. No coordinated flow; users hit one tool, leave, never enter the broader nurture sequence. Tools as orphans. Cost: each tool's investment does not compound; the audience that interacts with one tool is not connected to any next step; the team has tools but no architecture.
Kitchen-sink-funnels. One funnel for everyone. Same nurture sequence regardless of audience or entry point. SMB and enterprise get the same emails. New visitors and bottom-of-funnel get the same CTAs. Conversion rates regress to mediocre on every segment. Cost: the funnel optimizes for the average; no segment is well-served; downstream conversion is uniformly low.
Matched-funnels. Funnel architecture matches audience and stage. 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. Cost: the design effort upfront is significant; the maintenance is real; downstream conversion is meaningfully higher per segment.
The litmus test. Pick a recent visitor to the site. Can the team explain which segment the visitor falls into, which entry point they used, which nurture sequence they are in, and what the next-step CTA they will see is? If yes, the funnel is matched. If the answer is "they got the same flow as everyone else," the funnel is kitchen-sink. If the answer is "they used the calculator but I do not know what comes next," the funnel is silo.
Audience and stage segmentation
The foundation.
The principle. Funnel architecture starts with audience and stage segmentation. Without segmentation, every visitor goes through the same path; the funnel cannot match.
Audience dimensions.
- Company size or buyer type. Solo, SMB, mid-market, enterprise.
- Industry or vertical. Healthcare, finance, retail, technology.
- Use case. What the audience is trying to accomplish.
- Role. Founder, PM, marketer, executive, IC.
- Source. Paid traffic, organic, referral, partner.
Stage dimensions.
- Awareness. Just discovered the brand or the topic.
- Consideration. Evaluating options actively.
- Decision. Choosing between specific options.
- Customer. Already a customer; ongoing relationship.
The intersection. Audience x stage produces the matrix the funnel architecture serves. An enterprise PM in consideration is a different segment from an SMB founder in awareness; each warrants a different path.
Segmentation discipline. Start with 3-5 audiences and 3 stages. 9-15 cells in the matrix. Some cells may share paths; some may have unique paths. The discipline is naming the segments deliberately rather than treating "everyone" as the audience.
Detail in references/audience-and-stage-segmentation.md.
Entry-point architecture
How visitors land vs how they're routed.
The principle. The funnel architecture maps entry points (where visitors arrive) to segments and paths (what they do next).
Common entry points.
- Paid landing page. Visitor arrives via ad; high intent; specific to the ad's promise.
- Organic content page. Visitor arrives via search or content discovery; awareness or research stage.
- Direct. Visitor arrives by typing URL or via bookmark; often returning.
- Referral. Visitor arrives via partner or word-of-mouth; warmer than paid.
- Social. Visitor arrives via social post; awareness or interest.
- Tool entry. Visitor arrives via a calculator, quiz, or chatbot directly.
Entry-point routing.
- Each entry point has expected segments and stages.
- The first action available at the entry point should match likely segment and stage.
- Different entry points may route to different downstream tools and sequences.
Worked example. A visitor arriving via a paid ad about "B2B SaaS pricing" is likely in consideration stage looking for pricing information. The landing page should serve that need (clear pricing, comparison, calculator); the next-step offer should match consideration (demo, talk to sales). Same visitor arriving via an organic blog post about "B2B SaaS pricing strategy" is likely in awareness stage; the landing page should serve education (depth on pricing strategy); the next-step offer should match awareness (subscribe to content, get the framework).
Detail in references/entry-point-architecture-patterns.md.
Tool-to-funnel mapping
Which tools serve which entry points.
The principle. Each tool in the growth toolkit has a place in the funnel architecture. The tool serves specific segments at specific stages from specific entry points.
Mapping examples.
- Lead magnet. Often serves awareness-to-consideration transition. Captured email leads to nurture sequence.
- Calculator. Often serves consideration stage. The audience evaluating options uses the calculator to defend a specific decision.
- Quiz. Can serve any stage depending on design. Awareness quizzes for content marketing; consideration quizzes for product matching; decision quizzes for plan selection.
- Multi-step form. Often serves decision or qualification stage. The form captures qualified intent.
- Chatbot. Cross-cutting. Can serve any stage with intent recognition routing.
The tool-segment fit. Tools should serve segments that match their value proposition. A calculator for solo founders may need different inputs and outputs than a calculator for enterprise buyers; the same calculator cannot serve both well.
The portfolio approach. A team often has multiple tools serving different segments. The architecture maps each tool to its specific segments and stages.
Detail in references/tool-to-funnel-mapping.md.
Nurture sequence architecture
Per-segment, per-stage.
The principle. Different segments at different stages get different nurture sequences. The sequences match the audience's situation and stage.
Sequence variation by stage.
- Awareness sequence. Educational; broad value; brand-building. Soft offers if any.
- Consideration sequence. Comparative; specific value; product-fit signals. Demo or trial CTAs.
- Decision sequence. Confidence-building; risk-reversal; urgency cues. Direct purchase or commitment CTAs.
Sequence variation by audience.
- Enterprise audiences get different content (white papers, case studies, ROI analysis) than SMB audiences (templates, quick wins, peer testimonials).
- Different roles get different framing (founder content emphasizes business outcomes; IC content emphasizes practitioner depth).
- Different industries get different examples and language.
The kitchen-sink sequence failure. One sequence for everyone. Generic enough to send to all; specific enough for none. Conversion uniformly mediocre.
The matched sequence win. Sequence specific to segment-and-stage. The audience perceives the brand as understanding their situation; conversion compounds.
Detail in references/nurture-sequence-architecture.md.
Cross-tool data flow
Capturing context from tool to tool.
The principle. When the audience moves from one tool to another in the funnel, the audience signal travels with them. The chatbot conversation context informs the calculato
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
