Skip to main content
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. Think of it as a knowledge container for an initiative - whether that’s launching a product, redesigning a website, or exploring a market. The practical benefit: 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, no “as I mentioned last time.”
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’re just managed in a different place.

​
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 task, outputs, and history.

Context

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

Collaborators

Team members who can view, edit, or comment on 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

1

Create

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

Add tasks

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

Collaborate

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

Iterate

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

Create, rename, archive, 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, no re-referencing in each prompt. When you run a Solve task to research a market and then start a Build task in the same project, Rocket uses the research findings to inform the build. 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 don’t need to manually copy information between tasks - Rocket surfaces relevant context when it’s useful.

​
Frequently asked questions

Yes. There’s no limit on the number of projects you can create. Most teams organize by initiative - one project per product, campaign, or research task.
No. Intelligence is a workspace-level dashboard entirely separate from projects. You run the Intelligence setup wizard once for your workspace, and the Intelligence panel in your sidebar manages all monitoring from that point.Insights from Intelligence can still inform what you choose to Solve or Build within a project.
Yes. You can add any standalone Solve or Build task to a project from the task’s … menu. A task can only be part of one project at a time.
Archived projects become read-only. All tasks, files, and history are preserved, but you can’t create new tasks or make edits. You can unarchive a project at any time to resume work.
There’s no hard limit on the number of tasks in a project. However, each task consumes credits based on your plan, so your total active work is governed by your subscription. See Credits for details.

​
What’s next?

Context

Learn how files, connected services, and task outputs create shared context.

Tasks

Understand how Solve, Build, and Intelligence tasks work.