When you need to align the team on what to build next — a roadmap makes priorities visible and decisions defensible.
You are a senior {{role}} brought in to help {{target_user}} complete a Build a Product Roadmap. # Context Original working context: - Act as a Head of Product helping a startup founder build their first structured product roadmap. - Step 1: My product: {{describe}}. Current state: {{what_s_live}}. Customer feedback received: {{describe_key_themes}}. Business goals this year: {{describe}}. Biggest product gaps: {{list_3_4}}. - Step 2: Prioritize the product backlog: Apply the RICE framework to rank features/initiatives — Reach (how many users affected), Impact (effect on goals), Confidence (how sure are we?), Effort (weeks of engineering). Show the top 10 items ranked. - Step 3: Design the roadmap structure: Now / Next / Later format — what's committed (Now, 0–3 months), planned (Next, 3–6 months), and directional (Later, 6–12 months). - Step 4: Write the roadmap narrative: A 1-page roadmap summary for three audiences: engineering team (technical priorities), investors (what we're building and why), and customers (what's coming that helps them). - Step 5: Self-check: Is this roadmap solving customer problems or building features the founder wants? Is the 'Now' column actually achievable in 3 months given team capacity? # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When you need to align the team on what to build next — a roadmap makes priorities visible and decisions defensible.
The roadmap is a communication tool, not a commitment device. It tells the team where you're going and why. The best roadmaps change — because the best founders learn fast and update their priorities based on evidence, not ego.
Validate this business idea rigorously. Assess market size, competition, feasibility, and risk. Give an honest recommendation — do not flatter.
Conduct a structured competitor analysis. Map each competitor's strengths, weaknesses, positioning, pricing, and target customer. Identify the market gaps your business can own.
Write the complete narrative for a 10-slide pitch deck. For each slide, write the title, the key message (one sentence), and the talking points (3-5 bullets).
Recommend a pricing strategy with full rationale. Provide 3 pricing options (low/mid/premium tier) and explain what each achieves. Recommend one as optimal for the stated goal.