# Funnel flow architecture Human Guide ## What This Is For A senior growth practitioner's playbook for architecting cross-tool conversion flows that match audience and stage. It gives the agent a clearer input/output frame for funnel flow architecture: what context to ask for, what decisions to make, and what usable artifact to return. Use this as a human-readable version of the Funnel flow architecture agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions. ## When To Use This - Use this when you need a repeatable process for funnel flow architecture. - Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt. - Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact. ## When Not To Use This - Do not use this when you only need a quick factual answer. - Do not use this when the work depends on private data you cannot share with the assistant. - Do not use this as a replacement for legal, compliance, financial, or medical review. ## What You Need Before Starting - The goal or business outcome you want. - The audience, customer segment, or market context. - Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance. - Constraints such as tone, length, channel, deadline, region, or approval requirements. - A clear definition of what a good final answer should look like. ## Step-By-Step Workflow 1. State the job clearly: "Use the Funnel flow architecture guide to help me with..." 2. Add context: audience, goal, offer, channel, source material, and constraints. 3. Ask the assistant to identify missing inputs before producing the final output. 4. Have the assistant follow the skill-specific guidance below. 5. Review the result against the final checklist and ask for revisions where needed. ## Skill-Specific Guidance - `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. - **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. - **Awareness.** Just discovered the brand or the topic. - **Consideration.** Evaluating options actively. - **Decision.** Choosing between specific options. ## Decision Points And Nuance The original skill emphasizes: 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. Use these questions to steer the work: - What is the intended audience or buyer? - What source material must be preserved? - What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion? - What examples represent the desired quality bar? - What should the assistant avoid? ## Common Mistakes - **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 unmaintained-funnel.** Architecture designed once, never reviewed; decay accumulates. - **Funnel iteration discipline.** Refine continuously; redesign deliberately; avoid both extremes. - [`references/funnel-iteration-discipline.md`](references/funnel-iteration-discipline.md) - When to refine, when to redesign. Avoiding the continuous-redesign and frozen-architecture traps. - The pattern. Architecture designed once, never reviewed. Decay accumulates. - The signal. Conversion does not improve over time. Each redesign resets the learning. Tools never reach maturity. - The pattern. Architecture designed once; never iterated; treated as finished. ## Copy-And-Paste Prompt ```text Use the Funnel flow architecture human guide. My goal: [Describe the business outcome] Audience: [Describe who this is for] Context and source material: [Paste notes, examples, links, or existing copy] Constraints: [Tone, length, channel, timeline, must-include items, must-avoid items] Before producing the final output, ask me for any missing information that would materially improve the result. ``` ## Final Checklist - [ ] The output matches the original goal. - [ ] The audience and context are reflected in the answer. - [ ] Important constraints and source material were preserved. - [ ] The assistant made the relevant decisions explicit. - [ ] The final artifact is ready to use, review, or hand to the next person. ## Source This guide was generated from the rampstackco/claude-skills skill entry for `funnel-flow-architecture`. ## Source Skill Notes These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic. # 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-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`). --- ## 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`](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).