When we shipped the Favorites page last week, the natural next question was: ok, I've saved an opportunity — now what? This update answers that.
The AI build pipeline
Every saved opportunity now has a three-step AI workflow:
- Get Solution — a concrete product idea with a difficulty rating (Easy / Medium / Hard). This was already there, but it's now the first step in a pipeline.
- Get MVP — takes the solution and proposes a lean MVP: core features, target users, recommended tech stack, and a build effort estimate.
- Get Plan — takes the MVP and generates a phased implementation roadmap. Phase 1, 2, 3 with timelines, deliverables, and success criteria for each.
Each step feeds the next. You can stop at any stage — not every opportunity needs a full plan, and not every session has time for one.
All three outputs are cached by problem. The first person to generate a solution, MVP, or plan for a given problem pays the AI cost. Everyone after recalls the same output instantly (marked ⚡ recalled). Popular problems effectively get a community answer.
Download everything
Each panel now has a Download .md button. Solution, MVP, and plan each export as a clean markdown file named after the problem — ready to paste into Notion, Obsidian, Linear, or a README.
A cleaner tier structure
We restructured the plans around what people are actually trying to accomplish:
| Tier | Price | What you get |
|---|---|---|
| Free Trial | 7 days | Full Pro access — taste the whole pipeline |
| Hobbyist | $19/mo | AI solutions, unlimited cards, favorites |
| Pro | $29/mo | Solutions + MVP proposals + phased plans |
| Premium | $39/mo | Pro + API access + team seats |
| Agency | $499/mo | Premium + white-label + priority support |
The trial now shows you the full Pro feature set so you know exactly what you're deciding between when it ends. Hobbyist is for people who want market intelligence without the build pipeline. Pro is for people who want to go from "interesting problem" to "I know what to ship."
A note on the build process
The MVP and plan generation uses a longer context window than the solution step — a phased plan for a real SaaS idea can easily run 4,000+ tokens. We found out the hard way (JSON parse errors from truncated responses) and bumped the limit accordingly.
The plan prompt asks Claude to return properly escaped markdown inside JSON. The solution is cached immediately on first generation so a truncation or network error on a retry doesn't cause a double-generation.
What's next
Tier gating is live — MVP and plans are Pro+. The next thing we're watching is whether users stop at "Get Solution" or go all the way through the pipeline. That'll tell us whether the three-step workflow feels natural or whether we need to make the progression more obvious.
As always — if something feels off, hit Support and let us know.