---
title: "What you can build · Jetstack AI"
description: "Practical HubSpot use cases: understand an inherited portal, build an enquiry setup and adapt reusable assets for another destination."
url: "https://jetstack.ai/customers/"
---

Practical use cases

# What you can *build.*

A few ways to put Portal Audit, Projects and Portal reuse to work. Start with the portal and the problem—not a blank canvas.

01 / Portal Audit

## An inherited portal. *A clearer starting point.*

You need to understand a configuration before proposing work. Run a read-only audit, inspect scored evidence and bring relevant findings into a branded report or PDF.

- The artifact

  Scored findings and a report to review.

- The human decision

  Which issues belong in the implementation brief?

[Explore Portal Audit](https://jetstack.ai/audit)

Finding Read only

Configuration review / Workflows

### A dependency needs attention.

A workflow references a property that needs review. Inspect the evidence before deciding whether to change the workflow or its prerequisite.

Workflow reference Property dependency Review the evidence

Report finding ≠ automatic fix

02 / Projects

## A brief becomes *connected assets.*

Scope a website enquiry process: a property for the enquiry type, a form to capture it, and a workflow for the agreed follow-up logic. Review the plan before generating the assets.

- The artifact

  A dependency-aware asset plan and generated assets.

- The human decision

  Does the generated setup match the brief, and is it ready to deploy?

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

Asset plan One portal

1. Property **Enquiry type** Define the values the form needs.
2. Form **Website enquiry** Reference the agreed property.
3. Workflow **Enquiry follow-up** Review enrollment and routing logic.

Approve generation Review assets Approve deployment

03 / Portal reuse

## Keep the pattern. *Resolve the local detail.*

Bring selected assets from an established setup into another portal. Match destination assets and remap their references rather than carrying source IDs into a different environment.

- The artifact

  A destination-specific mapping and deployment result.

- The human decision

  What can be reused here, and what needs a different implementation?

[Explore Portal reuse](https://jetstack.ai/roll-out)

Destination review Per destination

Source

### Studio portal

Destination

### Harbour portal

- Property reference

  Match the destination schema

- Pipeline reference

  Resolve the destination ID

- Owner reference

  Review the local owner

Another destination means another review.

Your starting point

## Bring a real implementation to the *conversation.*

Use a live walkthrough to see where an audit, a Project or a reusable setup fits the work you need to do.

[Book a live build](https://jetstack.ai/contact)
