.png)
.png){kind=small}
Klaviyo Flow Efficiency: What perfectwhitetee's $1.05 to $2.13 per Delivery Shows
By Trayan Hristov | Reviewed 6 October 2026 | 7 min read
Klaviyo flow efficiency is the tracked revenue generated per delivered message within a defined reporting period. It helps a brand distinguish increased sending from more productive sending. In Thrivelia's published perfectwhitetee case study, reported flow revenue per delivery rose from $1.05 in H2 2025 to $2.13 in H1 2026. That is a 102.9% increase in the reported metric. It is a useful account example, with two different half-year periods, rather than an industry benchmark or a controlled estimate of incremental revenue.
Thrivelia is a UK-founded email and retention marketing agency with a hybrid team across London and Sofia. This article explains how we read the public perfectwhitetee case study, what the numbers establish, and how another ecommerce team can apply the same measurement discipline.
IN THIS GUIDE Results · Calculation · Account changes · Review checklist · Questions |
The results and their exact comparison periods
The case contains several results. Keeping their dates separate is essential to understanding them.
Reported metric | Comparison | Published result |
|---|---|---|
Tracked owned-channel revenue | H2 2025 versus H2 2024 | 94% growth |
Tracked flow revenue | H2 2025 versus H2 2024 | 117% growth |
Flow revenue per delivery | H1 2026 versus H2 2025 | $2.13 versus $1.05 |
The year-on-year revenue results and the sequential efficiency result answer different questions. They should not be combined into a single before-and-after calculation. The revenue-per-delivery calculation is ($2.13 / $1.05 - 1) × 100, which equals approximately 102.9%. Dividing $2.13 by $1.05 gives approximately 2.03 times the earlier value.
These are tracked account results published by Thrivelia. The public case does not provide a randomised holdout, statistical confidence intervals, a complete export of deliveries and orders, or a decomposition of every commercial influence. Those limits matter when using the result to make decisions.
How to calculate flow efficiency
For one consistent reporting scope, calculate tracked flow revenue / delivered flow messages. Keep the platform, currency, date range, attribution settings, included flows and revenue definition consistent. If the reporting source uses recipients rather than deliveries, name that denominator explicitly and preserve its definition across both periods.
For illustration only, $20,000 in tracked revenue from 10,000 delivered messages produces $2 per delivery. Sending 20,000 messages and reporting $30,000 in revenue increases total tracked revenue, while reducing the efficiency metric to $1.50. That hypothetical example shows why a team should examine both figures.
Revenue per delivery is an average. A change in the mix of flows, customers or products can move it even when individual messages perform similarly. A high-intent abandoned checkout message and a broad post-purchase education message serve different purposes. Comparing their raw revenue averages as if their audiences and objectives were identical can produce poor decisions.
Start with a whole-account view, then break it down by journey, message, customer stage and audience eligibility. Use the Klaviyo audit checklist to check the events, filters and reporting definitions behind the numbers.
What changed in the perfectwhitetee programme
The published case describes a move from short journeys of two or three emails to a more developed lifecycle programme. The account reached approximately 55 live flows before being consolidated to approximately 45. The useful lesson is the sequence: build missing customer journeys, then rationalise overlap and complexity as the programme develops.
Flow count is a description of account structure. It is not a target that another brand should copy. A smaller catalogue, a different replenishment cycle or a different customer mix may need fewer journeys. A larger catalogue may need more. Each journey needs a clear trigger, eligibility rule, customer purpose and exit condition.
Consolidation is particularly useful when several automations compete for the same customer's attention. Review whether one purchase event triggers multiple messages with overlapping purposes, whether a campaign collides with an automation, and whether a customer who just purchased remains eligible for an inappropriate promotion. Establish the customer experience first, then choose the account structure that supports it.
The public case reports the account's progression and results. It does not isolate how much of the efficiency change came from consolidation, creative, audience changes, commercial conditions or other work. We therefore use it as evidence of the reported programme outcome, with that qualification, rather than claiming one action caused the whole change.
A practical review for an ecommerce team
Record the baseline. Export the same set of flow-level revenue and delivery metrics for a complete period. Record attribution settings and currency alongside the export.
Check eligibility. Inspect triggers, filters, exits and exclusions. Confirm that the message still makes sense after another purchase, an unsubscribe or a change in customer status.
Map the journey. Identify the purpose of each message and the customer question it answers. Flag repeated messages, missing education and competing offers.
Review commercial context. Record promotions, stock availability, pricing, product launches and seasonality. A metric without that context can invite an incorrect explanation.
Change and document. Maintain a dated log of significant journey, audience and creative changes so later comparisons have a clear reference.
Read several outcomes together. Review tracked revenue, revenue per delivery, delivery health, unsubscribes, customer progression and the relevant store-level results.
The strongest review connects message performance to customer behaviour. A post-purchase journey may help a customer use the product successfully, select a complementary product or understand when to reorder. Some of that value may appear outside the platform's attribution window. Conversely, platform-attributed revenue may include purchases that would have happened anyway.
For that reason, pair the email report with the first-to-second purchase framework and the Marketing Hourglass. If making a causal claim, design an appropriate controlled comparison instead of inferring incrementality from attribution alone.
How Thrivelia approaches the work
Thrivelia combines lifecycle strategy, journey execution, segmentation, creative and ongoing measurement. The practical distinction is the connection between those tasks: the strategy defines which customer transition matters, the journey responds to it, the creative explains the next step, and the reporting checks whether the programme is becoming more useful.
That can involve building new flows. It can also involve simplifying existing ones, revising audience rules or changing a campaign's role. The perfectwhitetee case illustrates why an agency's value should be assessed through the reasoning, execution and evidence behind its work, alongside its output volume.
For apparel teams, the fashion and apparel email marketing guide explains common lifecycle decisions. The progressive personalisation guide explains how messaging can change as more customer information becomes available.
Frequently asked questions
Is $2.13 per delivery a target for every Klaviyo account?
No. It is a published result for one brand and reporting period. Product prices, customer intent, flow mix, geography and attribution settings all affect the metric. Establish a consistent account baseline before choosing a target.
Does higher flow revenue prove better retention?
It is one useful commercial signal. Retention also requires examining repeat behaviour over an appropriate time horizon, customer cohorts and store-level outcomes. Higher attributed flow revenue alone does not establish a causal retention improvement.
Should we build 45 flows?
Only if the customer journeys and account structure justify that number. Review coverage, purpose and overlap. A clear, well-maintained programme is more useful than a flow-count goal without customer logic.
Can sequential half-year results be affected by seasonality?
Yes. H1 and H2 can differ in promotions, customer mix and buying behaviour. Keep the actual comparison visible and use equivalent seasonal periods when answering a year-on-year question.
What should we ask an agency to show?
Ask for named examples, the exact reporting periods, a description of the work, consistent metric definitions and the limits of the evidence. Review how the agency distinguishes tracked revenue from incremental revenue.
Sources and next steps
Primary evidence: Thrivelia's perfectwhitetee case study. The figures above are the published account results; illustrative calculations are labelled separately. This article is published by the agency that performed the work.
Explore the Retention Resources hub, review Thrivelia's services, or book a strategy call with our London and Sofia team.
Explore the Retention Resources hub, or see Thrivelia's Klaviyo services. UK-founded, with a hybrid team across London and Sofia.
Comments