What Solve covers in a teardown
| Analysis type | What you get | Best for |
|---|---|---|
| Feature comparison | Side by side feature matrices across competitors | Product planning, differentiation strategy |
| Positioning analysis | How each competitor positions themselves (messaging, audience, value props) | Marketing strategy, brand positioning |
| SWOT analysis | Strengths, weaknesses, opportunities, and threats for each competitor | Strategic planning, board presentations |
| Pricing comparison | Plan tiers, feature gating, and pricing model breakdown | Pricing decisions, packaging strategy |
| User sentiment | Common praise and complaints from review sites and forums | Product differentiation, feature prioritization |
Example prompts
- Feature comparison
- SWOT analysis
- Positioning analysis
- User sentiment
- Full teardown
What results include
A competitive teardown report contains five sections. The gap analysis at the end connects findings to your strategic options.| Report section | What it covers |
|---|---|
| Executive summary | The competitive landscape at a glance: who is leading, where the gaps are, and the biggest takeaway for your strategy. |
| Competitor profiles | Brief overview of each competitor: what they do, who they target, approximate scale (revenue, users, funding), and core value proposition. |
| Feature matrix | Side by side comparison table showing which competitors offer which features. Solve marks gaps and relative strengths for easy scanning. |
| SWOT or positioning framework | Depending on your prompt, a structured SWOT analysis for each competitor or a positioning map showing differentiation. |
| Gap analysis and recommendations | Where the white space is: features nobody offers, audiences nobody serves, or positioning nobody owns. |
Example feature matrix
Here is a condensed example of what a feature comparison looks like in your report:| Feature | Figma | Sketch | Adobe XD |
|---|---|---|---|
| Real-time collaboration | Full multi-user | Limited (via Sketch for Teams) | Basic co-editing |
| Browser-based | Yes | No (Mac only) | No (desktop app) |
| Prototyping | Built-in, interactive | Built-in, basic | Built-in, advanced |
| Design systems | Robust (shared libraries) | Symbols and shared styles | Limited |
| Developer handoff | Inspect mode + Dev Mode | Sketch Cloud inspect | Design specs |
| Plugin ecosystem | 2,000+ plugins | 700+ plugins | 300+ plugins |
| Pricing (per editor/mo) | $15 | $12 | Included in CC ($55/mo) |
Example SWOT output
- Strengths
- Weaknesses
- Opportunities
- Threats
- Market-leading real-time collaboration with no install required
- Strong network effects (designers bring their entire team onto the platform)
- Extensive plugin ecosystem created by the community
- Free tier that is genuinely usable for small teams
Tips for better teardowns
Name your competitors explicitly
Name your competitors explicitly
Do not ask Solve to “find my competitors.” Name 3 to 5 specific competitors and ask for the comparison. You know your space better than any AI. Give it the right targets to analyze.
Specify comparison dimensions
Specify comparison dimensions
Tell Solve what matters: features, pricing, target audience, tech stack, go-to-market strategy, or user sentiment. Specifying dimensions keeps the analysis focused on what is actionable for you.
Request a specific framework
Request a specific framework
Ask for “a SWOT analysis,” “a positioning map,” or “a feature matrix.” Named frameworks give Solve a clear structure to work with. The output is also easier to share with your team.
Follow up on surprises
Follow up on surprises
If the teardown reveals something unexpected, ask a follow up question to explore it. “Tell me more about why no one has solved X” often surfaces the most valuable insights. Use @-mentions to carry findings forward.
Combine with market analysis
Combine with market analysis
Run a market analysis first to understand the landscape, then do a competitive teardown within that context. The combination gives you both the size and the player map.
What’s next
Pricing strategy
Use competitive insights to inform your pricing model.
Product direction
Turn competitive gaps into product roadmap priorities.
Work with reports
Export and share teardown results with your team.