Idea Book: Problem Discovery

Name your idea, define the problem, and show why it matters before you build.

Problem Discovery is where you turn a vague hunch into a testable problem story: who suffers, when it hurts, and what they do today instead of your product.

Structural overview: Idea Book roadmap, section fields, save, and AI entry points

Where to open it

• In-app: Open this section in the Idea Book (Plans → Idea Book).

UI at a glance

• Roadmap shows which Idea Book steps are complete, next, or locked behind prerequisites.
• Section body is the structured form for this step; scroll for extended fields where offered.
• Use Save as you go; watch for AI on individual fields or bulk enrich in the section header when enabled.

AI and automation

AI drafts from other Idea Book fields so wording stays consistent across steps. It does not replace customer discovery — pair with Validation when you need evidence. Pricing steps apply explicit locks that can disable AI until you unlock them.

Data and persistence

Stored with your venture’s Idea Book row for this step; downstream plans (GTM, Sales, Marketing, and others) may read these fields for gates and suggestions.

Getting started

• Open the section when the roadmap shows it as available (complete prerequisite fields first if it’s locked).
• Capture key fields before long-form prompts so AI and exports stay coherent.
• Save before you jump to another section; revisit after validation or pricing changes.

How to use this section

• Fill Idea title, industry, geography, and target audience first so AI and downstream tools share one context.
• Write a tight problem statement and a one-line solution — enough to align the team, not a full spec.
• Use extended fields (triggers, pain, frequency, cost of inaction) to prepare for validation and investor questions.

Why it matters

Other Idea Book steps and many product tools look here for a coherent “problem → who → why now.” Treat this as the narrative spine of your venture.

Open this section in the Idea Book