What is the Funnel flow architecture agent skill?

A senior growth practitioner's playbook for architecting cross-tool conversion flows that match audience and stage. The value is a focused slice of funnel flow architecture judgment, useful when several similar skills cover the same ground.

What inputs does Funnel flow architecture need?

Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.

What does Funnel flow architecture output?

A ready-to-use result: the analysis, copy, or recommendations the agent produces.

Funnel flow architecture

Quick answer

01What is it?: A senior growth practitioner's playbook for architecting cross-tool conversion flows that match audience and stage. The value is a focused slice of funnel flow architecture judgment, useful when several similar skills cover the same ground.
02Inputs: Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.
03Output: A ready-to-use result: the analysis, copy, or recommendations the agent produces.

Add this skill

Install-only

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal

$ npx skills add rampstackco/claude-skills --skill funnel-flow-architecture

Skill instructions

The instruction file for this skill. The skill also includes other files you need to install to use it.

SKILL.md

Preview only — coding agent install

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.

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 calculator's defaults; the calculator inputs inform the lead-magnet sequence; the quiz result informs the demo-request prefill.

Cross-tool data flow patterns.

Identity threading. When the audience is identified at any point (logged in, opted in, identified by email), their identity carries forward across tools.
Context capture. Inputs from one tool (calculator values, quiz results, form submissions) feed into the next interaction.
Segment tagging. Each interaction tags the audience with segment information that informs future routing.
Sequence-tool integration. Email sequences include links to specific tools matched to the audience's segment.

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.

Funnel measurement

What to measure, what is noise.

The principle. Funnel measurement should reveal architecture quality, not just tool quality.

Architecture-level metrics.

Cross-tool conversion. What percentage of audience that hits tool A then engages with tool B?
Sequence-to-tool conversion. What percentage of nurture sequence subscribers engage with downstream tools?
Segment-level downstream conversion. Per-segment conversion to the program's main goal (trial, demo, purchase).
Funnel-stage progression. What percentage of audience moves from awareness to consideration to decision over time?

Tool-level metrics.

Conversion rate per tool (covered by each tool's skill).

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.

Funnel iteration discipline

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:

Specific tools are underperforming relative to baseline.
Specific segments have lower conversion than peer segments.
Specific transitions in the funnel are producing drop-off.
Sequence engagement is declining for specific cohorts.

Redesign when:

Audience composition has fundamentally shifted.
Product or service strategy has changed.
Competitive landscape has shifted significantly.
Multiple refine cycles have not produced expected results, suggesting architectural issues.

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.

Architecture anti-patterns

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.

The framework: 12 considerations for funnel flow architecture

When designing or auditing a funnel architecture, walk these 12 considerations.

Matched-funnels, not silo or kitchen-sink. Architecture matches audience-and-stage; each tool is part of the architecture, not a standalone artifact.
Audience and stage segmentation defined. 3-5 audiences x 3 stages; the matrix the architecture serves.
Entry-point architecture mapped. Each entry point routed to expected segments and stages.
Tool-to-funnel mapping documented. Each tool serves specific segments at specific stages.
Nurture sequence architecture per segment. Sequences vary by audience and stage; not one sequence for everyone.
Cross-tool data flow integrated. Context travels across tools; the audience experiences continuity.
Architecture-level metrics tracked. Cross-tool conversion, sequence-to-tool conversion, segment-level downstream conversion.
Funnel iteration discipline. Refine continuously; redesign deliberately; avoid both extremes.
Tool portfolio balanced. Multiple tools serving different segments; not over-reliant on any single tool.
Audience-fit honest. The architecture serves the segments the brand can actually serve; out-of-fit audiences are filtered or routed elsewhere.
Maintenance ownership clear. Someone owns the architecture; quarterly review is calendared.
Expansion plan defined. When adding new tools, the architecture says where they fit; new tools earn their place rather than being added decoratively.

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.

Reference files

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.

Closing: funnels are architecture, not collections

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.

Closing: funnels earn investment when they compose

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.

Supporting file: references/architecture-anti-patterns.md

Architecture anti-patterns

The patterns that look like funnel architecture but degrade conversion. Anti-patterns are easy to ship; the cost shows up in downstream conversion, lead quality, and brand reputation over time.

The silo-funnels pattern

The pattern. Tools as orphans. No coordinated flow.

The signal. Each tool's metrics look fine individually; cross-tool metrics non-existent or near-zero. Downstream conversion does not match the sum of tool conversions.

The 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.

The cure. Add cross-tool data flow and explicit funnel architecture. Detail in references/cross-tool-data-flow-patterns.md and the broader skill.

The kitchen-sink-funnels pattern

The pattern. One funnel for everyone. Same nurture sequence regardless of audience or entry point.

The signal. Conversion rates regress to mediocre on every segment. No segment is well-served.

The cost. The funnel optimizes for the average; downstream conversion is uniformly low.

The cure. Segment-and-stage architecture. Different paths for different cells in the matrix. Detail in references/audience-and-stage-segmentation.md and references/nurture-sequence-architecture.md.

The over-segmented funnel

The pattern. So many segments that maintenance is impossible. 60 cells in the matrix; 60 distinct paths; nobody can keep up.

The signal. Specific paths get little attention; maintenance backlog grows; specific cells are theoretical with no real visitors.

The cost. The architecture exists on paper but not in execution. Tools and sequences for theoretical cells cost effort without producing value.

The cure. Reduce to 9-15 cells. Start with the minimum viable matrix; expand only when data justifies. Detail in references/audience-and-stage-segmentation.md.

The unmaintained-funnel

The pattern. Architecture designed once, never reviewed. Decay accumulates.

The signal. Conversion declines slowly; tools age; sequences go stale; segments shift; the architecture does not respond.

The cost. The architecture's value erodes. Audiences move on; the brand falls behind.

The cure. Quarterly audit. Refinement cadence. Detail in references/funnel-iteration-discipline.md.

The tool-driven-architecture

The pattern. Architecture organized around tools rather than around audience-and-stage. Each tool gets its own funnel regardless of whether that serves the audience.

The signal. The site has many tool-specific landing pages; users navigate to tools rather than tools serving users; the architecture is organized for the team, not the audience.

The cost. Audiences cannot find what they need; tools cannibalize each other; the architecture cannot scale because each tool is its own funnel.

The cure. Reorganize around audience-and-stage. The matrix drives the architecture; tools serve the matrix.

The metric-blind-architecture

The pattern. Architecture without measurement. Cannot diagnose where it works and where it does not.

The signal. Decisions made on intuition; no data to validate; iteration is guesswork.

The cost. The architecture cannot improve through measurement; refinement is random; redesign happens reactively.

The cure. Architecture-level metrics. Cross-tool conversion, sequence-to-tool conversion, segment-level downstream conversion, funnel-stage progression. Detail in references/funnel-measurement-patterns.md.

The single-tool-funnel

The pattern. Architecture that depends on one tool. Just the calculator. Just the chatbot. No resilience if that tool underperforms.

The signal. The tool's quarterly performance dictates overall funnel performance. A bad month for the tool is a bad month for the funnel.

The cost. The architecture is fragile. Tool failures cascade; redesigns of the central tool are high-risk.

The cure. Portfolio approach. Multiple tools serving different segments. The architecture's resilience comes from diversification.

The hand-off-broken-funnel

The pattern. Tools work individually but the transitions between them break.

The signal. Each tool's metrics look fine; cross-tool conversion is low. The architecture's transitions are silently failing.

The cost. The audience experiences the funnel as disconnected. Downstream conversion suffers because the bridges between tools are broken.

The cure. Audit transitions. Cross-tool data flow. Sequence-tool integration. Detail in references/cross-tool-data-flow-patterns.md.

The continuous-redesign funnel

The pattern. Architecture redesigned every quarter. Each iteration starts over.

The signal. Conversion does not improve over time. Each redesign resets the learning. Tools never reach maturity.

The cost. Investment dilutes across redesigns. Compounding does not happen.

The cure. Refine continuously; redesign infrequently and deliberately. Detail in references/funnel-iteration-discipline.md (continuous-redesign trap).

The frozen-architecture funnel

The pattern. Architecture designed once; never iterated; treated as finished.

The signal. Conversion declines slowly; tools and sequences feel dated; segments no longer match the audience.

The cost. The architecture's value erodes; the brand becomes uncompetitive.

The cure. Set refinement cadences. Quarterly audits. Detail in references/funnel-iteration-discipline.md (frozen-architecture trap).

The vanity-metric architecture

The pattern. Architecture measured by surface metrics (tool engagement, total visitors, email signups) without measuring downstream outcomes.

The signal. Metrics report looks healthy; business outcomes do not match.

The cost. The team optimizes for the wrong metrics; the architecture appears successful while underperforming on what matters.

The cure. Measure downstream conversion. Per-segment downstream conversion. Architecture-level metrics rather than tool-level activity.

The over-personalized funnel

The pattern. Architecture designed for personalization the team cannot actually deliver. Many entry points; many sequences; many tools; team capacity exceeded.

The signal. Personalization in design; generic in execution. Specific paths exist on paper; default to generic in practice.

The cost. The team built complexity that does not get used. Maintenance burden without payoff.

The cure. Match architecture complexity to team capacity. Start simple; add personalization where it produces meaningful lift; do not personalize for its own sake.

The under-personalized funnel

The pattern. Architecture treats every visitor the same when meaningful personalization would lift conversion.

The signal. Specific segments underperform; the audience's actual differences are not reflected in the funnel.

The cost. Conversion stays at the average; no segment exceeds.

The cure. Add personalization where data shows it would help. Start with segment-level differentiation; refine over time.

The orphan-tool architecture

The pattern. Tools added to the funnel without explicit segment-and-stage assignment. Each new tool exists; no architecture says where it fits.

The signal. The funnel's tool count grows; the architecture's clarity does not.

The cost. Tools compete for the same audience; users see overlapping options; conversion fragments.

The cure. Each tool earns its place. Architecture documents which segments and stages the tool serves. New tools are added with explicit mapping.

How to detect anti-patterns in a portfolio

Audit cadence. Quarterly review of the architecture, looking specifically for these anti-patterns.

Audit questions.

Do the tools work together (anti-pattern check: silo, hand-off-broken)?
Is there segment-and-stage architecture (anti-pattern check: kitchen-sink, tool-driven)?
Is the matrix maintainable (anti-pattern check: over-segmented, over-personalized)?
Are tools mapped to specific segments (anti-pattern check: orphan-tool, single-tool, under-personalized)?
Are architecture-level metrics tracked (anti-pattern check: metric-blind, vanity-metric)?
Is there iteration discipline (anti-pattern check: continuous-redesign, frozen-architecture, unmaintained)?

The retire decision. Anti-pattern architectures often warrant redesign. Patching anti-patterns rarely produces a good architecture.

Methodology-level choices that stay in the public skill

The catalog of anti-patterns. Signal-pattern-cost framing for each. Cures matched to anti-patterns. The audit cadence and audit questions. The retire decision.

Implementation choices that stay internal

Specific anti-patterns the team has shipped historically and the lessons learned. Specific portfolio audit results. Specific redesign decisions. The team's audit calendar and reviewer list. These vary by team.

Supporting file: references/audience-and-stage-segmentation.md

Audience and stage segmentation

The foundation. Audience dimensions, stage dimensions, the intersection matrix.

Funnel architecture starts with audience and stage segmentation. Without it, every visitor goes through the same path; the funnel cannot match. With it, the architecture has a definable map of who the audience is and where they are in their journey.

The segmentation principle

The funnel cannot be tailored without segments. Segments are the architecture's unit of design.

The discipline. Define 3-5 audience segments and 3 stages. The intersection produces 9-15 cells; each cell is a potential funnel path.

The trap. Over-segmenting. Defining 12 audiences x 5 stages produces 60 cells; the team cannot maintain that many distinct paths. Most cells end up sharing paths or being indistinguishable.

The discipline boundary. Start with the minimum viable segmentation. 3-5 audiences and 3 stages is enough to start. Expand only if the data shows meaningful differentiation that justifies more cells.

Audience dimensions

The dimensions that distinguish meaningful audience segments.

Company size or buyer type. Solo founders, SMB (10-50), mid-market (50-500), enterprise (500+). Different sizes have different buying processes, different budgets, different needs.

Industry or vertical. Healthcare, finance, retail, technology, education. Different industries have different language, regulations, examples, competitors.

Use case. What the audience is trying to accomplish. "Customer support automation," "sales pipeline management," "content production at scale."

Role. Founder, PM, marketer, sales lead, executive, IC. Different roles have different perspectives and different content preferences.

Source or channel. Paid traffic, organic search, content referral, partner referral, direct. Different sources signal different intent and stage.

Geography or language. Domestic vs international; English-first vs other-language audiences. May warrant different funnels for compliance, currency, or cultural reasons.

The audience dimensions to use depend on the brand's strategy. Most B2B brands segment primarily by company size and use case; most consumer brands segment by demographic and behavioral attributes.

Stage dimensions

The dimensions that distinguish where the audience is in their journey.

Awareness. Just discovered the brand or the topic. Has not yet committed to research or evaluation. The audience is open but uncommitted.

Content fit: educational, broad value, brand-building. CTAs that fit: subscribe to content, get a framework, follow. CTAs that do not fit: book a demo, start a trial, buy now.

Consideration. Evaluating options actively. Has identified a need; comparing solutions. The audience is engaged but not yet decided.

Content fit: comparative, specific value, product-fit signals. CTAs that fit: see a calculator, take a quiz, download a comparison, book a demo. CTAs that do not fit: just-published-content awareness asks; or hard sell.

Decision. Choosing between specific options. The audience has narrowed the field; selecting is imminent.

Content fit: confidence-building, risk-reversal, urgency cues. CTAs that fit: start a trial, talk to sales, sign up. CTAs that do not fit: top-of-funnel awareness; long-form education.

Customer. Already a customer; ongoing relationship. Often left out of growth-funnel architecture even though it matters for retention and expansion.

Content fit: success-deepening, capability-expanding, community. CTAs that fit: upgrade, refer, join community, attend event.

The four stages cover most audiences. Some programs combine awareness-and-consideration or consideration-and-decision into 2-stage models; the principle is the same.

The intersection matrix

Audience x stage produces the matrix the funnel architecture serves.

Example matrix for a B2B SaaS company.

Audience	Awareness	Consideration	Decision
Solo founder	Path A	Path B	Path C
SMB team	Path D	Path E	Path F
Mid-market	Path G	Path H	Path I
Enterprise	Path J	Path K	Path L

12 cells. Some may share paths (Path A and Path D might be similar awareness content for solo and SMB). The matrix is the architecture's map.

Cell-sharing patterns.

Awareness paths often share more than decision paths (broad content can serve multiple audience segments).
Consideration paths often diverge by audience (the comparison content for enterprise differs significantly from SMB).
Decision paths almost always diverge (the offer for enterprise is different from SMB).

The matrix shows where the funnel architecture invests in unique paths and where it shares.

Segmentation discipline

The discipline boundaries.

Discipline 1: Define segments before designing paths. Without segments, paths are arbitrary. Always start with the matrix.

Discipline 2: Name segments specifically. "Solo founder pre-launch" beats "small business." Specific names reflect specific audiences.

Discipline 3: Validate segments with data. A segment that does not appear in actual audience data is theoretical. Validate against site analytics, sales data, or audience research.

Discipline 4: Maintain the matrix. Audiences shift; the matrix should be reviewed quarterly. Segments may merge or split over time.

Discipline 5: Avoid over-segmentation. 60-cell matrices are not maintainable. Start with 9-15 cells; expand only with justification.

Segmentation worked example

A B2B SaaS analytics platform.

Audiences (4).

Data analysts at SMB companies (50-200 employees).
Data leaders at mid-market companies (200-1000 employees).
Engineering leaders at enterprise companies (1000+ employees).
Solo data practitioners and consultants.

Stages (3).

Awareness (researching the analytics topic).
Consideration (evaluating analytics platforms).
Decision (selecting and signing up).

Matrix (12 cells).

Audience	Awareness	Consideration	Decision
Data analyst SMB	Educational content	Calculator, quiz	Trial, demo
Data leader mid-market	Strategic content	Comparison, ROI calc	Demo, custom quote
Engineering enterprise	Technical depth	Technical demo, security	Custom evaluation
Solo practitioner	Practical content	Self-serve resources	Free tier signup

Each cell has a defined path. The architecture invests where the cells need unique treatment; shares where the cells can use the same path.

Segmentation maintenance

Segments decay.

What decays.

Audience definitions that no longer match actual visitors.
Stage definitions that have shifted as buying processes evolved.
Cells that have become empty (no visitors fit the segment).
Cells that have become bloated (too many visitors fit one segment; needs sub-segmentation).

Maintenance cadence. Quarterly review of the matrix against actual audience data.

The drift indicator. Sales reports that the funnel-sourced leads do not match expected segments; analytics show segments combining or splitting unexpectedly.

Segmentation and the rest of the architecture

How segmentation drives the rest of the architecture.

Entry-point architecture. Each entry point routes to expected segments. The matrix tells the architecture where each entry point's traffic likely lands.

Tool-to-funnel mapping. Each tool serves specific cells in the matrix. The matrix tells the architecture which tools belong where.

Nurture sequence architecture. Each cell may have its own sequence (or sequences may be shared across similar cells). The matrix is the sequence design map.

Cross-tool data flow. As the audience moves through the matrix (awareness to consideration to decision), data flows with them. The matrix tracks the journey.

Funnel measurement. Per-cell conversion is the architecture-level metric. The matrix is the measurement framework.

Common segmentation failures

No segmentation. "Everyone" treated as the audience. Funnel cannot match.

Theoretical segments. Segments defined that do not exist in actual audience data.

Over-segmentation. 60-cell matrix that the team cannot maintain.

Under-segmentation. 4-cell matrix when the audience genuinely splits into more meaningful segments.

Stale segmentation. Matrix designed once; audience shifted; matrix not updated.

Segments without paths. Matrix defined but no funnel paths designed for the cells; segmentation is decorative.

Paths without segments. Funnel paths designed without clear segment mapping; treatments are arbitrary.

Methodology-level choices that stay in the public skill

The segmentation principle and discipline boundaries. Audience dimensions. Stage dimensions. The intersection matrix. Segmentation discipline (5 disciplines). Worked example. Segmentation maintenance. Segmentation and the rest of the architecture. Common failures.

Implementation choices that stay internal

Specific segments for the team's audience. Specific tooling for segment tagging and analysis. The team's matrix maintenance calendar. Specific path designs per cell. These vary by team.

Supporting file: references/common-funnel-architecture-failures.md

Common funnel architecture failures

9+ failure patterns with diagnoses and cures. The patterns that surface as "the funnel is not converting" or "tools work individually but conversion is flat" or "we cannot tell where the funnel is broken."

"Tools work individually; conversion is flat."

The diagnosis. Silo-funnels pattern. Tools as orphans; no architecture connects them.

The cure. Add cross-tool data flow; map tools to specific segments; design transitions between tools. Detail in references/cross-tool-data-flow-patterns.md and references/tool-to-funnel-mapping.md.

"Every audience gets the same nurture sequence."

The diagnosis. Kitchen-sink-funnels pattern. One sequence for everyone.

The cure. Segment-and-stage sequences. Different cells in the matrix get different sequences. Detail in references/nurture-sequence-architecture.md.

"We have 12 tools and no clear architecture."

The diagnosis. Tool-driven architecture. Tools accumulated without explicit segment mapping.

The cure. Build the matrix; map each tool to specific cells; retire tools that do not have a mapping or that compete with better-mapped alternatives.

"Specific segments convert at half the rate of others."

The diagnosis. Architecture for those segments may be broken. Or the segments may not be served by the current tools and sequences.

The cure. Audit those segments' funnel paths. Are tools mapped to them? Are sequences designed for them? If not, build for those segments. If yes, refine the existing path.

"We cannot tell which tools or sequences are driving conversion."

The diagnosis. Architecture-level metrics not tracked. Cannot attribute outcomes to architecture choices.

The cure. Instrument cross-tool conversion, sequence-to-tool conversion, segment-level downstream conversion, funnel-stage progression. Detail in references/funnel-measurement-patterns.md.

"We redesign every quarter; nothing improves."

The diagnosis. Continuous-redesign trap. Each redesign resets learning; nothing compounds.

The cure. Establish "no major redesign for X months" discipline. Refine continuously; redesign deliberately and rarely. Detail in references/funnel-iteration-discipline.md.

"The funnel was great at launch; now conversion has dropped 40 percent."

The diagnosis. Frozen-architecture trap. Designed once; never iterated; decay accumulated.

The cure. Quarterly audit. Refinement cadence. Detail in references/funnel-iteration-discipline.md.

"Specific transitions in the funnel have high drop-off."

The diagnosis. Hand-off-broken pattern. Tools work but the bridges between them break.

The cure. Audit transitions. Add cross-tool data flow so context travels. Promote downstream tools at upstream tools' exits. Detail in references/cross-tool-data-flow-patterns.md.

"Our chatbot, calculator, and quiz all serve consideration-stage audiences."

The diagnosis. Tool overlap without differentiation. Three tools competing for the same audience.

The cure. Differentiate the tools' purposes. Calculator for ROI questions; quiz for product matching; chatbot for FAQ. Or consolidate to fewer tools with clearer roles.

"Sales says quiz-sourced leads, calculator-sourced leads, and lead-magnet-sourced leads are different qualities."

The diagnosis. Tools may be attracting different segments; the architecture's segmentation is working but the tools are not all matched to high-quality segments.

The cure. Investigate which tools attract which segments. Optimize tool placement and design for the segments the brand serves best; deprioritize tools that attract low-quality segments.

"We added a new tool last quarter; it does not seem to help conversion."

The diagnosis. Orphan-tool pattern. Tool added without architecture mapping.

The cure. Map the new tool to specific segments. Decide where it fits in the matrix. Promote it where it fits; remove it from places it does not.

"Our funnel has 8 stages; visitors only complete 2."

The diagnosis. Funnel may be over-architected. Too many steps; audience cannot or will not progress through them all.

The cure. Simplify the funnel. Combine stages; remove unnecessary tools; align the funnel length to the audience's likely journey.

"Cross-tool tracking is broken; we cannot tell who used what."

The diagnosis. Identity threading or event tracking issue. Architecture's measurement infrastructure is broken.

The cure. Audit identity threading. Verify event tracking. Fix the infrastructure before further iteration. Detail in references/cross-tool-data-flow-patterns.md.

"Audiences arriving from paid traffic and organic traffic perform completely differently."

The diagnosis. Either entry-point routing is not differentiating, or the funnel paths are not serving paid and organic audiences differently.

The cure. Different routing for different entry points. Specific landing pages and sequences for paid vs organic. Detail in references/entry-point-architecture-patterns.md.

"The team built personas; the funnel does not reflect them."

The diagnosis. Segments defined but not implemented in the funnel architecture. Decorative segmentation.

The cure. Map personas to funnel cells. Build paths for the cells. The personas should drive the architecture, not sit in a deck.

"Our sequence-to-trial conversion is high; trial-to-paid is low."

The diagnosis. Architecture handles funnel up to trial well; the trial-to-paid stage may need its own architecture (or may be a product issue rather than funnel issue).

The cure. Treat trial-to-paid as its own funnel-stage progression. Build paths for trial users; nurture toward paid conversion.

"We have 15 lead magnets; 3 produce most of the leads."

The diagnosis. Magnet portfolio not maintained. Most magnets are dead but still on the site.

The cure. Audit and retire dead magnets. Free capacity for the strong ones. Detail in lead-magnet-design.

"We built a fancy architecture; the team cannot maintain it."

The diagnosis. Over-architecture. Architecture exceeds team capacity.

The cure. Simplify. Match architecture complexity to team capacity. Expand only when capacity grows.

"Funnel-sourced leads are different from sales-sourced leads."

The diagnosis. Likely fine. Funnel and direct sales serve different segments and stages. Both can be valuable.

The action. Track them separately. Optimize each for its specific path.

The pattern across failures

Most funnel architecture failures fall into one of three patterns.

Pattern 1: Tools without architecture. Silo, kitchen-sink, tool-driven, orphan-tool. The fix is to add explicit architecture (matrix, mapping, data flow).

Pattern 2: Architecture without measurement. Metric-blind, vanity-metric, broken tracking. The fix is to instrument architecture-level metrics.

Pattern 3: Architecture without maintenance. Frozen, decayed, unmaintained. The fix is iteration discipline (refine continuously, redesign rarely).

The metric pattern: funnel architecture failures often look fine on tool-level metrics. The signal is in cross-tool conversion, segment-level outcomes, and funnel-stage progression. Programs that track only tool metrics keep shipping the same architectural patterns.

Methodology-level choices that stay in the public skill

The catalog of failure patterns with diagnoses and cures. The pattern across failures (tools-without-architecture, architecture-without-measurement, architecture-without-maintenance). The principle that tool-level metrics alone are insufficient.

Implementation choices that stay internal

Specific failure cases the team has encountered and the lessons learned. Specific architecture-level dashboards. Specific cures the team applies. The team's audit and redesign processes. These vary by team.

Supporting file: references/cross-tool-data-flow-patterns.md

Cross-tool data flow patterns

Identity threading, context capture, segment tagging, sequence-tool integration.

When the audience moves from one tool to another in the funnel, the audience signal travels with them. Done well, cross-tool data flow makes the audience experience continuous and lets the brand match content to the audience's specific journey. Done poorly, every tool starts from scratch and the audience signal is lost.

The continuity principle

The audience experience should feel continuous across tools. Their interactions in one tool inform their experience in the next.

The win. A visitor takes a quiz; the quiz tags them as "mid-market mid-funnel." When they later open the calculator, the defaults reflect mid-market context. When they download a lead magnet, the sequence delivered matches the segment. The visitor experiences a coordinated brand journey.

The fail. The same visitor takes the quiz; the calculator does not know they took it; the lead magnet sequence is generic. Each tool is an island. The audience signal captured in one tool is wasted in the next.

The discipline. Data flows. Each tool's interactions inform subsequent interactions.

Pattern A: Identity threading

When the audience is identified, their identity carries forward across tools.

How it works.

The audience opts in (email submission, account creation, login).
Subsequent interactions are associated with that identity.
Tools across the funnel access the identity record to personalize.

Strengths.

Most powerful continuity mechanism.
Lets all tools share context for the same person.

Weaknesses.

Requires identity infrastructure (CRM, data warehouse, customer data platform).
Privacy considerations (handling identity data carefully).

When to use. When the program has identity infrastructure and the audience is willing to be identified (typically post lead-magnet download or account creation).

Pattern B: Context capture

Inputs from one tool feed into the next interaction.

How it works.

Tool A captures specific inputs (calculator values, quiz answers, form responses).
Those inputs are stored with the identity (or with an anonymous session token).
Tool B reads the inputs; uses them as defaults or context.

Example.

Quiz captures "team size: 75."
Calculator's defaults reflect team size 75.
Lead magnet's recommended resource matches team size 75.

Strengths.

Concrete continuity; the audience sees their inputs reflected.
Reduces re-entry friction.

Weaknesses.

Requires structured data capture (not just behavioral signals).
Inputs from different tools must align (no conflict if quiz and calculator both capture team size).

When to use. When tools capture overlapping or related context that benefits from shared use.

Pattern C: Segment tagging

Each interaction tags the audience with segment information that informs future routing.

How it works.

Tool A determines the audience's segment based on inputs (the quiz result; the calculator's input pattern).
The segment tag attaches to the audience record.
Subsequent tools and sequences route based on the tag.

Example.

Quiz result: "Mid-market operator."
Tag: segment = mid-market.
Subsequent: lead magnet sequence is the mid-market sequence; calculator defaults are mid-market; chatbot routing is mid-market-aware.

Strengths.

Lightweight. The tag is small; the routing logic uses it.
Compatible with most marketing automation.

Weaknesses.

Tag accuracy depends on the source tool's accuracy.
Tags can conflict (different tools assign different segments).
Tag staleness (the audience's segment may change over time).

When to use. Default pattern for cross-tool routing.

Pattern D: Sequence-tool integration

Email sequences include links to specific tools matched to the audience's segment.

How it works.

Sequence email includes a CTA: "based on your situation, this calculator can help you compare."
The CTA link includes parameters that pre-fill the calculator with the audience's known context.
Audience clicks; calculator opens with their context already populated.

Strengths.

Explicit cross-tool connection; the audience sees the journey.
Reduces friction at the calculator (audience does not re-enter known information).

Weaknesses.

Requires tooling for parameterized links and pre-fill.
The pre-fill must respect what the audience consented to share.

When to use. When the sequence is steering the audience toward specific tools and pre-fill would meaningfully reduce friction.

Conflict and source-of-truth

When different tools capture different values for the same attribute.

The pattern. The quiz says team size 75; the multi-step form says team size 60. Which is correct?

Approaches.

Latest wins. The most recent capture overrides earlier captures.
Source authority. Specific tools are designated as authoritative for specific attributes (form > quiz for verified data).
User confirmation. Conflict surfaces a confirmation prompt: "We have you down as 75; is that still correct?"

The discipline. Define source-of-truth for important attributes. Latest-wins is simple but can lose data; source authority is more disciplined but requires explicit definition.

Privacy and consent

Cross-tool data flow involves handling user data. Consent matters.

The principle. The audience should know what data flows where. Pre-filling a calculator with previously captured information is fine if the audience expects it; surprising them with knowledge they did not consent to share breaks trust.

Consent patterns.

Explicit opt-in to identity tracking ("save my progress").
Disclosure of data flow ("we use your quiz answers to personalize subsequent recommendations").
Easy data deletion or account closure.

Privacy regulations. GDPR, CCPA, and other regulations affect what data can flow and how. Compliance is essential; the architecture must respect the regulations applicable to the audience.

Anonymous-session continuity

When the audience is not yet identified.

The pattern. Browser-based continuity (cookies, local storage) lets tools share context within the same session even before identity capture.

Strengths.

Continuity without requiring early opt-in.
Smooth experience across same-session tool interactions.

Weaknesses.

Lost when the audience switches devices or clears cookies.
Limited persistence (typically days, not weeks).
Privacy considerations (cookies-based tracking has its own complications).

When to use. As a supplement to identity-based continuity; for early-funnel interactions before opt-in.

Cross-tool data flow architecture

How to design the data flow at the architecture level.

The data layer. A single data layer (CRM, customer data platform, data warehouse) holds the audience records. All tools read from and write to this layer.

The integration layer. Tools integrate with the data layer either directly (API) or through a middleware (Zapier, Segment).

The privacy layer. Consent and data-control mechanics live across the architecture; the data layer respects them.

Architecture-level discipline. Cross-tool data flow is infrastructure work, not just tool work. Building the infrastructure is part of the funnel architecture investment.

Cross-tool measurement

Track how data flows across tools.

Metrics.

Cross-tool engagement. What percentage of subscribers who engaged with tool A also engaged with tool B?
Identity capture rate. What percentage of visitors who interact with tools become identified?
Pre-fill usage. When pre-fill is offered, what percentage of users engage with the pre-filled tool?
Segment tag accuracy. Sample-based audit of whether segment tags match actual audience profiles.

Diagnostic uses. Low cross-tool engagement signals tools are not connecting in the audience's journey; low pre-fill usage signals the pre-fill is not visible or not valued.

Cross-tool data flow audit

Periodically audit the data flow.

The audit.

Walk through critical journeys end-to-end. Does data actually flow?
Verify identity threading works (logged-in user is recognized across tools).
Verify context capture works (inputs in tool A appear in tool B as expected).
Verify segment tagging works (quiz result tag triggers correct downstream sequences).
Verify sequence-tool integration works (sequence links pre-fill correctly).

The drift. Integrations break silently. Tool updates change data formats. Audit catches the drift.

Common data flow failures

No data flow. Each tool isolated; identity and context lost between tools.

Identity threading broken. Logged-in user not recognized across tools; same person treated as new visitor multiple times.

Context capture incomplete. Tool A captures inputs but tool B does not access them.

Segment tag conflicts. Different tools tag the same person differently; downstream routing inconsistent.

Pre-fill broken. Sequence link includes parameters but the tool does not honor them; audience re-enters known information.

Privacy violations. Cross-tool data flow happens without consent; audience surprised; trust damaged.

Stale data. Audience's situation has changed but tools still use old captured data.

Methodology-level choices that stay in the public skill

The continuity principle. Patterns A through D (identity, context, segment, sequence-tool integration). Conflict and source-of-truth. Privacy and consent. Anonymous-session continuity. Cross-tool data flow architecture. Cross-tool measurement. Audit cadence. Common failures.

Implementation choices that stay internal

Specific data layer choices for the team's stack. Specific integration tooling. Specific consent flows and privacy disclosures. The team's audit calendars. These vary by team.

Supporting file: references/entry-point-architecture-patterns.md

Entry-point architecture patterns

How visitors land vs how they're routed. Common entry points and their routing.

The funnel architecture maps entry points (where visitors arrive) to segments and paths (what they do next). Without entry-point architecture, every visitor goes through the same first experience regardless of where they came from.

The entry-routing principle

Each entry point has expected segments and stages. The first action available at the entry point should match those expectations.

The win. A visitor arrives via an ad about "B2B SaaS pricing." The landing page serves consideration-stage pricing content. The first available action is a pricing calculator and a demo CTA. The entry point's routing matches the visitor's likely intent.

The fail. Same visitor arrives via the same ad. The landing page is the homepage. The visitor lands in awareness-stage content with no clear next step. The mismatch costs the conversion.

The discipline. Each entry point's first experience matches the visitor's likely segment and stage.

Common entry points

The entry points most growth programs work with.

Paid landing page. Visitor arrives via paid ad (search, social, display). High intent; specific to the ad's promise.

Expected segment: usually narrow (the ad targeted specific audience). Expected stage: usually consideration or decision (paid traffic is rarely awareness-stage). Routing: landing page should serve the ad's specific promise; next-step action should match consideration or decision stage.

Organic content page. Visitor arrives via search or content discovery; awareness or research stage.

Expected segment: variable (organic search may surface multiple audience types). Expected stage: usually awareness or early consideration (research-driven). Routing: content should serve the search intent; secondary CTAs offer movement toward consideration.

Direct or returning visitor. Visitor arrives by typing URL or via bookmark; often returning.

Expected segment: variable (depends on prior interactions). Expected stage: variable (could be any stage). Routing: homepage should provide multiple entry paths to different segments and stages; navigation matters more than single CTA.

Referral. Visitor arrives via partner or word-of-mouth; warmer than paid.

Expected segment: variable (depends on referral source). Expected stage: usually consideration or decision (referrals indicate active interest). Routing: page should match the referral context; next-step action should reflect the warmth (free trial, demo, talk to sales often work).

Social. Visitor arrives via social post; awareness or interest.

Expected segment: variable (depends on social audience). Expected stage: usually awareness (social discovery is rarely buying intent). Routing: page should serve the social post's promise; soft CTAs (follow, subscribe, learn more) often work better than hard sells.

Tool entry. Visitor arrives via a calculator, quiz, or chatbot directly (often via shared link or specific tool URL).

Expected segment: matches the tool's audience. Expected stage: usually consideration (the tool is a consideration-stage artifact). Routing: tool should serve its specific value; next-step actions should connect tool output to broader funnel.

Entry-point routing patterns

How to route each entry point.

Pattern A: Direct match. Entry point routes directly to a specific landing page and CTA. Simple; works when the entry point's segment and stage are well-defined.

Pattern B: Routing layer. Entry point routes to a routing page that asks 1-2 questions and then sends to the matched destination. Useful when the entry point's segment is variable.

Pattern C: Personalized landing. Entry point routes to a landing page that adapts based on visitor attributes (source, behavior, profile). Sophisticated; requires personalization infrastructure.

Pattern D: Quiz-as-router. Entry point routes to a quiz that segments and recommends. Detail in quiz-and-assessment-design.

The choice depends on entry-point variability and infrastructure. Most programs start with Pattern A and add complexity as data shows the need.

Entry-point and segment matching

Each entry point likely surfaces specific segments.

The discipline. For each entry point, document the expected segments. The first experience should serve those segments.

Worked example.

Entry point: paid ad targeting "data analytics for SaaS."
Expected segments: data analysts and data leaders at SaaS companies.
Expected stage: consideration.
Routing: landing page on data analytics for SaaS; calculator showing ROI; CTA to demo.

The match is deliberate. Visitors arriving via this entry point get a first experience that fits their segment and stage.

Entry-point and stage matching

The first experience should match the visitor's likely stage.

Common mismatches.

Awareness-stage visitor lands on a hard-sell decision-stage page; bounces because not ready.
Decision-stage visitor lands on awareness-stage content; bounces because oversold on what they already know.
Consideration-stage visitor lands on either; serves the wrong intent.

The cure. Match the entry point's expected stage to the page's stage. Awareness pages serve awareness traffic; decision pages serve decision traffic.

Multi-entry funnels

When the same visitor arrives via different entry points across visits.

The pattern. A visitor sees an ad on Tuesday (paid entry); reads a blog post on Wednesday (organic entry); types the URL on Thursday (direct entry). Each entry point may surface a different first experience.

Architecture implications.

Personalization across visits requires identity threading.
Nurture sequences may need to acknowledge prior visits.
Cross-channel attribution becomes important.

The discipline. Architecture should accommodate multi-entry without confusion. The visitor's progression through the funnel respects their cumulative interactions, not just the latest entry.

Entry-point measurement

Track per-entry-point performance.

The metric. Per entry point: visitors, segment composition, stage composition, conversion to next action.

Diagnostic uses.

Entry points with low conversion: routing may be mismatched.
Entry points with high conversion: investigate what is working; replicate to other entries.
Entry points whose segment composition does not match expectations: the source may have shifted; review.

Entry-point and audience-segment audit

Periodically audit entry-point routing.

The audit.

For each entry point: what segments and stages are arriving?
Does the first experience match those segments and stages?
Is conversion at this entry point above or below baseline?

The drift. Entry points decay as ad targeting shifts, content rankings change, partners evolve. Quarterly audit catches the drift.

Entry-point anti-patterns

The single-funnel-for-every-entry. All visitors go through the same first experience regardless of entry. Routing not matching segments or stages.

The over-personalized-entry. Entry routing so specific that maintenance is impossible; many entries route to landing pages that exist only for one entry source.

The mismatched-entry. Entry expects one segment; landing page serves a different one. Conversion suffers.

The unmeasured-entry. Per-entry data not tracked; routing decisions are guesswork.

The orphan-entry. Entry point exists; no landing page or routing defined; visitors land somewhere generic.

Common entry-point failures

One landing page for everyone. Different entry points get the same first experience; routing not matching variability.

Wrong stage routing. Awareness traffic gets decision-stage CTAs; decision traffic gets awareness content.

Personalization without infrastructure. Architecture designed for personalization that the team cannot actually implement.

Entry-point drift. Entry sources shifted; routing not updated.

Single-tool entry. Only one tool serves an entry point; if the tool fails, the entry has no recovery.

Entry-conversion attribution missing. Cannot tell which entry points produce which downstream conversion.

Methodology-level choices that stay in the public skill

The entry-routing principle. Common entry points (6 patterns). Entry-point routing patterns (4 patterns). Entry-point and segment matching. Entry-point and stage matching. Multi-entry funnels. Entry-point measurement. Audit cadence. Anti-patterns. Common failures.

Implementation choices that stay internal

Specific entry points for specific programs. Specific routing logic per entry. Specific landing pages per entry. The team's audit calendars. These vary by team and program.

Supporting file: references/funnel-iteration-discipline.md

Funnel iteration discipline

When to refine, when to redesign. Avoiding the continuous-redesign and frozen-architecture traps.

Funnel architecture compounds when refined; collapses when constantly redesigned. The discipline is knowing when each is appropriate.

The compound-vs-reset distinction

Refinement compounds. Redesign resets.

Refinement. Targeted changes to specific tools, sequences, or transitions within the existing architecture. The architecture's bones stay; the muscles get stronger.

Redesign. Overhaul of the architecture. Segments redefined; tool-to-funnel mapping changed; sequences rebuilt. The architecture restarts.

The discipline. Refine continuously; redesign deliberately and rarely. Constant redesign prevents compounding; never iterating allows decay.

When to refine

Five conditions that signal refinement is appropriate.

Specific tools are underperforming relative to baseline. A calculator with declining conversion benefits from input adjustment, default updates, or methodology refinement. The architecture is fine; the tool needs attention.

Specific segments have lower conversion than peer segments. A segment that converts at 4 percent while peer segments convert at 10 percent has a fixable architecture issue. Refine the segment's path.

Specific transitions in the funnel are producing drop-off. The transition from quiz to recommended product page has high drop-off. Audit the transition; fix.

Sequence engagement is declining for specific cohorts. Newer subscribers to a sequence engage less than older subscribers. The sequence may have decayed; refresh content.

Specific entry points are routing wrong segments. A paid ad source has shifted; visitors arriving from it no longer match the segment the landing page serves. Adjust the routing.

These are refinements. The architecture is sound; specific elements need attention.

When to redesign

Four conditions that signal redesign is appropriate.

Audience composition has fundamentally shifted. The brand pivots; the target audience changes; the segments are no longer accurate. The matrix needs redesign.

Product or service strategy has changed. The brand offers a fundamentally different product line; the funnel that served the old products no longer fits. Redesign.

Competitive landscape has shifted significantly. A new competitor reshapes the buying process; the funnel needs to respond. Redesign may follow.

Multiple refine cycles have not produced expected results. The team has refined repeatedly; conversion has not moved. The issue may be architectural rather than tactical. Redesign worth considering.

These are redesigns. The architecture's fundamentals need to change.

The continuous-redesign trap

Teams that constantly redesign never benefit from architectural compounding.

The pattern. Every quarter, the team rethinks the funnel. New segments; new tools; new sequences. Each redesign is partially built before the next redesign starts.

The signal. Conversion does not improve over time. Each iteration starts over. Learning does not accumulate because the structure keeps changing.

The cost. The team's investment dilutes across redesigns. Tools never reach maturity. Sequences never stabilize.

The cure. Redesign infrequently. Refine continuously between redesigns. Set a "no major redesign for X months" discipline if needed.

The frozen-architecture trap

Teams that never iterate watch their architecture decay.

The pattern. The funnel was designed once; the team treats it as finished. No refinement; no redesign; no audit.

The signal. Conversion declines slowly over months and years. Tools age; sequences go stale; segments shift. The architecture does not respond.

The cost. The architecture's value erodes. Audiences move on; competitors improve; the brand falls behind.

The cure. Set refinement cadences. Quarterly audit; targeted refinements based on data. Acknowledge that no architecture stays optimal forever.

The middle ground

Refine continuously; redesign infrequently and deliberately.

Refinement cadence. Monthly or quarterly. Targeted; data-driven; small enough to test in isolation.

Redesign cadence. Annually at most. Often longer. Major triggers (audience pivot, product change, competitive shift) drive redesign rather than calendar.

The discipline. Both rhythms running in parallel. Refinement maintains; redesign responds to fundamental change.

Refinement workflow

How to iterate productively.

Step 1: Identify the gap. Data-driven; specific to a tool, segment, transition, or sequence.

Step 2: Hypothesize the cause. What might explain the gap?

Step 3: Design a treatment. What change would address the hypothesis?

Step 4: Test if possible. A/B test or before-after measurement when feasible.

Step 5: Validate. Did the metric move? Did downstream metrics also benefit?

Step 6: Roll out or roll back. Successful refinements stick; unsuccessful ones revert.

The discipline. Each refinement is hypothesis-driven and validated. Random changes do not compound.

Redesign workflow

How to redesign without resetting everything.

Step 1: Articulate why. What has fundamentally changed that warrants redesign?

Step 2: Preserve what works. Identify elements of the current architecture that are still appropriate. Do not throw away learning.

Step 3: Design the new architecture. Segment matrix; entry-point routing; tool-to-funnel mapping; sequence architecture. Document everything.

Step 4: Plan migration. How to transition existing audience and tools to the new architecture without losing momentum.

Step 5: Pilot before full rollout. Test the new architecture with a subset of audience or one segment before full deployment.

Step 6: Migrate. Roll out the new architecture; retire the old one.

Step 7: Monitor closely. Architecture-level metrics in the first months show whether the redesign delivered.

The discipline. Redesign is a project, not a flip of a switch. Plan it; pilot it; migrate; monitor.

The decay-driven redesign signal

How to know decay has accumulated to redesign level.

Signals.

Multiple refine cycles have not moved the metric.
Segments no longer describe the audience accurately.
Tools designed for one segment are being used by others (mapping has drifted).
The architecture diagram no longer matches the actual experience visitors have.
Quarterly audits surface the same issues quarter after quarter without fix.

When these signals accumulate, refinement is not enough. Redesign is needed.

Iteration measurement

How to know iterations are working.

The metric. Architecture-level metrics improving over time. Cross-tool conversion rising; segment-level conversion rising; funnel-stage progression accelerating.

The trap. Improving one metric while others decline. A refinement that lifts cross-tool conversion but tanks lead quality is not net positive.

The discipline. Watch the portfolio of metrics, not individual ones. Refinement should improve the architecture's overall outcomes, not just one measure.

Common iteration failures

Continuous redesign. Architecture never stabilizes; learning does not compound.

Frozen architecture. Architecture never iterates; decay accumulates.

Random refinement. Changes without hypothesis or testing; results are noise.

Refinement without measurement. Cannot tell if changes are working.

Redesign without preserving learning. Throws away what was working alongside what was not.

Redesign without migration plan. Audience and tools left in transition; experience suffers.

Iteration without portfolio metrics. Improving one metric while damaging others.

Methodology-level choices that stay in the public skill

The compound-vs-reset distinction. When to refine (5 conditions). When to redesign (4 conditions). The continuous-redesign trap. The frozen-architecture trap. The middle ground. Refinement workflow. Redesign workflow. The decay-driven redesign signal. Iteration measurement. Common failures.

Implementation choices that stay internal

Specific iteration calendars for the team. Specific refinement and redesign processes. Specific tooling for testing iterations. The team's iteration history and lessons. These vary by team.

Supporting file: references/funnel-measurement-patterns.md

Funnel measurement patterns

Architecture-level vs tool-level metrics. What to measure, what is noise.

Funnel measurement should reveal architecture quality, not just tool quality. Tool-level metrics tell you whether each tool is working; architecture-level metrics tell you whether the tools work together.

The architecture-vs-tool measurement distinction

Two layers of measurement.

Tool-level metrics. Each tool's individual performance (calculator conversion, quiz completion, lead-magnet downloads). Detail in each tool's skill.

Architecture-level metrics. How the tools and sequences compose. Cross-tool conversion, sequence-to-tool conversion, segment-level downstream conversion, funnel-stage progression.

The discipline. Measure both layers. Architecture-level metrics are often the missing measurement.

Architecture-level metric: Cross-tool conversion

What percentage of audience that hits tool A then engages with tool B.

The metric. Count the visitors who interact with tool A (calculator, quiz, lead magnet, etc.). Of those, how many subsequently interact with tool B?

Why it matters. Cross-tool engagement signals whether the funnel is composing. High cross-tool conversion means the architecture is working; low cross-tool conversion means tools are silos.

Measurement methods.

Identity-based tracking (same identified user across tools).
Session-based tracking (same session sees multiple tools).
Cohort analysis (cohorts entering through tool A and their downstream tool engagement).

Diagnostic uses.

Low cross-tool conversion: tools may not be promoted to each other's audiences; transitions may be broken.
Specific tool pairs underperforming: those transitions need design attention.

Architecture-level metric: Sequence-to-tool conversion

What percentage of nurture sequence subscribers engage with downstream tools.

The metric. Count subscribers in a sequence. Of those, how many click through to a tool the sequence promoted?

Why it matters. Sequences should drive subscribers toward tools matched to their segment-and-stage. Low sequence-to-tool conversion signals that the sequences are not effectively bridging to tools.

Diagnostic uses.

Specific sequence emails with low click-through: the email's tool promotion may not match the audience.
Specific tools with low sequence-driven traffic: the sequences may not be promoting those tools enough.

Architecture-level metric: Segment-level downstream conversion

Per-segment conversion to the program's main goal.

The metric. For each segment in the matrix: what percentage convert to the main goal (trial, demo, purchase) within a defined timeframe?

Why it matters. Different segments will convert at different rates; segments significantly underperforming relative to peers signal architecture issues.

Diagnostic uses.

Segments with low downstream conversion: the funnel architecture for that segment may be broken or under-developed.
Segments with high downstream conversion: investigate what is working; replicate to other segments.

Architecture-level metric: Funnel-stage progression

What percentage of audience moves from awareness to consideration to decision over time.

The metric. Track audience as they progress through stages. Awareness audience this month; what percentage are in consideration next month; what percentage in decision the following.

Why it matters. The funnel's job is to progress audience through stages. Low progression signals the nurture sequences and tools are not advancing the relationship.

Diagnostic uses.

Slow progression: sequences may be too educational without enough advancement; or the audience may be getting stuck.
Fast progression but low conversion: progression without quality.

Tool-level metrics

Each tool has its own metrics. Detail in each tool's skill.

Calculator. Conversion rate per visitor; tier-2 (email gate) conversion; downstream conversion of calculator-sourced leads.

Quiz. Completion rate; per-segment downstream conversion; recommendation click-through.

Lead magnet. Download rate; sequence engagement; downstream conversion of magnet-sourced subscribers.

Multi-step form. Completion rate; per-step drop-off; lead quality.

Chatbot. Resolution rate per intent; escalation rate; downstream conversion.

The tool-level metrics tell you whether each tool is doing its job. The architecture-level metrics tell you whether the tools are doing the funnel's job.

What is noise

Metrics that look important but are not.

Total tool engagements. Volume without context. A tool with 10000 engagements per month tells you nothing without conversion context.

Email open rate alone. Open rate is a leading indicator at best; sequence-to-conversion is the metric that matters.

Time on page or session length. Often correlates with confusion as much as engagement.

Bounce rate alone. High bounce rate on awareness content may be normal; on decision content may signal a problem; aggregate bounce rate is noise.

The discipline. Measure outcomes, not activity. Activity metrics are noise unless connected to outcome metrics.

Measurement granularity

How granular to measure.

Per-tool measurement. Standard. Each tool tracked.

Per-segment-per-tool measurement. Measure each tool's performance per segment. Surfaces segment-specific tool issues.

Per-segment-per-stage measurement. Measure progression and conversion per cell in the matrix.

Per-cohort measurement. Track cohorts (groups arriving in the same period) over time. Surfaces evolution and decay.

The discipline. Granularity matters when it informs decisions. Per-segment-per-stage is often where the diagnostic value lives; per-cohort surfaces decay.

Attribution

Connecting outcomes to specific tools and sequences.

The challenge. Audiences interact with multiple tools and sequences. Which one drove the conversion?

Approaches.

First-touch attribution. Credit goes to the first interaction.
Last-touch attribution. Credit goes to the most recent interaction.
Multi-touch attribution. Credit distributed across interactions.
Position-based attribution. Credit weighted by position (often U-shaped or W-shaped).

The honest framing. Attribution is a model. No model is perfectly accurate. Choose a model deliberately; understand its biases; report consistently.

Measurement and architecture decisions

How metrics inform architecture changes.

The pattern. Metrics surface gaps; architecture decisions address them; subsequent metrics validate.

Examples.

Cross-tool conversion low: redesign transitions; promote tool B in tool A's exit; measure improvement.
Specific segment underperforming: review segment's funnel path; adjust tools or sequences; measure.
Funnel-stage progression slow: review sequence design; add or refine; measure.

The discipline. Metrics inform decisions; decisions are tested; results validated. Without measurement, architecture changes are guesswork.

Measurement instrumentation

What needs to be in place.

Identity tracking. Identified users tracked across tools. Event tracking. Each tool interaction logged with event data. Funnel definition. The funnel stages and segments defined in the analytics tool. Cohort capability. Ability to define and track cohorts. Reporting. Dashboards or reports that surface architecture-level metrics.

The discipline. Instrumentation should be in place before launch, not added later. Retrofitting measurement is harder than building it in.

Measurement cadence

How often to look at architecture-level metrics.

Weekly review. For high-velocity programs or recently launched architectures. Catches regressions and informs rapid iteration.

Monthly review. For stable programs. Tracks trends and surfaces gradual decay.

Quarterly review. Comprehensive architecture audit. Per-cell analysis; segment-level deep dive; funnel-stage progression.

Triggered review. When tools change, when segments shift, when external factors (market, competition) change.

Common measurement failures

Tool-level only. Architecture-level metrics not tracked; cannot diagnose composition issues.

Vanity metrics. Volume metrics without conversion context.

No segment-level granularity. Aggregate metrics hide segment-specific issues.

Attribution model not chosen. Reports inconsistent because attribution is ad-hoc.

No cohort tracking. Cannot see decay or evolution.

Metrics without action. Metrics reviewed but no decisions follow.

Confounded data. Multiple changes deployed without isolation; cannot attribute outcomes to changes.

Methodology-level choices that stay in the public skill

The architecture-vs-tool measurement distinction. Architecture-level metrics (cross-tool, sequence-to-tool, segment-level, funnel-stage). Tool-level metrics (cross-reference). What is noise. Measurement granularity. Attribution approaches. Measurement and architecture decisions. Instrumentation requirements. Measurement cadence. Common failures.

Implementation choices that stay internal

Specific dashboards for specific programs. Specific tooling for measurement. Specific attribution models. The team's reporting conventions. These vary by team.

Supporting file: references/nurture-sequence-architecture.md

Nurture sequence architecture

Per-segment, per-stage sequence variation. The matched sequence win.

Different segments at different stages get different nurture sequences. The sequences match the audience's situation and stage. Done well, sequences compound the brand's relationship with the audience; done poorly, sequences treat everyone the same and convert no one well.

The matched-sequence principle

Each segment-and-stage cell warrants a sequence designed for that cell. Different cells get different sequences.

The win. An SMB consideration-stage subscriber gets a 5-email sequence focused on SMB-relevant comparison content, ROI examples from similar SMB customers, and a soft demo invitation. The sequence reads as if written for them.

The fail (kitchen-sink sequence). Every subscriber regardless of segment or stage gets the same 5-email sequence. The content is generic enough to send to all; specific enough for none. SMB subscribers see enterprise examples; enterprise subscribers see SMB examples; conversion uniformly low.

The discipline. Sequences vary by segment and stage. The matrix from audience-and-stage-segmentation is the sequence design map.

Sequence variation by stage

Stage-specific sequence patterns.

Awareness sequence.

Goal: build relationship; deepen brand association with the topic.
Content: educational, broad value, brand-building.
Frequency: typically lower (weekly to bi-weekly); the audience is not in active research.
Soft offers: subscribe to newsletter, follow on social, attend webinar.
Hard offers: rare; awareness audiences are not buying yet.

Consideration sequence.

Goal: move from "evaluating" to "selecting."
Content: comparative, specific value, product-fit signals.
Frequency: higher (every 3-7 days); audience is actively evaluating.
Soft offers: see comparison guide, take quiz, calculator.
Hard offers: demo, trial, talk to sales (toward end of sequence).

Decision sequence.

Goal: commit; sign up; purchase.
Content: confidence-building, risk-reversal, urgency cues, case studies of similar customers.
Frequency: high (every 2-4 days); audience is close to deciding.
Soft offers: rarely; mostly hard offers.
Hard offers: trial, signup, talk to sales, custom quote.

Customer sequence (often missed).

Goal: deepen success; expand and retain.
Content: feature deep-dives, success stories from similar customers, community invitations.
Frequency: ongoing; matches product cadence.
Soft offers: attend events, refer others.
Hard offers: upgrade, add-on, expansion.

Sequence variation by audience

Audience-specific sequence patterns.

SMB audience.

Tone: practical, fast-execution, peer-to-peer.
Examples: SMB customers; focus on quick wins and resource constraints.
Content depth: shorter, scannable, action-oriented.

Mid-market audience.

Tone: strategic, considered, multi-stakeholder.
Examples: mid-market customers; focus on team adoption and process change.
Content depth: moderate; depth where it matters; summaries for executives.

Enterprise audience.

Tone: rigorous, evidence-based, formal.
Examples: enterprise customers; focus on security, scale, integration.
Content depth: deep; white papers, technical documentation, case studies with metrics.

Solo or creator audience.

Tone: personal, founder-to-founder.
Examples: similar solo practitioners; focus on individual impact and time savings.
Content depth: practical; templates and how-tos over strategy.

Sequence design discipline

How to design each sequence.

Step 1: Define the goal. What conversion does this sequence drive? Awareness to consideration; consideration to demo; demo to decision; decision to purchase.

Step 2: Define the audience. Which segment-and-stage cell does this sequence serve?

Step 3: Outline the arc. What is the email-by-email progression? Each email should have a purpose; cumulatively the arc moves the subscriber toward the goal.

Step 4: Match content to arc. What specific content (template, case study, framework, demo invitation) fits each step?

Step 5: Define triggers and cadence. What triggers the sequence (lead magnet download, demo request, behavior signal)? What is the spacing?

Step 6: Define the soft and hard offers. Where do soft offers appear? Where do hard offers appear? At what point does the sequence make a direct ask?

Step 7: Define the exit. When does the sequence end? Where do subscribers go after (newsletter, segment-specific stream, retired)?

The output is a documented sequence ready to build and ship.

Sequence cadence

How frequently to send.

Awareness cadence. Weekly to bi-weekly typical. The audience is not in active research; over-sending feels intrusive.

Consideration cadence. Every 3-7 days typical. The audience is actively evaluating; cadence matches their consideration pace.

Decision cadence. Every 2-4 days typical. The audience is close to deciding; cadence reflects urgency.

Customer cadence. Variable. Match product cadence and customer engagement patterns.

The cadence-too-frequent risk. Daily sends can fatigue; unsubscribe rates climb.

The cadence-too-infrequent risk. Weekly sends to consideration audiences can lose momentum; the audience moves on.

Sequence content sourcing

Where the content for sequences comes from.

Repurposed content. Existing blog posts, case studies, white papers can populate sequences. Cost-effective; benefits from existing content investments.

Sequence-original content. Content written specifically for the sequence. More effort; can be highly tailored to the audience and arc.

Hybrid. Most sequences mix repurposed and original. Original content for the key arc moments; repurposed content for supplementary value.

The discipline. Sequence content should fit the sequence's audience and stage; off-fit content (even good content) weakens the sequence.

Sequence triggers

What launches the sequence.

Trigger types.

Lead magnet download. Most common trigger.
Calculator completion. With segment data captured.
Quiz completion. With segment matched to result.
Multi-step form submission. Demo request, qualification.
Behavior signal. Visited specific pages, viewed pricing, abandoned cart.
Manual addition. Sales team adds a contact.

The trigger discipline. The trigger informs which sequence the subscriber enters. A lead-magnet download for an awareness-stage resource enters the awareness sequence; a calculator completion with consideration-stage signals enters the consideration sequence.

Trigger-segment routing. Multiple triggers can route to multiple sequences based on captured segment information. The trigger is one signal; segment is another.

Sequence intersection and routing

When subscribers might enter multiple sequences.

The challenge. A subscriber downloads two lead magnets in the same week. Each magnet has its own sequence. Should they enter both?

Approaches.

Override. Latest trigger overrides; subscriber enters the latest sequence and exits prior ones.
Concatenate. Subscriber completes the first sequence, then enters the next.
Pause. Active sequence pauses other triggers; subscriber returns to queue after current sequence.
Multi-path. Subscriber enters multiple sequences simultaneously (risk of frequency overload).

The choice depends on subscriber experience and sequence design. Most programs benefit from override or pause patterns to avoid frequency overload.

Sequence and offer alignment

The offers in the sequence must match the audience.

The principle. A sequence for SMB consideration-stage subscribers should pitch SMB-appropriate offers. Pitching enterprise offers in this sequence wastes the audience signal.

Offer alignment failures.

Magnet attracts SMB; sequence pitches enterprise.
Awareness sequence pitches hard sales offers prematurely.
Decision sequence pitches awareness content the subscriber outgrew.

The cure. Sequence offers reflect the audience and stage the sequence serves.

Sequence measurement

Per-sequence metrics.

Open rate. Per email; per sequence overall.

Click-through rate. Per email; per sequence.

Conversion to next step. What percentage of subscribers in this sequence completed the desired conversion?

Unsubscribe rate. Per email; per sequence.

Sequence-to-customer conversion. What percentage of subscribers in this sequence eventually became customers?

Diagnostic uses. Low open rates per email signal subject-line issues; low click-through signals content fit issues; high unsubscribe rates signal cadence or content problems.

Sequence maintenance

Sequences decay.

What decays.

Content references go stale (outdated case studies, retired products).
Offers change (new products, new pricing, new programs).
Audience composition shifts; sequence content no longer fits.
Email deliverability changes; subject lines that worked stop working.

Maintenance cadence. Quarterly review of every active sequence. Update content; refresh offers; verify links.

The drift indicator. Sequence performance declining over time signals decay; specific cohorts (newer subscribers vs older) performing differently signals audience shift.

Common sequence failures

One sequence for everyone. Kitchen-sink pattern; matches no segment specifically.

Sequence-trigger mismatch. The trigger captured one segment; the sequence is designed for another.

Offer misalignment. Sequence pitches offers that do not match the audience.

Cadence wrong for stage. Awareness cadence on consideration audience; consideration cadence on awareness audience.

No trigger logic. Subscribers enter the same default sequence regardless of how they were captured.

Sequence-orphan magnets. Lead magnets without follow-up sequences; subscribers go cold.

Stale sequence content. Sequence designed once; content no longer reflects the brand or product.

No sequence measurement. Sequence performance unknown; maintenance is guesswork.

Methodology-level choices that stay in the public skill

The matched-sequence principle. Sequence variation by stage (4 stages). Sequence variation by audience (4 audiences). Sequence design discipline (7 steps). Sequence cadence. Sequence content sourcing. Sequence triggers. Sequence intersection and routing (4 approaches). Sequence and offer alignment. Sequence measurement. Sequence maintenance. Common failures.

Implementation choices that stay internal

Specific sequences for specific segments. Specific email content in brand voice. Specific tooling for sequence automation and measurement. The team's cadence baselines. These vary by team.

Supporting file: references/tool-to-funnel-mapping.md

Tool-to-funnel mapping

Which tools serve which entry points and segments. Each tool in the growth toolkit has a place in the funnel architecture; the mapping makes the place explicit.

Without explicit mapping, tools end up serving everyone (and serving no one well) or getting deployed where they do not fit. With explicit mapping, each tool serves the segments where it adds the most value.

The mapping principle

Each tool serves specific segments at specific stages from specific entry points. The mapping is documented, not implicit.

The win. A team's calculator is mapped to consideration-stage SMB and mid-market visitors arriving via organic content. The calculator's design (inputs, defaults, methodology) reflects this segment. Other segments do not see the calculator featured prominently; they see tools matched to their segment.

The fail. A team's calculator is featured on every page for every visitor. The calculator's design is generic to serve everyone. SMB visitors see enterprise inputs; enterprise visitors see SMB defaults. The calculator serves nobody well.

The discipline. Each tool has a defined place. The architecture documents which segments and stages and entry points the tool serves.

Common tool-to-funnel mappings

How each growth tool typically maps.

Lead magnet. Often serves awareness-to-consideration transition.

Audience: awareness-stage visitors who would benefit from a focused resource.
Entry points: blog posts, content discovery, paid ads on educational topics.
Position in funnel: captures email; routes to nurture sequence that bridges to consideration.
Detail in lead-magnet-design.

Calculator. Often serves consideration stage.

Audience: visitors evaluating options who need to defend a specific decision.
Entry points: pricing pages, comparison content, paid ads on solution-evaluation.
Position in funnel: provides defensible numeric output; routes to demo or trial CTA.
Detail in calculator-design.

Quiz. Variable depending on design.

Awareness quizzes: content marketing, brand-building. Captures email; routes to broad nurture sequence.
Consideration quizzes: product matching, fit assessment. Captures email; routes to product-specific sequence.
Decision quizzes: plan selection, configuration. Captures email and routes to specific sales motion or signup.
Detail in quiz-and-assessment-design.

Multi-step form. Often serves decision or qualification stage.

Audience: visitors with high intent who need to provide structured information.
Entry points: demo CTAs, talk-to-sales pages, application flows.
Position in funnel: captures qualified intent; routes to sales or to next-stage automation.
Detail in multi-step-form-design.

Chatbot. Cross-cutting; can serve any stage with intent recognition routing.

Audience: any visitor who has questions the bot can handle.
Entry points: any page where conversation might add value.
Position in funnel: handles in-conversation routing; escalates to humans for complex cases.
Detail in chatbot-flow-design.

Mapping examples by audience segment

How tools map for specific segments.

Solo founder, awareness stage.

Lead magnet: practical template they can use today.
Quiz (optional): "what stage of growth are you in" with matched recommendations.
Chatbot: yes, for FAQ; lightweight routing.
Calculator, multi-step form: probably not at this stage.

SMB team, consideration stage.

Calculator: ROI estimate matched to SMB context.
Lead magnet: comparison guide or worked example.
Multi-step form: demo request capture.
Chatbot: yes, for product-specific questions.
Quiz (optional): plan recommendation.

Mid-market team, consideration-to-decision.

Calculator: ROI estimate with mid-market context.
Multi-step form: demo request with qualification.
Chatbot: yes, with escalation to sales for complex questions.
Lead magnet (optional): white paper or case study.
Quiz: probably not (mid-market buyers often skip quizzes).

Enterprise, decision stage.

Multi-step form: enterprise demo request with detailed qualification.
Chatbot: lightweight; escalation-heavy.
Custom calculator: with enterprise-specific inputs and ROI factors.
Lead magnet, quiz: usually not (enterprise buyers expect direct human attention).

The mapping is segment-aware. Tools that fit one segment may not fit another.

Mapping examples by stage

How tools map for specific stages.

Awareness stage.

Lead magnets prominent. Quizzes can serve. Calculators less common (consideration is when calculators earn their value). Chatbots support.
Goal: capture awareness-stage email; route to nurture sequence.

Consideration stage.

Calculators central. Quizzes useful for product matching. Lead magnets can deepen value. Chatbots support specific questions.
Goal: convert consideration into qualified intent; route to demo or trial.

Decision stage.

Multi-step forms central (demo requests, qualified intent capture). Calculators support specific decisions. Chatbots route to sales.
Goal: convert decision-stage intent into commitment.

Customer stage.

Onboarding flows (which can use multi-step forms). Chatbots for support. Lead magnets and quizzes less central; replaced by in-product education.
Goal: deepen customer success; expand and retain.

Mapping discipline

How to make the mapping rigorous.

Discipline 1: Document the mapping. Write down which tools serve which segments and stages. The document is the architecture's reference.

Discipline 2: Match tool design to mapping. A tool serving SMB should have SMB-relevant inputs and defaults; a tool serving enterprise should reflect enterprise context.

Discipline 3: Promote tools where they fit. Show calculators on consideration-stage pages; show lead magnets on awareness-stage pages. Generic tool placement on every page dilutes their value.

Discipline 4: Retire tools that do not fit. A tool that does not have a mapping is decorative. Either find its place or retire it.

Discipline 5: Audit the mapping quarterly. Mappings decay as audience composition shifts. Quarterly review catches drift.

Multi-tool segments

Some segments use multiple tools across their journey.

The pattern. A consideration-stage SMB visitor uses a lead magnet (awareness arrival), a calculator (consideration depth), then a multi-step demo form (decision intent). Three tools across the journey.

Architecture implications.

Each tool serves a specific moment in the visitor's journey.
Cross-tool data flow lets each tool benefit from earlier interactions.
Tools should not duplicate each other's value.

The discipline. Tools complement, not duplicate. Each tool earns its place in the segment's journey.

Tool overlap and choice

When multiple tools could serve the same segment-and-stage cell.

The pattern. A team has both a calculator and a quiz that could serve consideration-stage SMB.

The decision. Choose the tool that serves the segment best, or use both with clear differentiation.

Calculator: when the consideration involves a specific calculation (ROI, savings, sizing).
Quiz: when the consideration involves categorization or product matching.
Both: when the segment benefits from both, with clear positioning of when each helps.

The discipline. Avoid having multiple tools competing for the same segment without clear differentiation. Audiences pick the most prominent; the others underperform.

Tool gaps

When the mapping reveals gaps.

The pattern. The architecture documents which tools serve which segments. Some cells in the matrix have no tool; the audience there has no relevant tool to engage with.

The decision. Either build a tool to fill the gap, or accept that some cells use generic content rather than tools.

Build when the segment is high-value and the tool would meaningfully improve conversion.
Accept when the segment is small or the tool would not earn its build cost.

The architecture surfaces gaps; the team decides what to do about them.

Tool-mapping audit

Periodically audit which tools serve which segments and how well.

The audit.

For each tool: which segments does it currently serve? Which segments does it actually attract?
For each cell in the matrix: which tools are mapped to it? Are they performing?
Are any tools serving segments outside their intended mapping (drift)?

The drift indicators. Tool conversion drops; tool's audience composition changes; tool gets traffic from segments it was not designed for.

Common mapping failures

No mapping. Tools deployed without explicit segment-and-stage assignment.

Mismatched mapping. Tool serving segments it was not designed for; tool's design does not fit the audience.

Decorative mapping. Mapping documented but not enforced; tool appears everywhere regardless of mapping.

Stale mapping. Mapping designed once; not updated as tools or audiences evolved.

Tool overlap without differentiation. Multiple tools competing for the same segment; audience splits; none performs well.

Mapping gaps unaddressed. Cells in the matrix have no tool support; the architecture has holes.

Methodology-level choices that stay in the public skill

The mapping principle. Common tool-to-funnel mappings (5 tools). Mapping examples by audience segment (4 examples). Mapping examples by stage (4 examples). Mapping discipline (5 disciplines). Multi-tool segments. Tool overlap and choice. Tool gaps. Tool-mapping audit. Common failures.

Implementation choices that stay internal

Specific tool-to-segment mappings for specific programs. Specific tool placement decisions on specific pages. The team's audit calendars. These vary by team and program.

Common questions

How do I install Funnel flow architecture in Cursor, Claude Code, or Codex?

Run npx skills add rampstackco/claude-skills --skill funnel-flow-architecture in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Funnel flow architecture, not every skill in the repository.

Where does Funnel flow architecture come from and what license is it under?

Funnel flow architecture comes from the rampstackco/claude-skills repository on GitHub. That repository has 393 GitHub stars. The skill is published under the MIT license.

Prefer plain text? Read the Funnel flow architecture guide as markdown.