The Changelog
Everything your team
has tried. In one place.
Log every retention action your team takes — by date, store, tool, and tactic. So Leon never recommends what you've already done, and your team never loses track of what's been tried.
14 March 2026
Cancel flow update
US StoreTool: Loop Subscriptions
Function: Churn prevention
Added pause offer as first step in cancel flow. Presented to all subscribers attempting to cancel in months 2–4. Pause duration: 1 or 2 months. A/B test running against control (no pause offer).
28 February 2026
Klaviyo win-back sequence
CN StoreTool: Klaviyo
Function: Win-back
Launched 3-email win-back sequence for lapsed subscribers (cancelled 30–90 days ago). Emails at day 7, day 21, day 45 post-cancel. Subject line test running on email 1.
Retention teams try a lot of things.
Most of them get forgotten.
A new cancel flow goes live. A Klaviyo sequence runs for six weeks. A pause offer gets tested and quietly dropped. Three months later, no one can remember what was tried, when, or whether it worked.
The Changelog fixes this. Every action your team takes — logged in one place, tagged by store and tool, visible to everyone. So your retention history never lives only in someone's head.
How it works
Log it once. Everyone benefits.
Log an action in under 30 seconds
Every time your team implements a retention tactic — a new cancel flow, a Klaviyo campaign, a pricing test — log it in the Changelog. Date, store, tool used, retention function, and any notes about the setup. That's it.
Tag by store, tool, and retention function
Each entry is tagged so it's searchable and filterable. Connect it to the store it applies to, the tool you used (Loop, Klaviyo, Recharge, Solvpath, etc.), and the retention function it addresses — onboarding, churn prevention, win-back, pause flows, and more.
Your whole team sees the same history
No more asking 'did we already try this?' No more duplicate work between team members or agencies. The Changelog is shared across everyone with access to the store — one source of truth for what has been done.
Leon reads it before every recommendation
Before Leon generates any recommendation, he checks your Changelog. If you've already tried a tactic, he won't suggest it again. Every recommendation you get is something genuinely new and relevant to where your retention programme is today.
Why this matters for recommendations
Leon doesn't recommend
in a vacuum.
Most AI tools generate recommendations from your data alone. They have no idea what you've already tried — so they suggest the obvious things you tested six months ago and quietly dropped.
Leon is different. Before he recommends anything, he reads your Changelog. He knows your cancel flow launched in January. He knows you tested a pause offer in Q4. He knows Klaviyo is already handling your win-back sequence.
So what you get from Leon isn't a list of generic retention tactics. It's a shortlist of things you haven't tried yet, that are calibrated to your specific data, your brand profile, and where your retention programme actually is right now.
“I've looked at what you've already done. Here's what I'd try next.”
— Leon, after reading your Changelog
Who it's for
Built for retention teams of every shape.
Solo founders
When you're doing everything yourself, the Changelog keeps your retention history organised and makes sure Leon's recommendations always build on what you've already done — not repeat it.
In-house retention teams
Different people own different tools. The Changelog gives the whole team a shared view of what's live, what's been tested, and what's next — without a weekly sync just to stay aligned.
Agencies and consultants
Working across multiple brands? Log your work on each store as you go. When you hand off to a client or bring in another team member, the full history is already documented.
What a Changelog entry looks like
Straightforward to log. Powerful to have.
14 March 2026
Cancel flow update
US StoreTool: Loop Subscriptions
Function: Churn prevention
Added pause offer as first step in cancel flow. Presented to all subscribers attempting to cancel in months 2–4. Pause duration: 1 or 2 months. A/B test running against control (no pause offer).
28 February 2026
Klaviyo win-back sequence
CN StoreTool: Klaviyo
Function: Win-back
Launched 3-email win-back sequence for lapsed subscribers (cancelled 30–90 days ago). Emails at day 7, day 21, day 45 post-cancel. Subject line test running on email 1.
Every entry is visible to all team members with access to that store.
When teams use it
Every retention action worth logging.
Launching a new cancel flow
Log the date, the tool (Loop, Recharge, Solvpath), the step you added, and the offer. Leon won't recommend cancel flow changes until he has new data on how yours is performing.
Running a Klaviyo campaign
Log every sequence you activate — win-back, on-boarding, pause nudges. Know exactly which campaigns are live and which have already run, without digging through Klaviyo.
Testing a pricing change
Log the date the new pricing went live, the store it affects, and any notes on the setup. See the impact in your retention cohorts in the weeks that follow.
Start building your retention history today.
Available on all Eternly plans. Free to start.
Leon uses it from day one.