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

# Research to launch

> Complete Rocket.new workflow: Solve, Build, and Launch.

export const LlmsDirective = () => <blockquote className="llms-directive">
    For the complete documentation index, see <a href="/llms.txt">llms.txt</a>.
    For a lightweight markdown version of this page, append .md to the URL.
  </blockquote>;

<LlmsDirective />

This workflow chains Rocket's core capabilities into a single end-to-end process: research your market with Solve, build the product with Build, and deploy via Launch. It's the most common path for launching something new - from a SaaS product to a landing page to a mobile app.

## When to use this workflow

* You're starting a new product and want to make informed decisions before building
* You need market validation, competitive context, or strategic direction before committing
* You want a structured process from idea to live product

## The workflow

<Steps>
  <Step title="Phase 1: Research with Solve">
    Start with a **Solve task** to understand the landscape before you build anything.

    **Example scenario:** You want to launch a project management tool for freelancers.

    ```plaintext wrap theme={null}
    What is the market for project management tools targeted at freelancers and solo consultants? Who are the top 5 competitors? What do freelancers complain about most with existing tools? What features would a simple, freelancer-focused tool need to compete? What pricing model works best for this audience?
    ```

    Review the report. It might reveal that freelancers care most about simplicity, invoicing integration, and affordability - insights that shape what you build.

    **Follow-up prompt:**

    ```plaintext wrap theme={null}
    Based on this analysis, what should a v1 MVP include? Prioritize features by impact and feasibility. What can wait for v2?
    ```

    Solve gives you a prioritized feature list and strategic direction - before you write a single line of code.
  </Step>

  <Step title="Phase 2: Build based on findings">
    Create a **Build task** and translate your Solve findings into a product. Reference what you learned to write a focused prompt.

    ```plaintext wrap theme={null}
    Build a project management app for freelancers. Based on my research, the v1 should include: a simple task board with drag-and-drop columns (To Do, In Progress, Done), a client management section with contact info and project history, a time tracker that associates hours with projects and clients, a basic invoice generator that pulls from tracked hours, and a dashboard showing active projects, upcoming deadlines, and hours this week. Use a clean, minimal design - freelancers want simplicity, not enterprise complexity. Include authentication and a settings page.
    ```

    Rocket generates the full app. Preview it, test the flows, and iterate:

    ```plaintext wrap theme={null}
    Add a calendar view that shows project deadlines and scheduled tasks. Make it toggleable between the board view and calendar view.
    ```

    ```plaintext wrap theme={null}
    The invoice generator should allow the user to add their logo and business details, and export invoices as PDF.
    ```

    Keep refining until the app matches your vision.
  </Step>

  <Step title="Phase 3: Launch">
    When your app is ready, click **Launch** in the top-right corner to deploy.

    1. **Test in staging** - walk through every user flow in the [staging environment](/build/launch-web/launch-your-site)
    2. **Run the pre-launch checklist** - content, functionality, design, SEO, and security
    3. **Click Launch** - your app goes live instantly with a shareable URL
    4. **Connect a custom domain** - set up your own domain for a professional presence
    5. **Optimize** - run [SEO](/build/polish/seo) and [performance](/build/measure/performance) reports, then ask Rocket to implement improvements

    Your product is live. Track how users interact with it using [analytics](/build/measure/analytics) and iterate based on real feedback.
  </Step>
</Steps>

## Example: launching a SaaS product

| Phase    | Capability | Action                                        | Output                                    |
| -------- | ---------- | --------------------------------------------- | ----------------------------------------- |
| Research | Solve      | Market sizing and competitive analysis        | Structured report with feature priorities |
| Build    | Build      | Create the app based on research findings     | Working full-stack SaaS product           |
| Iterate  | Build      | Refine UI, add features, connect integrations | Polished, production-ready app            |
| Deploy   | Launch     | Test in staging, launch, connect domain       | Live product accessible to users          |
| Optimize | Build      | SEO, performance, analytics                   | Optimized, discoverable product           |

## Tips for this workflow

* **Let Solve inform your Build prompt.** The more specific your research, the better your Build output. Copy key findings directly into your Build prompt.
* **Don't over-research.** A single Solve task with a follow-up is usually enough. Move to Build quickly and let real app interaction reveal what's missing.
* **Use staging for stakeholder feedback.** Share the staging URL with co-founders, advisors, or early users before publishing to production.
* **Launch early, iterate often.** A live app with one core feature beats a perfect app that never ships.

## What's next?

<CardGroup cols={2}>
  <Card title="Competitive response" icon="bullseye-arrow" href="/learn/workflows/competitive-response">
    React to competitor moves with Intelligence → Solve → Build.
  </Card>

  <Card title="Your first task" icon="play" href="/learn/tutorials/your-first-task">
    Hands-on tutorial walking through the full workflow.
  </Card>

  <Card title="Solve overview" icon="magnifying-glass" href="/solve/overview">
    Learn how Solve research tasks work.
  </Card>

  <Card title="Build overview" icon="hammer" href="/build/overview">
    Explore everything Build can create.
  </Card>
</CardGroup>