Trigger On The Moment
An email tied to what a user just did outperforms one tied to what day it happens to be.
Most onboarding sequences are built around a calendar, not a customer. Day 1 gets a welcome, day 3 gets a feature tip, day 7 gets an upgrade pitch, whether or not the person has opened the product since signup. The day tells you nothing about the user. The action does. Swap the timer for a product event and the same email gets read differently, because it now describes something that just happened to the person reading it, not something that happens to fall on a schedule.
What to do: Replace the generic day-1, day-3, day-7 onboarding drip with sends triggered by actual product milestones: a first successful action, a usage threshold crossed, a specific feature touched for the first time. Wire the send to an event your product already logs, not to a timer, so it only fires when something true just happened.
Why it works: A message about what you just did reads as relevant. A message about what day it is reads as a company emailing on a schedule.
Example: Grammarly's weekly Insights email runs on a fixed cadence but derives its content entirely from what a person actually did that week: total words checked, an accuracy score, and how that stacks up as a percentile against other users, plus their most frequent mistakes. Grammarly's own support documentation describes it as an analysis built from that week's real usage, not a template with your name dropped in. Someone who wrote nothing gets a thin email, because there is nothing to report. That is the tell that the trigger is usage, not the calendar, and it is why the email gets forwarded and screenshotted instead of archived like a newsletter. It is a report about the reader, not about the sender.
Walk it through
Grammarly's own support articles lay out exactly what goes into that email, and the structure maps onto a pattern any team can copy.
1. The cadence is fixed. The content is not. The email goes out on a regular weekly schedule, but what is inside depends entirely on what you typed in the days before. No usage, barely an email.
2. It is a scorecard, not a status update. Productivity is your total word count for the period, benchmarked against other users. Mastery is an accuracy score, calculated from how many corrections you needed against how much you wrote. Vocabulary counts unique words used. Every figure comes from a logged product event, not from a static field on your account.
3. It surfaces the extremes, not the average. Grammarly's documentation describes calling out your top few grammar mistakes and your most-repeated word, the specific, slightly embarrassing details that make you want to open the email and see how bad it was.
4. The comparison is the hook. Grammarly explains the percentile mechanic with an example of its own: a score of 90 means your writing beat 90 percent of others working toward the same goal. Every metric sits next to a comparison like that. The whole email is built to produce one sentence worth screenshotting.
That is the shape. Build the same shape around your own product:
5. Pick one action that predicts retention. Not a page view. A completed task, a saved item, a threshold in usage that correlates with people who stick around.
6. Log it as an event tied to a user and a count, so you can ask "has this person crossed N yet" instead of "has three days passed."
7. Write the copy around the number the user just produced. Name it specifically. Add a comparison only if you actually have the data to back one up.
The read
Three things separate a trigger-based email from a calendar-based one, and all three show up in Grammarly's version.
- The event is the subject line's job. Whatever data point is freshest becomes the reason to open, not a canned "check out what's new."
- The threshold turns usage into a story. Crossing a number, first time, tenth time, hundredth word, is a moment. A day on the calendar is not.
- Silence is data too. If nobody crosses your threshold, that is not a broken automation. That is a segment of users who have not reached the value moment yet, and now you know exactly who they are.
Steal it
Start by listing the events your product already logs, then pick three to five that correlate with people who stick around, not every click you happen to have instrumented. Ship one trigger at a time. A single well-timed email that fires on a real milestone will outperform a whole redesigned drip campaign that still fires on day 1, day 3, day 7.
Defend the other side of this too. Anyone can sign up for a free trial, perform your product's core actions one at a time, and log every triggered email they receive to reconstruct your entire activation sequence, your thresholds, and which milestones you think matter enough to message on. If you would rather a competitor not have your activation playbook, keep the specific numbers out of subject lines and don't name your internal milestone in a way that reads like documentation.
Gotchas
- Data latency kills the moment. If your event pipeline batches hourly or daily, "you just did this" arrives after the fact and reads like it was scheduled after all. The pipeline needs to be close to real time or the premise breaks.
- Not every action deserves a trigger. Fire an email on every small interaction and you have rebuilt the generic drip with better targeting. Reserve triggers for actions that predict retention or expansion, not for anything you happened to instrument.
- Watch the framing, not just the trigger. "You just crossed 10,000 words" reads as a personal report. "We noticed you crossed 10,000 words" reads as surveillance. Same event, same data, opposite reaction, and the difference is entirely in the copy.