# Fix one real product UI issue ## Short narrative Bring one real product UI issue: a shipped screen, a visible drift from design intent, or a polish problem that has not been worth a full engineering cycle. Mode should help move it toward reviewable output. ## Why this wedge matters Question it answers: > What should someone actually try first when they see Mode? Narrative: > A single real UI issue is the easiest bridge from launch message to product action. It gives users a concrete job: take one shipped screen, one annoying polish problem, or one design QA miss and move it toward a reviewable change. This protects us from the bad interpretation: > "Mode sounds interesting, but I do not know what I would use it for first." The stronger story is: > Bring Mode one real product UI issue. Mode helps turn that specific issue into a scoped, production-aware change path instead of another abstract exploration. ## How it supports the launch spine This is the strongest activation wedge for the launch spine. The broad promise says Mode lets Design Engineers change the actual product; this wedge tells them the first change to bring. ## Strategic bet Concrete entry beats abstract exploration. If users can immediately imagine one product issue they would try Mode on, the launch motion can convert narrative interest into product behavior. ## Why Mode is suited Mode can make a scoped change in context: real product surface first, component/code context visible, engineering review preserved. ## Product entry / CTA path Use this for launch replies, self-serve prompts, onboarding, and proof capture: > Bring one real product UI issue. ## Proof needed The hero proof packet should show the complete loop: real product surface -> one issue -> Mode-assisted change -> before/after -> reviewable output. Say `PR` only if the demo creates a real PR/diff/branch. ## Launch-spine relevance This is the strongest CTA wedge. It can sit beneath the broader launch promise (`Your design system should be the prompt` / `Mode helps Design Engineers change real product UI with context intact`) as the thing users are asked to do first. ## Risks / confusions - Too narrow if it becomes only visual-bug cleanup. - Too manual if it sounds like Mode will personally fix submitted issues. - Needs careful routing from reply/request to self-serve or founder-assist workflow.