> ## 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.
# Market entry
> Enter a new market with Rocket.new: Intelligence, Solve, Build, and Launch.
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 guides you through entering a new market - from monitoring the landscape to deep research, building a market-specific product, and launching it. It chains all four Rocket capabilities into a structured expansion strategy.
## When to use this workflow
* You're expanding into a new geographic market or customer segment
* You're exploring an adjacent market for your existing product
* You want to validate market fit before committing full resources
* You need to understand local competitors, regulations, and customer expectations
## The workflow
Before committing to a new market, run the **Intelligence setup** wizard to set up ongoing monitoring of the landscape. Intelligence is a one-time workspace setup - run it once and it monitors continuously from that point.
**In the wizard, add competitors in the target market:**
Add the top three to five companies in your target category. Provide each company's name and website URL. Select channels that cover the signals that matter most: website for product and pricing moves, news for funding and partnerships, social for messaging shifts.
**Also track regulatory and industry changes:**
Intelligence monitors news and web sources automatically. In the "Your context" step, mention that you're evaluating a market entry so Intelligence can surface relevant regulatory or industry developments.
Let the signals accumulate for a few weeks. This builds your understanding of market dynamics, key players, and timing.
Once you have enough signals to form a hypothesis, use **Solve tasks** for deep analysis.
**Market sizing and opportunity:**
```plaintext wrap theme={null}
What is the market opportunity for [your product category] in [target market]? Include: total addressable market, current penetration rate, growth projections, key customer segments, and the competitive landscape. What are the top barriers to entry? What local factors (cultural, regulatory, infrastructure) should a new entrant understand?
```
**Go-to-market strategy:**
```plaintext wrap theme={null}
Recommend a go-to-market strategy for launching [your product] in [target market]. Consider: pricing strategy (should we match local competitors or price differently?), distribution channels, partnership opportunities, localization requirements (language, payment methods, design preferences), and the first 90 days of launch activities. What did successful entrants in similar categories do?
```
**Follow-up:**
```plaintext wrap theme={null}
Based on this analysis, what should the MVP look like for [target market]? What features are essential vs. what can wait? Should the product differ from our existing version?
```
These reports give you a data-driven entry plan. Share them with your team in a project workspace for alignment.
Create a **Build task** that incorporates your market research findings.
**Build a localized version:**
```plaintext wrap theme={null}
Build a version of [your product] tailored for [target market]. Key adaptations based on my research: [list localization needs - e.g., support for local currency, local payment methods, right-to-left text, specific compliance features]. Include a landing page that speaks to [target audience's specific pain points and language]. Keep the core feature set from our existing product but adjust the onboarding flow to match local expectations.
```
**Build a market-specific landing page:**
```plaintext wrap theme={null}
Build a landing page targeting [audience] in [market]. Address their specific pain points: [list from Solve research]. Include testimonials or case studies from similar customers (use placeholders). Price in [local currency]. Support [local language] if applicable. The design should feel familiar to [market] audiences - reference [competitor examples from Solve] for visual conventions.
```
Iterate until the product feels native to the target market, not like a copy of your main product.
Deploy your market-specific product and start learning from real users.
1. Test in [staging](/build/launch-web/launch-your-site) with local team members or early adopters
2. Click **Launch** to go live
3. Connect a market-appropriate [custom domain](/build/launch-web/custom-domain) (e.g., yourproduct.co.uk, yourproduct.jp)
4. Run [SEO optimization](/build/polish/seo) targeting market-specific keywords
5. Set up [analytics](/build/measure/analytics) to track market-specific metrics
**Continue monitoring with Intelligence:**
Intelligence is already running from your initial wizard setup. Add channels for user feedback sources - forums, social media, review sites - by managing your competitor list in the Intelligence dashboard. This surfaces how users in the new market respond to your product versus local competitors.
Use ongoing signals and analytics to drive rapid iteration. The first version rarely gets everything right - iterate weekly based on what you learn.
## Example: expanding a SaaS product into the European market
| Phase | Capability | Action | Timeline |
| -------- | -------------------- | ----------------------------------------------------------- | --------- |
| Monitor | Intelligence | Watch top 5 EU competitors and GDPR developments | Weeks 1–3 |
| Research | Solve | Market sizing, localization needs, GTM strategy | Week 4 |
| Build | Build | Localized app with EUR pricing, GDPR compliance, EU hosting | Weeks 5–6 |
| Launch | Build | Deploy with .eu domain, EU-focused SEO | Week 7 |
| Iterate | Intelligence + Build | Monitor user feedback, iterate on product weekly | Ongoing |
## Tips for market entry
* **Monitor before you commit.** A few weeks of Intelligence signals tell you more than assumptions. You might discover the market is smaller than expected - or bigger.
* **Localization isn't just translation.** Payment methods, design conventions, trust signals, and regulatory requirements all vary by market. Use Solve to surface these differences.
* **Launch an MVP, not a port.** Don't try to replicate your entire product for a new market. Launch with the features that matter most to local users and expand from there.
* **Keep monitoring after launch.** Your competitors will respond. Intelligence keeps you informed so you can adapt quickly.
## What's next?
Simpler workflow for launching a new product.
React to competitor moves in your new market.
Set up continuous market monitoring.
Deep-dive market research and analysis.