Getting StartedSolveBuildIntelligenceLearnHelpWhat's New
PROJECT

Overview

A Rocket.new project groups related tasks together and shares files, integrations, and collaborators so every task starts with the same context.

A project is a space in Rocket where all related work lives together. Every Solve task and Build task you create inside a project automatically shares the same files, connected services, and team members. It acts as a knowledge container for an initiative, whether that is launching a product, redesigning a website, or exploring a market.

The practical benefit is that you front-load your context once. Upload your company overview, financial model, or strategy deck when you create the project, and every task inside it has that foundation from the start. No re-uploading, no re-explaining.

Intelligence is separate from projects. Monitoring and the Intelligence dashboard live outside of projects entirely. They operate at the platform level, not scoped to any single project. You can still use Intelligence insights to inform what you Solve or Build. They are managed from the Intelligence panel.

What's inside a project

Tasks

Solve and Build tasks that represent the actual work. A project can hold any number of tasks, and each task has its own chat history, outputs, and conversation.

Context

Files from your device, connected documents, and Notion pages that inform your tasks. See Context.

Collaborators

Team members who can view or edit the project and its tasks.

Solve & Build

Two task types available inside a project. Solve for strategic research, Build for app creation.

When to use a project

ScenarioUse a projectUse a standalone task
Building a product with research and an appYes, group the Solve and Build tasks together
Quick one-off question about a marketYes, create a Solve task directly
Team working on a website redesignYes, shared context and collaboration
Testing a single app idea soloEither works; a project adds organizationEither works; standalone is faster to start
Ongoing monitoring of a competitorNo project needed. Intelligence is managed at the workspace level

You can always add a standalone task to a project later. There's no penalty for starting simple.

The project lifecycle

Start a new project from the home screen. Give it a name that describes the initiative.

Create Solve and Build tasks inside the project. Each task gets its own conversation, but they all share the project's files and connected services.

Invite team members to the project. Everyone works in the same shared space with access to all tasks, files, and context.

Keep adding tasks, uploading files, and refining outputs. Context flows between tasks within the project, so later work benefits from earlier research.

Create, rename, star, and delete projects. Step-by-step instructions.

How context flows

Grouping tasks in a project means shared context. Files uploaded to the project are available to every task automatically. No re-uploading or re-referencing required.

When you run a Solve task to research a market and then start a Build task in the same project, Rocket can use the research findings to inform the build if you use cross-task context. Connected services provide live data across the board.

This works in both directions. A Build task's outputs can prompt new Solve questions, and Solve findings can shape what you build next.

Context flow is automatic within a project. You do not need to manually copy information between tasks. Rocket surfaces relevant context when it is useful.

Frequently asked questions

What's next?

On this page