Home
# Redesign the Nexus join flow: proposal (nothing edited yet)
Repo: jg-financial-workspace, branch claude/project-thread-7buc82, git status clean at start. No push, no deploy, no DialRush.
Screens: /join (public request form) and /start (the first screen a new agent sees, "Your checklist"). Fake agents only.
Before shots: /mnt/project-files/join-redesign/before/ (390 and 1440 px, every state).
## Three biggest friction points
1. **/join ends in a dead end.** After "Send request" the agent reads "Request received. Your upline will send your AIL job
application." and nothing else: no what happens next, no how long, no way to the sign-up. Also the page's one button
is the faint "ghost" style, and on a phone the upline list drops over the Send button.
2. **/join spends the phone screen on decoration, and asks a jargon question.** Rings, particles and the logo push the first
box to y=285 of 844. "Direct Upline (must be currently contracted)" is carrier language; a recruit picks from a search box
of every leader.
3. **/start shows AIL's raw status word and nine steps at once.** "Invitation eMail sent to Applicant" has no plain meaning
and no owner. All nine contracting steps show together, including ones that cannot start yet (Impact, Nonresident State
needs a writing number). The only button is "Update my license", even when the agent is simply waiting. Blocked says
"Talk to your upline" with no who. Training group, carrier upline and dialer clearance are not shown as three separate
things anywhere. Text is 12 to 13 px, under the 14 px rule.
## Proposed redesign (existing components only, one primary action per screen)
- **/join:** the form moves up (compact logo only), labels in plain words ("Who invited you?", carrier line kept as the
small label), the list opens as a sheet that never covers Send. Send is the page's one primary button. The confirmation
becomes three lines: what you sent, what happens next (your upline sends the AIL application email), what to do while
you wait (check the inbox, search "ailagentadmin" in spam).
- **/start:** one top card with one plain sentence and one primary button, then ONE current step expanded, the rest
collapsed under "Coming up". Below it, three separate rows, each with its own label and owner:
AIL application row now; Training group and Dialer clearance stay separate and hidden until they have data. They never merge into one status.
- **States on /start:**
- **Ready** (cleared): no /start screen, the agent goes to the Dashboard. A short "You're cleared" line is shown once.
- **Waiting on a trainer:** primary button "Message your upline" is not offered (no new contact data). Primary is the
current step; the card says who it is waiting on and what the agent can do now.
- **Blocked** (AIL cancelled / declined / expired): the card names the AIL word in plain words, says "Your upline
needs to restart it", primary action "Update my license" removed; the one action is a link to the checklist step.
- Phone first: text 14 px or larger, taps 44 px or taller, no dark-black default decisions made here (see question 2).
## Files I would change
- web/src/app/join/JoinForm.tsx, join/page.tsx, lib/join/fields.ts (words), join/__tests__/page.test.tsx
- web/src/app/start/Checklist.tsx, start/start.module.css
- web/src/lib/onboard/model.ts (view per state), lib/onboard/steps.ts (one-step-at-a-time, no wording change)
- web/src/app/dev/start/page.tsx (rows for ready / waiting / blocked in the mock twin)
- Not touched: supabase/, api/join, onboard_me, any permission rule.
## What I could NOT do from the code
- **Training group and dialer clearance have no data on this screen today** (OnboardMe holds only license, exam, AIL word).
Showing real values needs a database read = new SQL = permission work. Per the CRM rules that means Opus plus an
independent Fable review, and the merge goes through Matteo. I propose building the three rows now with only the
carrier line live; the other two stay hidden until that read exists.
- The company design system (soft stone, floating tiles) is being picked in another thread. /join and /start are on
the older dark gold look today. I would reuse the current Nexus components now and re-skin later.
## Risks / not tested
- Nothing built or tested yet. Hide-by-state logic touches who sees the checklist, so the build gets a Fable review.
- Preview ran on mock data with a practice secret, never live.
## Struck after review
- Plain label "Who invited you?" and a filled primary Send: not built. The label is Bryan's wording and the site has no filled button; /join keeps the one regular button.