Variation 2: Instant Value — Zero-Quiz Direct Path

Concept Summary

A zero-quiz funnel that replaces the traditional question flow with a 3-card micro-configuration UI embedded in a product-forward landing page. Users select their role, note format, and session type — not as quiz answers, but as app configuration. Each selection instantly updates a live note preview, showing what Twofold will generate for them. Signup is embedded alongside the preview. No quiz framing, no progress bars, no "question" language. Best for cold mobile traffic where the 54.52% first-question drop-off suggests quizzes themselves are the friction, not the warming process.

Strategic Rationale

Core hypothesis: Cold Facebook traffic drops off at Q1 not because they need more warming, but because a quiz is friction they did not ask for. Removing the quiz entirely and replacing it with an immediate demonstration of value — "here is what your note looks like" — will convert more users than any quiz length. The fastest path to showing what the product does wins.

Evidence:

• Freed: Direct signup, no quiz. $100M+ ARR. Clinicians searching for documentation tools do not need to be sold via quiz — they need to see it works.
• Heidi Health: Minimal friction signup produced 80% adoption (2-4x SaaS benchmark). Simplicity itself is the conversion mechanism.
• Grammarly: Product-as-landing-page. The writing assistant demonstrates itself on the page. Users experience value before signup.
• Zocdoc: Booking is the signup. The action the user came to do IS the conversion event. No intermediate warming steps.
• PostHog data: 54.52% drop off at Q1 — the single biggest leak in the current funnel. Once users record, 90%+ succeed. The bottleneck is getting them to start, not keeping them engaged.
• NUX experiment: Guided first action = +24.84% activation lift. Showing users exactly what to do, immediately, is more effective than warming them.
• Google Ads data: Content-rich /lp/* pages already convert at 7.18% overall. High-intent users respond to demonstration, not quizzes. Note Types keywords convert at 11.22%.

What this variation challenges: The assumption that cold traffic needs psychological warming via a quiz before they will sign up. V1 (Speed Start) keeps the quiz but makes it fast. V2 (Instant Value) asks: what if the quiz is the problem? The 3-card micro-selector retains the minimum viable personalization data while reframing the interaction from "answer questions" to "configure your tool."

Design direction signals (LOW WEIGHT): Grammarly's product-forward landing page, Figma's interactive playground, Canva's template selector. Configuration UIs that let users see the output before committing.

---

Current Flow Decisions

---

Funnel Structure

Step-by-Step Flow

Flow Diagram

FB Ad → [Landing: 3-Card Micro-Selector + Live Note Preview]
                            ↓ (selections update preview in real time)
        [Note Preview + Embedded Signup: "Save your workspace"]
                            ↓
        [Auto-eject to system browser]
                            ↓
        [/new: Guided recording with pre-loaded template]

Total Steps

3 interactive selections + preview/signup + ejection + first-action = 6 steps (4 interactive, 2 automatic)

Estimated Completion Time

30-45 seconds to signup (3 selections + email/password entry)

---

Design Direction

Layout Pattern

Split or stacked layout (responsive). On desktop: left side holds the 3-card micro-selector, right side shows the live note preview updating in real time. On mobile: stacked — micro-selector cards at top, note preview below (scrollable, but signup CTA pinned above fold via sticky positioning). No quiz card, no progress bar, no question framing. The page looks and feels like a product configuration screen, not a marketing funnel.

Visual Hierarchy

1. Headline — "Your notes, done before the next session." Large, top-center.
2. Micro-selector cards — 3 horizontal cards (desktop) or 3 stacked cards (mobile). Each card is a single-tap selector with clear label and pill options. Currently selected option highlighted.
3. Live note preview — The dominant visual element. A realistic-looking clinical note that updates as selections change. The note is the hero, not the headline.
4. Signup form — Embedded adjacent to/below the note preview. Two fields (email, password) + one CTA button. Not a separate page.
5. Trust footer — HIPAA badge + "20,000+ clinicians" + 4.8 rating — persistent, non-intrusive.

Mobile-First Considerations

• Micro-selector cards: full-width, 48px+ tap targets for each option pill
• 3 cards visible without scrolling on standard mobile viewport (375px width). Each card is compact: label + 1 row of pill options
• Note preview: visible with minimal scroll. Preview container is 200-250px height on mobile, showing the top portion of the note with "scroll to see full note" fade
• Signup form: sticky bottom bar with email/password fields that slides up when user reaches preview, OR embedded inline below preview with CTA above fold
• No keyboard input until signup (all 3 selections are tap-only multiple choice)
• In-app browser safe: no OAuth, no complex scroll, no heavy animations

Component Patterns

• Micro-selector card: Compact card with label ("I'm a..."), pill options in a single or double row, selected state with brand accent fill. Cards use subtle borders, no shadows.
• Pill options: Rounded rectangles, 44px height, arranged in a responsive grid. Selected: filled accent color with checkmark. Unselected: light border, transparent fill.
• Note preview panel: Styled to look like an actual clinical note document — white background, monospaced or clean serif for note content, section headers (S/O/A/P for SOAP), realistic clinical language. Subtle "generating..." animation when selections change.
• Signup form: Minimal — two stacked input fields with floating labels, one button. Embedded in the same visual container as the note preview (not a modal or separate card).
• Trust footer: Horizontal bar at bottom of viewport: HIPAA shield + clinician count + star rating.

Transition & Animation Direction

The key animation is the note preview update. When a selection changes:

1. Note preview content fades out (150ms)
2. Brief "typing" animation as new content appears (300ms) — simulating AI note generation
3. New note content fades in with a subtle top-to-bottom reveal (200ms)

This animation is the core psychological hook — it demonstrates the product working. Every tap on a selector produces an immediate, visible result. The animation should feel like watching Twofold generate a note in real time.

Page transitions between landing and signup are unnecessary — signup is embedded on the same page. Ejection transition: brief "Opening your workspace..." overlay (500ms) before system browser opens.

---

Content (with Variations)

Landing Headline

• Version A: "Your notes, done before the next session."
• Version B: "See your AI-generated notes in 3 seconds."
• Version C: "What if documentation took 20 seconds instead of 20 minutes?"

Landing Subheadline

• Version A: "Pick your role and note format. Watch Twofold write your note."
• Version B: "Twofold listens to your sessions and writes compliant clinical notes automatically. Configure yours below."

Quiz/Demo Intro (Micro-Selector Framing)

• Version A: "Set up your workspace" — no intro text, just the 3 cards with clear labels. The configuration IS the intro.
• Version B: "3 taps to see your notes, done." — One line above the selector cards, then the cards themselves.

Signup CTA

• Version A: "Save your workspace" (continuation framing — workspace was configured, now save it)
• Version B: "Start free — keep this setup" (value preservation — keep what you just configured)
• Version C: "Try my first real note" (action-forward — what happens after signup)

Onboarding Messaging

• Version A: N/A — onboarding is removed. Configuration happened on the landing page.
• Version B: N/A — same. If any post-signup message is needed: "Your workspace is ready. Everything you selected is configured."

NUX Messaging

• Version A: "Your [SOAP] template for [Therapist] sessions is loaded. Record your first note to see Twofold in action."
• Version B: "Remember that sample note? Now make a real one. Tap below when you're ready."

First-Action Experience Messaging

• Version A: "Record a session. Twofold writes the note. Start whenever you're ready — or try a 30-second demo."
• Version B: "Your workspace is configured for [SOAP] notes. Tap to record, and your note appears in seconds."

Key Messaging Themes

1. Show, don't tell — "See your notes" / "Watch Twofold write" / the preview IS the pitch
2. Speed — "3 seconds" / "Before the next session" / "20 seconds"
3. Configuration, not quiz — "Set up your workspace" / "Pick your format" — professional framing
4. Continuity — The note you saw on the landing page becomes your real workspace
5. Zero risk — "Start free" / "No credit card" / "Keep this setup"

Tone

Direct, product-confident, minimal. Not warm or empathetic (that is V3's territory). Not thorough or professional (that is V2 Deep Commitment's tone). Instead: efficient, clear, demonstrative. Like a product walkthrough, not a conversation. "Here it is. It works. Try it."

---

Quiz/Interactive Design

Questions

The 3 micro-selections are NOT quiz questions — they are configuration inputs. But they serve the same data collection purpose with fundamentally different psychology.

Selection 1: "I'm a..."

• Text: "I'm a..."
• Options: Therapist / Psychiatrist / Psychologist / Social Worker / Counselor / Other
• Purpose: Core personalization. Determines template selection, note terminology, sample note content, peer count displayed.
• Psychology: Identity framing, not interrogation. The user is telling the product who they are so it can configure itself. This feels like setting up an app (choosing a profile), not answering a test question. Lower cognitive load, lower perceived commitment than a quiz Q1.

Selection 2: "My notes are usually..."

• Text: "My notes are usually..."
• Options: SOAP / DAP / BIRP / Progress Notes / Not sure
• Purpose: Direct product configuration. Determines which note format the preview generates and which template loads on /new.
• Psychology: Product-relevant selection that signals competence. "Not sure" defaults to the most common format for their selected role (e.g., Therapist -> SOAP). The preview updating immediately after selection creates a reward loop: tap -> see result.

Selection 3: "Sessions happen..."

• Text: "Sessions happen..."
• Options: In person / Virtual / Both
• Purpose: Recording mode configuration (in-person mic vs. screen audio vs. hybrid). Also validates product fit.
• Psychology: Final selection completes the configuration. The note preview is now fully personalized. The user has invested 3 taps and received a visible, tangible output — a complete clinical note configured for their exact workflow.

Branching Logic

No branching. All 3 selections are independent and can be changed freely (not sequential gates). The note preview updates reactively to any combination of the 3 selections. "Not sure" on note format uses the most common format for the selected role.

Results Personalization

There is no "results page" — the note preview IS the result, and it updates in real time:

• Role drives: note terminology ("the client" vs. "the patient"), clinical language specificity, sample presenting concern, and peer count ("Join 4,200+ therapists")
• Note format drives: note structure (SOAP sections vs. DAP sections vs. BIRP sections), section headers, content organization
• Session type drives: context mentions in the note (in-person vs. telehealth language), recording mode defaults

The preview note contains realistic clinical content for their configuration. Example for Therapist + SOAP + In person:

S (Subjective): Client presented for their scheduled 50-minute individual therapy session. Client reported increased anxiety related to work transitions, stating "I've been having trouble sleeping and can't stop thinking about the changes at work." Client rated current anxiety at 7/10, up from 5/10 at previous session...

---

Signup & Payment Strategy

When is signup requested?

On the same page as the note preview — after the user has made 3 selections and seen their personalized note. No separate page transition. Signup fields appear alongside/below the preview. The user is staring at the output of the product when they encounter the signup form.

What's required at signup?

Email and password only. Two fields. No first name, no phone number, no additional data — the micro-selector already captured role, format, and modality.

Phone number collection

Not collected at signup. Offered post-activation: "Want a text when your first real note is ready?" or "Get a reminder before your next session." Phone collection happens on /new page after first recording attempt.

Credit card timing

Not required. Free trial starts on signup. No credit card until trial expiration. Upgrade prompt after first successful note generation.

Free trial details

7-day free trial with full feature access. Trial framing: "Your workspace is configured and your free trial is active. Generate unlimited notes for 7 days."

In-App Browser Handling

Signup-First ejection (default):

1. User makes 3 selections and sees note preview in the in-app browser
2. User enters email + password on the same page
3. Clicking "Save your workspace" simultaneously: (a) creates account server-side with configuration data, (b) triggers automatic browser ejection via deep link / universal link to app.trytwofold.com/new?token={session}
4. User opens in system Safari/Chrome, already authenticated, with template pre-loaded from selections
5. No intermediate "open in browser" page
6. Fallback: If ejection fails, server sends "Continue in your browser" email with magic link within 30 seconds

Future A/B variant (Eject-First): Collect email only in the in-app browser after note preview -> eject to system browser -> full signup (email pre-filled + Google SSO available) -> /new page. Not the default — noted for future testing.

Rationale

V2 Instant Value's thesis is that showing the product IS the conversion mechanism. Signup happens when the user is looking at their note — peak "I want this" motivation. The in-app browser constraint (no Google SSO) is offset by the minimal signup ask (2 fields) and the fact that the user just saw exactly what they are signing up for. No other variation shows the actual product output before signup.

---

Social Proof Strategy

Types of social proof used

• User count ("20,000+ clinicians")
• Star rating (4.8/5)
• HIPAA compliance badge
• Role-specific peer count ("4,200+ therapists")
• Speed-of-adoption stat ("Average setup: 30 seconds")

Placement

1. Trust footer (landing page): HIPAA badge + "20,000+ clinicians" + 4.8 rating — persistent bottom bar, never competing with the note preview
2. Below note preview: Role-specific count: "Join 4,200+ [role] clinicians already using Twofold" — appears after the preview is fully generated, reinforcing that this is a proven product
3. Adjacent to signup fields: "No credit card required. HIPAA compliant. Cancel anytime." — objection-killing micro-copy at the point of conversion
4. /new page: Brief peer quote from a clinician in the user's role near the recording CTA

Specific examples

• Trust footer: HIPAA Compliant | 20,000+ Clinicians | 4.8/5 Rating
• Below preview: "4,200+ therapists generate their session notes with Twofold."
• Signup adjacent: "No credit card. HIPAA compliant. Your data is encrypted end-to-end."
• /new page: "I set it up in 30 seconds and had my first note before the next client walked in." — Licensed Clinical Social Worker

---

Personalization Logic

Data points used

• Role (Selection 1) -> Template selection, note terminology, clinical language, peer count, sample note content
• Note format (Selection 2) -> Note structure (SOAP/DAP/BIRP/Progress), section headers, template pre-loading
• Session type (Selection 3) -> Recording mode default, session context language in preview note

How personalization manifests

• Note preview (landing page): Fully personalized sample note matching all 3 selections. Different clinical content, structure, and terminology per combination.
• /new page: Template pre-selected (e.g., "SOAP Mental Health" for Therapist + SOAP). Recording mode defaults to session type answer. Greeting references role.
• Sample note on /new: Matches the preview they saw on the landing page — visual continuity reinforces that their configuration "followed them."
• Activation messaging: References their specific format: "Your [SOAP] template is ready. Record a session to generate your first real note."

Personalization depth

Light-Medium — 3 data points produce meaningfully different note previews and product configurations. Lighter than V1's 5 data points and much lighter than Deep Commitment's 13. The trade-off is intentional: fewer questions = less personalization but dramatically lower friction. The note preview itself compensates by demonstrating personalization visually (the user SEES what's different) rather than telling them.

---

Post-Onboarding Activation Strategy

What the user sees on /new after ejection

A single-focus page with strong continuity from the landing experience. Top: "Your workspace is ready." Below: the same note format they saw in the preview, now as an empty template ready for their first recording. Large "Record your first note" button centered in the page. Below the CTA: "Your [SOAP] template is loaded. Recording takes 60 seconds." Sidebar: the sample note from the landing preview, now labeled "Sample note — yours will look like this."

First-action guidance approach

Guided linear flow (per NUX experiment learnings):

1. Template indicator shows pre-loaded format: "[SOAP Mental Health] ready" — visual confirmation of configuration
2. Single dominant CTA: "Record Your First Note" — large, centered, unmissable
3. Inline guidance: "Tap to start recording. Twofold listens and writes your [SOAP] note in about 20 seconds."
4. After pressing record: "Recording... Twofold is listening. Tap Stop when you're done."
5. After stop: "Generating your [SOAP] note..." with the same typing animation from the landing page preview — continuity
6. Note appears: "Your first real note is ready. Review it, then copy to your EHR."

How alternatives to live recording are presented

"Not in a session right now?" link below the primary CTA (subtle, not competing). Opens two options:

• "Try a 30-second demo" — Pre-written clinical scenario script the user reads aloud. Generates a real note from the recording.
• "View your sample note" — The same sample note from the landing page preview, now in the actual app interface. User can explore structure, sections, and formatting.

Mobile-specific considerations

• Large touch target for recording button (80px+ height, full-width)
• No scroll needed to see CTA and guidance text
• Permission prompt for microphone with pre-prompt: "Twofold needs microphone access to listen to your sessions. Recordings are processed and deleted — never stored."
• For users clearly not in session (mobile Facebook traffic): after 10 seconds of inaction on /new, surface the demo recording option more prominently: "Not with a client? Try a 30-second demo to see how it works."
• Sticky bottom CTA on mobile scroll — recording button always reachable

Personalization of /new page based on funnel data

• Template: Auto-loaded from Selection 1 + Selection 2 (Role + Format)
• Recording mode: Default from Selection 3 (In person -> standard mic / Virtual -> screen audio)
• Greeting: "Your [Therapist] workspace is ready" — uses role from configuration
• Sample note: The exact same note generated in the landing preview — continuity

How the design accommodates users who aren't ready to record yet

• "Not in a session right now?" appears after 10 seconds on /new page
• Demo recording option: "Read this 30-second script to see your first real note"
• Sample note browseable — the preview from landing page carries over
• "Remind me" option: "Send me a reminder before my next session" (collects phone number HERE, not at signup)
• /new page state persists — user returns to the same guided flow on next login
• Email follow-up at 24h if no recording: "Your [SOAP] workspace is still configured and waiting. Record your first note in 60 seconds."

---

Psychological Principles Applied

• Demonstration Effect (Bandura / Observational Learning): The live note preview shows the product working before signup. Users who SEE the output have higher confidence in the product than users who are TOLD about it. Where applied: Note preview on landing page. How: Each micro-selector tap updates the preview in real time. Effect: Reduces perceived risk of signup — the user already knows what they are getting.

• Endowment Effect (Kahneman): Users feel ownership of the configured workspace and generated note preview. "Save your workspace" framing implies they already have something worth keeping. Where applied: Signup CTA and /new page. How: The note preview is "theirs" — configured by their selections, displayed as if it already exists. Effect: Increases signup conversion — abandoning means losing something they "own."

• Cognitive Fluency (Alter & Oppenheimer): The 3-card selector is cognitively simple — role, format, session type are immediately understandable with zero explanation. Low processing difficulty = higher trust and conversion. Where applied: Micro-selector UI. How: 3 clear labels, familiar options, no ambiguity. Effect: Reduces first-question drop-off (currently 54.52%) by making the first interaction trivially easy.

• Immediate Gratification (Mischel / Delay Discounting): Every selection produces an instant visible result (note preview update). Zero delay between action and reward. Where applied: Each micro-selector tap. How: Real-time preview animation. Effect: Creates a reward loop — each tap feels productive, motivating the next interaction.

• Social Proof (Cialdini): Role-specific peer counts normalize adoption within the user's professional identity group. Where applied: Below note preview, trust footer. How: "4,200+ therapists already use Twofold." Effect: Reduces "am I the first?" anxiety for clinicians evaluating new technology.

• Anchoring (Tversky & Kahneman): The note preview anchors the user's expectation of what Twofold produces. By showing a complete, well-structured clinical note, the perceived quality is established before signup. Where applied: Note preview. How: High-quality sample note content with proper clinical language. Effect: Sets quality expectations that motivate signup and first recording.

• Zeigarnik Effect (Bluma Zeigarnik): The note preview is a sample — not a real note. The "unfinished" state (seeing what the note COULD be, but not yet having a real one) creates tension that completing signup and recording resolves. Where applied: Landing to /new transition. How: Preview is labeled "sample" — real notes require signup. Effect: Motivates signup as completion of the started experience.

---

Trust & Compliance

Trust signals

• HIPAA compliance badge (shield icon) — persistent on all views
• "Recordings are processed and deleted — never stored" — near signup and recording CTA
• BAA support mention
• 4.8/5 star rating
• "20,000+ clinicians" user count
• Role-specific peer count
• "End-to-end encryption" mention adjacent to signup fields

Compliance requirements

• HIPAA badge visible on the landing page and adjacent to signup fields
• Terms of Use and Privacy Policy links on signup form
• BAA link accessible from signup
• Clear data handling statement near recording CTA on /new page
• Note preview must include disclaimer: "Sample note — generated from template, not real patient data"

Placement

• Trust footer (landing page): HIPAA + clinician count + rating — persistent, bottom of viewport
• Adjacent to signup fields: "HIPAA compliant. End-to-end encryption. Your data is protected." — directly below or beside password field
• Note preview: Small "Sample note" label to clarify this is not real patient data
• /new page: "Recordings are processed and deleted — never stored. HIPAA compliant." near recording button

---

Expected Metrics

Funnel completion rate target

40-55% ad click to signup. This is the highest target of any variation because the path is the shortest (3 selections + 2 fields). No quiz abandonment possible — there is no quiz. The 54.52% who currently drop at Q1 never encounter that friction point. Benchmark: Freed achieves high signup rates with direct signup (no quiz). Grammarly's product-as-landing-page converts at industry-leading rates for its category.

Activation rate target

50-60% signup to first recording pressed. Slightly lower than V1's target because V2 users invested less time pre-signup (30 seconds vs. 60-90 seconds). Lower sunk cost = slightly lower activation motivation. Offset by the note preview setting clear expectations — users know exactly what they are recording for. Benchmark: Current NUX dialog achieves 62.42%; V2's guided flow should approach this.

Subscription rate target

7-10% trial to paid. Potentially lower than V1 because the minimal pre-signup investment may attract more "just looking" users. The note preview partially qualifies intent (users who sign up after seeing the product output are more likely to be genuine), but the bar is lower than a 5-question quiz. Benchmark: Current rate ~8.92% with NUX dialog.

Benchmarks

• Freed: Direct signup, $100M+ ARR (no quiz)
• Heidi Health: 80% adoption with minimal-friction signup
• Grammarly: Product-demonstration landing page, best-in-class freemium conversion
• Current Twofold Q1 drop-off: 54.52% — V2 eliminates this entirely
• Current Twofold /new -> recording: 50% desktop, 35% mobile

Key risk factors

1. 3 selections may not build enough investment — users who sign up in 30 seconds may have the lowest commitment of any variation. Activation and subscription could suffer even if signup rate is high.
2. Note preview may set wrong expectations — if the sample note looks too polished, users may be disappointed by real notes from messy recordings. If it looks too clinical, non-MH providers may disengage.
3. No pain acknowledgment — unlike V1 (Q3, Q4) and Deep Commitment (Phase 2), V2 never asks about documentation pain. Users may not connect Twofold to their specific problem. The note preview shows what, but not why.
4. Revenue per click may not improve — highest signup rate does not guarantee highest revenue per click. If activation and subscription rates drop enough, V2 could convert more people to signup but fewer to paid.
5. In-app browser ejection reliability — same risk as all variations. Untested at scale.
6. Configuration fatigue for "Other" roles — users who select "Other" get a generic note preview that may not feel personalized enough to demonstrate value.

---

Implementation Complexity

Technical requirements

• Server-side in-app browser detection (FBAN user-agent string)
• Landing page with reactive micro-selector UI (3 independent selectors update a shared preview state)
• Note preview generation engine: pre-rendered sample notes for each Role x Format combination (6 roles x 5 formats = 30 note templates, with "Not sure" defaulting per role)
• Real-time preview animation (typing effect on content change)
• Embedded signup form on same page as preview (no page transition)
• Browser ejection mechanism (universal links / deep links with auth token)
• Fallback email sender for failed ejections
• /new page modifications: guided activation flow, template pre-loading from selection data, sample note carryover from landing preview
• Session persistence: selection state must survive page refresh in the in-app browser

Content requirements

• 30 sample clinical notes (6 roles x 5 formats) with realistic clinical language per specialty
• 2-3 versions of landing headline/subheadline copy
• Role-specific peer counts
• Clinician testimonials segmented by role (at least 4 roles)
• Demo recording script
• Email follow-up templates for non-activating users

Estimated effort

Medium — The core challenge is the note preview system (30 pre-rendered templates + reactive UI). The landing page itself is simpler than any quiz variation (no multi-step flow, no progress tracking). Main technical work: preview animation system, template library, and reactive selector state.

Dependencies

• 30 sample note templates must be written and reviewed by clinical team for accuracy
• Browser ejection mechanism validated on iOS and Android
• PostHog event tracking for: landing page view, each selection tap, preview generation, signup, ejection success/failure, first recording
• Server-side user-agent detection for in-app browser routing

---

Google Ads Addendum

This section describes how Variation 2 (Instant Value) adapts for Google Ads high-intent search traffic. The core spec above is the Facebook/Instagram version. The addendum covers only what DIFFERS.

Should this variation use a quiz for Google traffic?

No. V2 Instant Value is the most natural fit for Google traffic of any variation. The zero-quiz approach aligns perfectly with high-intent search users who are already solution-aware. Google searchers do not need warming — they searched for the product category. A configuration UI + live note preview is exactly the "answer the query and convert" pattern that Google traffic demands.

For ALL keyword clusters — specialty-specific, product feature, competitor targeting, compliance-driven, and pain-driven — the direct path converts better than a quiz. No exceptions.

Entry point for Google Ads visitors

Users land on enhanced /lp/* pages that now include a note preview element. The existing content-rich /lp/* template (hero > testimonials > features > how-it-works > pricing > privacy > FAQs) is preserved for Quality Score, but the hero section is modified to include the 3-card micro-selector and a live note preview. The preview is embedded above the fold, replacing the current hero CTA area.

For specialty-specific landing pages (/specialties/*), the micro-selector pre-fills Selection 1 (role) based on the page context (e.g., /specialties/psychiatry pre-selects "Psychiatrist") so the user only needs to make 2 selections.

Landing page hero / above-the-fold content

For /lp/ai-therapy-notes (specialty-specific):

• Headline: "AI Therapy Notes — Generated in Seconds"
• Subheadline: "Twofold listens to your sessions and writes compliant clinical notes automatically. See what your notes look like below."
• Primary CTA: "Try Free — No Credit Card" (button scrolls to embedded signup form adjacent to note preview, or sticky header CTA on scroll)
• Trust signals above fold: HIPAA Compliant badge | 20,000+ Clinicians | 4.8/5 Rating | "Recordings never stored"

For /lp/soap-note-generator (product feature):

• Headline: "SOAP Notes, Written by AI in 20 Seconds"
• Subheadline: "Record your session. Twofold generates a complete, compliant SOAP note. Configure yours below."
• Primary CTA: "Generate Your First SOAP Note Free"
• Trust signals above fold: HIPAA Compliant | 4.8/5 Rating | "Used by 20,000+ clinicians"

For /specialties/psychiatry (specialty page):

• Headline: "AI Documentation for Psychiatrists"
• Subheadline: "Twofold writes your psychiatric notes while you focus on patients. See a sample note for your practice below."
• Primary CTA: "Start Free — See Your Notes"
• Trust signals above fold: HIPAA Compliant | BAA Available | "Trusted by 3,100+ psychiatrists"

The 3-card micro-selector and live note preview are embedded in the hero section below the headline and above the existing page content. For specialty pages, Selection 1 is pre-filled. For feature pages (e.g., SOAP), Selection 2 is pre-filled.

Signup flow changes

Google traffic lands in a full system browser, which changes the signup equation significantly:

1. Google SSO is the default signup method. "Continue with Google" button is the primary, most prominent option. Email+password is secondary ("Or sign up with email").
2. No ejection needed. User is already in the system browser. After signup, redirect directly to /new — no deep link, no universal link, no fallback email.
3. Signup form is embedded on the same page as the note preview (same as Facebook version), but with Google SSO button added above the email+password fields.
4. Password managers work. The full browser supports credential saving, reducing signup friction further.
5. Signup flow: Google SSO (1 tap) -> redirect to /new (authenticated) -> guided first action. Total: 3 selections + 1 tap signup = ~20 seconds to activation page.

Google ad copy alignment

Specialty-specific keywords (e.g., "AI therapy notes", "psychiatry AI scribe"):

• Headline 1: "AI Therapy Notes — Done in Seconds"
• Headline 2: "See Your Notes Before Signing Up"
• Description: "Twofold listens to therapy sessions and writes SOAP, DAP, or BIRP notes automatically. HIPAA compliant. Preview your notes free — no credit card required."

Product feature keywords (e.g., "SOAP note generator", "therapy dictation software"):

• Headline 1: "SOAP Notes Generated by AI"
• Headline 2: "From Recording to Note in 20 Seconds"
• Description: "Stop spending hours on clinical documentation. Twofold records your session and generates compliant notes instantly. Try free — see a sample note for your specialty."

Compliance-driven keywords (e.g., "HIPAA compliant AI notes"):

• Headline 1: "HIPAA Compliant AI Note Generator"
• Headline 2: "BAA Available — SOC 2 Compliant"
• Description: "Twofold generates clinical notes with end-to-end encryption. Recordings are processed and deleted — never stored. Trusted by 20,000+ clinicians. Try free."

Competitor targeting keywords (e.g., "[Competitor] alternative"):

• Headline 1: "Looking for a [Competitor] Alternative?"
• Headline 2: "See Your Notes Before You Sign Up"
• Description: "Twofold generates clinical notes from your sessions — SOAP, DAP, BIRP, and more. Preview your notes free. No credit card. HIPAA compliant. Switch in 30 seconds."

Pain-driven keywords (e.g., "reduce clinical documentation time"):

• Headline 1: "Finish Notes Before the Next Patient"
• Headline 2: "AI Writes Your Clinical Notes in Seconds"
• Description: "Spending hours on documentation? Twofold records your sessions and generates compliant notes automatically. See a sample note for your specialty — try free."

What stays the same as the Facebook variation

• 3-card micro-selector design (role, format, session type) — identical selections, identical UI
• Live note preview system (same 30 templates, same animation)
• Post-signup /new page experience (same guided activation flow)
• Sample note content and template library
• Trust signals and social proof copy
• Post-activation flows (demo recording, sample note, reminder system)
• Personalization logic (same 3 data points, same mapping)

Technical requirements specific to Google

• Server-side rendering (SSR): All /lp/* and /specialties/* pages must be fully server-rendered with semantic HTML. The micro-selector and note preview must render meaningful content on initial page load (not blank until JavaScript loads). The current pages are already SSR — the embedded selector must maintain this.
• Semantic HTML: H1 for page headline, H2 for section headers, proper heading hierarchy. Note preview should use semantic markup (not just styled divs).
• Structured data: Maintain existing Product schema (4.9/5 rating), FAQPage schema, and add HowTo schema for the "configure your notes" flow. BreadcrumbList schema for specialty pages.
• Meta tags: Title and description must echo the target keyword cluster. Open Graph tags for social sharing. Canonical URLs for /lp/* variants.
• Page speed: Note preview must not block initial render. Use progressive enhancement: page loads with a static sample note, then JavaScript enables the reactive selector. Core Web Vitals must pass: LCP < 2.5s, FID < 100ms, CLS < 0.1.
• robots/indexing: /lp/* pages must be indexable (no noindex). Selector state changes must not create separate indexable URLs (use JavaScript state, not URL parameters).
• Google SSO integration: OAuth 2.0 flow with Google Identity Services. "Continue with Google" button must follow Google's branding guidelines. Handle account linking if user already has an email+password account.
• Keyword-specific page variants: For high-volume keyword clusters, create dedicated /lp/* pages with pre-filled selectors (e.g., /lp/soap-note-generator pre-fills "SOAP" in Selection 2). This improves message match and Quality Score. Estimated 8-12 page variants to cover active ad groups.
• Conversion tracking: Google Ads conversion tracking pixel fires on signup completion. Enhanced conversions with hashed email for better attribution. Google Analytics 4 events for each selection tap and preview generation.