---
title: "Projects for HubSpot implementation · Jetstack AI"
description: "Turn a client brief into a reviewable plan and connected HubSpot assets. Approve generation and deployment separately, then check the receipt."
url: "https://jetstack.ai/build/"
---

Projects

# From a client brief to *reviewed assets.*

Turn a client brief into a reviewable plan and connected HubSpot assets. Approve generation, approve deployment separately, then check a receipt of what actually happened.

[Book a live build](https://jetstack.ai/contact) [Read the Projects quickstart](https://jetstack.ai/docs/projects/quickstart)

Projects / Northline

01 A portal-scoped brief

## A considered *starting point.*

Set up an enquiry handoff for the advisory team.

- Capture the service region.
- Track the enquiry pipeline.
- Route the follow-up.

One Project → one portal

02 Reviewable plan

- Property Service region
- Pipeline Advisory enquiries
- Workflow Regional handoff

03 Dependencies, made explicit

A → B means B uses A

Property Service region

Pipeline Advisory enquiries

Workflow Regional handoff

The workflow needs both references. They are not independent tasks.

04 Generation approval

### Approve the plan.

Generate the reviewed scope.\
No deployment yet.

Human decision

05 Deployment approval

### Approve what goes live.

Review readiness and target.\
A separate decision.

Human decision

06 Durable run + receipt

### Check the result, not just the request.

Per-asset outcomes

- Property Service region

  Authored fields verified

- Workflow Regional handoff

  Review remaining setup

Run\
receipt

One portal per Project Separate build + deploy approvals Read-back verification

A brief, not a bag of prompts

## Build the pieces as a connected system.

Bring field lists, pipeline stages, workflow descriptions and client documents. Keep the business intent alongside the assets.

01

### Shape the CRM

Properties · pipelines · association labels

Define the fields and process structure around the client’s actual requirements.

02

### Connect the work

Workflows · segments · forms

Build related assets with their references and dependencies in view.

03

### Review the delivery

Plans · deployment scope · receipts

See what is proposed, what is ready and what happened to each asset.

Support depends on the asset type, your HubSpot subscription and the available API or extension lane. Some assets need manual setup after deployment.

[Check supported capabilities →](https://jetstack.ai/docs/projects/capabilities) [Working with client knowledge →](https://jetstack.ai/docs/projects/knowledge)

Human gates

## Two different decisions. Keep both.

Generating an asset and changing a client’s portal are not the same action.

01 / Generation

### Approve the scope before generation.

Review the proposed scope. Approve the plan to start generation, which creates asset specifications inside the Project.

Result: generated assets to review.\
**Not live in the portal.**

02 / Deployment

### Approve the assets for this portal.

Review what is ready, what is excluded and why. Approve the deployment scope separately; complete any required browser handoff.

Result: a run and per-asset outcomes.\
**Check verification and remaining setup.**

[Plans and cards →](https://jetstack.ai/docs/projects/chats) [Deployment, verification and fixes →](https://jetstack.ai/docs/projects/deployment)

Delivery, with a record

## The work doesn’t end *at “request sent”.*

Projects tracks generation and deployment as durable runs. Dependencies inform the order; assets that are not ready can wait with a reason rather than being treated as finished.

After deployment, read-back verification compares supported authored fields with HubSpot. Use the receipt to distinguish live assets from failures, browser work and setup that still needs your attention.

Verification is scoped to the authored fields the asset’s verifier supports. It does not replace testing the client’s full business process.

[Read the delivery guide →](https://jetstack.ai/docs/projects/deployment) [When a run needs attention →](https://jetstack.ai/docs/projects/troubleshooting)

The Jetstack advantage

## Why Projects beats assembling a delivery toolchain.

Whether the alternative is an AI chat or building by hand, Jetstack puts the whole HubSpot delivery lifecycle in the product: plan, generate, approve, deploy and verify.

- ### [Jetstack vs Claude](https://jetstack.ai/compare/hubspot-mcp-claude)
  [Claude can talk to HubSpot. Jetstack delivers the build: plan, approvals, dependency-aware deployment and a receipt.](https://jetstack.ai/compare/hubspot-mcp-claude)
- ### [Jetstack vs ChatGPT](https://jetstack.ai/compare/chatgpt)
  [Stop turning conversations into a delivery process. Put the build in Projects.](https://jetstack.ai/compare/chatgpt)
- ### [Jetstack vs HubSpot Breeze](https://jetstack.ai/compare/hubspot-breeze)
  [Breeze drafts a workflow from a prompt. Jetstack Projects plans and ships the whole HubSpot build, with approvals and a receipt.](https://jetstack.ai/compare/hubspot-breeze)
- ### [Jetstack vs Manual implementation](https://jetstack.ai/compare/manual-implementation)
  [Spend your expertise on the solution, not on clicking through every asset by hand.](https://jetstack.ai/compare/manual-implementation)

[All projects comparisons →](https://jetstack.ai/compare#projects)

Questions, answered

## Before you build.

What is a Project scoped to?

A Project is bound to one HubSpot portal. Its brief, knowledge, chats and assets stay in that context. Reusing assets in another portal is a separate destination-specific workflow.

Are generation and deployment separate approvals?

Yes. For a new build, approving the plan starts generation. Review the resulting assets and approve the deployment scope separately before those assets go live. A proposal alone does not start a run.

What does a receipt verify?

The run records per-asset outcomes. After deployment, read-back verification compares supported authored fields with the destination state. A receipt can still show failures, waiting assets or setup to finish; it is not a blanket guarantee that the whole implementation is complete.

What if an asset needs the Chrome extension?

Some HubSpot areas need a browser connection rather than the public API. That work appears in the extension’s Projects Inbox. Review the task and start it in the correct connected portal.

How is this different from connecting Claude or ChatGPT to HubSpot?

Those tools can connect to and act in HubSpot. Projects adds an implementation workflow around the work: a portal-scoped brief, reviewable plans, dependency-aware generation and deployment, explicit approvals, durable runs and read-back receipts.

Can I start using Projects immediately?

Projects access is organisation-specific and currently limited release. The quickstart explains the prerequisites. Book a walkthrough to discuss access and whether your intended asset types and HubSpot setup are supported.

Elsewhere in the platform
