Skip to main content
Product decisions are hard because the data is scattered across user feedback, competitor moves, market trends, and team intuition. Solve pulls these together into structured analysis for prioritization, validation, and roadmap planning. Share your backlog and constraints, then ask Solve to rank options using a framework. You can also attach internal documents like user research summaries or feature specs to give Solve additional context.

​
What Solve can do for product direction

​
Example prompts

​
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.
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.
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.
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.
Classifies features as basic expectations, performance features, or delighters. Helps you understand which features prevent churn (basic), drive satisfaction (performance), and create differentiation (delight).
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.

​
Tips for better product direction analysis

Tell Solve what you have already built, your target audience, and your stage (pre-launch, early traction, scaling). Context prevents generic advice and produces recommendations that match your situation.
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.
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.
After getting a recommendation, follow up with: “What is the strongest argument against this prioritization?” Challenging the analysis surfaces risks you might have missed.
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.

Reports

Share prioritization analysis with your team and stakeholders.