Skip to main content
This workflow uses Projects to coordinate team-based product development. Multiple team members contribute research, builds, and feedback in a shared workspace - from initial Solve research through Build iterations to Ship deployment.

​
When to use this workflow

  • You’re working with a team (co-founders, designers, developers, stakeholders)
  • The project involves multiple phases that different people own
  • You need a shared workspace where research, builds, and decisions live together
  • Stakeholder feedback and approval is part of your process

​
The workflow

1

Set up a project

Create a new Project in Rocket to serve as the shared workspace. A project holds all related tasks - Solve reports, Build outputs, Intelligence monitors, and conversations - in one place.Name the project descriptively (e.g., “Q3 Customer Portal” or “Website Redesign 2025”). Invite team members who need access.
Everyone in the project can see all tasks, results, and conversations. Use this as your single source of truth for the initiative.
2

Phase 1: Research with Solve

One or more team members kick off Solve tasks to build the strategic foundation.Product lead runs competitive research:
Compare the top 5 customer portal solutions for B2B SaaS companies. What features do they offer? How do they handle billing management, support tickets, and usage analytics? What are the key gaps in the market?
Designer runs design research:
What are the best-designed customer portals and dashboards in B2B SaaS? Show me 5-10 examples with analysis of what makes their UX effective. What design patterns are emerging for customer self-service interfaces?
All reports land in the shared project. Team members can read each other’s findings and align on direction before building.
3

Phase 2: Build collaboratively

The team creates Build tasks within the project. Different team members can own different parts:Developer builds the core app:
Build a customer portal with: a dashboard showing subscription status, usage metrics, and billing history. A support ticket system where customers can create, track, and respond to tickets. An account settings page with team management and billing preferences. Use Supabase for auth and database. Based on our research, prioritize simplicity and clarity over feature density.
Designer iterates on the visual design:
Refine the design of the customer portal. Apply a professional, enterprise-friendly aesthetic: use [brand colors], clean typography, generous spacing. Add subtle animations to the dashboard metrics (count-up on load). Make the ticket status badges more visually distinct. Ensure the mobile experience is fully usable, not just responsive.
Team members can review each other’s work through the staging URL and leave feedback in the project conversation.
4

Phase 3: Review and iterate

Share the staging URL with the broader team and stakeholders for feedback.
  • Product manager reviews feature completeness
  • Designer checks visual consistency
  • Developer tests edge cases and integrations
  • Stakeholders provide business feedback
Collect feedback and iterate. Each team member can make changes within the Build task by chatting with Rocket.
Based on feedback: add a "Quick Actions" section to the dashboard with shortcuts for common tasks (view invoice, create ticket, upgrade plan). Move the usage chart to be the first thing users see. Add a "Last login" timestamp to the account page.
5

Phase 4: Ship together

When the team agrees the product is ready:
  1. Run through the pre-launch checklist as a team
  2. Product lead publishes to production
  3. Set up analytics to track engagement
  4. Run SEO and performance optimization
  5. Share the live URL with the team and celebrate
Post-launch, use the same project for ongoing iteration. New Solve tasks can research expansion opportunities, and new Build iterations can add features based on user feedback.

​
Example: building a client dashboard

A three-person team (founder, designer, marketer) builds a client-facing dashboard for their consulting business.
PhaseTeam memberTask typeAction
ResearchFounderSolveCompetitive analysis of client dashboards
ResearchMarketerSolveWhat do consulting clients value most in a portal?
BuildFounderBuildCore dashboard with project tracking and invoicing
DesignDesignerBuild (iterate)Visual polish, brand alignment, micro-interactions
ContentMarketerBuild (iterate)Onboarding copy, help text, email templates
ReviewAll-Stakeholder review via staging URL
ShipFounderShipPublish, connect domain, set up analytics

​
Tips for team product development

  • Start every project with research. Even a single Solve task gives the team a shared foundation. It’s cheaper than building the wrong thing.
  • Let different people own different tasks. The designer iterates on visuals while the developer builds integrations. Parallel work in the same project.
  • Use the staging URL for reviews. It’s the fastest way to get feedback from people who aren’t in Rocket.
  • Keep conversations in the project. Don’t discuss decisions in Slack and build in Rocket. The project should be the source of truth.
  • Ship incrementally. Launch a v1 fast, then iterate based on real user feedback.

​
What’s next?

Market entry

Expand into a new market with Intelligence → Solve → Build → Ship.

Research to launch

Streamlined solo workflow from research to deployment.

Projects overview

Learn how projects organize tasks and collaboration.

Launch your site

Manage environments and version history.