Skip to main content

Before you begin

You need a verified AI Blueprint account and enough AI credits for the action you start. You can register with email and password or continue with Google.
1

Describe the product idea

On Dashboard, explain the product, target users, problem, and desired outcome. Add important constraints such as platform, region, compliance, integrations, or offline use.Write in Indonesian or English. AI Blueprint detects the idea language and uses it for generated documents.
2

Review the enriched idea

Read the Smart Requirement Summary. Confirm that the product definition matches what you intend to build.Do not approve a vague or incorrect assumption. Correct it while the context is still being formed.
3

Answer critical questions

Resolve decisions that materially change scope, actors, data, security, or delivery. A question may include a suggested answer, but the final decision is yours.
4

Approve the Idea Review / VPC

Sign only when the product context is accurate. This approval automatically starts document generation in the background, and you may safely close the tab.
5

Review generated documents

Check Application Journey, Technical Foundation, Database Schema when relevant, App Map, and every other generated document. There is no second global structure approval.
6

Approve each current document

Use Blueprint Summary to inspect open items, project health, and version history. Open each applicable document and use its Sign Approve action. The Summary reaches 10/10 Approved when every current document is signed.
Idea input followed by review, decisions, and Blueprint

Sanitized example of the idea-to-review path.

A useful idea brief

Include enough information to distinguish your product from a generic app:
  • who uses it and what each actor needs;
  • the problem and measurable outcome;
  • the main journey or transaction;
  • data, payment, file, notification, or external-system needs;
  • constraints such as mobile-only, offline-first, multi-tenant, or a launch deadline;
  • what is explicitly outside the first release.
Approval records your decision against the current version. If regeneration changes a signed document, read the changes and approve the new version again.