Updated 28 September. What changed since Saturday:
Everything is being implemented now. Account setup first:
Then build all of these now, in parallel as Kamil's data arrives. The order is priority if two compete. Each link has the full copy, timing, trigger and build notes.
| # | Build | Deadline | Waiting on Kamil for |
|---|---|---|---|
| 1 | Yearly renewal reminder · 15 and 3 days before | Now; live by 16 October | Renewal date and amount |
| 2 | Failed payment · only for people who have paid before | Now; live before 1 November | Billing portal link, 14-day Stripe retries, Stripe's own failed-payment email off on your go-live day |
| 3 | Trustpilot review · the campaign once, then the flow | Now; the flow once the campaign has gone out | The Trustpilot list with 10% held back |
| 4 | Trial users win-back · wave 1, 4,805 people, 50% off the first month | Now | Wave 1 list, the 50% first-month code |
| 5 | Trial cancellation flow · anyone who cancels a trial from now on, reusing the win-back emails | Now | Survey answer on the profile, segmented by answer |
| 6 | Subscription cancelled · the branch email when they press cancel, then "Your plan ends" 3 days before the plan ends | Now | Survey answer, plan end date, early-bird flag, an event when someone undoes a cancel, GAMER and FREEMONTH codes |
| 7 | Sign-up and trial started | Now | Sign-up event and source, installer link, trial end date |
| 8 | Abandoned checkout | Now; live when the event arrives | Checkout Abandoned event |
| 9 | After purchase · one email only | Now; turn it on once the paid event is redone | The paid event redone (71 of 159 recent payers were skipped); FAQ link |
Trustpilot, how it runs. Kamil sends one list: settled yearly and monthly payers, with a random 10% marked held back. Upload it as "Trustpilot · send" and "Trustpilot · held back" without changing consent, and set trustpilot_asked = true on everyone in both. Send yearly first, monthly a week later, leaving out anyone with a failed-payment email in the last 30 days. After 30 days we compare cancellations; if there's no lift, the held-back group gets it once. Then turn on the flow. No reward for a review, and don't filter by how happy anyone seems.
Subscription cancelled, how it runs. Triggered when they press cancel, not when the plan ends, with a 1-hour wait so the survey answer lands. Two emails per person: the email for their survey answer, then "Your plan ends on (date)" 3 days before the plan ends, with their code again if unused. Skip the second email if the plan ends within 4 days of cancelling. Exit if they pay or undo the cancel.
Trial users win-back, how it runs. About 21,000 people who tried Hypertune were suppressed and never unsubscribed. A list-triggered flow, about 1,000 unsuppressed a day, three emails offering 50% off the first month, a 50/50 split test of a short design against plain text, and non-clickers suppressed again at day 14. Stop a wave if bounces pass 2% or spam 0.1%. Kamil sends the lists and the discount code.
Links: Kamil posts every URL that goes into an email in one pinned Slack message, labelled by button. Build from that list only.
How to build: follow the build rules for sender, links, tracking, Smart Sending and transactional settings. Build every email from the design team's new templates, not the old designs. Put a test profile through every flow and send Vinson desktop and mobile screenshots before anything goes live.
Every Friday: what shipped, what's blocked and on whom, and hours used.