Beta Preview — Phase 1 Marketing-Feedback Flow

Route: /beta/preview/[token] Flag: FLAG_BETA_PREVIEW_MARKETING (new — distinct from FLAG_BETA_WALKTHROUGH which is Phase 2) Date: 2026-06-12 Designer: ux-designer

Purpose

Read-only NDA-gated screenshot tour of what Raxx will do, with per-section motive copy and structured feedback collection. Goal: validate brand + positioning BEFORE investing in polish. No actual app interaction. No live data. This is Phase 1.

Phase 2 (interactive IC builder + tax engine) lives at /beta/walk/[token]/walkthrough/ — already shipped in PR #3513.

Screen index

Screenshots

Each screen has desktop (1280×800) and mobile (390×844):

screenshots/
  screen-1-persona-match-desktop.png
  screen-1-persona-match-mobile.png
  screen-2-ic-builder-desktop.png
  screen-2-ic-builder-mobile.png
  screen-3-tax-engine-desktop.png
  screen-3-tax-engine-mobile.png
  screen-4-dashboard-desktop.png
  screen-4-dashboard-mobile.png
  screen-5-final-feedback-desktop.png
  screen-5-final-feedback-mobile.png

Microcopy index

Screen 1 — Persona Match header

RAXX — Your structure. Your rules.
Welcome to the Raxx preview.
Before we show you anything, 3 quick questions to anchor what you'll see.

CTA: Show me Raxx → Skip: Skip questions, show me the preview

Q1 (Screen 1)

Label: Experience Question: How long have you been trading options or equities? Options: Less than 6 months / 6 months – 2 years / 2 – 5 years / More than 5 years

Q2 (Screen 1)

Label: Current Tools Question: What tools do you currently use to manage your trades? Checkboxes: Spreadsheets / Trade journal / Account platform only / thinkorswim / Other: [free text]

Q3 (Screen 1)

Label: Frustration Question: What is your single biggest frustration with how you manage trades today? Hint: 1–3 sentences is plenty. No wrong answers.

Motive paragraphs — verbatim

Screen 2 — IC Builder (structure gate)

Most platforms let you enter the trade, then complain. Raxx stops the trade if it violates the structure you wrote — before you submit. You override only with intention, not by accident.

The rules you set are the ones you wrote when you weren't in the trade — when emotion wasn't in the room. Raxx holds those rules in place for you. If you want to break them, you can. But you have to mean it.

Screen 3 — Tax Engine

The right tax decision happens at trade-time, not at year-end. We surface wash-sale exposure, §1256 status, and lot-selection method for every fill — before you submit, not in April.

Most traders discover tax problems after the fact. By then, the election window is closed and the paperwork is expensive. Raxx records what you chose, per fill, so your year-end picture reflects actual decisions — not platform defaults you never noticed.

Screen 4 — Dashboard Hero

Raxx doesn't predict. We show you what already happened, with the structure you set, with the markers that matter — so you can decide what's next.

Every annotated event on your chart was something that already occurred on your own data. The gate-fired markers show where your structure held. The timeseries shows the P&L picture those decisions produced. No forecast. No probability cone. Just your history, organized.

Per-panel feedback prompts

Screen 2 — IC Builder

Quick reaction prompt: Does this concept resonate? Options: Yes, exactly the problem I have / Sort of — depends on context / Doesn't feel like my problem

Free-text prompt: What would make this even more useful for your trading?

Screen 3 — Tax Engine

Quick reaction prompt: How does seeing tax context inline change how you'd trade? Options: Significantly — I'd make different decisions / Somewhat — nice to have, I'd reference it / Not much — I handle tax separately

Free-text prompt: Which tax surfaces would be most valuable to you specifically?

Screen 4 — Dashboard

Quick reaction prompt: Does this dashboard answer the right question for you? Options: Yes — this is exactly what I'd want to open first / Partially — some of it, but something's missing / No — what's missing is below

Free-text prompt: What's the FIRST thing you'd want to see on a dashboard like this?

Screen 5 rubric questions (verbatim from PR #3510 schema)

Screenshot source notes for feature-developer

Recommendation: For Phase 1 (read-only), embed the panel screenshots from the existing mockup PNGs rather than iframes. Simpler, no JS dependency, no interactive confusion. Feature-dev can use <img> tags pointing at the existing screenshot PNGs.

Design decisions made without operator input

1. 5-step progress indicator — used consistent step labels: About You / IC Builder / Tax Engine / Dashboard / Feedback. Steps use checkmarks when done and moss glow ring when active. No step is locked; user can navigate back.
2. "Skip this question" on each panel — per feedback_signup_never_blocks, every feedback prompt has a skip link. Applies to per-panel questions only; Screen 1 persona questions also have a skip-all.
3. Privacy/NDA notice on Screen 1 — small bronze-tinted callout explaining answers are private. No legal language beyond "NDA-bound."
4. Founders badge on Screen 3 — bronze star chip labeling the tax engine as Founders-tier value. Placement: below the panel header before the mockup.
5. Dashboard mockup is dark-themed — matches existing status-dashboard-redesign Variant A/C which use ink background. Wrapped in a simulated browser chrome frame for context clarity.
6. Annotation callouts — black pill annotations beneath each mockup to explain the "why this fires" or "why here not April" — these appear in the preview but not in the actual app.
7. Likert scale format — 5 horizontally-arrayed radio buttons with anchors "Strongly disagree" / "Strongly agree". Mobile collapses gracefully.
8. Submit block styling — dark ink card at Screen 5 bottom, moss CTA button. Matches the "ask moment" gravity without feeling alarming.

Open questions for Kristerpher / PM before feature-dev picks up

1. Email capture on Screen 5? The survey doesn't currently collect email. If the tester arrives via a token-ed URL, the backend knows who they are. If the token is anonymous (shared link), email needs to be collected somewhere. Where — Screen 1 pre-questions, or post-submit?
2. Iframe vs static PNG for screenshot panels? Current design uses inline HTML/CSS that approximates the real surface. Feature-dev options: (a) screenshot PNG from existing mockup dirs embedded as <img>, (b) iframe of real Phase 2 mockup HTML, (c) keep this mockup's simplified representation. Option (a) is cheapest and keeps Phase 1 truly read-only.
3. Is "thinkorswim" the right brand name in Q2? Per feedback_no_backend_branding, we avoid broker names in customer copy. thinkorswim is a platform name, not a broker per se — but confirm it's acceptable before shipping.
4. Order confirmation for Screen 5 "Yes — I'd pay $29 right now" (P1)? Should clicking that selection trigger any immediate action (e.g. Stripe Founders checkout flow) or is this purely feedback data?
5. NPS scale layout on mobile — 11 buttons (0–10) in a row clips on 390px. Current design wraps. Confirm wrapping is acceptable or if a slider would be preferred.