Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rampstack-skills
Architects cross-tool conversion flows matched to audience and stage. Distinguishes silo, kitchen-sink, and matched funnel patterns. Use when auditing growth programs where tools work individually but conversion is flat, or architecting a funnel from scratch.
npx claudepluginhub rampstackco/claude-skills --plugin rampstack-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/rampstack-skills:funnel-flow-architectureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
references/architecture-anti-patterns.mdreferences/audience-and-stage-segmentation.mdreferences/common-funnel-architecture-failures.mdreferences/cross-tool-data-flow-patterns.mdreferences/entry-point-architecture-patterns.mdreferences/funnel-iteration-discipline.mdreferences/funnel-measurement-patterns.mdreferences/nurture-sequence-architecture.mdreferences/tool-to-funnel-mapping.mdDesigns marketing funnels, maps customer journeys, models attribution, analyzes drop-offs, and optimizes conversion paths.
Maps the complete customer journey from stranger to repeat buyer across TOFU/MOFU/BOFU stages with page templates, copy hooks, and conversion targets.
Defines high-level marketing funnel strategy including goal, target audience, price point, traffic source, and conversion path. Recommends funnel type and blueprint before coding.
Share bugs, ideas, or general feedback.
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.
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-design are tools that LIVE INSIDE the funnel architecture this skill designs. They zoom into specific tool design.content-distribution covers how content reaches audiences. This skill is what audiences DO once they reach content.experiment-design validates funnel changes. This skill designs the architecture; experiment-design tests it.landing-page-copy covers 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).
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.
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.
Stage dimensions.
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.
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.
Entry-point routing.
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.
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.
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.
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.
Sequence variation by audience.
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.
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 calculator's defaults; the calculator inputs inform the lead-magnet sequence; the quiz result informs the demo-request prefill.
Cross-tool data flow patterns.
The siloed-tool failure. Each tool captures its own data; nothing flows between them. The chatbot conversation is forgotten when the user opens the calculator; the calculator inputs are forgotten when the user opens the lead magnet.
The integrated-funnel win. Data flows. The audience experiences continuity; the brand can match content and offers to the audience's specific journey.
Detail in references/cross-tool-data-flow-patterns.md.
What to measure, what is noise.
The principle. Funnel measurement should reveal architecture quality, not just tool quality.
Architecture-level metrics.
Tool-level metrics.
Architecture-level vs tool-level. Tool-level metrics tell you whether each tool is working; architecture-level metrics tell you whether the tools work together. Both matter; architecture is often the missing measurement.
Detail in references/funnel-measurement-patterns.md.
When to redesign, when to refine.
The principle. Funnel architecture compounds when refined; collapses when constantly redesigned. The discipline is knowing when each is appropriate.
Refine when:
Redesign when:
Continuous-redesign trap. Teams that constantly redesign never benefit from architectural compounding. Each redesign resets the learning; nothing accumulates.
Frozen-architecture trap. Teams that never iterate watch their architecture decay as audiences and markets evolve.
The middle ground. Refine continuously; redesign infrequently and deliberately.
Detail in references/funnel-iteration-discipline.md.
Patterns that look like funnel architecture but degrade conversion.
The silo-funnels pattern. Tools as orphans; no architecture.
The kitchen-sink-funnels pattern. One funnel for everyone.
The over-segmented funnel. So many segments that maintenance is impossible; segments are not actually distinguishable.
The unmaintained-funnel. Architecture designed once, never reviewed; decay accumulates.
The tool-driven-architecture. Architecture organized around tools rather than around audience-and-stage; each tool gets its own funnel regardless of whether that serves the audience.
The metric-blind-architecture. Architecture without measurement; cannot diagnose where it works and where it does not.
The single-tool-funnel. Architecture that depends on one tool (just the calculator, just the chatbot); no resilience if that tool underperforms.
The hand-off-broken-funnel. Tools work individually but the transitions between them break.
Detail in references/architecture-anti-patterns.md.
When designing or auditing a funnel architecture, walk these 12 considerations.
The output of the framework is a funnel architecture that compounds over time, matches audience-and-stage segments, integrates tool data flows, and produces measurable downstream conversion.
references/audience-and-stage-segmentation.md - The foundation. Audience dimensions, stage dimensions, the intersection matrix.references/entry-point-architecture-patterns.md - How visitors land vs how they're routed. Common entry points and their routing.references/tool-to-funnel-mapping.md - Which tools serve which entry points and segments.references/nurture-sequence-architecture.md - Per-segment, per-stage sequence variation. The matched sequence win.references/cross-tool-data-flow-patterns.md - Identity threading, context capture, segment tagging, sequence-tool integration.references/funnel-measurement-patterns.md - Architecture-level vs tool-level metrics. What to measure, what is noise.references/funnel-iteration-discipline.md - When to refine, when to redesign. Avoiding the continuous-redesign and frozen-architecture traps.references/architecture-anti-patterns.md - The patterns that look like funnel architecture but degrade conversion.references/common-funnel-architecture-failures.md - 9+ failure patterns with diagnoses and cures.The growth programs that compound are the ones that architect their funnels deliberately. Not collect tools. Not optimize one-tool-at-a-time. Architect.
The architecture is the difference between tools that produce engagement and a funnel that produces business outcomes. The chatbot, the calculator, the quiz, the lead magnet, the multi-step form: each one is a tool. None of them are a funnel. The funnel is the architecture that makes them work together.
That is the bar. Below the bar are silo-funnels (tools as orphans) and kitchen-sink-funnels (one path for everyone). Above the bar are matched-funnels where audience-and-stage segmentation drives entry-point routing, tool-to-funnel mapping, nurture sequence design, cross-tool data flow, and architecture-level measurement.
Each tool in the growth toolkit costs investment to build and maintain. The investment compounds when the tools compose; the investment dilutes when the tools sit in silos. Architecture is the discipline of composition.
The compounding mechanism. A visitor arrives. The architecture routes them based on entry point and observable signals. The first tool they encounter serves their segment-and-stage. The data they generate informs the next tool they encounter. The sequence they enter matches their context. Each interaction deepens the brand's understanding of the audience; each tool's contribution compounds with the others.
When in doubt, ask: does each tool in the program serve a defined segment-and-stage, do the tools share data and context, can the team explain the architecture in one diagram, and does the team measure architecture-level outcomes (not just tool-level metrics)? If yes to all of those, the funnel is real architecture. If no to any, the gap is where the program's tools are failing to compose.