Trial users ghost at day 7 because you're sending the same message to someone who activated on day 1 and someone who never logged in.
Most SaaS trials fail not because the product is bad, but because the nudge is wrong. A user who imported data on day 2 needs a different message than a user still on the login screen at day 6. This workflow splits your trial cohort into activation buckets, queues templated follow-ups tied to each bucket, and routes them through human review before hitting inboxes. The gate is critical: a generic "last chance" email to a power user looks desperate. A personalized "here's what you can do next" email to a stalled user looks helpful. The system works like this: 1. Trigger fires when a trial user hits day 5 (or any milestone you set). 2. Automation queries their activation state: Did they log in? Import data? Invite teammates? Create their first asset? 3. Based on state, it queues one of 3–5 pre-written message templates into a review queue. 4. A human (founder, CS lead, whoever owns conversion) approves or edits the message in <2 minutes. 5. Message sends, tagged with the activation bucket for later analysis. 6. If a user converts, the sequence stops. If they don't, a second nudge fires at day 9 (or you mark them as "lost trial"). Why this beats a single broadcast email: Activation state predicts conversion intent better than tenure alone. A user who set up SSO is 3x more likely to convert than one who never left the onboarding screen. Sending them the same message wastes both your credibility and their inbox. The human gate prevents two failure modes: (1) sending a "final warning" to someone about to convert, and (2) sending a feature-focused pitch to someone still stuck on basics. It also keeps your brand voice consistent—no AI-generated tone drift. Expect 15–25% of trials to move to paid after a well-executed follow-up sequence. The real win is the data: you'll see which activation states convert and which don't, letting you fix your onboarding for next month's cohort.
Trigger: Trial user reaches day 5 (or configurable milestone) AND has not yet converted to paid plan
1. Define activation states: log in, feature use (e.g., create first project), data import, team invite, SSO setup. Pick 3–5 that matter for your product. 2. Build 3–5 message templates in your email tool or CMS, one per state. Keep them short (3–4 sentences). Example: "You imported data—here's how to invite your team" vs. "We noticed you haven't logged in yet—start here." 3. Set up a workflow trigger in your automation platform (Zapier, Make, or native CRM automation) that fires at day 5 for all trial users. 4. Add a query step: check the user's activation state against your CRM or product database (API call or direct query). 5. Route to message queue: based on state, queue the matching template into a Slack channel or email draft folder labeled "Trial Follow-ups – Review". 6. Create a human review gate: assign one person (or round-robin) to review queued messages daily. They approve, edit, or skip. Approval triggers send. 7. Tag all sent messages with the activation state and trial cohort for analysis. 8. Set a second trigger at day 9: if no conversion yet, queue a final nudge (or mark as lost and move to nurture). 9. Test with 20 trials first. Measure conversion lift before scaling.