# Guided funnel creator

Research and implementation: October 25, 2026. Available through **Guided creator**
or **Start with a plan** in the funnel library, in both demo and connected workspace
views. It creates a draft using the existing editor and persistence boundary.

## Experience

1. **Your campaign:** business, audience, one of ten industry groups (or Other), and
   one goal: contact enquiry, resource request, or event interest.
2. **Your approach:** choose an original strategy, with explanation, suitable uses,
   source links, and a clear distinction between our interpretation and the source.
3. **Your offer:** name, headline, customer context, up to six deliverables, action
   wording, and the actual follow-up process. Evidence and ways to reduce hesitation
   are optional. Missing evidence is omitted from the resulting page.
4. **Your look:** industry recommendations plus search across all 199 templates.
   Keep the chosen design's native hero structure, photos, colors, and typography.
5. **Review & create:** actual native landing/follow-up previews at desktop/phone
   sizes, editorial checks, and creation into the existing visual editor.

The three approaches change native section order. All sample marketing copy and
follow-up content are replaced by the user's answers. Form-led hero designs keep
one early form; other designs close with one form. All primary buttons target it.
Every generated funnel has a native thank-you step that describes the supplied
process, rather than claiming a booking, purchase, or delivery happened.

The creator assembles pages from answers; it does not pretend to make an AI call.
The existing editor still supports AI rewriting when the workspace is configured.
It does not configure automatic resource delivery, event reservations, payments, or
external scheduling. Those boundaries are explained where users choose a goal and
write the follow-up. No new schema, backend function, or deployment is required.

Moving backward preserves answers. Native required fields and trimmed/length/line
validation prevent incomplete or truncated briefs. A failed save preserves the
creator state and allows retry. Closing the creator or reloading before creation
discards the unsaved brief; only explicitly created funnels are persisted.

## First-party sources and original interpretations

| Our approach     | Educational reference                                                                                                     | Application                                                                                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Offer first      | [Alex Hormozi / Acquisition.com: The Value Equation](https://www.acquisition.com/training/offers4)                        | Make the offered result and contents concrete, support claims, and explain the effort involved. |
| Customer story   | [Donald Miller / StoryBrand: Your Brand Is Not the Hero](https://storybrand.com/downloads/your-brand-is-not-the-hero.pdf) | Reflect the customer's situation and give them an understandable path forward.                  |
| Explain & invite | [Russell Brunson / ClickFunnels: Hook, Story, Offer](https://www.clickfunnels.com/blog/hook-story-offer/)                 | Connect an opening promise to useful context and a clear invitation.                            |

These sources describe their authors' marketing ideas. They do not establish a
conversion uplift for our implementation. The rationale text explicitly labels
our interpretation. No source statistics or earnings claims are adopted. The
questions, helper text, previews, and page assembly are our own. There is no copied
worksheet, branded diagram, course material, or competitor logo. Attribution stays
in the creator's educational UI, not the visitor's generated landing pages.

## Naming and intellectual-property boundary

The [U.S. Copyright Office](https://www.copyright.gov/help/faq/faq-protect.html)
distinguishes ideas/methods from their particular expression. The
[USPTO's likelihood-of-confusion guidance](https://www.uspto.gov/trademarks/search/likelihood-confusion)
explains that similar marks and related offerings can cause confusion about source.
That guidance is the basis for the following product choices, not legal clearance:

- Use our own descriptive approach names; do not brand a feature as an official
  Hormozi, StoryBrand, or ClickFunnels product or certification.
- Identify third parties only as educational sources, linked to original material.
- State that the guide is independent and not affiliated, certified, or endorsed.
- Write original prompts and examples, and retain our own interface and designs.

"Inspired by" by itself does not establish permission or remove confusion risk.
These implementation choices do not establish that all proposed marketing uses
are legally cleared. Brand-forward commercial claims would need separate review.

## Validation

`tests/funnel-guide.test.ts` checks all 199 visual designs for valid native drafts,
one visible form, two semantic H1s (one per page), working next steps, valid SEO
business/title fields, and no missing publish destinations. It also checks strategy
ordering, supplied-only evidence, all industry groups, cross-industry search,
unknown designs, whitespace, lengths, and excessive offer-detail lines.

`tests/integration/funnel-guide.mjs` exercises all five steps and all three methods,
desktop/phone layouts, source links, native and semantic validation, design search
reset, review pages, inactive preview forms, backward navigation, storage failure
and retry, editor creation, and reload persistence. Outputs are ignored under
`artifacts/funnels/guided-review/`. Real backend writes, AI calls, messages, and
production deployment are outside this local validation.

Final results: 65 unit tests pass, including generation from every existing visual
design. A fresh production build and all three desktop/phone creator walkthroughs
pass. Generated drafts complete simulated private-preview form journeys. The
existing editor drag/drop/history/save regression passes. A real Tailscale browser
walkthrough also passes. No page/hydration errors or POST requests occurred in
successful runs. The wizard's mobile progress bar keeps the active step visible.
