Roadmap Prioritizer: Leads Edition
The Roadmap Prioritizer: Leads Edition prompt evaluates prospective customer needs (leads) against current development plans to prioritize, defer, or reject features, maximizing a specified North Star Metric while maintaining engineering health.
What is the Roadmap Prioritizer: Leads Edition prompt?
Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.
ROLE: You are an expert Strategic Product Manager and Growth Lead with a specialization in high-velocity B2B software environments. Your expertise lies in balancing short-term revenue gains with long-term product vision by mathematically weighing lead requirements against existing roadmap priorities. GOAL: Your objective is to evaluate a set of prospective customer needs (leads) against current development plans to determine which features should be prioritized, deferred, or rejected. You must provide a data-driven recommendation that maximizes [NORTH STAR METRIC] while maintaining engineering health. CONTEXT: I am currently managing a product roadmap and need to decide how to accommodate new requests from high-value prospects. Use the following variables to inform your analysis: - TARGET REVENUE: [TARGET REVENUE] - CURRENT ROADMAP: [CURRENT ROADMAP] - PROSPECT REQUESTS: [PROSPECT REQUESTS] - ENGINEERING CAPACITY: [ENGINEERING CAPACITY] - NORTH STAR METRIC: [NORTH STAR METRIC] INSTRUCTIONS: 1. Impact Analysis: Match the [PROSPECT REQUESTS] against the [CURRENT ROADMAP]. Identify which requests align with the current vision and which are "extracurricular" or bespoke. 2. Value Calculation: For each prospect request, estimate its potential impact on [NORTH STAR METRIC] versus the effort required based on [ENGINEERING CAPACITY]. 3. Strategic Trade-offs: Identify exactly which items from the [CURRENT ROADMAP] must be delayed or removed to accommodate any "must-have" prospect requests if they were to be prioritized today. 4. Risk Assessment: Highlight the technical debt or product fragmentation risks associated with building exactly what the prospects are asking for versus building a more generalized solution. 5. Recommendation: Provide a finalized priority list that optimizes for [TARGET REVENUE] without sacrificing the product’s long-term scalability. OUTPUT FORMAT: - EXECUTIVE SUMMARY: A brief overview (3-4 sentences) of the overall strategy for this period. - PRIORITIZED BACKLOG: A table including Feature Name, Strategic Fit (High/Medium/Low), Estimated Impact on [NORTH STAR METRIC], and Recommendation (Keep/Add/Decline). - TRADE-OFF LOG: A specific list of what gets bumped from the [CURRENT ROADMAP] to make room for new leads. - RATIONALE: A detailed explanation for the 'Decline' recommendations to assist Sales in managing prospect expectations. QUALITY BAR: The output must be strictly analytical. Avoid generic advice; use the specific context provided in the variables to create a realistic, actionable trade-off plan. Do not suggest "doing it all" if the [ENGINEERING CAPACITY] does not support it. Ensure every recommendation is tied back to achieving [TARGET REVENUE].
What variables does the Roadmap Prioritizer: Leads Edition prompt use?
| Variable | What to put | Example |
|---|---|---|
| TARGET REVENUE | The specific revenue goal you aim to achieve with product decisions. | e.g. $5M ARR increase in Q3 |
| CURRENT ROADMAP | A list or summary of existing product features and initiatives planned for development. | e.g. {Feature A: Q1 2024, Feature B: Q2 2024, Technical Debt Refactor: Ongoing} |
| PROSPECT REQUESTS | Detailed descriptions of features or functionalities requested by prospective high-value customers. | e.g. {Prospect X: Custom reporting module, Prospect Y: Advanced integration with CRM Z} |
| ENGINEERING CAPACITY | An estimate of available engineering resources or bandwidth for development work. | e.g. 3 dev teams @ 80% capacity for 6 weeks |
| NORTH STAR METRIC | The single most important metric indicating the product's success and growth. | e.g. Monthly Active Users (MAU) or Customer Lifetime Value (CLTV) |
How do I use the Roadmap Prioritizer: Leads Edition prompt?
- 1Step 1: Identify and gather all relevant data for the variables: TARGET REVENUE, CURRENT ROADMAP, PROSPECT REQUESTS, ENGINEERING CAPACITY, and NORTH STAR METRIC.
- 2Step 2: Replace each bracketed variable in the prompt body with your specific data. Ensure the information is concise and well-structured.
- 3Step 3: Submit the enriched prompt to your chosen AI model (e.g., GPT-4o, Gemini 2.5 Pro).
- 4Step 4: Review the EXECUTIVE SUMMARY, PRIORITIZED BACKLOG, TRADE-OFF LOG, and RATIONALE. Use this output to inform your product strategy and communicate decisions to stakeholders.
When should you use the Roadmap Prioritizer: Leads Edition prompt?
Integrating Sales-Driven Features
Use this prompt when sales teams are bringing in high-value prospect requests that need a formal assessment against the current product roadmap.
Balancing Short-term Revenue with Long-term Vision
Apply this prompt to make informed decisions that can lead to immediate revenue gains without compromising the product's strategic direction or technical health.
Roadmap Re-evaluation
Utilize this prompt for quarterly or bi-annual roadmap reviews when new market opportunities or significant lead requests emerge.
Communicating Prioritization Decisions
Leverage the structured output to clearly articulate feature prioritization rationale to sales, engineering, and leadership teams.
Optimizing Engineering Resources
Employ this prompt to ensure engineering capacity is allocated to the most impactful features, whether from the existing roadmap or new lead requests.
Managing Technical Debt
Use the risk assessment to proactively identify and mitigate future technical debt or product fragmentation caused by bespoke feature development.
What does the Roadmap Prioritizer: Leads Edition prompt output look like?
EXECUTIVE SUMMARY: This period's strategy will selectively integrate high-impact prospect requests to boost Q3 ARR, specifically focusing on critical integrations. We will defer lower-impact items from the current roadmap to maintain agility without sacrificing our long-term MAU growth. Strict evaluations are in place to avoid unnecessary technical debt, ensuring scalable progress. PRIORITIZED BACKLOG: - Feature A: Keep, High, +10% MAU - Feature B: Keep, Medium, +5% MAU - Custom Reporting Module (Prospect X): Add, High, +$1.2M ARR - Advanced CRM Z Integration (Prospect Y): Add, High, +$0.8M ARR - Technical Debt Refactor: Keep, High, Engineering Health - Legacy System Migration: Decline, Low, -2% MAU impact TRADE-OFF LOG: - Legacy System Migration: Bumped from Q3 to Q4 to accommodate Custom Reporting Module and Advanced CRM Z Integration. - UI/UX Refinement Sprint: Delayed by 2 weeks. RATIONALE: - Legacy System Migration: While strategically important, its immediate impact on our North Star Metric (MAU) is relatively low compared to the high-value prospect requests. Sales can communicate that this is a Q4 initiative, assuring prospects of future improvements. - UI/UX Refinement Sprint: A minor delay here is acceptable as the immediate ROI from the new prospect features significantly outweighs the short-term impact of this enhancement. This sprint will be rescheduled once the high priority lead features are delivered.
Which AI model works best with the Roadmap Prioritizer: Leads Edition prompt?
Excellent for detailed strategic reasoning, complex trade-offs, and generating structured outputs with nuanced explanations.
Strong in handling multi-faceted inputs, making detailed quantitative estimations, and providing clear, actionable recommendations for product management.
Good for generating coherent narratives around prioritization, risk assessment, and clear communication points for stakeholder management.
What are the pros and cons of the Roadmap Prioritizer: Leads Edition prompt?
Pros
- Provides a systematic method for feature prioritization
- Balances short-term revenue with long-term product health
- Generates data-driven recommendations
- Highlights critical trade-offs and risks
- Offers structured output for stakeholder communication
- Optimized for high-velocity B2B environments
Cons
- Requires accurate input data for effective analysis
- Estimates (e.g., impact, effort) are subjective without real data
- May struggle with highly ambiguous or conflicting requests
- The quality of the output heavily depends on the user's input precision
How can you get better results from the Roadmap Prioritizer: Leads Edition prompt?
- Be as specific as possible when defining [CURRENT ROADMAP] and [PROSPECT REQUESTS].
- Clearly articulate your [NORTH STAR METRIC] to guide the AI's recommendations.
- Provide quantitative estimates for [ENGINEERING CAPACITY] (e.g., story points, sprint weeks).
- Iterate on the prompt by refining variable inputs based on initial outputs.
- Use real-world examples or summaries for prospect requests to enable more accurate impact analysis.
- Define clear criteria for 'High-value prospects' when providing requests.
Frequently asked questions about the Roadmap Prioritizer: Leads Edition prompt
What is the Roadmap Prioritizer: Leads Edition prompt?
It's a prompt designed to help product leaders strategically evaluate new customer requests against an existing product roadmap to make informed prioritization decisions that balance revenue goals and product vision.
Who can benefit most from this prompt?
Strategic Product Managers, Growth Leads, and Product Executives in B2B software companies will find this prompt particularly useful for managing roadmap complexities driven by sales and prospect demands.
What kind of information should I provide for 'PROSPECT REQUESTS'?
You should provide clear, concise descriptions of the features or functionalities requested by high-value prospects, including any perceived value or urgency they've expressed.
How does this prompt help manage technical debt?
The prompt includes a specific 'Risk Assessment' step that identifies potential technical debt or product fragmentation risks associated with building bespoke features, guiding you towards more generalized solutions.
Can I use this prompt for internal feature prioritization as well?
While optimized for lead-driven requests, the underlying methodology can be adapted for general internal feature prioritization if you define internal requests similarly to 'PROSPECT REQUESTS' and set clear metrics.
What if my 'NORTH STAR METRIC' is not purely financial?
That's perfectly fine. The prompt is flexible enough to accommodate various North Star Metrics, such as user engagement, retention, or customer satisfaction, as long as it's clearly defined.
How accurate are the 'Value Calculation' and 'Impact Analysis' outputs?
The accuracy depends heavily on the specificity and quality of the input data you provide. The AI will make the best estimations possible based on the context given.