Bridge Funnel

Split page, StoryBrand left, concierge right. Email gate at the aha moment. TP-24/TP-25.

BUILT-DARK, traffic paused

One page, split left and right. The left is a StoryBrand-clear promise with a face. The right is the Sales Concierge running a 12-scene guided journey: three easy taps, a visible score building, the email gate right at the aha threshold, one prescribed next step, a Trust x Heat x Weight routed close. Same spine for every business. Five thin variant configs point it at five different jobs.

This is the Journey Widget vision made concrete, wearing the Seven Moves as its skeleton. It implements TP-24 (the Bridge Page) and TP-25 (vetted call booking) from the Customer Journey Map.

The expert dossier, in one line

Priestley names the promise, Miller writes the left panel, Hormozi prices it in effort, Levesque orders the questions, Brunson closes the scene.

Hormozi, the value equation. Dream Outcome x Perceived Likelihood, over Time Delay x Effort. The score maxes all four: the outcome is clarity about THEIR business, likelihood feels high because it’s computed from their own answers, time delay is about two minutes, effort is a handful of taps. Give away the diagnosis, sell the treatment.
Levesque, bucket first. The first question segments, every question after personalizes. Non-threatening questions first, momentum before anything sensitive, contact info near the end, one qualifying question max, asked after value is visible.
Brunson, one job per scene. Hook, story, offer, in strict sequence. At the close, the stack (everything included) renders before any price. One offer only, the tree picks the rung.
Miller, the left panel is the guide introducing itself. Two signals earn the guide role: empathy (one line proving we understand the problem) and authority (a face plus one real number). The grunt test: within five seconds a stranger can answer what is this, what do I get, what do I do next.
Priestley, the score is the marketable promise. People act to find out where they stand. Named bands, each with its own prescription, are the routing rails.

The left panel, seven elements

Dark panel left, light interactive panel right. One CTA concept on the whole panel: the journey itself. The panel never mentions price.

#	Element	Spec
L1	Featured visual	Expert photo (friendly, real) or offer image. Photo default: the concierge fronts for a real person
L2	Named promise headline	Formula: [Named Score] + [what it tells you] + [how fast]. One sentence
L3	Empathy sub-line	One line proving we understand the problem this solves
L4	2-3 “what you get” bullets	The instant result, the artifact, the effort statement (“6 questions, about 2 minutes”)
L5	Quiet authority line	ONE real number. “50,000+ entrepreneurs served.” Real numbers only
L6	Transparency microcopy	Privacy line + AI disclosure (“I’m [name]’s AI concierge”)
L7	Mobile behavior	Panel compacts to a hero (L1-L4) with one “Get started” button that opens the journey full-screen

The journey, scene by scene: BF-01 to BF-12

The canonical scene map. “Fix BF-06” now means the email gate, in any session, forever.

BF-01 · Land

Split screen renders, right panel already shows question one, live and tappable. Zero start friction on desktop. Progress shows “1 of 6” with arrival already counted. Known visitor via magic link is greeted by name.

BF-02 · Quick win 1, the bucket

“Which best describes you?” Four tap cards max, most likely pre-highlighted. Segments everything, easiest tap in the whole funnel.

BF-03 · Quick win 2, the stakes

One situational question. On answer, the score dial appears and starts moving, plus one instant micro-insight. A real partial result before any ask.

BF-04 · Quick win 3, the goal

“Where do you want to be in 90 days?” Feeds the score AND reads heat. Cold-visitor question budget is now spent: max 3-4 taps pre-gate.

BF-05 · Pre-reveal

“Your [Score Name] is ready.” Result renders blurred or teased behind the gate. Honest tease, the score genuinely exists at this point.

BF-06 · THE EMAIL GATE

Right at the aha threshold. Framing: delivery, never toll. “Where should I send your full report? Your score shows on the next screen.” Email field only, no name field. Known visitors SKIP this scene entirely. Capture fires through the one write door, bbe-lead (TP-08). This is TP-07 made real.

BF-07 · The aha

Full reveal: the score, its named band, and the one insight that reframes their problem. The screenshot moment. If they close the tab right now, they still won. Report is simultaneously queued to their inbox.

BF-08 · Prescribe

One recommended path, visually elevated, built from their answers so it reads co-authored. Band decides the prescription. Never a menu.

BF-09 · Prove

One testimonial matched to their bucket and band, real numbers only, the guarantee said out loud before they ask.

BF-10 · Close

The routed CTA. Stack renders first (everything you get), then the single action: buy, book, or claim. Objection chips (price / time / fit), each answered honestly one screen deep. Coded offer with the honest countdown attaches here when active (TP-12).

BF-11 · Reassure

Confirm exactly what happened and what arrives when. Applies to all three routes, a nurture exit gets “your report is in your inbox, here’s what I’d read first.”

BF-12 · Exit routes

Every branch lands somewhere with a next step. Disqualification is a value moment: “honestly, this feels early for you,” plus a genuine free resource. No dead ends, ever.

Ask order and the identified fork

Q1 Bucket (who are you). Easiest tap first.
Q2 Situation (where are you now). Feeds the score.
Q3 Goal (where you want to be). Feeds the score, reads heat.
[GATE] email only.
Q4 Qualifier (budget, timeline, or role). Asked after the aha, framed as personalization. One sensitive question max.
Optional Q5 depth question, only if the prescription genuinely needs it. Hard cap.

Magic-link visitors (win-back sends, member emails, coded offers) skip the gate AND skip whatever the ledger already knows. Recognize replaces Q1: “welcome back, you grabbed the Checklist in March.” Their question budget spends on going deeper.

The routing logic

Computed at BF-10 from three variables: TRUST from the ledger, HEAT from this session, WEIGHT from the offer catalog.

Condition	Route	Scene behavior
Trust >= warm AND heat = hot AND weight in checkout zone ($47-$1,500, no custom scoping)	BUY NOW	Stack, price, in-flow checkout. Coded offer + honest countdown eligible
Weight high (DWY/DFY, custom scope) OR trust thin on a big ask	BOOK THE CALL	Only if the Q4 qualifier passes vetting. Calendar receives the full brief: score, band, answers, transcript
Heat low, any trust	NURTURE	Email the report + a named 30-day plan, tag the profile, warm exit with the door open
Qualifier fails vetting	DISQUALIFY AS VALUE	Honest redirect + genuine alternative resource. They keep the full report

Only prospects who answer the right way ever see a booking link. Everyone books educated, primed, and briefed.

Five use cases, one spine

The spine never changes. A variant is a thin config: promise, face, buckets, scoring dimensions, qualifier, offer catalog, routing thresholds, DQ resource.

Config	DH Club	Bex+Co Franchisees	Bex+Co Stylists	FranDevCo Clients	BBP VIP Vetting
Named promise	Brand Leverage Score	Franchise Readiness Score	Salon Independence Score	Franchise Growth Score	“Do you qualify for a free strategy call?”
Primary close	BUY ($1,500 anchor)	BOOK, heavily vetted	BOOK (tour / apply)	BOOK (discovery call)	BOOK (the vetted free call)
Countdown eligible	yes, coded offers	no, weight too high	no	no	no

The franchisee funnel is the profit case: cold outreach into the bridge page into the Franchise Readiness Score into a capital-vetted calendar. The BBP VIP variant inverts the usual shape: the call IS the offer, so the gate is harder and disqualification is the star feature.

The build architecture

The block: one purpose-built bridge-split registry block, left content slots (visual, headline, empathy_line, bullets, authority_line, transparency_micro), right region config (widget_src, widget_variant, min_height). Existing knob vocabulary only, surface_left/surface_right, a new ratio value (50-50 / 45-55 / 40-60).
The embed: an iframe, not script injection. GET /?embed=1&v={variant_id}&src={touchpoint}. Keeps engine and worker runtimes hard-separated, one vocabulary shared as token names, nothing else. A five-message bf:* postMessage protocol (bf:ready, bf:height, bf:progress, bf:gate_passed, bf:route) carries only sanitized signals, no PII crosses the boundary.
One brand, two renderers: the brand pack feeds both halves. theme.source = {brand_pack, version} is the drift guard, the gauntlet flags a mismatch.
The report: GET /report?t={signed} on the tenant worker, a personal HTML page rendered from ledger events plus the pack, never a generated file. It re-enters the journey (the report IS a magic link) and never goes stale. Brevo fires the transactional send at BF-06 gate-pass, but email is the copy and the page is the master: BF-11 shows the same signed URL on-page as a fallback.
Events, zero new tables: one bf_* family with dimensions {tenant, instance, variant_id, scene, src}: bf_land, bf_tap, bf_gate_hit, bf_gate_pass, bf_aha, bf_route_buy/book/nurture/dq, report_sent, report_opened, offer_minted/clicked/redeemed.
Mobile: panel-first. Offer card (L1-L4 compact) with one full-width Start button. Tap expands the widget to a full-viewport takeover, the offer panel collapses to a slim header chip, a thin progress bar rides the top. Desktop keeps the zero-friction live question, mobile buys context first with one honest tap.

The setup flow: fill-and-ship

The AI asks

About 10 minutes of conversation: what do you sell, what’s the promised outcome of the free thing, who shows up, what are the next steps, where’s your brand kit.

The AI drafts everything

Left panel copy, the full BF-01..12 scene set, routing thresholds, the theme block, the bridge recipe.

The human confirms a fixed 10-item checklist

Every price and checkout URL, that the promise is deliverable, that proof entries are real, the refund line, qualifier thresholds, the calendar link and who answers it. Structure is machine work, promises are human work. That line never moves.

A new instance goes from intake conversation to deployed-dark in under 2 hours.

V1 cut line

In v1: one instance, the DH Club journey, built dark end to end. bridge-split promoted, embed mode + bf:* protocol, pack v1.1 journeys + theme, email gate through bbe-lead with identified-skip, on-page reveal + signed HTML report + Brevo send, bf_* event chain with variant_id stamped, coded-offer events, mobile takeover, AI setup as a session-run intake.

Deferred, explicitly: marquee scrollers and proof walls, automatic split assignment, Brevo-native A/B, the /admin New Instance wizard, provisioning script, PDF attachment, RAG, SMS, the standalone domain and name.