Playbooks give you a quick plan for each idea your plan opens: what to build first, a stack, ways to charge, the main risks and how to find your first customers. Open "Playbooks" in the "Discover" group of the menu, or go to Playbooks.
Who can use Playbooks
Playbooks come with every paid plan. The line above the page title counts yours ("… playbooks on your plan"). On the free plan, the page says "Playbooks are a premium feature", with a "View plans" button that opens Pricing.
Find and open a playbook
- Pick a chip: "All", "SaaS", "Mobile", "Extension" (browser extensions), "Bot" (bots for team chat apps) or "API". Every other niche sits under "SaaS".
- Type in the search box to search titles, ecosystems and descriptions. The count under it shows how many match.
- Click "Open full blueprint" on a card. The playbook opens in a side panel.
Cards are sorted so strong pain and weak competitors come first, with a pager at the bottom. Each card shows the "Pain" score, the build time, a pricing idea, "Comp" (the average star rating of the existing products), and short blocks such as "Build steps", "MVP scope", "Stack" and "Top risk", plus a first step to find customers.
Inside a playbook
The head shows badges for the type, ecosystem, complexity and signal (where the pain shows up), then four numbers: "Opportunity" (pain mixed with how weak the existing products are), "Pain Score", "Comp Rating" (lower means weaker competitors) and "Build Time". Below them are five tabs:
- "Overview": the "Executive summary" (the idea in three lines) and the "Validation checklist", measurable checks to pass before you write code.
- "Market": "Top 3 competitors" and the "Ideal customer profile": "Beachhead" (the first group to win), "Where they hang out" and "Willingness to pay".
- "Product": "5 suggested names & domains", "MVP scope", "Monetization" (example price tiers) and "Risks & mitigations".
- "Stack": the "Recommended stack", with a tool and a reason for each part of the product. When the type badge says "SaaS Gap" or "Mobile Gap", an "Engineering primer" adds a rules file for AI coding tools: click "Copy" and save it in your code project's main folder.
- "GTM" (go to market): steps to win your first customers, in order, and three "North-star metrics" to watch each week.
Template guidance and AI parts
Most of a playbook is template guidance: fixed advice for this kind of product, filled in with the niche's own details, as the line "Built from this niche's type and ecosystem" on each card says. Two niches of the same kind get much the same steps, stack, price tiers, risks and metrics. Everything except the three parts below works this way.
Three parts are written by AI once per niche, from its title, type, ecosystem and description: the "Validation checklist", "Top 3 competitors" and "5 suggested names & domains". They are written the first time someone opens them, and from then on everyone whose plan opens the niche gets the same stored text. If a part does not load, click "Retry". These parts use no credits.
- Competitors come from what AI already knows, with no live web search. Each links to the company's site: check it before you rely on it.
- Each name comes with a few domains, checked with the domain registries when the names were written. The main one shows "Available", "Taken" or "Unknown". Taken alternatives are crossed out. The check is not repeated, so check again, and look for trademarks, before you buy.
Playbooks, reports and Build this with AI
- A report's "What to build" act ("Who it's for", "MVP", "Pricing & ways to monetize" and "Risks") is written by AI for that one idea, from its stored complaints and measured data. A playbook is a quicker, general plan for the kind of product. See the report guide.
- "Build this with AI" turns a report into a prompt for AI coding tools and app builders, and each click on a tool counts as an export. A playbook is for you to read: it sends nothing to another tool. See Build this with AI.