> 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/ai-workbench-qore/console/app-builder/plan.md).
# Plan
Define requirements and architecture before generating app code.
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](/ai-workbench-qore/console/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, add them as collaborators from **Share** 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.
Rollback to a previous version.
* Choose to either **View Version** to load it temporarily, or **Revert to Version** to restore it. While you view a version, **Back to Latest** returns you to the newest one. See [App Workspace › Versions and publishing](/ai-workbench-qore/console/app-builder/app-workspace.md#versions-and-publishing).
View or Revert to a version
## 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.
{% hint style="warning" %}
**Sharing grants access at the account level.** Inviting someone by email adds them to the account as a collaborator, which lets them open, edit and publish apps across that account — not only the one you shared. Per-app access levels and public view-only links are not available today. Check with your platform administrator before sharing an app that contains sensitive material.
{% endhint %}
Share Project where owners can manage collaborator emails and access levels.
***
When the blueprint is right, click **Start building** — or read [Build](/ai-workbench-qore/console/app-builder/build.md) first.
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul AI-assisted, human-approved
{% endcolumn %}
{% endcolumns %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/console/app-builder/plan.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
