What Solve can do for product direction
| Analysis type | What you get | Best for |
|---|---|---|
| Feature prioritization | Ranked list of features based on impact, effort, and market demand | Sprint planning, roadmap decisions |
| User needs analysis | Structured breakdown of what users want, grouped by persona or segment | Product discovery, validation |
| Roadmap input | Research-backed recommendations for what to build and in what order | Quarterly planning, strategy docs |
| Build vs. buy analysis | Tradeoffs of building in house vs. integrating a third party tool | Architecture decisions, resource allocation |
| Feature gap analysis | What competitors offer that you do not, and whether it matters | Competitive response, differentiation |
Example prompts
- Feature prioritization
- User needs analysis
- Roadmap input
- Build vs. buy
- Feature gap analysis
Prioritization frameworks Solve can use
Request a specific framework by name, or let Solve choose the most appropriate one based on your context. If you have already run a competitive teardown, reference those findings to strengthen the prioritization.Impact vs. effort matrix
Impact vs. effort matrix
Plots features on a 2x2 grid of high/low impact and high/low effort. Quick wins (high impact, low effort) go first. Solve estimates impact based on market demand and competitive positioning, and effort based on typical engineering complexity.
RICE scoring
RICE scoring
Scores each feature on Reach, Impact, Confidence, and Effort. Produces a numeric score you can use to rank your backlog. Ask Solve to estimate each component and show the calculation.
MoSCoW prioritization
MoSCoW prioritization
Categorizes features as Must-have, Should-have, Could-have, and Won’t-have. Useful for defining an MVP or a release scope. Solve maps features to categories based on competitive necessity and user expectations.
Kano model
Kano model
Classifies features as basic expectations, performance features, or delighters. Helps you understand which features prevent churn (basic), drive satisfaction (performance), and create differentiation (delight).
Value vs. complexity
Value vs. complexity
Similar to impact/effort but framed around customer value and technical complexity. Works well for B2B products where customer value ties to willingness to pay or retention metrics.
You do not have to pick a framework. If you ask “prioritize these features,” Solve chooses the most appropriate one. Naming one gives you more control over the output format.
What results include
A product direction report contains five sections. Review the context summary first to confirm Solve is working from the right assumptions.| Report section | What it covers |
|---|---|
| Context and assumptions | Summary of the product, market, and target user that Solve is working from. Review this to verify the analysis is grounded correctly. |
| Prioritized recommendations | Ranked list or framework-based output showing which features to build first and why. Each recommendation includes reasoning, not just ranking. |
| Supporting evidence | Data points from competitor analysis, user sentiment, and market trends that support the recommendations. This is what you show stakeholders. |
| Risks and tradeoffs | What you give up by prioritizing one direction over another. Solve flags dependencies, competitive risks, and resource implications. |
| Suggested next steps | Follow up research, validation experiments, or decisions that come next. Connects the analysis to action. |
Tips for better product direction analysis
Share your current state
Share your current state
List your backlog
List your backlog
Include a list of features you are considering in the prompt. Solve works better when evaluating specific options rather than generating a list from scratch.
Name your constraints
Name your constraints
Include constraints that matter: “We have a team of 3 engineers,” “We need to ship in 6 weeks,” or “We cannot build anything that requires SOC 2 compliance yet.” Constraints shape practical recommendations.
Ask for the counter-argument
Ask for the counter-argument
After getting a recommendation, follow up with: “What is the strongest argument against this prioritization?” Challenging the analysis surfaces risks you might have missed.
Connect to other Solve analyses
Connect to other Solve analyses
If you have already run a market analysis or competitive teardown, reference those findings. “Based on the competitive gaps we identified, which features should we prioritize?” builds on previous work. Use @-mentions to carry insights forward.
What’s next
Market analysis
Ground product decisions in market data and opportunity sizing.
Investment analysis
Build the business case around your product direction.
Work with reports
Share prioritization analysis with your team and stakeholders.