/ghl-saas-builder
Agent 33: SaaS on GHL AI Studio (S6 GHL ops)
Packages an already-built GHL sub-account into a resellable SaaS product: snapshot creation is manual-fallback (no API), but provisioning a new customer location (POST /locations/ with snapshotId), enabling SaaS billing, setting the subscription plan/price, and reading it back are all real, agency-scoped API calls. Proves the resold location still works with Claude and every other plugged-in tool via a real GET /locations/{locationId} read-back.
verified (fixture) 2026-09-08 · needs-connector: ghlv0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #33 — SaaS on GHL AI Studio · §3.13
Example requests
- “turn our GHL setup into a SaaS product”
- “resell our sub-account as a SaaS plan”
- “onboard a new SaaS customer”
- “ghl saas builder”
What it needs, and what it hands back
Needs connected
- ghl
Hands back
- clients/<business-slug>/plans/ghl/saas-builder-<date>.md (snapshot checklist, pricing design, provisioning/subscription read-backs)
Stops and asks
- enabling a real subscription/billing for a named customer sub-account
Steps it cannot do through an API, and hands you instead: packaging the reusable snapshot in Settings -> Account Snapshot -- no API endpoint exists to create one.
How it runs
These are the headings of its own written instructions — 228 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Package the snapshot (manual-fallback for creation)
- Step 2 — Provision and bill (real API, once a snapshot exists)
- Step 3 — Prove it connects with Claude and every other tool