Fig. 3 One snapshot, every venue
Venue onboarding cut to one configuration point
A rebuilt GHL snapshot where one set of custom values configures a whole venue account, plus security, email and automation work on the hub the team runs venues from.
- Client
- Wedding venue marketing agency
- Industry
- Wedding venue marketing SaaS
- Year
- 2026
- Discipline
- GHL systems, Custom apps
Drawing
66 active, 12 internal, 14 archived
How it works
Step 01
New venue signs up
Step 02
Sub-account created
Step 03
Snapshot installed
Step 04
Custom values filled in
Step 05
Venue is live
The problem
The agency runs GHL for wedding venues, one sub-account per venue. Their snapshot was bloated, so every new venue meant hunting through assets by hand. Onboarding was slow and depended on hands-on setup.
Built with
- GoHighLevel
- Snapshots
- Custom values
- React
- TypeScript
- Supabase
- Gmail API
- Google Drive API
What I built
- 01Audited and rebuilt the snapshot around custom values, so emails, messaging, branding and links all read from one place. Install, fill in the values, and the venue is live.
- 02Automated new sub-account provisioning, cutting the manual steps and the human error in onboarding.
- 03An encrypted password vault for each venue's tools, visible only to the staff assigned to that venue, with every reveal logged.
- 04Moved the hub's emails onto the team's own Gmail after mapping all 31 functions that touch email, with a backup sender kept in place.
- 05Fixed a silent gap that left some new venues without their embed-code sheets, with no duplicate folders or files created.
Build notes
Encrypted password vault for every venue, with reveal audit
Venue logins that sat in plain text are now encrypted, visible only to admins and assigned staff, and every reveal is logged. The audit trail survives even if the credential is deleted. Review caught a regression before release.
Every new venue now gets its embed-code sheets
A Drive folder was being created but never recorded, so the embed-code automation skipped some venues. The fix heals that gap without duplicate folders or sheets and is live in production. Also restored deploys after an expired access token.
Hub emails moved to the team's own Gmail
Nearly all hub emails now go out from the team's own Gmail, with the old provider kept only as a backup. Mapped all 31 functions that touch email, then switched each one still on the old provider.
Next drawing
Five trading brands, one sales-to-ops system