Product Builder

When to use Product Builder

Use Product Builder after Product Studio has selected an exact directly buildable format. V1 native builder work should focus on PDF-like products: guides, planners, workbooks, checklists, trackers, and worksheet packs.

What Builder can create

Builder can help create structured product assets in stages. Each generated output should be saved and tied to the workspace, opportunity, selected idea, and builder mode.

• Product brief and outline.
• Content draft and worksheets.
• Marketing copy, FAQ, and listing copy.
• UGC scripts and ad-copy angles.
• Spreadsheet schema or planning notes where relevant.
• Asset plan and export package manifest.

Content maturity matters

Builder should not pretend work exists before it has been generated, imported, or saved. Tabs such as Outline, Draft, Copy, UGC, Schema, Assets, and Export should unlock from matching saved records or show honest not-yet-generated states.

Credit-confirmed generation

Generated builder jobs should open a confirmation before spending credits. Existing saved output should be reused without charging again. If generation cost or provider state is unknown, the action should be disabled or deferred instead of guessing.

Artifacts and review

Private beta artifact exports can create protected PDF, SVG, ZIP, or Markdown versions for validation. These are not public storefront files, customer delivery assets, Google Docs or Sheets, or final marketplace listings. Versions should have review states such as needs review, approved, or changes requested.

When not to use Builder

Do not force unsupported formats into Product Builder. Spreadsheets, Notion packs, Canva packs, mini-apps, physical products, services, existing products, and custom products should use Product Setup, build briefs, external tools, or import flows until real builder modes exist.