> ## Documentation Index
> Fetch the complete documentation index at: https://dhiwisepvtltd-5e04e6a4.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Competitive teardowns

> Run competitive teardowns in Rocket.new Solve: compare features side by side, generate SWOT analysis, and map competitor positioning in one report.

Solve produces structured competitive breakdowns covering features, positioning, strengths, and weaknesses. Instead of spending days auditing competitor websites manually, create a Solve task and get a structured analysis.

Pair your teardown with a [market analysis](https://dhiwisepvtltd-5e04e6a4.mintlify.site/solve/research/market-analysis.md) to see both "how big" and "who's here" in one picture.

## 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**

```plaintext wrap theme={null}
Compare Figma, Sketch, and Adobe XD on their core features: prototyping, collaboration, design systems, developer handoff, and plugin ecosystem. Create a feature matrix and identify where each tool is strongest and weakest.
```

**SWOT analysis**

```plaintext wrap theme={null}
Run a SWOT analysis on Shopify as an e-commerce platform for small businesses. Consider their recent AI features, international expansion, and competition from Amazon and newer players like Fourthwall.
```

**Positioning analysis**

```plaintext wrap theme={null}
How do Linear, Jira, and Shortcut position themselves differently? Analyze their homepage messaging, target personas, and key differentiators. Which positioning leaves the most room for a new entrant?
```

**User sentiment**

```plaintext wrap theme={null}
What are the top 5 complaints about HubSpot CRM from G2, Capterra, and Reddit? Group them by theme and estimate how many users each issue affects. What does this reveal about opportunities for a competing product?
```

**Full teardown**

```plaintext wrap theme={null}
Do a full competitive teardown of the email marketing space. Compare Mailchimp, ConvertKit, Beehiiv, and Resend on: features, pricing, target audience, strengths, and weaknesses. End with a gap analysis showing underserved needs.
```

## 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**

* 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

**Weaknesses**

* Performance degrades with very large files (1,000+ frames)
* Limited offline capability (requires internet connection)
* Advanced prototyping still less powerful than dedicated tools
* Enterprise pricing is steep compared to alternatives

**Opportunities**

* AI-powered design generation is still nascent (first-mover advantage possible)
* Developer workflow integration (design to code) is a growing demand area
* Expansion into non-design use cases (whiteboards, docs) via FigJam

**Threats**

* Adobe's deep pockets and existing Creative Cloud user base
* Open-source alternatives like Penpot gaining traction
* Potential commoditization as AI makes design tools more accessible

## Tips for better teardowns

> **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**
>
> 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**
>
> 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**
>
> 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**
>
> Run a [market analysis](https://dhiwisepvtltd-5e04e6a4.mintlify.site/solve/research/market-analysis.md) 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](https://dhiwisepvtltd-5e04e6a4.mintlify.site/solve/research/pricing-strategy.md)**
>
> Use competitive insights to inform your pricing model.

> **[Product direction](https://dhiwisepvtltd-5e04e6a4.mintlify.site/solve/research/product-direction.md)**
>
> Turn competitive gaps into product roadmap priorities.

> **[Reports](https://dhiwisepvtltd-5e04e6a4.mintlify.site/solve/results/reports.md)**
>
> Export and share teardown results with your team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.