Evidence type: [inference]
Time horizon: After launch
Files: frontend/src/components/layout/AuthLayout.tsx:49-89, frontend/index.html:11, frontend/src/config/menuConfig.ts:45-172
What's happening: Every positioning surface (sign-in copy, meta description, sidebar groups) describes records administration; the AI tutoring suite — the entire cost base and differentiation — appears nowhere in the framing.
Why it matters: Presenting as a records portal sets the expectation of a low-frequency, low-engagement behavior rather than the high-frequency, habit-forming one the AI features are meant to drive.
Recommendation: Rewrite the value proposition and top-level IA around the AI capabilities; route first sign-in into a tutor session rather than the records dashboard.
Expected impact: Aligns first-run expectation with the differentiated capability.
Effort estimate: M
Finding ID: UX-S2
Source: docs/agents/pre-launch-report.md
Evidence type: [inference]
Time horizon: After launch
Files: frontend/src/components/layout/AuthLayout.tsx:49-89, frontend/index.html:11, frontend/src/config/menuConfig.ts:45-172
What's happening: Every positioning surface (sign-in copy, meta description, sidebar groups) describes records administration; the AI tutoring suite — the entire cost base and differentiation — appears nowhere in the framing.
Why it matters: Presenting as a records portal sets the expectation of a low-frequency, low-engagement behavior rather than the high-frequency, habit-forming one the AI features are meant to drive.
Recommendation: Rewrite the value proposition and top-level IA around the AI capabilities; route first sign-in into a tutor session rather than the records dashboard.
Expected impact: Aligns first-run expectation with the differentiated capability.
Effort estimate: M
Finding ID: UX-S2
Source: docs/agents/pre-launch-report.md