Skip to content

opensite-ai/opensite-skills / funnel-flow-architecture

funnel-flow-architecture

Verified

Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when audience segments share one nurture path, or when a funnel is being architected from scratch.

references/funnel-iteration-discipline.md

View on GitHub
# 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.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall