---
title: "AI for in-house HubSpot & RevOps teams · Jetstack AI"
description: "Turn the next RevOps request into a reviewed HubSpot implementation. Audit workflows and portal setup, build with Projects and inspect deployment receipts."
url: "https://jetstack.ai/in-house/"
---

For in-house HubSpot & RevOps teams

# Less HubSpot backlog. *More work shipped.*

Sales needs a new process. Marketing needs a better segment. You need more than another task to configure. Investigate what’s there, turn the agreed request into a Project and review the build before it reaches HubSpot.

[Bring a RevOps request ](https://jetstack.ai/contact) [Follow a change request](https://jetstack.ai/in-house/#team-workflow)

One portal. A connected brief.

The business request

## Give every inbound enquiry a clear next step.

Sales routing + marketing segmentation

1. 01

   **Enquiry type**

   A shared property for the routing rules

   Property

2. 02

   **Inbound sales**

   Stages for the agreed qualification process

   Pipeline

3. 03

   **Unassigned enquiries**

   The audience needing follow-up

   Segment

4. 04

   **Route the next enquiry**

   Workflow logic using the agreed references

   Workflow

Review plan Approve generation Approve deployment

From request to reviewed implementation

## Keep the context. Move the work forward.

A useful change starts with the portal you already have—not an empty canvas or a conversation with no delivery process.

01 / Find the real work

### Before you change it, understand it.

Audit the wider portal. Investigate workflow health, dependency paths and potential impact. Use evidence and the read-only workflow advisor to separate the symptoms from the work worth doing.

[Inside Workflow Audit](https://jetstack.ai/audit#workflow-audit)

02 / Build the agreed change

### A request is not a plan. Projects gives it one.

Bring the requirements into a portal-scoped Project. Review the proposed implementation, approve generation and inspect supported properties, pipelines, workflows and segments before deployment approval.

[Explore Projects](https://jetstack.ai/build)

03 / Review what shipped

### Leave a record. Not a guessing game.

Review the durable run, receipt and read-back verification. See the deployment results, understand partial outcomes and keep the follow-up work explicit for the people managing the portal next.

[How deployment is reviewed](https://jetstack.ai/docs/projects/deployment)

Your portal. Your priorities.

## Keep the judgment. *Lose the blank page.*

Your team owns the business decisions. Jetstack supplies an audit and implementation workflow around them.

- The process

  You define the qualification criteria, handoffs and exceptions. Projects turns the reviewed requirements into supported asset specifications.

- The existing setup

  Review evidence, assets and dependencies in context. Audit findings inform the brief; they do not silently become fixes.

- The release decision

  Review generated assets before a separate deployment approval. Check permissions and extension requirements, and validate results in the destination.

More than one portal?

## Keep your useful work *ready for the next setup.*

If your team also manages another business unit or brand portal, reuse supported library assets with dependency-aware import, destination mappings and reference rewriting. Review each destination separately; this is not continuous synchronization.

[Explore dependency-aware reuse ](https://jetstack.ai/roll-out#dependency-engine) [Plan a HubSpot implementation](https://jetstack.ai/guides/hubspot-implementation)

Questions, answered

## For the team running HubSpot.

Is this built for teams managing just one HubSpot portal?

Yes. Portal and Workflow Audit help investigate an existing portal, while Projects turns a scoped brief into supported HubSpot assets. You do not need multiple portals or an asset-copying use case to use that workflow.

Will an audit automatically fix what it finds?

No. Both audits are read-only. You choose which findings become work and carry the agreed requirements into a separately reviewed Project. The Workflow Audit advisor investigates a completed snapshot; it is not a live monitor or an automatic repair agent.

Can the AI change our live HubSpot setup without review?

Projects requires approval for generation and a separate approval for deployment. Review the generated assets and destination before approving a write. Supported asset coverage, permissions and extension requirements still apply; approvals are not a guarantee of a risk-free change. A Portal reuse deployment can be rolled back, and an asset a Project deployed can be retired or removed.

Can we use Claude or another AI assistant alongside Jetstack?

Yes. Portal Audit supports CLI/MCP creation of eligible public-API runs, status checks and report-data retrieval with authorized access to the run. Extension-only capture still uses the app and extension. Standalone Workflow Audit has REST investigation endpoints and an in-app advisor, not dedicated CLI/MCP wrappers.

## A different kind of HubSpot team?

The same platform. A workflow shaped around your work.

### [HubSpot Solutions Partners](https://jetstack.ai/partners)

[Win the audit. Deliver the build. Reuse your best work.](https://jetstack.ai/partners)

### [Franchise & multi-location teams](https://jetstack.ai/franchise)

[Build a shared standard. Make it work in each portal.](https://jetstack.ai/franchise)
