Give one useful workflow a home.

Plan a SaaS workspace with managed records, app accounts, owner-funded in-app AI and Stripe test purchase flows, then expand with connected companions.

Review the prepared brief in Studio. A build starts when you send it.

Build the product's primary action first

Define the work a user should finish during their first visit. A writing assistant might organize source notes and draft a response, while an operations tool might turn a request into a tracked work item. Place that action on the first signed-in screen and make its saved outcome visible. Marketing copy, pricing and onboarding should describe the exact working scope.

Treat AI usage and subscriptions as separate systems

Managed in-app AI uses the application owner's capacity and admission rules. Test error and exhausted-capacity states as well as a successful response. A subscription price card needs an implemented entitlement policy before it can control production access. Use the supported test Checkout workflow to evaluate purchasing, and validate live billing separately.

Prove one paid-product workflow before adding billing

For a project assistant, make the first release an account plus a saved work item. A test visitor should create a brief, reload, reopen the same record and edit it. Add the summary action only after the record can be recovered when the model is unavailable. Document the limit and retry behavior, then decide which product action would actually need a subscription entitlement.

Give each screen its own job.

These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.

Plan the records and their owners.

Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.

CollectionSuggested fieldsAccess to decide
work_itemsowner, title, status, resultEach app user can access their own work items.
ai_requestsowner, work_item_id, state, result_referenceKeep prompts and results private to the authorized principal.

Verify the outcome, then expand.

From this brief to your first version.

  1. Review the proposed workflow

    Start with this editable blueprint brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.

  2. Build and check the result

    Review the isolated preview and execute the checks listed on this page. Begin with Marketing, onboarding, account and the primary SaaS workspace. Resolve missing service setup and save verified progress before expanding the scope.

  3. Connect or export when ready

    Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.

Make the starting point your own.

Name your project and review the brief. Building starts when you send it.

Start at $0. Source unlock $4.99 once per project.Compare $10 Plus, $20 Pro and $60 Ultra monthly plans

Questions before you build.

Will the AI actions use my customers' model accounts?

The managed in-app AI path is owner-funded and subject to its configured allowance and limits. Review the cost and authorization model before publishing.

Can I add subscriptions to the plan?

Yes. Describe the access rules and billing lifecycle. Verify which parts are supported by the configured payment service and separately implement and test production entitlements.

Read the public Markdown reference