.png)
.png){kind=small}
Updated: 12 hours ago
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
HISTORICAL RESULTS
reported monthly flow revenue
Historical reporting: May–August 2023
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 WORK
The decisions behind the journey.
Start with core shopping journeys
The historical summary records welcome, abandonment, browse and post-purchase work during the initial flow phase.
Add reasons to return
Later work covered replenishment, loyalty, shipping and back-in-stock journeys. These extended the programme beyond recovering a first order.
Connect campaigns to the foundation
The account then combined campaign and flow work. Later periods included seasonal peaks and declines, so the story is not a claim of straight-line growth.
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
What could your email programme do next?
Find the opportunities in your customer journey.
Comments