Hi Gavin,
We're rebuilding all of Hypertune's email. Vinson has written every email, the design team is building three new templates, Kamil is sending the data Klaviyo needs, and you build and test everything in Klaviyo. Here is exactly what I need from you.
This week: account setup
Then build, in this order. Each link has the full copy, timing, trigger and build notes.
| # | Build | Target | Waiting on Kamil for |
|---|---|---|---|
| 1 | Failed payment · only for people who have paid before | Live before 1 November | Billing portal link, 14-day Stripe retries |
| 2 | Subscription cancelled and trial cancelled | Next two weeks | Survey answer on the profile, segmented by answer |
| 3 | Sign-up and trial started | Next two weeks | Sign-up event and source, installer link |
| 4 | Abandoned checkout | Draft now, live when the event arrives | Checkout Abandoned event |
| 5 | Yearly renewal reminder | Live by 15 November | Renewal date and amount |
| 6 | Trustpilot review campaign · subscribers past 31 days | Once the lists arrive | The two customer lists |
| 7 | After purchase · one email only | After 1 to 6 | Nothing |
Trial users win-back. About 21,000 people who tried Hypertune were suppressed and never unsubscribed. Build the win-back from the trial users report: a list-triggered flow, about 1,000 unsuppressed a day, three emails, a 50/50 split test of designed against plain, and non-clickers suppressed again at day 14. Confirm their original consent is still valid first. Stop a wave if bounces pass 2% or spam 0.1%. Kamil sends the lists and the discount codes.
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. Please send your hours estimate for all of the above before you start.
Thanks,
Austin