# Prototype in the product, not beside it ## Short narrative Live prototyping is only a real wedge for Mode if it means exploring product changes inside the product that already exists. It should not sound like fake-prototype generation, a Figma clone, or another blank-canvas app-builder promise. ## Why this wedge matters Question it answers: > Can Mode help teams explore changes without falling back into fake prototypes? Narrative: > Product teams still need to explore ideas before committing them, but Mode's version of exploration should happen against the product that already exists. The useful promise is not "make a prototype"; it is "test a product change in product context, then decide whether it should become reviewable output." This protects us from the bad interpretation: > "So Mode is a Figma clone, prototype generator, or app-builder preview tool?" The stronger story is: > Mode supports product-native exploration: prototype against the existing product surface, preserve real constraints, and keep a path to engineering review. ## How it supports the launch spine This is a careful supporting or future wedge unless proof is especially strong. It can reinforce the spine when phrased as product-native exploration, but leading with `prototype` risks pulling the story away from real-product change. ## Strategic bet Teams still need to explore changes before committing them. Mode can make that exploration more valuable by anchoring it to existing product context and giving the work a path toward reviewable output. ## Why Mode is suited Mode can frame prototyping as product-native exploration: live route/surface first, existing components and state in view, scoped change, and a decision about whether the result becomes a reviewable proposal. ## Product entry / CTA path Ask users to prototype one change against the product they already have, then decide whether it should move toward engineering review. ## Proof needed Show an existing app/product surface, a scoped explored change, and a path from exploration to inspectable output. Do not show or describe Mode as generating a detached prototype beside the product. ## Launch-spine relevance This can support the launch spine when phrased as `product-native exploration`, but it should not displace the stronger real-product/design-QA/one-issue wedges unless product proof clearly supports it. ## Risks / confusions - `Prototyping` is a dangerous label because it invites Figma and fake-product comparisons. - Needs explicit `existing product` and `reviewable output` language. - May be a future candidate rather than active launch if self-serve/onboarding cannot support this first job yet.