Most SaaS companies above $1M ARR run both motions: product-led growth for the self-serve segment and a sales-assist layer for accounts above a certain size or complexity threshold.
The challenge is that these motions need different automation logic. PLG accounts need frictionless self-serve onboarding. Sales-assist accounts need a human in the loop fast. Most GHL builds treat them as one undifferentiated mass — and both motions suffer.
The SaaS Snapshot handles both from the same system with a routing layer that decides in real-time which motion applies to each account.
The routing decision
The first question after a trial signup is: is this account self-serve or sales-assist?
Getting this right matters a lot. If you route a self-serve account to a sales rep, you slow them down and waste the rep’s time. If you route a high-value account to a self-serve sequence, you leave significant expansion revenue on the table.
Routing signals the snapshot uses by default
Push toward sales-assist:
- Company size ≥ 50 employees (from signup form or enrichment).
- Seat count requested ≥ 10 at signup.
- Enterprise email domain (custom domain + known enterprise pattern).
- Specific use-case signals: mentions of SSO, SAML, custom contracts, procurement.
- Company revenue signals above your ICP threshold (enrichment-driven).
- Manual override: account owner tags the account
sales-assist.
Keep in PLG:
- Small company / solo operator.
- Low seat count.
- Credit card on file at signup (strong PLG indicator — they intend to self-serve).
- Activation happening fast (if they’re 50% through activation in the first 24 hours, they don’t need a sales call).
The routing workflow
When a new trial signs up, GHL fires an enrichment webhook (Clearbit, Clay, or Apollo — your choice). Within 5 minutes, routing signals are populated on the contact record and the routing workflow evaluates the threshold.
Result is written to a custom field: motion = plg or motion = sales_assist.
Every subsequent workflow checks this field to decide which branch to follow.
The PLG motion in GHL
PLG accounts need three things: fast activation, frictionless trial-to-paid conversion, and expansion triggers when they outgrow their initial plan.
Onboarding sequence (PLG)
The PLG onboarding sequence is designed for self-serve success — no humans required.
- Day 0: Welcome email with a single next step toward activation.
- Day 1: “Did you hit the milestone?” check-in. If yes, skip to social proof sequence. If no, re-engage with the 5-minute setup offer.
- Day 3: Social proof story email.
- Day 5: Offer a 15-minute screenshare for stuck users — but optional, not pressure.
- Day 9: Feature depth email for activated-but-not-converted.
- Day 12: Trial ending soon.
- Trial expiry: Conversion or graceful downgrade.
The entire sequence is automated. A human only touches a PLG account if they raise their hand (book a screenshare, email back, or hit an at-risk signal).
PLG expansion triggers
PLG accounts often grow organically — they add seats, hit feature limits, or cross plan thresholds. The snapshot watches for these signals and triggers an in-context upgrade prompt automatically.
The sales-assist motion in GHL
Sales-assist accounts need a human fast, a qualification step, and a handoff to a calendar.
Sales-assist onboarding sequence
When the routing workflow tags an account sales_assist:
- Immediate: Create a high-priority task for the SDR/AE assigned to this segment.
- Hour 0-1: Send an automated email from the account owner (not a sequence drip — an email that looks like it came from a person): “Welcome — I saw you just started a trial. I’d love to spend 15 minutes learning about your use case and making sure we’re set up for you specifically. Here’s my calendar: [link]”
- Hour 4: If no booking, SMS from the AE: “Hi [Name], sent you a note. Happy to set up a call whenever works — grab time here: [link]”
- Day 1: If still no booking, SDR task: manual call attempt.
- Day 2-3: If call connected, enter the post-discovery sequence. If no response, enter the “low-engagement sales-assist” sequence (3-4 more touches over 7 days before routing back to PLG).
The discovery → demo flow
When a sales-assist account books a discovery call, GHL does the following:
- Sends a confirmation email with a pre-call prep question: “In 2-3 sentences, what’s the main pain point you’re hoping [Product] solves?”
- Creates a CRM record with the response pre-populated.
- Sends the AE a “prep brief” 30 minutes before the call: account details, signup-to-call activities, seat count, company size.
After the call, GHL creates a follow-up task with a 24-hour deadline and a “next step” dropdown: Demo, Proposal, Legal/Procurement, Closed Won, Closed Lost.
Custom pricing and contract flow
For enterprise accounts that need custom pricing:
- An
enterprise_dealtag routes the account out of standard sequences entirely. - A separate pipeline stage (“Enterprise”) tracks the deal through procurement.
- Legal review workflows (redline acknowledgment tracking, MSA signature status) handle the paperwork loop.
Monitoring both motions together
One challenge with running dual motions is reporting — you need to see PLG and sales-assist conversion separately to optimize each.
The SaaS Snapshot includes two separate conversion dashboards:
- PLG dashboard: Trial → activation rate, activation → conversion rate, time-to-activation, time-to-paid, MRR from self-serve channel.
- Sales-assist dashboard: Trial → discovery call rate, discovery → demo rate, demo → closed-won rate, average deal size, sales cycle length.
The most important cross-motion metric: overlap rate — what % of accounts that started in PLG got picked up by sales-assist before converting? This tells you whether your routing logic is calibrated correctly. If it’s above 20%, your PLG threshold may be too aggressive (you’re routing too many accounts to sales). If it’s below 5%, you may be leaving enterprise revenue in the self-serve funnel.