Founders rarely need one isolated AI output. They need a product that works, a clear story about it, a way to reach customers, and evidence that each step actually happened. PromptUI keeps those jobs in one connected journey: build, verify, launch, grow, and learn.
1. Build a product, or continue the one you already have
Builder can start from an idea, continue an existing PromptUI project, or import a GitHub codebase. It turns the request into a build plan and explicit acceptance criteria—the important outcomes the result should satisfy—then generates an editable React or Next.js product.
The work can include sign-in, stored data, payments, uploads, email, analytics, and AI tool calling when the request needs them. Named providers and explicit exclusions stay attached to the build. A preview that still uses sample data is not presented as a live production integration.
2. Verify what is real with Guardian
Guardian uses the same project and acceptance record. It can check supported routes, rendering, mobile layouts, important interactions, runtime behavior, and requested requirements, then attach evidence to the result. Untested work stays unverified; a partial implementation is not turned into a pass.
For eligible managed apps, Guardian can also correlate supported live issues, prepare a bounded repair, redeploy through the existing project owner, and mark the issue resolved only after the repaired route is proved live. This is stronger release evidence, not a universal promise that every defect can be found or repaired automatically.
3. Keep the business story in Brand Memory
For an existing business, PromptUI can read its website or store into a proposed Brand Profile: identity, products or services, audience, voice, offers, calls to action, claim boundaries, source evidence, and visual direction. The user reviews it before saving.
That approved, compact context becomes Brand Memory. Builder handoffs, launch assets, Growth Agent drafts, and campaign work can refer to the same business truth instead of asking the owner to repeat it in every tool. It stores useful decisions and references—not an indiscriminate transcript of everything the user has done.
4. Publish through one Launch Room
When the product is ready, the Launch Room brings together the live app, evidence, brand, campaign, creative assets, and video readiness. Publishing shows the real credit charge before confirmation. The separate Get Found step checks practical discoverability basics such as the title, description, share image, headline, robots file, and sitemap, then turns gaps into Builder-ready fix requests.
5. Create and manage growth work
Growth Agent uses the approved product and business context to prepare campaign briefs, posts, images, carousels, launch packs, and short-form video. Work follows one queue through draft, review, approval, scheduling, publishing, results, archive, and reuse. Editing media or copy invalidates the old approval so a changed asset cannot silently inherit permission to publish.
Supported social connections can publish approved work. Coverage depends on each platform’s account type, permissions, and review status, so PromptUI shows connection and readiness separately rather than treating an OAuth login as proof that every action is available.
6. Automate safely and read the results
PromptUI supports account-scoped API keys, MCP tools, and signed webhooks for selected Builder and Growth Agent actions. In everyday language, those let Codex, Claude Code, Cursor, or a customer system ask PromptUI to build, check status, create content, review the queue, publish an approved item, or read analytics without creating a second workflow.
The current analytics owner combines available connected-channel results with PromptUI publishing history. Webhook delivery has bounded retries, signed payloads, and compact receipts. Broader advertising, commerce, CRM, and lead-source rollups remain provider-by-provider work rather than a claim that every outside system is already connected.
7. Keep paid campaigns controlled
The business-safe Meta campaign workflow is currently a Preview release candidate while external app review and one final native hierarchy proof complete. It requires an explicit advertiser, Page, verified dataset and sales events, product evidence, stock acknowledgement, budget and time bounds, a readable campaign summary, and fresh approval after edits. Its write boundary is PAUSED: it must not activate spending.
That distinction matters. PromptUI already has a substantial Growth Agent. It should not publicly claim a complete paid advertising and lead-generation team until the native image, campaign, ad set, creative, ad, Page, dataset, and zero-spend receipts have all been read back, and the real merchant commerce loop has been proved.
8. Use Guide without adding another AI lane
The PromptUI Guide is a zero-credit coach and router. It can send a user to the right existing workflow, retain the project lineage across reloads, and offer real retry or human-help actions after repeated Builder trouble. The next maturity step is a small, read-only journey summary from the existing Builder, Brand Memory, Launch, connection, queue, and campaign owners so Guide can recommend one genuinely relevant next action. It does not need a new model, database, or duplicate memory system to do that.
What is ready now, and what is still gated
- Live with production evidence: core Builder, acceptance reporting, eligible Guardian repair proof, Brand Profile and Brand Memory, the content queue, supported publishing, MCP tools, webhook automation, and the first read-only Growth analytics facade.
- Live but deliberately bounded: automated checks, physical-device coverage, supported social platforms, and Guardian repair eligibility.
- Preview release candidate: business-safe Meta campaign submission and the wider small-business commerce workflow.
- Still externally gated: Meta Marketing API review, one complete PAUSED hierarchy readback, and real merchant Shopify purchase, refund, and cancellation attribution.
Start with Builder for a product, Growth Agent onboarding for an existing business, Import for an existing codebase, or the MCP guide to use PromptUI from Codex or Claude Code.