# Production-aware AI for existing products ## Short narrative Useful AI UI starts from the product you already have: the real surface, codebase, components, constraints, and review path. ## Why this wedge matters Question it answers: > Why is Mode different from the AI tools that generate a nice-looking app from a prompt? Narrative: > Most serious teams already have a product, codebase, components, design system, and review process. Mode is stronger when it sounds like AI for changing that existing product, not AI for inventing a separate one. This protects us from the bad interpretation: > "So this is another prompt-to-app builder with a more serious brand?" The stronger story is: > Mode is production-aware AI for existing products: it works inside product context and respects the path from design change to engineering review. ## How it supports the launch spine This is a guardrail for the spine, not necessarily the clearest top-three launch hook. It keeps the public story anchored on real code, real components, and existing-product constraints instead of generic app-builder language. ## Strategic bet The market is crowded with AI tools that generate new screens or apps. Mode can stand apart by focusing on existing-product change: teams already have products, design systems, components, and reviewers. They need AI that works inside those constraints. ## Why Mode is suited Mode's launch language can emphasize product/code/component context and reviewable output. That makes Mode feel like an existing-product workflow, not another blank-canvas generator. ## Product entry / CTA path Ask users to bring an existing product UI issue rather than a new app idea. ## Proof needed Show the workflow beginning from an existing product surface or repo. Show the context the AI is using. Avoid `production-ready` unless the proof supports it; prefer `production-aware`. ## Launch-spine relevance This wedge gives the launch spine its core contrast: Mode starts where generic AI UI tools fail, with the product that already exists. ## Risks / confusions - If overused, it can sound like defensive competitor positioning. - If under-proven, `production-aware` may feel like hand-wavy language. - Needs clear product visuals or proof assets to avoid becoming a conceptual claim.