> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Competitive response
> React fast with Rocket.new: Intelligence, Solve, and Build.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
This workflow helps you respond to competitive moves quickly. Intelligence detects the change, Solve analyzes the impact, and Build ships your response - all within the same platform.
## When to use this workflow
* A competitor launches a new feature, changes pricing, or updates their positioning
* You receive an Intelligence signal that requires a strategic response
* You need to move fast - research, decide, and build in the same day
## The workflow
Run the **Intelligence setup** wizard once to set up monitoring for your key competitors. Once approved, Intelligence automatically surfaces changes to your dashboard.
**In the wizard, for each competitor you add:**
* Provide the company name and website URL
* Select the signal categories that matter most to you (e.g., Pricing and packaging, Product updates)
* Set frequency (daily for fast-moving markets, weekly otherwise)
**Example signal:** Intelligence alerts you that Competitor A just launched a free tier and updated their pricing page to undercut your Pro plan.
When a signal arrives that needs a response, create a **Solve task** to understand the implications.
```plaintext wrap theme={null}
[Competitor A] just launched a free tier and restructured their pricing. Their new tiers are: Free ($0, limited to 3 projects), Pro ($19/month, was $29), and Enterprise (custom pricing). Analyze the impact on our business: How does this change the competitive landscape? Should we respond with pricing changes? What features differentiate us at each tier? What's the risk of not responding?
```
Review the analysis. Solve will give you a strategic assessment with options - adjust pricing, differentiate on features, target a different segment, or a combination.
**Follow-up:**
```plaintext wrap theme={null}
If we keep our current pricing but add a limited free tier, what features should the free tier include to be competitive without cannibalizing our Pro plan?
```
Based on the analysis, create a **Build task** (or iterate on your existing app) to ship your competitive response.
**Example - new pricing page:**
```plaintext wrap theme={null}
Update my pricing page. Add a new Free tier ($0/month, 3 projects, 1 user, community support). Keep the Pro tier at $29/month but add these features to justify the price gap: unlimited projects, priority support, custom branding, and advanced analytics. Add a comparison table that clearly shows the value of upgrading. Highlight the Pro tier as "Most Popular."
```
**Example - new feature to differentiate:**
```plaintext wrap theme={null}
Add a collaborative workspace feature to my app. Multiple users should be able to work on the same project with real-time updates. Include: a shared project view, comment threads on tasks, an activity feed showing team actions, and role-based permissions (admin, editor, viewer). This differentiates us from [Competitor A] who only supports single-user projects.
```
Test your changes in [staging](/build/launch-web/launch-your-site), verify everything works, and click **Launch** to deploy. Speed matters - competitive responses lose value the longer they take.
If something goes wrong, use [one-click rollback](/build/launch-web/launch-your-site#roll-back-a-release) to revert instantly.
## Example: responding to a pricing change
| Phase | Capability | What happens | Time |
| ------- | ------------ | ------------------------------------------------------------ | ------------- |
| Detect | Intelligence | Signal: Competitor drops prices and adds free tier | Automatic |
| Analyze | Solve | Impact assessment with strategic options | 5 minutes |
| Decide | - | Choose to add a free tier and differentiate on collaboration | - |
| Build | Build | New pricing page + collaborative features | 30–60 minutes |
| Launch | Build | Test in staging, click Launch to deploy | 10 minutes |
Total time from detection to live response: under two hours.
## Tips for competitive responses
* **Set up monitoring before you need it.** You can't respond to what you don't see. Run the Intelligence setup wizard now and it will already be watching when something changes.
* **Don't panic-respond.** Use Solve to analyze before you build. A quick, informed response beats a faster knee-jerk one.
* **Focus on differentiation over matching.** Copying a competitor's move puts you in a race to the bottom. Use Solve to find where you can win differently.
* **Keep rollback as a safety net.** Launch fast but know you can roll back in one click if something isn't right.
## What's next?
Benchmark and redesign your entire website.
Set up continuous competitor monitoring.
Learn how to run strategic analysis.
Test and deploy with confidence.