Trial Activation Playbook 2026
Your converted customers show you what a good first week looks like. This play checks every trial against that pace each day, confirms a trial is really stuck before anyone acts, and puts the move on the account in your CRM: personal outreach for high-fit trials, an unblock message or check-in your team chose to automate – or no move, with the reason noted.
Calendar-based trial nurture sends welcome on day one, tips on day three, a discount on day thirteen. None of it knows whether the account has actually done anything.
Your converted customers already show you what a good first week looks like – the two or three things nearly all of them did, and when. A trial that's behind that pace is a gap you can see while there's still time to do something about it.
This play checks every trial against that pace each day. Each check ends with a move – a person for the trials most like your paying customers, a message your team chose to automate for the rest – or a note on why there isn't one. Measure it on the share of trials on pace and days to the first milestone – and, above all, trial-to-paid conversion.
How it works10 steps
01SignalCompare every trial with what your converted trials did
Build the benchmark once, refresh it quarterly:
- Comparison trials: the last six to twelve months of trials that converted and were still paying 90 days later. Aim for 20; with fewer, label it low confidence.
- The milestones: the actions most converted trials took in week one and most other trials didn't – inviting a teammate, connecting a data source, creating the thing your product exists to create. Default: a milestone counts if three in four converted trials hit it in week one and fewer than half of the other trials with a known outcome did. Keep required setup steps that every trial completes separate from the milestones, and check the pattern holds on later trials. Keep it to two to four.
- The pace: the day by which three in four converted trials had hit each milestone.
- Fit: the company size band and use case that hold most of your revenue. A trial in both is High; a student, a competitor or a personal email domain is Not a fit; the rest are Standard. Your growth or CS lead approves all four.
A trial is behind when a milestone's day has passed and it hasn't hit it.
Say a 40-person agency is on day four with its data connected but nobody invited; converted trials had invited two teammates by day three, and agencies that size pay $4,800 a year – a comparison, not a forecast. (The numbers are illustrative.)
Run it as a daily saved query in PostHog, Amplitude or Mixpanel, grouped by account, not user. Under about a hundred trials a month, do it by hand in a spreadsheet each morning.
02ScoreCheck the records before calling it stalled
- Active users: for a team-use trial, check whether the people needed to test the shared workflow have joined. Until they have, one busy enthusiast still counts as behind.
- Sales already talking? An open deal or a booked call in the CRM means the AE's plan stands.
- Setup blocker? An open ticket, SSO waiting on IT, an import still running. Support may already be on it.
- Most active user: who to write to – not whoever filled in the form.
03DecisionDecide whether there's a move worth making now
Leave it alone if the trial is on pace, is Not a fit, sales is already talking, or support is working the blocker. Everything else picks a move.
04ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to the next point it could change – usually the next milestone's day. Trials on pace get silence; it buys attention for the messages that matter. More on the no-move call in leave it alone.
05DecisionPick the move the evidence supports
Rules, in order (defaults to tune):
- High fit: Trial fit is High. A person reaches out, whatever the reason it's behind.
- Gone dark: no activity for five days. Check-in note.
- Stalled: everything else behind – active, but two days past a milestone's day. Unblock message.
06ActionDraft personal outreach for high-fit trials
A task for the account owner with the evidence and the draft below. Offer help with their setup, not a demo of what they've already seen.
07Human stepThe AE or CSM decides and writes
They send it as drafted, change it, or pass, from their own inbox. Before sending, they record the success measure and the review date.
08ActionStalled: an unblock message your team chose to automate
One message per milestone, in-app and by email, pointing at the exact step they're stuck on – with a template or example that removes the blank page. Approve these by hand for the first couple of weeks; then your team can choose to let them run. When the trial's state changes, the automation stops before its next send, and in-app messages expire within a day: a "need help getting started?" an hour after they hit the milestone tells them nobody's paying attention.
09ActionGone dark: a short check-in from a real inbox
Two plain-text lines from the account owner's address – no images, no tracking pixels. Replies go to a person, and the sequence stops when they reply.
10OutcomeReview what changed, then sharpen the benchmark
Four weeks after the trial ends, record three answers: did they pay, did they hit the missing milestone, and what else played a part – a sales call, a price change, a teammate who already knew the product? Sending is activity; a milestone is progress; a paid plan is the result.
Each month, your growth lead grades each lane on its own. If a lane isn't moving trials to the milestone, change the message, stop the lane, or give it another month. If trials keep stalling at the same milestone whatever the message says, it's a product problem – hand it over. Each quarter, add the new converted trials to the benchmark. Once a trial pays, the handoff play takes its first 30 days.
Setup and templates
Sources. Milestones and last activity: your product events in PostHog, Amplitude or Mixpanel, grouped by account. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. Fit: company size and industry on the CRM record. Sales and support: open deals, meetings and tickets in the CRM and your help desk. By hand: one spreadsheet row per trial, a column per milestone.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Trial day | Number | Daily check |
| Milestones hit | Multiple checkboxes | Daily check |
| Milestones due by today | Number | Daily check |
| Trial fit | Dropdown select: High · Standard · Not a fit | Daily check |
| Recommended move | Dropdown select: Personal outreach · Unblock message · Check-in note · No move | Daily check |
| Move reason | Single-line text | Daily check |
| Success measure | Single-line text | Daily check (automated lanes), account owner (outreach) |
| Review date | Date picker | Daily check, then account owner |
| Review result | Dropdown select: Paid · Paid, other cause likely · Extended · Didn't convert | Billing, then account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The daily list is a saved view: Recommended move is Personal outreach, lowest trial day first. A second view, Review date is today or overdue, is the review list. In HubSpot that's two filter groups: Review date is Today, or Review date is before Today. Personal outreach creates a task for the owner, "Trial: personal outreach – [company]", with the draft in the body. The default success measure for the automated lanes is the missing milestone hit within a week. Each send shows on the contact in HubSpot, and both lanes skip trials with an open deal or outreach in progress.
The check-in is a HubSpot sequence sent from the owner (Sales or Service Hub Professional). Enrolling it from a workflow, without the owner, needs Sales or Service Hub Enterprise. Before enrolling, the owner checks the trial has no open deal and no outreach in progress. No tracking pixels means turning off one-to-one email tracking for the account (Settings, Objects, Activities); it can't be turned off per sequence. On Salesforce, the emails need Sales Engagement (included in Unlimited, a paid add-on otherwise). On Pipedrive, enroll the trial as a lead, and stop its sequence by hand when they reply.
The unblock message runs in Customer.io, and in-app messaging needs Customer.io's SDK in your app. Sync Number of open deals and Recommended move into Customer.io and exit on either. Exit the automation when the milestone is hit, and set in-app messages to expire within a day. Set the message to queue as drafts until you're happy, then switch it to send automatically. Add a webhook step after each Customer.io send to log it on the HubSpot record. For email, sending from a HubSpot user's address with a BCC to your HubSpot logging address also works. If you use Userlist, build the HubSpot logging with webhooks or Zapier. Apply these checks to marketing emails sent by hand or automatically: permission to send, accurate sender details, required address information, an easy unsubscribe and shared suppression checks. Keep required service notices separate from marketing.
Personal outreach (High fit):
Hi [name] – I saw [company] has [milestone hit] in [product]. Teams like yours usually [missing milestone] next, and that's where it clicks. Would fifteen minutes on your setup help? [owner]
Use this peer claim only if your records support the specific comparison, including any timing. Otherwise, describe this account's activity.
Unblock message (Stalled):
[Name] – you're one step from [missing milestone]. Here's [template or example] to start from: [link]. Stuck on something else? Just reply.
Check-in note (Gone dark):
Hi [name] – you set up [what they did], then things went quiet. Did something get in the way? [owner]
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. We check every trial in the agreed segment against it, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which moves run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive, and Customer.io for Userlist or Ortto. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Onboarding Cliff Rescue Playbook 2026
Your best customers show you what the first 90 days after go-live look like. This play checks every new account against them at the same stage each week, confirms the slip is real, and puts the move on the account in your CRM: an unblock call on the missed step, a note for the champion, a self-serve nudge – or no move, with the reason noted.
Sales to CS Handoff Playbook 2026
Start while the deal is fresh. This play puts the deal's promises on the CRM record at closed-won, gets kickoff done inside a week, and at day 14 compares the account with customers who onboarded well. On track, it's left alone with a note; stalled, the CSM gets a drafted setup session or re-plan to run.
Second-Value Seeding Playbook 2026
Your best customers show you which feature comes after the first. This play checks every account against them each week, finds the feature customers like it added next and kept, and puts the move on the account in your CRM: an in-app prompt and a short story, the CSM on the next call – or no move, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.