Before you start
Make sure your GoHighLevel account is on at least the Agency Pro plan — that’s required for snapshot deployment. If you’re not sure, log in and check Settings > Agency.
If you don’t have GHL yet, you can sign up directly during onboarding — we’ll guide you through the sub-account setup.
What you’ll need to provide
- Your product name and brand — name, logo (SVG preferred or 1024×1024 PNG transparent), primary and accent hex codes.
- Your activation milestone — the specific action in your product that signals a user has experienced core value (e.g., “created first workflow,” “connected first integration”). This drives the trial sequences.
- Your billing provider — Stripe, Paddle, or Chargebee, plus admin access to configure webhooks.
- Your product event webhooks — a way to send behavioral events (logins, core actions, seat counts) from your product to GHL. Zapier integration is supported if you don’t have native webhook capability.
- Your ICP description — your ideal customer’s role, company size, and problem — drives lifecycle messaging tone and segmentation.
- Your NPS survey timing preference — default is 60 days after activation and every 90 days thereafter.
- Your dunning window — how many days from failed payment before access pauses (default: 14 days).
- Your response signature — name, role, and photo URL for email signatures. The lifecycle emails perform better when they come from a named person.
What happens during install
Hours 0-2 — Snapshot pushed to your GHL. Pipelines, custom fields, workflows, calendars, forms, NPS survey, health score logic, dunning sequences, expansion triggers, and all four SaaS calculator landing pages land in your sub-account.
Hours 2-8 — Default templates applied. Email templates (40+ messages), SMS templates, and workflow messaging are populated with SaaS-tuned defaults using your product name as a placeholder.
Hours 8-16 — Integration scaffolding configured. Billing webhook receivers pre-configured for your chosen provider. Product event webhook endpoint live and tested. TCPA and CAN-SPAM opt-out handlers wired. A2P 10DLC registration verified for SMS sending.
Hours 16-24 — Branding pass. Your product name, brand colors, logo, and sender identity applied to every template, form, funnel, and calculator page.
Day 2-3 — Integration walkthrough call. We screenshare your live snapshot, walk through the integration configuration for your billing provider and product events, and answer questions. You provide tweaks; we apply them.
Day 4 — Test run. First test contact runs end-to-end through the full lifecycle — trial activation sequence, health score check, NPS dispatch, and dunning simulation. We monitor and tune.
Day 5 — Go live. Point your trial signup flow at GHL. First real customers start flowing through the system.
After install — the first 7 days
The first week is the tuning window. Watch the first 20-30 trial signups move through the system and note:
- Are activation milestone events arriving from your product correctly?
- Is the health score calculating on schedule and producing sensible scores?
- Are trial activation emails landing in inbox (not spam)? Check your DNS alignment: SPF, DKIM, DMARC.
- Do the dunning webhooks fire correctly on a test failed payment?
- Are NPS surveys going to the right contact segment?
We monitor with you and apply fixes during the 15-day support window included with every snapshot.
After install — the first 30 days
By day 30, the snapshot should be producing:
- Trial activation sequences running on every new signup.
- Health scores calculating weekly for all paying accounts.
- At-risk alerts triggering for accounts below score threshold.
- NPS surveys dispatching to the Day 60 cohort (if you had paying customers 60 days before install, these will fire immediately).
- Dunning sequence live and recovering failed payments.
- At least one expansion trigger firing (if you have accounts approaching seat or feature limits).
If any of these aren’t running by day 30, we treat it as a setup issue and fix it.
The most common setup mistakes
Activation milestone too broad. “Logged in” is not an activation milestone — it’s a precondition. If your milestone is too easy to hit, your activation rate will appear high but your trial-to-paid conversion won’t improve. Define the milestone as the moment a user has experienced genuine product value.
Missing product event webhooks. The health score calculation workflow needs live behavioral data from your product. If you skip the webhook configuration, the health score calculation falls back to time-based proxies (less accurate) rather than actual usage signals. Set up the webhooks in week one, not month three.
Sending email from a free domain. Lifecycle emails sent from founder@gmail.com or founder@yourproduct.io without proper SPF/DKIM alignment hit spam filters at much higher rates. Set up a subdomain for sending (e.g., mail.yourproduct.io) and align DNS before you go live.
Skipping the dunning window configuration. The default dunning window (14 days from failed payment to access pause) is appropriate for most SaaS products but wrong for some — especially annual plans or high-touch enterprise accounts. Review the window for your specific pricing model.
What the 30-day guarantee covers
If after 30 days the snapshot isn’t producing measurable improvement on at least two of these metrics (trial activation rate, trial-to-paid conversion, failed-payment recovery), we’ll work with you until it is. The guarantee covers setup issues, integration failures, and workflow misconfiguration — not market conditions or fundamental product fit problems outside the automation layer.
One-time price, no recurring fees
The snapshot is one-time pricing — $1,200. There’s no monthly fee to us. Your only ongoing cost is your GoHighLevel subscription (Agency Pro: $297/month). If you decide GHL isn’t right for your stack, you stop paying GHL and that’s the end. We’re not charging recurring snapshot fees.