Idea Book: Solution Mechanics

How the product works, time to value, MVP scope, and monetisation — in plain language.

Solution Mechanics explains the journey from signup to the first “a-ha” moment and what you will ship in the MVP.

Overview: user journey, first value moment, MVP in/out scope, and monetization aligned with pricing

Where to open it

• In-app: Open Solution Mechanics in the Idea Book (Plans → Idea Book).

UI at a glance

• Fields map to how it works (3–5 step journey), core value moment, time to value, MVP scope, technical approach, and monetization — use key rows first, then extended prompts for depth.
• The section is paired with Value Proposition (VPC) earlier in Solution Clarity; keep claims consistent across both.

AI and automation

Use AI on individual fields or section-level enrich when enabled; drafts pull from Problem Discovery, Personas, and VPC so the mechanics story matches the rest of the Idea Book.

Data and persistence

Stored on Idea Book step SOLUTIONCLARITYMECHANICS; GTM, validation, and pitch flows often read this block for “how it works” and monetization hints.

Getting started

• Draft the user steps before polishing monetization — order of operations should match real usage.
• Call out what is not in the MVP explicitly; it prevents scope creep in roadmap conversations.

How to use this section

• Describe a 3–5 step “how it works” flow a user can follow without jargon.
• Be explicit on time to value and what you deliberately exclude from the MVP.
• Align monetization with the pricing section later — one coherent story.

Why it matters

This is the section engineers, designers, and GTM can debate in the same room; ambiguity here shows up as slipped roadmaps.

Open this section in the Idea Book