The library ·Room & Screen · Edition 17
SaaS Company GHL Snapshot Edition
Trials, demos and the fourteen days that decide it.
A trial that starts on Monday is usually decided by Thursday. This edition is set for the fourteen-day clock: activation rather than signup, demos qualified on seat count and use case, and renewal worked before the date.
A trial that reaches day fourteen untouched was lost on day two, when nobody noticed.
The case
What is going wrong now
Four things, specific to a SaaS company. If none of them is true of your week, this edition is not worth $2,485 to you and we would rather you knew that here than after paying.
01
Signup is not activation
A user creates an account, connects nothing, invites nobody, and the trial runs down while your dashboard counts them as a lead. On day fifteen they become a churn number with no conversation attached to them.
02
Demos booked blind
A demo request arrives with a work email and nothing else: no seat count, no use case, no sign of whether they can buy at all. The team spends a booked hour discovering it was a student on the free plan.
03
The silent self-serve user
Self-serve users never speak to anyone until the card fails or the plan is cancelled. The first human conversation you have with them is the exit interview.
04
Renewal by surprise
An annual renewal comes round with no contact since onboarding, and the champion who signed it has left the company. The invoice turns into a procurement review that nobody on your side prepared for.
The change
What is different by the second month
- Standing Type
Day two, not day fifteen
The trial sequence is timed to the fourteen days rather than to a monthly send, and it changes register the moment a user activates instead of repeating the welcome mail. A user who has not made a first import by day three hears about that, and not about your funding round.
- The Message Desk
Demos that qualify themselves
Seat count, current tooling and use case are asked before a slot is offered, and a free-plan browser is routed to the self-serve track rather than to an account executive. The calendar fills with demos that could actually sign a contract.
- The Callback Round
The silent user reached
A trial with real product usage that has gone quiet gets a phone call, not a fifth in-app nudge. The account that would have churned without a word becomes a conversation while there is still usage to talk about.
- The Diary Guard
Renewal seen coming
The renewal date sits on the account with a countdown of its own, and the check-in happens while there is still time to fix whatever is wrong. Nobody finds out the champion has left during the week the invoice goes out.
The specimen sheet · SaaS Company
The nine, cut for a SaaS company
The same nine components every edition carries, written for what actually happens in a SaaS company. Cover the title and you should still know whose page this is.
The Answering Desk
AI receptionist, on the phone around the clock
Answers the number on the pricing page when a buyer wants to know whether it does single sign-on and what the price does above fifty seats. It takes the seat count, the tool they are replacing and the timeline, then books the demo onto the right calendar. A pricing-page call is the highest-intent contact this trade ever gets, and it usually arrives outside your working hours because the buyer is in another market.
- Asks seat count before offering a slot
- Answers the single sign-on question
- Books demos in the buyer's time zone
The Message Desk
AI chat across the site, text, email and social
Sits inside the product and on the pricing page, where the questions are about plan limits, integrations and what happens on the day the trial ends. It answers those from your own documentation and hands anything about contracts or procurement to a person, with the account usage attached. A trial user with an unanswered question rarely opens a ticket; they simply stop logging in.
- Answers plan limits and integration questions
- Hands contract questions to a human
- Tells trial users from paying accounts
The Standing Page
the website, written and built to be found
The pages are written to the search a software buyer actually runs, which is a category, a competitor name and the word alternative. Pricing and seat tiers sit on the page instead of behind a form, because a buyer made to ask the price goes and reads someone else's. Each use case gets a page of its own, so the trial begins already framed by the job the user came to do.
- A page per use case, not feature
- Pricing and seat tiers on the page
- Comparison pages for tools you replace
The Diary Guard
confirmations, reminders and no-show recovery
Confirms the demo with an agenda, the seat count the buyer gave, and a note of what will be shown on the screen. Reminders run the day before and again an hour before, because a missed demo costs a booked hour of an account executive and a slot a serious buyer wanted. The last reminder asks them to bring whoever signs, since a demo without the decision-maker only produces a second demo.
- Confirmation restates the seat count given
- Reminder an hour before the slot
- Asks them to bring the signer
The Callback Round
AI outbound calling on misses and cold leads
Rings the trial that has real usage behind it and has gone quiet around day nine, and rings the demo request that never picked a slot. The call opens on what the user actually built in the account rather than on a script about features. Self-serve users will never start that conversation themselves, and once the plan is cancelled there is nothing left to say.
- Calls trials with usage, not empty ones
- Opens on what they built
- Chases demo requests that never booked
The Ask
the review request, fired at the right moment
The ask fires at the activation moment rather than the payment moment: the first import that completed, the first teammate invited, the first report a user sent to their own manager. That is the hour the product visibly worked for them. Ask on the renewal invoice instead and you get a review about billing.
- Fires on the first real success
- Waits until a teammate is invited
- Never fires on an invoice
The Review Press
the ongoing review engine and its cadence
The engine works the software review sites your buyers read before they read your homepage, and it asks the same account again at genuinely different moments: after activation, after the team grows, after a renewal that went well. Admins and end users are asked in different words, because an admin praises the audit log and an end user praises the thing that saved an afternoon. Anything under four stars reaches customer success before it reaches a public listing, since a bug and a misunderstanding need entirely different replies.
- Asks admins and end users differently
- One ask per milestone, not monthly
- Low scores routed to customer success
The Cold File
database reactivation of dormant contacts
Works the trials that expired without converting, the accounts that dropped to the free plan, and the deals that went cold in procurement. Each is approached with what has changed since they left: the integration they wanted, the limit they hit, the tier that did not exist then. An expired trial already knows what the product does, which makes it the cheapest pipeline in the building.
- Reopens trials that expired unconverted
- Names the integration they asked for
- Revisits deals lost at procurement
Standing Type
lifetime nurture, seasons, referrals
Once the card clears, the type is left standing. Onboarding, the seat-upgrade prompt when a team fills the plan it bought, the quarterly check-in and the renewal run-up all keep running without anyone remembering to run them. Expansion inside an existing account is cheaper than a new logo, and it only happens if something notices the team grew.
- Prompts seat upgrades when plans fill
- Renewal run-up starts a quarter early
- Referral ask goes to power users
The run · SaaS Company
The run, in a SaaS company
Five formes, from the first enquiry to the user you still have in three years.
A forme is the page of type locked up and put on the press. Five of them make an edition: setting, proofing, imposition, impression, and the type left standing for next time.
Setting
lead capture and first contact
A pricing-page call, an in-product question and a demo form are three different grades of intent, and each is answered in the minute it arrives.
1.1The call
The number on the pricing page is answered whatever the hour, because the buyer evaluating you is often in a market that is awake when you are not. Seat count, the tool being replaced and the timeline are taken before any slot is offered.
1.2The message
In-product chat and the site widget answer plan limits, integrations and trial terms from your own documentation. Anything about contracts, security review or procurement goes straight to a person with the account usage attached to it.
1.3The form
The demo form asks for seat count and use case rather than only a work email. A ten-seat team and a two-hundred-seat rollout leave down different paths from the moment they press submit.
Proofing
the ten-day nurture
A trial has fourteen days and a demo request has about a week of memory, so the follow-up is timed to the clock the buyer is on rather than to a monthly newsletter.
2.1Days one to three, by email
The first days go on activation instead of features: connect the source, import the data, invite one teammate. What is sent branches on whether those things have actually happened, so a user who has already activated never receives the getting-started mail again.
2.2Days four to seven, by text
Text carries the deadline, because the trial end date is real and nobody opens a fifth email. It is short, it names what they have already built in the account, and it offers a person if they are stuck on the import.
2.3Days eight to ten, by voice
The call goes to trials with usage behind them and opens on what they did rather than on a pitch. Empty trials stay on the email track, because ringing somebody who never logged in twice is a cold call with a wasted number.
Imposition
booking and no-show prevention
A demo slot is a booked hour of an account executive that another buyer wanted, so it is confirmed hard and defended harder.
3.1The confirmation
The confirmation restates the seat count and use case the buyer gave, and says what will be shown on the call. It goes out inside the minute, and the calendar invitation carries the agenda rather than a bare link.
3.2The reminders
Reminders run the day before and an hour before, and the last one asks the buyer to bring whoever signs. A demo where the decision-maker is missing costs the same hour and only produces another demo.
3.3The recovery call
A buyer who misses the slot gets a call inside the hour with a shorter slot offered in the same week, not a rebooking link dropped into a full inbox. The target is 70% no-show recovery, and a recovered demo carries the whole seat count behind it.
Impression
reviews and social proof
Software buyers read the review sites before they read your homepage, so the ask is aimed at the hour the product visibly worked.
4.1The ask
The ask fires on activation: the import that completed, the report a user sent to their own manager, the teammate who accepted the invitation. It goes to the person who did the thing rather than to the billing contact.
4.2The reply
A score under four reaches customer success before it reaches a public listing, with the account usage already attached so the reply addresses the real problem. Public reviews are answered naming the release that fixed what was raised.
4.3The display
What comes back is set on the pages where a buyer is comparing you, not pooled on a testimonials page nobody visits. A review from a ten-seat marketing team is shown to the ten-seat marketing teams reading that use-case page.
Standing Type
retention and reactivation
The type is left standing for the whole life of the account: onboarding, expansion, renewal, and the ones who left.
5.1The season
The renewal run-up starts a quarter out, and the seat-upgrade prompt fires when a team is close to filling the plan it bought. Annual accounts get the value summary before the invoice rather than stapled to it.
5.2The support line
Users who go quiet mid-contract, and admins who have stopped logging in at all, are picked up by a line that answers rather than a ticket queue that ranks them below outages. The champion about to move companies is the one you most want to catch.
5.3The revisit
Expired trials, downgrades and deals lost at procurement are revisited on the day the thing they asked for actually ships. The message names that one thing and nothing else.
The delivery list · SaaS Company
What actually lands in the account
Thirteen things arrive with every edition. Below each one is the problem it is there to solve for a saas company, what changes when it runs, and how it pays for itself. No quantities are quoted, because a counted promise is a promise, and we would rather make the ones we can keep.
- 01
1 AI Receptionist
- The problem
- The call from the pricing page comes in while your sales team is asleep and the buyer is mid-evaluation in another market.
- What changes
- It is answered live, the seat count and use case are taken, and the demo lands on the right calendar rather than in a voicemail box.
- How it pays back
- If a fifty-seat conversation is worth a year of your average plan, one such call caught out of hours covers the cost of this edition.
- 02
1 AI Chatbot
- The problem
- Trial users hit a plan limit or a missing integration and quietly stop logging in instead of opening a ticket about it.
- What changes
- Chat inside the product and on the site answers limits, integrations and trial terms straight away, and escalates contract questions with usage attached.
- How it pays back
- Every question answered inside the trial window is a day of the fourteen not spent waiting on a support reply.
- 03
Pipelines
- The problem
- Trials, demo requests, paying accounts and renewals sit in one undifferentiated list, so nobody can see whose fourteen days end on Friday.
- What changes
- Stages are built to the funnel this trade actually has: signed up, activated, demo booked, converted, expanding, renewing, at risk.
- How it pays back
- A list of trials that activated but have not converted is the shortest route to revenue you already own.
- 04
Workflows
- The problem
- Activation, trial expiry, seat limits and renewal dates each need something to happen on an exact day, and nobody is watching the calendar.
- What changes
- Each gets a sequence triggered by what the user did in the product rather than by how long they have been on a list.
- How it pays back
- A trial that stalls at the import step gets help on day two instead of a churn survey on day fifteen.
- 05
Appointment reminders, confirmations and no-show recovery
- The problem
- Demo no-shows burn a booked hour of an account executive and take the slot a buyer with budget was asking for.
- What changes
- Confirmations restate the agenda and seat count, reminders run the day before and the hour before, and a miss triggers a call rather than a rebooking link.
- How it pays back
- If your team runs thirty demos a week and loses six of them to no-shows, recovering most of those is a working day of selling handed back.
- 06
Funnels
- The problem
- One signup path for every use case means a support team and a data team are shown the same generic product tour.
- What changes
- Each use case and each competitor comparison gets its own path into the trial, with seat tiers and trial terms stated on the page.
- How it pays back
- A user who arrives on a page about their own job starts the trial already knowing what to build in the first hour.
- 07
AI Studio website
- The problem
- The site sells features while buyers are searching a category, a competitor name and the word alternative.
- What changes
- Pages are written to those searches, with pricing and seat tiers visible rather than gated behind a contact form.
- How it pays back
- Traffic landing on a comparison page has already decided to switch from something. It needs a trial link, not a brochure.
- 08
Nurture campaign
- The problem
- After the welcome email, a trial user hears exactly the same thing whether they imported ten thousand rows or nothing at all.
- What changes
- The nurture reads product usage and changes with it, so activation, stalling and expiry each get different words on different days.
- How it pays back
- The gap between a trial that converts and one that lapses is usually a single unblocked step in the first three days.
- 09
Review automation
- The problem
- Reviews are asked for on the renewal invoice, the one moment a customer is thinking about money rather than about the product.
- What changes
- The ask fires at activation and at real milestones, admins and end users are asked differently, and low scores reach customer success first. The engine is set to target 5 to 10 reviews a month.
- How it pays back
- Buyers here read the review sites before your site, so a steady stream of recent reviews is doing top-of-funnel work while you sleep.
- 10
Seasonal automation
- The problem
- Renewals, budget cycles and the January tooling review arrive on a calendar nobody has ever automated.
- What changes
- Renewal run-ups, end-of-quarter procurement windows and annual value summaries run on their own dates without a reminder in anyone's diary.
- How it pays back
- An annual account that hears from you a quarter before the invoice renews as a decision rather than as a review of alternatives.
- 11
Custom values
- The problem
- Trial length, seat price, the security page link and the support address are retyped into every sequence and go stale the day pricing changes.
- What changes
- They are held once as custom values and pulled into every trial email, demo confirmation and renewal notice.
- How it pays back
- When the trial goes from fourteen days to thirty, it changes in one place instead of in every sequence you have ever written.
- 12
Custom fields
- The problem
- Seat count, plan tier, activation date, trial end date and renewal date live in a note where nothing can be segmented on.
- What changes
- Each becomes a field on the account record, so trials ending Friday or accounts near their seat limit are a filter rather than a report request.
- How it pays back
- The expansion conversation happens because a field says the team grew, not because a rep happened to notice in a call.
- 13
Forms and surveys
- The problem
- The demo form asks for a work email and nothing that would let anybody route the request sensibly.
- What changes
- Forms ask seat count, current tooling and timeline, and a short post-demo survey catches the objection while the buyer still remembers it.
- How it pays back
- Routing a two-hundred-seat enquiry off the self-serve track and onto a rep is the cheapest thing in this whole list.
The hours
Eight to twelve hours a week
Say you take eighty trial signups and thirty demo requests a week, and somebody currently reads each one to decide who is worth a call. That triage, plus manual follow-up on stalled trials and the chasing of renewal dates, is comfortably more than a day of someone's week. The sequences do the triage on product usage and seat count, so the team only touches accounts that have already shown intent. Put your own signup and demo volume in and the shape holds.
When it pays back
Assume your plan sells at four hundred dollars a month, you take eighty trials a week, and one in twenty converts today. If the trial track and the callback round bring one further conversion each week, that is an additional plan on the books every seven days. On those assumptions the edition is covered inside the first month, before any expansion revenue is counted. Substitute your own price and conversion rate and the arithmetic still runs.
The scenario assumed
- A plan at $400 a month
- Eighty trial signups a week
- One further conversion each week
An illustration with its assumptions printed beside it, not a measured result. Change any assumption and the answer changes.
The arithmetic desk
Do the sum with your own numbers
Nothing below is a result anybody has measured. It is your four numbers multiplied together, printed with the assumptions showing, so you can see what the answer depends on and change any of it. If the sum does not work at your numbers, it does not work.
The only performance figures we quote anywhere are the system’s targets: a seventy per cent no-show recovery and five to ten reviews a month. Neither is used in this sum.
Installation
Free. 11 hours, inside 9 days.
Installation is free: eleven hours of dedicated installation time, to be booked and used within nine days of purchase.
That is eleven hours of work, not nine days of standing by. When the hours are used or the nine days are up, further work is quoted.
Delivery
Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend.
9am–5pm Central · 10am–6pm Eastern · 3pm–11pm UK
Refunds
All sales are final. Once the order is created and the snapshot link has been sent, the edition is non-refundable — the link is the goods, and it cannot be returned once it has been handed over.
Questions before you buy, or want a look at an edition first?Book a call and someone will walk you through the account rather than send you a brochure.
The hours cover
- Loading the edition into your GoHighLevel account
- Rebranding the website — your name, your colours, your copy corrections
- A2P / 10DLC registration and setup
- Email service setup, including your own domain email inside GoHighLevel
- A few extra automations where your process needs them
Never included, on any package
- Third-party integrations
- Third-party software
- Custom software development
Those three are quoted separately, or run by a GoHighLevel VA on a retainer. They are not withheld — they are simply a different job with a different price, and pretending otherwise is how installation windows overrun.
Queries · SaaS Company
What a SaaS company asks before buying
01Does this need product usage data to work?
It works far better with it and still works without it. If your product can post an event when a user activates, invites a teammate or hits a plan limit, the sequences branch on that and stop treating an empty trial like an engaged one. Without events the trial track runs on elapsed time alone, which is where most companies start and then improve once the events exist.
02We sell both self-serve and sales-assisted. Does one snapshot cover both?
Yes, and separating the two is most of the point. The demo form and the pricing-page calls take seat count and use case, and anything under your threshold is routed to the self-serve trial track instead of onto a rep's calendar. Both paths sit in the same pipeline, so you can see which of them is actually producing revenue rather than activity.
03Our buyers run a security review before they sign. Does this get in the way of that?
No. The snapshot lives in your GoHighLevel account and handles sales and marketing communication, not your product or its data. It is worth loading your security page and subprocessor list as custom values, so the answer to that question is a link that never goes stale. In this trade the security question tends to arrive at the exact moment the deal is closest, and a slow answer stalls it.
04Is this only for new trials, or does it handle expansion and renewal too?
Both, and expansion is where most of the value sits. Seat counts and renewal dates live on the account record, so the run-up begins a quarter out and the seat-upgrade prompt fires when a team is close to filling the plan it bought. Nothing in here assumes the relationship ends at the first successful payment.
05How quickly do I get it, and is setup included?
The snapshot link is sent inside one working day, counted as 24 business hours between 9am and 5pm Central, Monday to Friday, with no weekend deliveries. Installation is free: eleven hours of installation time, to be used within nine days of purchase, which covers loading your plan tiers, trial length, demo routing and pricing values. All sales are final once the snapshot link is sent.
Letters
Sample setting
The review wall, in proof
These are sample entries, written by us to show how this section reads. They are not customers, not testimonials and not results. Real reviews replace them the moment we have them, and the structured data stays switched off until they do.
The part I did not expect was the recovery call. Somebody booked a Saturday slot, did not answer the door, and the account had already called them and rebooked for Monday before I had finished the job I was on. That would have been a lost morning before.
Sample entry — a plumbing companyOwner, three vans
What sold it was that the reminders say nothing clinical. I have seen systems text a patient the name of their treatment. This one sends the time, the chair and a way to move it, which is all it should ever have said.
Sample entry — a dental practicePractice manager
Loading it was the easy half. Getting the registration through and the domain email actually delivering was the half I always underestimate, and that was the part they did without me chasing it.
Sample entry — an agency principalRuns eleven sub-accounts
The writing is the difference. It knows the difference between a storm call and a maintenance call, and it asks the questions in the order I would ask them. I have bought snapshots that clearly did not know what a supplement was.
Sample entry — a roofing contractorOwner
The shelf
Other editions on the shelf
Same system, different trade, different writing.
The last word
Take the SaaS Company edition
$2,485, once. Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend. Installation is free and included: 11 hours to be used inside 9 days. All sales are final. Non-refundable once the snapshot link is sent, which is why the whole specimen is published above.
- Delivery
- Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend.
- Installation
- Installation is free: eleven hours of dedicated installation time, to be booked and used within nine days of purchase. That is eleven hours of work, not nine days of standing by. When the hours are used or the nine days are up, further work is quoted.
- Refunds
- All sales are final. Once the order is created and the snapshot link has been sent, the edition is non-refundable — the link is the goods, and it cannot be returned once it has been handed over.
- Rates
- 17 editions, $885 to $2,485. No edition is ever discounted below $850.