Plan
Define requirements and architecture before generating app code.

Plan Mode

Iterative building

Template Marketplace

Version history


Collaboration

Last updated
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.

Planning is optional. Build Mode is the default, and for a small or well-understood app you can prompt straight into Build. Switch to Plan Mode from the header dropdown when the logic is complex, regulated, or needs sign-off before code exists.
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.

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 below.
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.

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.

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.

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.

When the blueprint is right, click Start building — or read Build first.
Last updated

