Getting StartedSolveBuildIntelligenceLearnHelpWhat's New
TASK

Launchpad

Connect Notion, Linear, Supabase, Google, Airtable, Mixpanel, or Directus so Rocket uses them as the foundation for better builds and smarter research.

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. The Airtable base. The Mixpanel project. The Directus collection. Rocket reads it, extracts intent, and launches from that foundation.


Supported sources

This is the initial supported set. More connectors will be added in future releases.


How it works

You can reference a source in two ways:

  • Paste a URL to a Notion page, Linear issue, Supabase project, Google Doc, Google Sheet, Airtable base, Mixpanel project, or Directus instance. Rocket detects the reference automatically.
  • Type @ at the start of your prompt, select Connectors, then choose from the available connectors:
    • First message: Notion, Google, Linear, Airtable, Supabase, Mixpanel, or Directus
    • Follow-up messages: Notion, Google, or Linear

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 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 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


Solve examples


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.

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, Supabase can be your launchpad (Rocket reads the existing schema) and an app connector (the generated app uses Supabase for auth and database) 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 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?

On this page