A record of every change
Every applied plan leaves a change record: what changed, and how to undo it.
For HubSpot agencies
Describe what a client needs. Spriggit plans the portal setup from blueprints and your standards, marks every step, and waits for a person to approve it.
Approve and apply to sandbox
Spriggit compares each request with the live portal and writes a plan: every step, what it touches, and whether it can be undone. Steps that can’t be undone are marked before anyone approves, and nothing in the plan is applied until someone does.
Describe what a client needs in plain words, pick a blueprint, or start from an audit finding.
Spriggit compares the request with the live portal and lists each step: what it touches and whether it can be undone. Nothing changes yet.
Your standards are checked and a person approves the plan. Deletes, invitations and changes to a live portal are applied by a person in the web app.
Spriggit starts in developer mode, which changes only sandbox, test and demo portals. A live portal changes only in live mode, which a person turns on in the web app with an authenticator app, for a set time.
The plan leaves a change record of what changed, and the portal’s reference docs are generated from the portal itself.
An undo is a new plan, reviewed and applied like any other.
| Can be undone | An undo plan can put it back. |
|---|---|
| Undo after export | It can be put back, but only from an export of the data taken before the change. |
| Has side effects | It does something beyond the portal’s setup, such as turning on a workflow or inviting a user. |
| Can’t be undone | The plan says so before anyone approves it. |
Every applied plan leaves a change record: what changed, and how to undo it.
A data dictionary, pipeline guide, automation catalog and role guide, generated from the portal itself.
Audits check the portal against HubSpot’s documented limits and say what they didn’t check. Onboarding, offboarding and quarterly hygiene run as playbooks.
Your clients see your agency in their workspace and their docs. Client admins can sign off a list of fixes, or start the playbooks you offer them, such as onboarding a new user.

When Spriggit says what HubSpot allows, it cites a fact. Most facts carry a source: HubSpot’s own documentation, or a test on a developer account, with the date it was checked.
Browse the HubSpot factsSpriggit is AI-native HubSpot configuration for agencies. It plans client portal changes from blueprints and the agency’s standards, marks which steps can be undone, and waits for a person to approve each plan before it’s applied.
No. Every change Spriggit makes is a plan, and nothing is applied until a person approves it. A live portal changes only in live mode, which a person turns on with an authenticator app, for a set time.
HubSpot’s MCP server and Agent CLI can already write to a portal. Spriggit is about how a change reaches a client’s portal: built from your standards, planned with every step marked, approved by a person and recorded after.
Your clients see your agency in their workspace and their docs. HubSpot’s list of connected apps shows the app’s own name unless your agency has its own app, which comes with Scale.
It’s your client’s call. Each client has a setting for whether record values may go into AI prompts, and only the client’s admin can loosen it. Audit checks that use AI run only when it allows them, and replace names, emails, phone numbers and card or Social Security number shapes with tokens first.
The Spriggit Scan is free. Plans are priced by the number of production client portals, and every tier has every feature. See pricing
A demo takes a short brief, plans the portal, applies the plan to a test account and undoes it.
Book a demo