Skip to main content

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.

Launchpad lets you point Rocket at your existing docs, tickets, or data so it builds apps and produces research grounded in real material instead of a blank prompt. Every rocket needs a launchpad to launch properly. Without one, it launches from thin air. No structure, no direction. With a launchpad, there is solid ground. The launch is more powerful, more precise, more directed. Your existing work is the launchpad. The Notion doc. The Linear ticket. The Google Sheet. Rocket reads it, extracts intent, and launches from that foundation.

​
Supported sources

Notion

PRDs, product notes, specs, feature lists, strategy docs, meeting notes.

Linear

Issues, projects, epics, feature requests, acceptance criteria, status history.

Google Docs

Requirements documents, briefs, RFCs, design docs, long-form notes.

Google Sheets

Structured data, metrics trackers, competitive dossiers, planning sheets.
This is the initial supported set. More connectors will be added in future releases.

​
How it works

1

Reference a source in your prompt

Paste a URL to a Notion page, Linear issue, Google Doc, or Sheet. Rocket detects the reference automatically.
2

Connect (if needed)

If the connector is not yet linked to your workspace, Rocket prompts you to connect it. If already connected, Rocket reads the source immediately.
3

Rocket reads and understands

Rocket pulls context from the source. For Build tasks, it extracts features, workflows, data shape, and scope. For Solve tasks, it identifies entities, metrics, timelines, and relationships.
4

Launch

Build tasks produce apps grounded in your specs. Solve tasks produce research grounded in your data. Follow-up questions are sharper because Rocket already understands what you have.

​
Build vs Solve

Launchpad works in two flows. The source material is the same, but Rocket uses it differently depending on what you ask for.
FlowWhat Rocket does with your source
BuildReads the source to understand what app to create. Extracts features, screens, workflows, and data models, then generates a complete app that matches your source material.
SolveReads the source to ground research in real material. Cites exact records, references actual docs, pulls real numbers, and produces deliverables anchored in your data.

​
Build examples

Sources: Notion, Google SheetsRocket reads the event plan from Notion and the sponsorship tracker from Google Sheets. The generated app includes a conference schedule, speaker directory, and sponsorship pipeline.
Build an event management dashboard for TechConf 2026. Use my event plan at [NOTION_URL] and sponsorship tracker at [SHEETS_URL].
Sources: Notion, LinearRocket reads product requirements from a Notion PRD and issue history from Linear. The generated app includes submissions, voting, and admin moderation.
Build a customer feedback portal from this Notion PRD: [NOTION_URL]. Use feature requests from this Linear project: [LINEAR_URL].
Source: LinearRocket reads the full Linear project including issues, statuses, and acceptance criteria. The generated app shows completed work by epic, in-progress items with progress bars, and blockers.
Generate a sprint review page for stakeholders from this Linear project: [LINEAR_URL]. Show completed work by epic, in-progress items with progress bars, and blockers.
Sources: Google Docs, Google SheetsRocket reads the client brief from Google Docs and a billing log from Google Sheets. The generated app includes client filters, active projects, team assignments, and a monthly summary chart.
Build a client reporting dashboard from my client brief at [DOCS_URL] and billing data at [SHEETS_URL]. Show per-client status, active projects, and monthly billing summaries.

​
Solve examples

Source: Google SheetsRocket reads your usage metrics spreadsheet, identifies workspaces with declining activity, flags accounts that stopped using key features, and produces a prioritized risk report with retention recommendations.
Analyze at-risk workspaces from my usage tracker at [SHEETS_URL]. Flag accounts with declining usage over the last 90 days and recommend retention actions.
Source: LinearRocket traces each issue through its status history, identifies blockers, and produces a structured memo with what shipped, what slipped, and recommended next actions.
Summarize delivery progress for this Linear epic: [LINEAR_URL]. Include what shipped, what is blocked, and recommended next steps for the team.
Sources: Google Sheets, NotionRocket reads competitor feature matrices from Sheets and positioning notes from Notion, then produces a one-pager with win themes, objection handlers, and comparison tables.
Create a competitive battlecard using my competitor dossier at [SHEETS_URL] and positioning doc at [NOTION_URL]. Include win themes, objection handlers, and a feature comparison.
Sources: Google Docs, Google SheetsRocket reads account notes from Google Docs and billing data from Google Sheets, segments accounts by health score, and produces a rollup with per-account recommendations.
Produce an account health report from my account notes at [DOCS_URL] and billing tracker at [SHEETS_URL]. Segment by health score and flag at-risk accounts.

​
Solve deliverable formats

When Launchpad is used with a Solve task, Rocket can produce:
  • Memos and briefs - narrative write-ups that summarize findings and cite exact docs, issues, or rows.
  • PDFs and one-pagers - shareable summaries for leadership or partners, with claims tied to real source material.
  • Battlecards - competitive or account-level cards built from Sheets and Notion pages.
  • Playbooks and SOPs - step-by-step guides assembled from decision logs, process docs, and operational records.
  • Dashboards and rollups - structured views over Sheets that aggregate real metrics.
  • Research reports - longer analyses that cross-reference PRDs, issues, docs, and data to answer strategic questions.
Source context is what makes every deliverable defensible. Launchpad gives Rocket something real to cite.

​
Launchpad vs app connectors

Launchpad and app connectors serve different purposes. Both can appear in the same prompt.
IntentWhat it meansExample
LaunchpadRocket reads from a connector to understand context”Use this Notion PRD as the requirements.”
App connectorA connector becomes part of the generated app’s functionality”Add Stripe payments to the app.”
The same connector can play both roles. For example, Google Sheets can be your launchpad (Rocket reads the existing data) and an app connector (the generated app syncs with Sheets) in the same prompt.
Launchpad does not automatically embed the connector into the generated app. It uses the source to understand your intent. If you also want the connector as a live feature in the app, say so explicitly.

​
Tips for better results

  • Point to the most precise source you have. A structured PRD produces a better launch than a brainstorm with loose notes.
  • Be explicit about connector roles. If you want Google Sheets as your launchpad and as a live data source, say both: “Read my metrics from Sheets and use Sheets as the data source in the app.”
  • Mix Launchpad with app connectors. Reference a Notion PRD (launchpad) and ask for Stripe payments (app connector) in the same prompt.
  • For Solve, ask a specific question. The sharper your research question, the more precisely Rocket can use your source material.
  • Make sure the source is accessible. Connect the relevant connector to your workspace before starting, or Rocket will prompt you during the flow.

​
What’s next?

Build from an idea

Start a Build task from a plain-language description.

Solve quick start

Run your first research task with Solve.

Workspace connectors

Connect Notion, Linear, and Google to your workspace.

All Build connectors

Browse every connector available for Build tasks.