Beta Tester Rubric — Phase 1 Closed Beta

Raxx — "Really Likes the Idea" Qualification Instrument

Version 1.0 | 2026-06-08 | Issue: #3403

Overview

This rubric is the complete instrument for the Phase-1 closed-beta tester session. A single tester completes the full flow in 15-20 minutes. The operator reads the scoring summary per tester and uses the "promote" recommendation to decide who advances to Phase 2.

What it produces: - Sentiment score: 0-100 composite per tester (rank-sortable) - Failure-mode map: where they got lost or bounced - Verbatim quotes for marketing (NDA-gated attribution) - Promote / Hold / Pass recommendation per tester - Roll-up patterns across the cohort

Section 1: Pre-Walkthrough Survey

Complete before the tester sees anything. 3 questions. 2 minutes.

Q1. How long have you been trading options or equities? (one-tap)

• Less than 6 months
• 6 months to 2 years
• 2 to 5 years
• More than 5 years

Scoring: not scored directly. Used for persona-match analysis in Section 5.

Q2. What tools do you currently use to manage your trades? (check all that apply — one-tap multi-select)

• Spreadsheets (Excel, Google Sheets)
• A trade journal app
• My account platform only (no external tool)
• ThinkorSwim / platform scanner
• Other ___

Scoring: not scored. Used to identify structure-gap awareness in debrief.

Q3. What is your single biggest frustration with how you manage trades today? (free-text, 1-3 sentences)

Scoring: not scored directly. Stored verbatim. Used to calibrate resonance questions in post-survey.

Section 2: Walkthrough Script

The tester navigates the live site and/or demo environment. The operator (or a session facilitator) gives verbal instructions in this order. Do not redesign the product — just sequence it.

Total time budget: 8-10 minutes.

Step 1 — Marketing site (2 min)

"Go to getraxx.com. Read the hero and the first section below it. Do not click anything yet — just read until it feels like you understand what Raxx is."

Observe: Do they scroll past the hero? Do they pause at the persona card that matches them? Do they click the CTA unprompted?

Failure signal: Tester reads hero and says "so it's like a trade journal?" or "is this a broker?" — comprehension gap; note it.

Step 2 — Structure-enforcement core (2 min)

"Now look at the section that describes how Raxx handles entries, credits, and exits. Walk me through what you think that means in a real trade."

Observe: Can they translate the structural language into their own trading context?

Failure signal: Tester describes it in terms of an external signal ("it tells me when to buy") rather than a rules-enforcement frame ("it keeps me to the rules I wrote"). Note framing.

Step 3 — Shape / retrospective section (2 min)

"Find the part of the site about how Raxx looks at your own trade history. What does it tell you?"

Observe: Do they connect this to their current frustration (from Q3)?

Failure signal: Tester cannot find the section, or describes it as predictive ("it predicts what will work") rather than retrospective ("it shows what worked"). Note both.

Step 4 — Pricing page (1 min)

"Go to the pricing section. Just look at it — do not do anything yet."

Observe: Reaction to the Founders / Pro / Pro+ tiers. Facial expression or verbal reaction to $29 Founders price before you ask about it in the survey.

Step 5 — Task check: wash-sale detection (2 min)

"Without me pointing you anywhere — can you find where Raxx would flag a potential wash-sale situation?"

Task pass: Tester navigates to the relevant section or correctly identifies where in the platform that feature lives.

Task fail: Tester cannot locate it or guesses wrong. Note where they looked.

If the feature is not yet accessible in the demo, substitute: "Based on what you have seen, where would you expect this feature to live?"

Section 3: Post-Walkthrough Survey

Complete immediately after the walkthrough. 5-7 minutes. 12 items.

Comprehension block (Likert 1-5)

C1. After the walkthrough, I understand what Raxx does. 1 — Not at all | 2 | 3 — Somewhat | 4 | 5 — Completely

C2. I can explain Raxx to another trader in one sentence. 1 — No | 2 | 3 — Maybe | 4 | 5 — Yes, clearly

Resonance block (Likert 1-5)

R1. The "structure gap" problem — that you trade better rules than you follow — describes my actual experience. 1 — Not at all | 2 | 3 — Sometimes | 4 | 5 — This is exactly my problem

R2. Raxx addresses a problem I have tried to solve before and failed. 1 — Not at all | 2 | 3 — Somewhat | 4 | 5 — Yes, clearly

Differentiation block (Likert 1-5 + free-text)

D1. Raxx is different from the tools I already use. 1 — Seems like the same thing | 2 | 3 | 4 | 5 — Clearly different

D2 (free-text). In your own words: how is Raxx different from a trade journal or a spreadsheet? (1-3 sentences — verbatim captured for marketing use with NDA-permitted attribution)

Pricing block (one-tap)

P1. Founders access — 6 months of full features for $29 total. Would you pay that today?

• Yes
• Maybe, depends on what I see in the platform
• No

P2. After the 6-month Founders period, would you pay a monthly subscription for Raxx if it does what you think it does?

• Yes, if it saves me from one bad trade a month
• Maybe
• No

Onboarding friction block (Likert 1-5 + free-text)

O1. The walkthrough felt clear and easy to follow. 1 — Confusing throughout | 2 | 3 — Mixed | 4 | 5 — Clear throughout

O2 (free-text). What was the most confusing or frustrating part of what you saw today? (1-3 sentences — verbatim)

Surprise + delight block (free-text)

S1 (free-text). What stood out positively — something you did not expect? (1-3 sentences — verbatim)

Net Promoter Score

NPS. How likely are you to recommend Raxx to a friend who trades? 0 (not at all likely) — 10 (extremely likely)

Promotion + continuing interest (one-tap)

PR1. Is there a specific person in your trading circle you would send this to? - Yes (name not required — just yes/no) - No

CI1. Would you want to be in the next round of beta testing? - Yes, definitely - Maybe - No

Section 4: Scoring Methodology

Total score: 0-100 composite. Computed from the post-walkthrough survey only.

Raw inputs

Maximum achievable: 105 → normalize to 100 (divide by 1.05)

Rounding: floor to nearest integer. Display as integer (e.g., 78/100).

Qualitative adjustment (operator override, not auto-scored)

The operator may add or subtract up to 5 points based on the free-text responses (D2, O2, S1). This is an explicit judgment call — document the reason in the tester record. Default: no adjustment.

Task check (separate from score)

The wash-sale detection task pass/fail is recorded as a binary flag alongside the score. It is not added to the composite — it is a failure-mode signal, not a sentiment signal.

Section 5: "Really Likes the Idea" Definition

Promote to next round: score >= 70 AND P1 is Yes or Maybe AND CI1 is Yes

Hold (invite to extended trial, not full beta): score 50-69 OR P1 is No but score >= 65 — these testers are interested but not yet bought in; a second session after more product exposure may convert them

Pass (do not advance): score < 50 OR CI1 is No — no fit signal

Persona match filter

Cross-reference Pre-Survey Q1 (trading experience) and Q2 (tools used) against the tester's R1 score. A tester who scores R1 >= 4 AND uses only their platform account (Q2 = "My account platform only") is a high-value persona match: they have the problem and no existing structure. Flag them in the weekly digest.

Section 6: Weekly Digest Spec

The operator receives a weekly roll-up. Each row is one tester. Format:

Per-tester row

Cohort roll-up (bottom of digest)

• Average score
• Score distribution: Promote / Hold / Pass counts
• Top 3 friction themes (operator reads O2 verbatim and tags)
• Most common comprehension gap (from C1/C2 low scores)
• Best 2-3 verbatim quotes (operator selects for marketing use)
• Task pass rate (wash-sale detection)
• Persona match rate (% of testers with high R1 + platform-only tools)

Alignment note: this digest spec feeds the marketing-strategist's nightly brief format. The "Standout quote" field maps to the brief's attribution block. All verbatim quotes used in marketing copy are NDA-gated; tester must be notified before publication even if NDA permits. No names, handles, or identifying info in the digest rows.