LIFECYCLE CASE STUDY

The product sends a signal. The email responds.

Foxy AI’s lifecycle work moved from email creative into subscription and transactional journeys, where event quality and reliable fallbacks mattered as much as the copy.

Selected milestones: August 2025–May 2026

LIFECYCLE CASE STUDY

Three decisions behind the work.

Selected milestones: August 2025–May 2026

01 · THE CONTEXT

The starting point

For a subscription product, a renewal, a plan change and a cancellation are different moments. Useful communication depends on recognising those moments and having the correct plan information available.

02 · THE WORK

The decisions behind the journey.

Develop the lifecycle creative

The project included onboarding, dormant-lead and churn creative. The shared Figma board became the reference for the email work.

Launch the transactional foundation

A May 2026 update confirmed transactional flows were live. Password reset remained pending because the required event was missing.

Use reliable fallbacks

Plan-change messages used generic wording while dynamic credits and plan variables were being resolved. The team also checked for duplicate transactional sends from other systems.

INSIDE THE DECISIONS

The message depends on the product event.

Foxy AI’s subscription communication needed to distinguish onboarding, a renewal, a plan change and cancellation. Each moment has different required information. The May launch of transactional flows established a working foundation, while the missing password-reset event remained a separate dependency.

For plan changes, the team used generic wording while dynamic plan and credit values were being resolved. That is a useful fallback when the email cannot yet rely on all its intended properties. The wording should remain accurate without guessing a balance, entitlement or plan detail that the source system has not supplied.

One event should have a clear communication owner.

The duplicate-send checks recognised that another system could already be messaging the same customer. A subscription programme needs agreement about which platform owns each notification, alongside the creative and event mapping. Otherwise one account change can produce conflicting or repeated instructions.

Build a small event map with the source signal, required properties, responsible message and fallback for missing information. Test renewals, changes and cancellations as separate scenarios. Treat the later retention and upsell work as a different phase, with paid activation and renewal measures of its own. Transactional implementation does not by itself establish reduced churn.

03 · THE OUTCOME

What the work delivered.

Transactional journeys were live by the May update, with remaining event and variable dependencies documented. The later retention and upsell roadmap was a proposed next phase, not a proven reduction in churn.

WHAT TO APPLY

Take the lesson into your own programme.

For every transactional message, define the source event, required properties and safe fallback. Verify that another platform is not sending the same message. Measure paid activation and renewal separately from email engagement.

Selected milestones: August 2025–May 2026. This case study covers the specific work described. Journey diagrams explain the approach.

QUESTIONS ABOUT THE WORK

What this case study shows.

What makes a subscription email useful after a plan change?

Foxy AI’s work included subscription and transactional journeys where product events and reliable fallbacks mattered. A renewal or plan-change message needs the correct state, clear next steps and a destination that works. Test the event payload and missing-data cases alongside the copy; a polished design cannot correct the wrong account state.

How do you verify that an automated customer journey actually works?

Test the path from the source event to the intended recipient and destination. Check the payload, customer state, eligibility, missing-data fallback and link after the click. Record creative approval, activation and observed delivery separately. A live switch alone does not establish that the right people receive the right message.

YOUR NEXT CHAPTER

What could your email programme do next?

Find the opportunities in your customer journey.

Browse all Thrivelia case studies

Discuss your customer journey with Thrivelia

Original campaign example

Explain the repeatable use case

The designed Foxy email builds one argument around a consistent creator identity. It moves from the problem to examples, then repeats a clear product action. This is a useful distinction for an AI subscription: the creative needs to explain how the product can become part of an ongoing workflow, as well as showing what it can generate once. The visual examples support the same theme throughout.

For SaaS and AI, measure the product action after the click: a completed creation, recurring use or an upgrade. Email engagement alone does not demonstrate activation.

Foxy AI · Original campaign email · 2026-05-31

Explore the service and a related guide

For a similar customer journey, explore our retention marketing services and the SaaS and AI lifecycle guide. Use the case's scope and measurement context to decide which lessons fit your account.

Review the available engagement scopes and pricing before choosing a delivery model.