Input

• Product: Notion-competitor B2B wiki tool called Struct (SaaS, $12/user/month)
• Problem: Free-to-paid conversion sitting at 2.1% vs. industry expectation of 6–8%; trial-to-paid drop-off concentrated in days 1–3
• Funnel data: 18,400 monthly trial signups; 387 convert; biggest self-reported reason for leaving: "didn't see the value fast enough"
• Competitors to benchmark: Confluence, Notion, Coda
• Traffic: ~6,200 weekly active trial users available for experiments

---

Output (abbreviated)

/optimize-experience — Struct Conversion Optimization

Scope: Free-to-paid conversion | Baseline: 2.1% | Target: 5.5%+ within 90 days

---

Step 1 — /ux-audit: Usability Gap Assessment

Method: Heuristic evaluation + session replay analysis (Hotjar) + exit survey synthesis

Priority Findings

#	Finding	Severity	Affected Stage	Est. Drop Impact
1	Empty-state onboarding shows blank canvas with no guided template path	Critical	Day 0 activation	~34% of churners
2	"Invite teammates" CTA buried in Settings > Workspace, not surfaced in flow	High	Day 1–2	~22% of churners
3	Permission model (Spaces vs. Pages vs. Blocks) not explained before users hit a wall	High	Day 1–3	~18% of churners
4	Upgrade prompt triggers on day 1 before user has created any content	Medium	Day 1	Friction, not drop
5	Mobile app lacks template library available on web	Low	Ongoing	Minimal at trial stage

Immediate action candidates: Findings 1, 2, 3 Backlog candidates: Findings 4, 5

---

Step 2 — /ux-benchmark: Competitive UX Comparison

Competitors analyzed: Confluence, Notion, Coda

Pattern Extraction

UX Pattern	Confluence	Notion	Coda	Struct (current)	Verdict
Guided "first doc" template prompt on signup	✓	✓	✓	✗	Industry standard — Struct uniquely missing
Teammate invite in onboarding checklist	✗	✓	✓	✗	Struct behind Notion/Coda
Progress-based onboarding checklist	✗	✓	✓	✗	Struct uniquely missing
Contextual upgrade prompts tied to feature use	✓	✓	✓	✗ (time-based)	Struct's approach is weaker
In-app permission explainer tooltip	✓	✗	✓	✗	Addressable gap

Key insight: Struct's empty-state and absence of an onboarding checklist are not industry norms — they are uniquely bad. Fixing these brings Struct to parity before any differentiation work begins.

---

Step 3 — /funnel-analysis: Funnel Diagnostic

Funnel Stages & Drop-off

Signup                     18,400   ████████████████████  (100%)
Completed profile setup     9,850   ██████████▌           (53.5%)  ← -46.5%
Created first document      5,210   █████▋                (28.3%)  ← -25.2%
Invited ≥1 teammate         1,940   ██▏                   (10.5%)  ← -17.8%
Reached "aha moment"*         820   ▉                      (4.5%)  ← -6.0%
Converted to paid             387   ▏                      (2.1%)  ← -2.4%

*Defined as: created ≥3 docs + invited ≥1 teammate within 7 days

Stage-Level Opportunity Sizing

Stage	Current Rate	Benchmark Rate	Gap	Revenue Impact if Closed (50%)
Signup → Profile complete	53.5%	75%	21.5pp	+$48K MRR
Profile → First doc	28.3%	55%	26.7pp	+$61K MRR
First doc → Teammate invite	10.5%	30%	19.5pp	+$89K MRR ← highest leverage
Teammate invite → Aha moment	42.3%	65%	22.7pp	+$34K MRR

Diagnostic conclusion: The teammate invite step is the single highest-leverage conversion lever. Users who invite a teammate convert at 4.7× the rate of solo users. Current UX buries this action.

---

Step 4 — /ab-test-planner: Prioritized Experiment Roadmap

Test Queue

Test 1 — Onboarding Checklist (Highest Priority)

Parameter	Detail
Hypothesis	Adding a 5-step onboarding checklist (visible days 1–7) will increase "first doc created" rate from 28.3% → 38%+
Variant A	Control: current blank canvas
Variant B	Persistent checklist: Set up profile → Create first doc → Import content → Invite teammate → Set permissions
Primary metric	% users creating first doc within 48 hours
Secondary metric	Day-7 retention
Required sample size	3,100 per variant (80% power, α=0.05, MDE=10%)
Est. runtime	11 days at current traffic
Owner	Growth PM + Frontend

Test 2 — Teammate Invite Placement

Parameter	Detail
Hypothesis	Surfacing "Invite teammates" in the post-first-doc modal will increase invite rate from 10.5% → 18%
Variant A	Control: Settings-buried CTA
Variant B	Post-save modal: "Your doc is ready — get more from Struct by inviting your team"
Primary metric	% trial users inviting ≥1 teammate within 72 hours
Required sample size	2,800 per variant
Est. runtime	~9 days
Owner	Growth PM + Backend

Test 3 — Contextual Upgrade Prompt (Medium Priority)

Parameter	Detail
Hypothesis	Replacing day-1 time-based upgrade nag with feature-triggered prompt (fires when user hits permissions wall) will increase upgrade CTR without harming retention
Variant A	Control: Day 1 timer-based banner
Variant B	Contextual: Prompt fires first time user tries to set granular permissions
Primary metric	Upgrade page CTR
Required sample size	4,400 per variant (lower baseline rate)
Est. runtime	15 days

Run Tests 1 and 2 concurrently (non-overlapping user segments). Test 3 follows.

---

Step 5 — /activation-optimization: Activation Strategy

Aha Moment Redefinition

Current proxy: Any paid conversion Recommended activation moment: User creates ≥3 docs AND invites ≥1 teammate within 7 days Rationale: This cohort converts at 19.4% vs. 0.8% for solo users. It's the signal, not a lagging indicator.

Onboarding Flow Audit & Redesign

Current flow (5 steps, avg. completion 12%): Signup → Email verify → Blank workspace → Explore on your own → Day-1 upgrade prompt

Recommended flow:

Signup
  ↓
Role/use-case question (3 options: Personal, Team Wiki, Engineering Docs)
  ↓
Pre-populated template loaded based