PromptUI started as a place where apps begin from a prompt. But the people signing up increasingly arrive with something already: a store, a service business, a repo an AI coding tool wrote for them. This wave reworked the first run around that fact.
Three doors, one decision
A brand-new account now gets one routing decision instead of a drop into a builder chat: Build something new, Grow an existing business, or Import code you built elsewhere. Each door lands in a flow made for it — and if you arrived knowing what you want, a prompt or template skips the doors entirely.
Your Brand Kit, read from your website
The grow door’s first job is teaching the workspace who you are. Paste your website or store address and PromptUI reads it — name, tagline, offers, products — into a proposed Brand Kit. Every field waits for your review before it saves, and everything the Growth Agent drafts afterwards is grounded in that saved kit, not a placeholder brand. A clear button exists too, because your workspace should never contain anyone’s business but yours.
A launch journey that ends in being found
Deploying an app now opens onto a five-stage journey: deployed, launch kit, published, get found, results. The new Get Found stage checks the findability basics of your live app — title, description, share image, headline, robots and sitemap files — and turns every failing basic into a fix request you can hand straight back to the builder. Guided Google Search Console and Business Profile checklists follow, with starter keywords drawn from your own product context.
Learn it in one sitting
There is now a step-by-step Growth Agent guide naming every button in the order you will meet it, plus solution pages written in the language of specific trades. One rule repeats through all of it: drafts wait for your approval, and nothing publishes without you.
And if your app already exists
The third door is for code born elsewhere. Push it to GitHub — from Claude Code, Codex, Lovable, Bolt, Replit, or your own editor — and import it into PromptUI: verification runs on the real rendered app, deploy is one click, and the launch journey above picks up from there.