Launchpad lets you point Rocket at your existing docs, tickets, schemas, 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. The Supabase schema. Rocket reads it, extracts intent, and launches from that foundation.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.
Supported sources
Notion
PRDs, product notes, specs, feature lists, strategy docs, meeting notes.
Linear
Issues, projects, epics, feature requests, acceptance criteria, status history.
Supabase
Existing schema, tables, field structure, live data for analysis.
Google Docs
Requirements documents, briefs, RFCs, design docs, long-form notes.
Google Sheets
Structured data, metrics trackers, competitive dossiers, planning sheets.
Airtable
Bases, tables, records, CRM data, operational records.
This is the initial supported set. More connectors will be added in future releases.
How it works
Reference a source in your prompt
Paste a URL to a Notion page, Linear issue, Supabase project, Google Doc, Sheet, or Airtable base. Rocket detects the reference automatically.
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.
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.
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.| Flow | What Rocket does with your source |
|---|---|
| Build | Reads 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. |
| Solve | Reads 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
Event management dashboard
Event management dashboard
Sources: Notion, Airtable, Google SheetsRocket reads the event plan from Notion, the speaker database from Airtable, and the sponsorship tracker from Google Sheets. The generated app includes a conference schedule, speaker directory, and sponsorship pipeline.
Customer feedback portal
Customer feedback portal
Sources: Notion (launchpad), Supabase (launchpad + app connector)Rocket reads product requirements from a Notion PRD and the existing schema from Supabase. The generated app includes submissions, voting, admin moderation, and uses Supabase for live auth and storage.
Sprint review page
Sprint review page
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.
Client reporting dashboard
Client reporting dashboard
Sources: Airtable, Google SheetsRocket reads two Airtable tables (Clients and Projects) and a Google Sheets billing log. The generated app includes client filters, active projects, team assignments, and a monthly summary chart.
Solve examples
Churn risk analysis
Churn risk analysis
Source: SupabaseRocket reads your audit_events table, identifies workspaces with declining activity, flags accounts that stopped using key features, and produces a prioritized risk report with retention recommendations.
Sprint delivery summary
Sprint delivery summary
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.
Competitive battlecard
Competitive battlecard
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.
Account health rollup
Account health rollup
Sources: Airtable, Google SheetsRocket reads CRM records from Airtable and billing data from Google Sheets, segments accounts by health score, and produces a rollup with per-account recommendations.
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, Notion pages, and Airtable records.
- Playbooks and SOPs - step-by-step guides assembled from decision logs, process docs, and operational records.
- Dashboards and rollups - structured views over Supabase, Sheets, or Airtable that aggregate real metrics.
- Research reports - longer analyses that cross-reference PRDs, issues, docs, and data to answer strategic questions.
Launchpad vs app connectors
Launchpad and app connectors serve different purposes. Both can appear in the same prompt.| Intent | What it means | Example |
|---|---|---|
| Launchpad | Rocket reads from a connector to understand context | ”Use this Notion PRD as the requirements.” |
| App connector | A connector becomes part of the generated app’s functionality | ”Add Stripe payments to the app.” |
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 Supabase as your launchpad and as a live backend, say both: “Read my existing schema from Supabase and use Supabase for auth and storage 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, Supabase, Google, and Airtable to your workspace.
All Build connectors
Browse every connector available for Build tasks.

