Skip to content
Book a 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.

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

  • PropertyService region
  • PipelineAdvisory enquiries
  • WorkflowRegional handoff

03 Dependencies, made explicit

A → B means B uses A
PropertyService region
PipelineAdvisory enquiries
WorkflowRegional 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

PropertyService region
Authored fields verified
WorkflowRegional handoff
Review remaining setup
Run
receipt

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.

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.

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.

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.

All projects comparisons →

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.

See the workflow

Bring a real implementation brief.

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