Jetstack AI vs Claude
An implementation platform.
Not another conversation.
A chat window doesn’t know your delivery process. You’d have to build that around it. Jetstack Projects gives your HubSpot brief a plan, generated assets, separate generation and deployment approvals, dependency-aware execution and a verified run record. The implementation workflow is the product.
The Jetstack advantage
Buy the implementation system. Not another orchestration project.
Jetstack packages the delivery lifecycle around your client portal.
The portal is the workspace.
Keep the brief, portal context, reviewable plan and generated assets together in a Project.5
Control the whole build.
Approve generation separately from deployment and execute supported assets with their dependencies in view.57
End with evidence.
Review durable run receipts and read-back verification, not the last message in a chat thread.57
What Jetstack covers
Real HubSpot assets. Not just instructions.
Plan → generate → approve → deploy → verify
Projects turns an implementation brief into a reviewable plan and supported asset configurations. The build spans CRM structure, automation, sales enablement, reporting and the workspace around them.
-
Data & schema
- Properties, including calculated and rollup fields
- Custom objects
- Association labels
-
Pipelines & automation
- Deal and ticket pipelines
- Lists / segments
- Workflows, deployed switched off
-
Marketing
- Forms and conditional fields
- Marketing emails
- Snippets
-
Sales & service
- Sequences and sales templates
- Playbooks, task queues and deal tags
- Lead scores
-
Reporting
- Custom reports
- Dashboards
- Assigned goals and goal templates
-
Workspace & settings
- Record page layouts, CRM cards and preview views
- Permission sets
- Supported portal settings, including lifecycle stages and stage-required properties
A delivery lifecycle around every build.
Review the plan and approve generation. Inspect the output, then separately approve deployment. Projects orders dependencies, records deployed IDs and receipts, and reads supported assets back from HubSpot. API-backed types deploy directly; extension-backed types require the Chrome extension and a connected portal.
See the deployment lifecycleGeneration coverage is different from library import/copy coverage. CMS content such as pages and blog posts is not generated by Projects. Unsupported work becomes an explicit manual step. HubSpot subscriptions, permissions and type-specific limits apply. Read-back confirms saved configuration, not runtime behavior; functional testing stays with your team.
Built to go further
A connector isn’t a delivery system.
Hooking an assistant up to HubSpot gives you a chat that can make changes. Everything that makes a build safe is still yours to design.
The Jetstack advantage
The lifecycle comes with the product.
- Start with the client brief and a portal-scoped implementation plan.5
- Generate and deploy supported assets through explicit review and approval stages.567
- Keep the run receipt and read-back result as part of the Project.57
Where it falls short
You become the delivery system.
- The native connector reads and writes. There’s no plan, dependency order or deployment stage unless you build one.13
- Need more? Wire up custom MCP servers and developer tools, then maintain them yourself.24
- HubSpot’s Audit Log records that the connector changed something. It won’t tell you whether the build works.1
Side by side
See what Jetstack brings
to the build.
Individual features are only part of the story. Jetstack puts the implementation workflow around the client’s HubSpot portal.
| The delivery job | Jetstack Projects | Claude + HubSpot tools |
|---|---|---|
| Where the build lives | A portal-scoped workspace for the brief, plan, generated assets and implementation runs.5 | A chat thread, plus whichever connectors you’ve added.12 |
| Generating the implementation | Supported HubSpot assets generated and deployed within the Project lifecycle.56 | Connector writes, extended by custom MCP or developer tools you set up.134 |
| Approvals built around delivery | Plan review, generation approval and a separate deployment approval.57 | Per-action approval prompts in the chat.12 |
| Cross-asset execution | Dependency-aware execution built into the Projects lifecycle.57 | No dependency-aware lifecycle. Orchestration is whatever you build.14 |
| After deployment | Durable run receipts and read-back verification, included.57 | An Audit Log entry. Checking the result is up to you.1 |
Explore Projects, read the implementation guide, or see pricing.
Your team stays in control
What comes with Projects
A purpose-built workflow for HubSpot implementation.
Coverage, access and deployment requirements
Questions, answered
Before you make the switch.
Why is Jetstack better for HubSpot implementation?
Jetstack supplies the implementation lifecycle instead of asking your team to assemble one: portal context, a plan, supported asset generation, separate approval gates, dependency-aware deployment and verified run evidence. You focus on the client brief, not on building delivery tooling.
Claude can already write to HubSpot. Isn’t that enough?
Writing to HubSpot is the easy part. A real build needs a plan the client agrees to, assets created in dependency order, a deployment someone approves and proof that it landed. With Claude, you design and maintain all of that yourself. With Jetstack, it’s the product.
Could we build our own system around Claude?
You could. Then your agency is in the tooling business: custom MCP servers, orchestration, verification and upkeep for every HubSpot change. Jetstack ships that lifecycle so your team can spend its time on delivery instead of infrastructure.
What assets can Projects build?
Properties, pipelines, association labels, segments, forms and workflows, among others on the capability list. Generation and deployment have separate approvals; some deployment paths use the Chrome extension.
Can I keep using Claude with Jetstack?
Yes. Jetstack has its own CLI and MCP surfaces for supported operations, including portal-audit run, status and report data. Use Claude for the conversation and Jetstack for the build.
Backed by product documentation
The evidence
behind our case.
Written by Jetstack AI from each vendor’s public documentation, checked on the dates shown.
- 01Set up and use the HubSpot connector for Claude
Read, create and update scope, user permissions and Audit Log attribution. Page updated 19 Oct 2026.
- 02Use connectors to extend Claude’s capabilities
Native and custom connections and per-action approval controls.
- 03HubSpot connector tool directory
The tools the HubSpot connector advertises.
- 04Developer MCP tools
A separate local development surface for scaffolding, validation, upload and deployment.
- 05Projects: the implementation lifecycle
Portal-scoped plans, generation and deployment approval, run evidence and verification.
- 06What Projects can build
The HubSpot asset types Projects generates and deploys.
- 07Projects deployment
Dependency order, deployment controls, run receipts and read-back verification.
- 08Jetstack MCP server
Connect compatible AI clients with authorized credentials. Portal-audit tools include run_audit, get_audit_status and get_audit_data.
- 09Jetstack CLI and Claude Code integration
Portal-audit run, status and data commands for the terminal and Claude Code.
More reasons to choose Jetstack