Approve the scope
before generation.
Review the proposed scope. Approve the plan to start generation, which creates asset specifications inside the Project.
Not live in the portal.
Projects
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.
01 A portal-scoped brief
Set up an enquiry handoff for the advisory team.
One Project → one portal
02 Reviewable plan
03 Dependencies, made explicit
A → B means B uses AThe workflow needs both references. They are not independent tasks.
04 Generation approval
Generate the reviewed scope.
No deployment yet.
05 Deployment approval
Review readiness and target.
A separate decision.
06 Durable run + receipt
Per-asset outcomes
Start with the client’s process and a specific portal. The brief describes what needs to change, not just which assets to create.
Start with the client’s process and a specific portal. The brief describes what needs to change, not just which assets to create.
Review the proposed assets and scope. A plan is a proposal for your review, not a background write to HubSpot.
The workflow references a property and pipeline. Their dependencies inform generation and deployment order.
Approve the plan to start generation. Generated asset specifications are not yet deployed to the portal.
Review the deployment scope and approve it separately. Readiness checks can hold assets that need more work or browser steps.
A durable run records the outcome. Read-back verification compares supported authored fields with what is in HubSpot; failures and remaining setup still need attention.
A brief, not a bag of prompts
Bring field lists, pipeline stages, workflow descriptions and client documents. Keep the business intent alongside the assets.
Properties · pipelines · association labels
Define the fields and process structure around the client’s actual requirements.
Workflows · segments · forms
Build related assets with their references and dependencies in view.
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.
Human gates
Generating an asset and changing a client’s portal are not the same action.
Review the proposed scope. Approve the plan to start generation, which creates asset specifications inside the Project.
Review what is ready, what is excluded and why. Approve the deployment scope separately; complete any required browser handoff.
Delivery, with a record
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.
The Jetstack advantage
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.
Claude can talk to HubSpot. Jetstack delivers the build: plan, approvals, dependency-aware deployment and a receipt.
Stop turning conversations into a delivery process. Put the build in Projects.
Breeze drafts a workflow from a prompt. Jetstack Projects plans and ships the whole HubSpot build, with approvals and a receipt.
Spend your expertise on the solution, not on clicking through every asset by hand.
Questions, answered
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.
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.
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.
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.
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.
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
See the workflow
Walk through a plan, its dependencies, the approval gates and the receipt. We’ll discuss access and the fit for your portal.
Book a live build