Updated: Nov 8
HISTORICAL RESULTS
Flows first. A reported 2.1× in monthly flow revenue.
Luxapolish’s historical account summary reports flow revenue moving from approximately $20,000 in May 2023 to $42,000 in August as the lifecycle programme expanded.
Historical reporting: May–August 2023
Brand imagery · Luxapolish
HISTORICAL RESULTS
reported monthly flow revenue
Historical reporting: May–August 2023
Email examples · Copy and message structure
Inside the emails.
Selected excerpts from the original production copy or email briefs, presented in a reading layout. Drafts and proposed messages are labelled.
Original production copy · excerpt
Your personal invitation to join us, {Name} 💅
Hi {Name},
I am Leah, the founder and passionate pioneer of Luxapolish.
I am delighted to personally invite you to join our thriving Luxapolish community on Facebook.
It's a space brimming with creativity, where nail techs like you share their exquisite designs, explore new techniques, and support one another in mastering the craft.
Original production copy · excerpt
Give the first purchase a community next step
A founder-led post-purchase draft moves the relationship into education and community participation.
Excerpts preserve the original wording. They show the message structure; they are not screenshots or proof of a send. Historical offers are shown as archive copy.
01 · THE CONTEXT
The starting point
The work started with flows while the client continued sending campaigns. Campaign management then expanded alongside the automation work. That sequence matters when interpreting the reported figures.
02 · THE PROGRAMME ARCHITECTURE
Recover the first order. Create reasons for the next one.
Luxapolish started with flows while the client continued sending campaigns. The programme then expanded into more customer moments before campaign management grew alongside it. These were successive layers of work, rather than one email redesign.
Capture existing intent
Initial flow phase
Welcome
Abandonment
Browse
Post-purchase
The core shopping journeys gave interested customers a defined follow-up before and after an order.
Make returning useful
Later retention scope
Replenishment
Loyalty
Shipping
Back-in-stock
Availability, order progress and the next purchase became distinct reasons to contact the customer.
Connect the calendar
Campaign expansion
Campaign management expanded alongside the automation programme. Seasonal peaks and later declines remained part of the account history.
The reported revenue progression below describes the account’s flow contribution. It does not isolate the effect of any one layer.
A community invitation gives post-purchase a different job.
The founder-led excerpt above invites nail technicians into Luxapolish’s Facebook community to share designs, explore techniques and support one another. Its next action is participation, rather than another immediate discount.
Four months show the progression.
The retrospective report lists approximately $20k, $23k, $38k and $42k in monthly flow revenue from May to August 2023. Keeping each month visible makes the reported 2.1× endpoint comparison more useful.
Programme layers come from the historical account summary; the community invitation is original production-copy evidence. The archive does not assign exact activation dates to every journey, and the copy excerpt does not establish a send or community-join result.
INSIDE THE DECISIONS
Recovery was the first layer, not the whole retention plan.
Luxapolish began with the familiar shopping moments: welcome, abandonment, browse and post-purchase. Later replenishment, loyalty, shipping and back-in-stock work gave the programme additional reasons to contact customers after the first order. That progression matters because recovering existing intent and creating a useful next-purchase conversation serve different purposes.
The client continued sending campaigns during the initial flow phase before campaign management expanded. A clear timeline lets a reader see which parts of the programme were changing together, rather than assigning the entire account history to one redesign.
A monthly progression tells more than one multiplier.
The recovered summary shows approximately $20k, $23k, $38k and $42k in flow revenue across May to August 2023. Keeping all four months visible shows how the reported contribution developed. It also retains the historical basis of the figures instead of presenting rounded retrospective reporting as a fresh raw-data export.
For the next review, compare the revenue trend with customer entries, the mix of active flows and wider trading conditions. Campaigns and seasonal peaks can change the opportunity available to automation. Use the 2.1× figure to describe the reported endpoints, then inspect the individual journey evidence before deciding which change deserves credit or further investment.
03 · THE OUTCOME
The figures, with their context.
The retrospective account report, written on 14 April 2024, lists approximately $20k in flow revenue for May 2023, $23k for June, $38k for July and $42k for August. August was about 2.1 times May. These rounded, historically reported figures describe platform-attributed flow revenue; they are not independently re-exported raw data, incremental revenue or profit.
August vs May 2023 · rounded historical figures. Revenue is platform-attributed, not incremental or profit. No store-wide financial totals are shown.
WHAT TO APPLY
Take the lesson into your own programme.
Separate the flow build from the campaign-management phase in your timeline. Show the monthly progression and label historical, rounded figures clearly. That makes the lesson useful without overstating attribution.
Historical reporting: May–August 2023. This case study covers the specific work described. Journey diagrams explain the approach.
QUESTIONS ABOUT THE WORK
What this case study shows.
What does Luxapolish’s 2.1× result compare?
A historical account summary reported monthly flow revenue rising from approximately $20,000 in May 2023 to $42,000 in August 2023 as the lifecycle programme expanded. This is a comparison of two reported months, not a controlled incrementality test or a whole-business growth claim. The implementation lesson is to build core journeys before expanding the retention programme.
Does attributed email revenue prove incremental profit?
No. Attribution assigns orders to a channel under a reporting model. It does not show how many orders would have happened without the messages. Assess the stated dates, baseline, channel overlap and wider store performance, then use margin data and suitable holdout tests when the decision requires an estimate of incremental profit.
YOUR NEXT CHAPTER
Connect product discovery to the next purchase.
Tell us about your products, customers and current lifecycle programme. We’ll discuss the priorities and scope that fit your business.


.png)
Comments