Skip to content
JetStack AI Documentation

Projects Quickstart

This guide walks you through your first project from a blank workspace to a deployed HubSpot implementation. The full path takes about 15–30 minutes of active work, plus roughly 15–25 minutes of asynchronous AI generation in between approval and review.

Before You Start

Section titled “Before You Start”

You need:

  • An organisation with Projects access enabled
  • At least one connected HubSpot portal to deploy into — see Connecting a Portal if you have not done this
  • (Optional) Process documentation, call transcripts, or a revenue model to upload during context gathering — Projects works without them, but the blueprint is sharper when you provide context

If you intend to deploy assets that require the Chrome extension (dashboards, reports, snippets, etc.), you will also need the JetStack AI extension installed and signed in to the same HubSpot portal you plan to deploy to.

Step 1 — Create the Project

Section titled “Step 1 — Create the Project”
  1. Open the dashboard and click Projects in the left sidebar.
  2. Click New Project in the top-right.
  3. Give the project a name (e.g., “Acme Corp — Sales Onboarding”) and a brief one-line description.
  4. Pick the destination portal the project will eventually deploy to. You can change this later, but selecting it up front lets Jetty tailor proposals to the portal’s existing configuration.
  5. Click Create.

The project workspace opens with an empty conversation panel on the right and four tabs (Overview, Blueprint, Assets, Deployment) in the main content area. You are now in Phase 1 — Context Gathering.

Step 2 — Context Gathering

Section titled “Step 2 — Context Gathering”

This is where you tell Jetty what you are building.

There are two ways to provide context, and you can mix them freely:

  • Talk in chat. Type or paste a description of the business model, the team’s current process, the outcomes you want to measure, or anything else that informs the implementation. Jetty will ask follow-up questions when something is unclear.
  • Upload documents. Drag PDFs, DOCX, TXT, CSV, JSON, or Markdown files into the chat. Jetty extracts the text, summarises it, and incorporates it into the project context. Common uploads: discovery call transcripts, process documents, sales playbooks, revenue models, existing CRM exports.

When Jetty has enough context to design a blueprint, it will say so explicitly and offer to move on. You can also ask it to advance whenever you feel ready — there is no minimum number of turns.

Step 3 — Approve the Blueprint

Section titled “Step 3 — Approve the Blueprint”

Once context gathering completes, Jetty produces a blueprint — a structured visualisation of the implementation it intends to build.

The blueprint includes:

  • Object families — the CRM objects you will use (Contacts, Companies, Deals, custom objects), grouped by purpose
  • Properties — the custom and standard fields each object needs
  • Lifecycle stages — the stages contacts move through, and what triggers each transition
  • Automations — workflows, lists, and sequences proposed for each business goal
  • Outcomes — the measurable results the implementation is designed to produce, with a traceable link from each outcome to the assets that support it

Review every section. You can:

  • Edit inline — click any item to refine the name, description, or definition
  • Ask Jetty in chat — “rename Deal Source to Origin” or “add a Service-Hub ticket pipeline for renewals”
  • Approve as-is — click Approve Blueprint in the Blueprint tab toolbar to advance

Approval is required before asset generation runs. The blueprint is your last chance to shape the shape of the implementation before specific assets get generated — once generation completes, smaller edits are easier than structural changes.

Step 4 — Generate Assets

Section titled “Step 4 — Generate Assets”

After you approve the blueprint, Jetty starts producing concrete HubSpot assets. The progress strip at the top of the Assets tab shows what’s in flight; assets appear in the list as they finish, grouped by type.

Generation is asynchronous and typically takes 15–25 minutes for a typical project; small projects can finish in 8–10 minutes, large ones with many workflows and reports can stretch to 30–40 minutes. You can:

  • Watch generation progress live — every asset shows a status indicator (drafting / ready / error)
  • Open finished assets as they appear — the detail panel renders each spec in the visual format that matches its type (a pipeline as stages, a workflow as enrollment + branches, a report as a chart config, etc.)
  • Leave the workspace and come back — generation continues in the background and the UI catches up to current state when you return

If individual assets fail, they are flagged with an error icon and a brief reason. You can re-trigger generation for just the failed items from the asset detail panel — see Asset Generation for the full failure-recovery workflow.

Step 5 — Review and Edit Assets

Section titled “Step 5 — Review and Edit Assets”

Click any asset in the list to open its detail panel. The panel renders the spec visually:

  • Properties show their field type, group, and options
  • Pipelines show their stages, probabilities, and required properties
  • Workflows show enrollment criteria and action sequences
  • Lists show their filter logic
  • Forms show their field layout
  • Dashboards & reports show their layout and chart configuration

You have three ways to change what you see:

  • Inline edits — small adjustments (renames, threshold tweaks, adding a stage) can be made directly in the detail panel
  • Chat instructions — for bigger changes, ask Jetty: “split the Lead Stage into MQL and SQL stages, and update the pipeline to match”
  • Regenerate from the blueprint — if a structural blueprint change is needed, edit the blueprint and re-trigger generation; the affected assets are recreated and any unchanged ones stay as they are

When the asset list looks right, click Proceed to Deploy in the Assets tab header.

Step 6 — Deploy

Section titled “Step 6 — Deploy”

The Deployment tab shows the deploy plan: which assets go via the public HubSpot API and which go via the Chrome extension, in dependency order.

  1. Confirm the destination portal at the top of the Deployment tab — if you change it now, the plan is re-validated against the new portal’s existing assets.
  2. Review the API-deployable group. These run directly from the server using your portal’s OAuth token: properties, pipelines, workflows, lists, forms, marketing emails, association labels, custom objects.
  3. Review the Extension-deployable group. These require an authenticated HubSpot browser session and are pushed via the Chrome extension: dashboards, reports, snippets, playbooks, goal templates, lead scores, CRM cards, preview views.
  4. Click Start Deployment. The API group runs first. As assets are created, any references between them are wired up automatically.
  5. When the API group completes, the extension prompts you to launch the extension group. Open the extension on the target portal — the deploy plan appears automatically and one click runs the remaining assets.

Deployment is durable — if the connection drops or you close the browser, the deploy resumes when you reopen the project. Failed assets are surfaced with their HubSpot error message so you can decide whether to retry, edit, or skip them.

What Happens to the Source Portal?

Section titled “What Happens to the Source Portal?”

Projects never reads from a source portal — there is no source. Your project is built from the conversation, your uploads, and the AI’s knowledge of HubSpot conventions. The only portal touched is your destination, and only during deployment.

This is the key difference from Implementations: Implementations is a portal-to-portal pipeline, while Projects is a conversation-to-portal pipeline.

Next Steps

Section titled “Next Steps”