Skip to main content
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 with Ship. 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

1

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.
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:
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.
2

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.
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:
Add a calendar view that shows project deadlines and scheduled tasks. Make it toggleable between the board view and calendar view.

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

Phase 3: Ship the result

When your app is ready, deploy it through Ship.
  1. Test in staging - walk through every user flow in the staging environment
  2. Run the pre-launch checklist - content, functionality, design, SEO, and security
  3. Publish to production - click Publish to go live
  4. Connect a custom domain - set up your own domain for a professional presence
  5. Optimize - run SEO and performance reports, then ask Rocket to implement improvements
Your product is live. Track how users interact with it using analytics and iterate based on real feedback.

​
Example: launching a SaaS product

PhaseCapabilityActionOutput
ResearchSolveMarket sizing and competitive analysisStructured report with feature priorities
BuildBuildCreate the app based on research findingsWorking full-stack SaaS product
IterateBuildRefine UI, add features, connect integrationsPolished, production-ready app
DeployShipTest in staging, publish, connect domainLive product accessible to users
OptimizeShipSEO, performance, analyticsOptimized, 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.
  • Ship early, iterate often. A launched app with one core feature beats a perfect app that never ships.

​
What’s next?

Competitive response

React to competitor moves with Intelligence → Solve → Build.

Your first task

Hands-on tutorial walking through the full workflow.

Solve overview

Learn how Solve research tasks work.

Build overview

Explore everything Build can create.