Home/Docs/Product Studio

Product Studio

Compare product paths, choose exact product ideas, and generate saved reports only when the user asks for them.

Product docs draft. Last updated May 21, 2026.

Product Studio's job

Product Studio turns one validated opportunity into a product-path decision and then an exact product idea. It should help answer what to create, why that path fits, what to test first, and where the product should go next.

Product paths before product ideas

The first decision is the product path: digital product, physical product, service or offer, software or mini-tool, creator bundle, existing product, or custom manual product. After a path is selected, Product Studio can help choose the exact idea inside that path.

  • Digital Product is a parent path, not an automatic PDF decision.
  • Existing Product should route toward import or manual product profile setup.
  • Physical, service, software, and custom products should route through Product Setup or external build briefs.
  • Creator Bundle should make creator fit and Deal Room context visible early.

Capability lanes

Product Studio should be honest about what TrendRise can directly build in V1. Native Builder covers PDF guides, planners, workbooks, checklists, trackers, and worksheet packs. Guided Setup covers spreadsheets, Notion packs, Canva packs, templates, swipe files, and bundles until real builders exist. External Build Brief covers mini-apps, physical products, services, existing products, and custom products.

Reports are explicit actions

Recommendation, Market Fit, Price and Positioning, Go-To-Market, and Validation Plan should be saved report surfaces after a path is selected. They should not automatically generate just because the user opens the page.

  • Path comparison should be free exploration.
  • Generated reports should show a clear credit estimate before running.
  • Saved reports should be reused on later visits without spending credits again.
  • Comparison or regeneration should create a candidate that the user accepts before replacing the current report.

Keep the offer narrow

A useful product idea names one audience, one painful job, one promised outcome, one delivery format, one first channel, and one first validation step.

  • Audience: who is this for?
  • Outcome: what changes after they use it?
  • Format: what is the smallest useful product?
  • Channel: where can the buyer be reached?
  • Validation: what would prove or disprove this quickly?

Where Product Studio can route

The correct next route depends on the selected idea and capability lane. Native products can open Product Builder. Guided and external ideas can open Product Setup. Existing products can open Existing Product Import. Any path can move to Pipeline, Launchpad, or Creator Finder when enough context exists.

FAQ

Can Product Studio write the whole product?

No. Product Studio chooses the path and can generate saved reports or product ideas. Product Builder handles drafting where TrendRise has a supported builder lane, and all generated output still needs review.

Why does Product Studio ask for an exact format after Digital Product?

Because a PDF planner, spreadsheet, Notion pack, checklist bundle, template pack, swipe file, and lightweight tool need different builders, setup questions, launch assets, and customer expectations.

Should Product Studio spend credits when I select a path?

No. Selecting and saving a path should persist the decision. Credits belong to explicit generated reports, ideas, drafts, copy, outreach, and exports.