> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/app-builder/plan.md). # Plan Building a great financial app starts with a solid blueprint. This phase establishes core logic, team alignment, and architectural integrity **before** generating code. * **Objective**: Define application requirements and vet logic using **Plan Mode**. * **Outcome**: An accurate blueprint that eliminates technical guesswork and reduces technical debt.

The Platform Planner proposing a structured architecture for a Subscription Management Hub.

{% hint style="info" %} Planning is optional. **Build Mode** is the default, and for a small or well-understood app you can prompt straight into [Build](/app-builder/build.md). Switch to Plan Mode from the header dropdown when the logic is complex, regulated, or needs sign-off before code exists. {% endhint %} ## Plan Mode Think of **Plan Mode** as your strategic sandbox for talking through the "why" and "how" of your application. * **Logic Mapping**: Map out complex workflows, such as loan eligibility or KYC processes, before committing to a build. * **Transparency**: Toggle the **"Thought"** dropdown to view the AI's reasoning and ensure alignment with business goals.

Reviewing proposed logic and "Extra Ideas" generated by the AI System Planner.

{% hint style="warning" %} The **Publish** action is unavailable while in Plan Mode. To share early work with stakeholders, use the public view links from **Share Project** instead — see [Collaboration](#collaboration) below. {% endhint %} ## Iterative building Refine and adjust your requirements in real time using the chat with the Planner. * Use **"Revise plan"** to add features or modify logic (e.g., "Add a masked payment method column"). * Experiment with different data models or structures without overwriting a working build.

Using the chat and 'Revise plan' to iteratively update the blueprint before the build phase.

## Template Marketplace Use industry-standard templates to bypass boilerplate setup and establish a functional baseline. * Select a financial template (e.g., Budget Tracker) from the dashboard. * Templates come with pre-configured layouts and common components, so you can focus your energy on your unique proprietary logic. * Once you load a template, you can use **Plan Mode** to strip it down, add new features, or completely rebrand it to match your bank's identity.

Create New App from the Template Marketplace

## Version history Manage project iterations and eliminate the risk of failed experiments during the design phase. * Access the **Version** dropdown to view previous prompts and architectural states.

* Choose to either **View a version** temporarily or **Revert** to restore a previous state permanently.

## Collaboration Shipping enterprise apps requires input from multiple experts to vet compliance and UI design. * Use **Share** to bring in developers, risk officers, or co-founders via email. * Assign **Full Edit** permissions for co-authoring or **View-Only** for stakeholder reviews.

Share Project where owners can manage collaborator emails and access levels.

*** When the blueprint is right, click **Start building** — or read [Build](/app-builder/build.md) first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.uptiq.ai/app-builder/plan.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.