The first 90 days of Klaviyo retention work, week by week

Most Klaviyo accounts under-deliver because the architecture work was skipped on the way in. The flows exist, the campaigns send, the dashboard reports green, and the revenue percentage attributed to email plateaus at single digits. Lifting it past 30 percent of total revenue requires structural work in a specific order, shipped over the first 90 days of Klaviyo retention work. This is the order we run for ecommerce brands above 30k euro a month.

The problem is not effort. Most teams already send a welcome email, a cart abandonment sequence, and the occasional broadcast. They are diligent. What they are missing is the structural layer underneath the flows: the deliverability work, the segment architecture, the lifecycle map, the review cadence. Without that layer, every additional flow added on top compounds the surface area of a system that was never solid in the first place. Five edits in a quarter clustered on the welcome flow is a tell that the architecture, not the copy, is the thing that needs replacing.

What the first 90 days of Klaviyo retention work actually look like

A 90-day Klaviyo retention roadmap is not a content calendar. It is a sequenced rebuild of the program from the deliverability layer up, with the foundational lifecycle flows shipped in priority order so that revenue starts compounding inside the first two weeks. The order matters more than the speed. A brand that ships six flows in week one without fixing the sender domain will see worse numbers than a brand that ships zero flows in week one and spends the time on SPF, DKIM, DMARC, and a list-hygiene pass.

The work splits into four blocks. Week one is foundation. Weeks two to five build the high-leverage lifecycle flows that drive most of the early revenue lift. Weeks six to eight layer in the secondary flows that catch the audiences the first set misses. Weeks nine to twelve add the seasonal lane, the A/B testing layer, and the operating cadence that keeps the program compounding after the engagement ends.

The output, by week 12, is a program that is structurally complete. Six lifecycle flows running, deliverability sound, segments clean, a weekly review cadence in place, and revenue attributed to Klaviyo running between 25 and 40 percent of total brand revenue. That is the published outcome band for this engagement. Per-brand specifics live on the brand side of the wall.

Who this roadmap is for

This is built for ecommerce brands past roughly 30k euro a month in brand revenue, with at least one product category that supports repeat purchase. Below that threshold the math is different. Above it, the structural work pays back inside the first 30 to 60 days because there is enough purchase volume to give the post-purchase and replenishment flows real signal to work with.

The brands that get the most out of this roadmap have the same shape: a working ecommerce stack, a list of at least 10k engaged subscribers, a real product story, and an operator who can give a 30-minute weekly review the priority it deserves. The roadmap does not require a Klaviyo specialist on the brand side. It requires an operator who can decide.

Why the order is non-negotiable

Skipping week one to ship flows is the single most common failure mode. The flows then send into a compromised inbox, the open rates lag the benchmarks, the team blames the copy, the copy gets rewritten, the rewritten copy lands in the same compromised inbox, and the program plateaus. Three months later the brand decides email does not work for them. The flows were fine. The deliverability layer underneath was not.

Week 1: audit and deliverability

Before any flow gets touched, the deliverability layer has to be sound. That means SPF, DKIM, and DMARC alignment on the sending domain, a dedicated subdomain for marketing sends, and a list-hygiene pass that suppresses bounced addresses and segments unengaged for more than 90 days. A clean send domain with a decent reputation is what makes everything that comes after it actually land in the inbox.

The audit also surfaces what is already in place. If a brand has working Welcome and Abandoned Cart flows that perform, those stay. The 90-day work supplements existing infrastructure rather than replacing it. The output of week one is a single document: the deliverability score, the list-hygiene state, the inventory of existing flows with a keep or rebuild verdict on each, and the priority order for weeks two onward.

The deliverability checklist

SPF record published with the right ESP and any additional senders authorised. DKIM keys generated and published per sending subdomain. DMARC policy published, started at p=none for diagnostic visibility, ramped to p=quarantine once alignment is clean. A dedicated subdomain like send.brand.com or mail.brand.com isolated from the transactional sender so a marketing complaint spike cannot pollute receipts. Suppression rules in Klaviyo set so anyone who has not opened in 90 days is excluded from broadcast sends until they re-engage. None of this is glamorous. All of it is what makes the flow numbers move when the flows ship in week two.

What the audit captures

The pre-existing flow inventory, with screenshots and sample renders. The current revenue split: how much of total brand revenue Klaviyo is attributing this month, and what proportion comes from broadcasts versus flows versus campaigns. The list health: total subscribers, engaged in the last 30 days, engaged in the last 90, and the long tail. The segment map: which segments exist, which are populated, which are stale. The audit document is the contract for the next 11 weeks.

Weeks 2 to 3: Welcome and Abandoned Cart

The Welcome flow is the first revenue lever and the easiest to instrument. Three to five emails over 14 days, segmented by acquisition source where the data supports it. The interesting variable is timing rather than content. Brands that send the first welcome inside an hour of signup outperform brands that wait four hours by a measurable margin. The first message is not the place to discount. It is the place to introduce, set expectations, and make a soft offer that frames the brand voice for everything that follows.

Abandoned Cart is the second-easiest revenue lever. Three messages over 48 hours, with a real reason in each. The first message recovers users who genuinely got distracted; the second handles objections; the third is a soft last call. Stacking a discount in every message trains the audience to wait, which depresses unconverted-cart revenue at the customer-lifetime level. Most brands lose more by over-discounting cart abandonment than they ever lose to actual abandonment.

Welcome flow structure

Email one inside 60 minutes of signup, content-led with a soft conversion. Email two on day two, expanding the brand story or the founder reason. Email three on day five, with the first concrete commercial offer if it fits the category. Email four on day nine, social proof or a use case. Email five on day 14, the soft close. Segmented by source where the volume supports separate variants: paid social, organic, referral, and existing-customer signup all behave differently in the first 14 days.

Abandoned Cart structure

Email one at 90 minutes after abandonment, simple reminder, no discount, link back to the cart. Email two at 24 hours, objection handling, FAQ, sometimes a free shipping nudge if the cart sits below the free shipping threshold. Email three at 48 hours, soft last call. The discount, if it appears at all, lives in email three only and is positioned as a thank-you for completing rather than a recovery incentive. The framing matters because the audience reads it.

Weeks 4 to 5: Post-Purchase and Replenishment

Post-Purchase is where most retention programs leave money on the floor. Three to four messages between order and 90 days post-delivery: shipping confirmation that does more than confirm, a use case that makes the product land, a reorder reminder when relevant, a soft cross-sell when the catalogue supports it. Brands without this flow lose roughly one in five repeat purchases that the customer was already willing to make. The customer is in the highest-intent window of the entire lifecycle and the brand stops talking to them.

Replenishment is the post-purchase variant for consumables. The cadence is product-class-specific: coffee runs at three weeks, supplements at 30 days, skincare at six weeks, cleaning products at eight to ten weeks. Getting the cadence wrong trains the audience to ignore the brand. Replenishment timing should be set per SKU class, not per brand, because the same brand often sells products with very different consumption rates.

What the Post-Purchase flow ships

Order confirmation email that does triple duty: confirms, sets the unboxing expectation, and starts the relationship. Day-three usage email tied to the specific SKU purchased, content-only, no commercial ask. Day-14 reorder or cross-sell email keyed off the catalogue logic. Day-45 review request with a real ask, framed as helping the next customer. Day-90 win-back trigger if no second purchase has happened. Five touches over three months, none of them spammy because each one earns its place.

Replenishment cadence by category

Coffee at 21 days. Supplements at 30 days. Skincare at 42 days. Pet food at 28 days. Household consumables at 60 to 75 days. The first replenishment email lands roughly five days before predicted depletion, the second on or around the depletion date, and the third only if the customer has not reordered seven days past depletion. Three messages total, not five, because the cost of over-emailing this segment shows up as unsubscribes on the most valuable customers.

Weeks 6 to 8: VIP, Win-Back, and Browse Abandonment

VIP segmentation builds a top-decile audience that gets first access to drops and limited inventory. The flow itself is light: one quarterly thank-you, one early-access drop, one occasional gift. Over-emailing the VIP segment is what breaks them. The trap is that brands look at the VIP segment, see the high revenue per subscriber, and decide to email them more. Doing that converts the VIP segment from a top-decile asset into a churned former asset inside one quarter.

Win-Back targets customers between 60 and 180 days post-purchase who have not re-ordered. Two messages, 14 days apart, with a reason to come back that is not always a discount. Discounts work, but a new product launch, a category-relevant content piece, or a reactivation gift work better at the customer-lifetime level. Browse Abandonment fills the gap between site visit and abandoned cart. Open rates run high and click rates moderate. Revenue attribution lands at three to six percent of program revenue, which is meaningful given how cheap the flow is to build.

VIP entry criteria

Two qualifying paths in most categories. Path one: lifetime spend above the brand-specific top-decile threshold. Path two: three or more orders inside the last 12 months at any spend level. Either qualifies. The segment is reviewed monthly and people drop out gracefully, not abruptly, when they no longer qualify. Quiet exit is what keeps the segment trustworthy.

Browse Abandonment guardrails

Cap the flow at two emails. Suppress anyone who has bought in the last 14 days. Suppress anyone in the active Abandoned Cart flow. Trigger only when the browse signal is meaningful: viewed a product detail page, spent more than 30 seconds, or viewed three or more PDPs in one session. Do not trigger on a homepage view. The guardrails are what keep the open and click rates high enough to make the flow worth running.

Weeks 9 to 12: seasonal lane, A/B layer, weekly review cadence

By week nine the foundational flows are in production. The next layer adds the seasonal lane (BFCM, key drops, peak windows) and a lightweight A/B testing layer on subject lines and hero treatments. The A/B layer exists to confirm what already works against what could replace it. Most A/B tests confirm rather than overturn. That is fine. The discipline of running them is what builds the institutional memory the program compounds against.

The weekly review cadence is what keeps the program compounding after the engagement ends. One 30-minute look at revenue per inbox-placed send, list growth, unsubscribe rate, and the bottom three segments by performance. Adjust the bottom three; the top three usually take care of themselves. The review is not a meeting. It is a focused operator session, ideally on the same day each week, with the same dashboard view, with one decision per low-performer.

The seasonal lane

Built once, reused every year. BFCM gets its own multi-week ramp with pre-pre-Black Friday teaser, Black Friday early access for VIPs, the main BF send block, the Cyber Monday block, and the post-event last-call. Spring and summer drops get their own lighter ramps. The seasonal lane is not improvised in November. It is documented in October at the latest and the playbook gets versioned every year so the brand actually learns from one season to the next.

What the weekly review looks at

Revenue per inbox-placed send, week over week. List net growth, gross signups minus unsubscribes minus suppressions. Unsubscribe rate by source so a single bad send does not sink the average. Segment performance ranked, with the bottom three flagged for action. Flow-level revenue split so a regression in one flow is visible inside seven days, not 90. Thirty minutes is enough if the dashboard is built once and reused weekly.

Worked example: an illustrative ramp

This is illustrative, not a case study. Suppose a brand at 30k euro a month is converting 8 percent of revenue through Klaviyo when the engagement starts. Week one ships the audit and the deliverability fix, no flow changes. By the end of week three the welcome and cart flows have replaced the existing ones. Revenue from email moves into the mid-teens by the end of week four because the welcome capture rate roughly doubles and the cart recovery rate moves with it.

Weeks four to eight ship the post-purchase, replenishment, VIP, win-back, and browse flows in priority order. The post-purchase flow is the inflection. Repeat purchase rate inside 90 days lifts because the flow exists where there was none. By end of week eight, revenue from Klaviyo is in the mid-20s percent. Weeks nine to 12 layer the seasonal lane and the review cadence on top. The brand exits the engagement somewhere in the 25 to 40 percent band, which is the published outcome range. Where they land inside the band depends on category, list size, and the operator review cadence post-engagement.

The 12-week runbook

1. Run the deliverability audit and the existing-flow inventory in week one. Ship the SPF, DKIM, DMARC, and subdomain isolation work. Suppress unengaged segments older than 90 days. 2. Ship the rebuilt Welcome flow in week two and the rebuilt Abandoned Cart flow in week three. Segment Welcome by source where the volume supports it. 3. Ship the Post-Purchase flow in week four. Configure the cadence per SKU class. 4. Ship the Replenishment flow in week five for any consumable category. Set cadence per product class, not per brand. 5. Ship VIP, Win-Back, and Browse Abandonment across weeks six to eight. Set guardrails on each before they go live. 6. Build the seasonal lane in week nine. Document it once and version it annually. 7. Ship the A/B testing layer in week 10 on subject lines first, then hero treatments. 8. Stand up the weekly 30-minute review in week 11 and run the first one with the operator in week 12 so the cadence outlives the engagement.

When this roadmap is wrong

Brands below the 30k euro a month threshold often do better with a smaller, three-flow program than with the full six. The math on the secondary flows is thin when monthly order volume is low, and over-architecting at small scale builds maintenance debt the operator cannot service. Brands without a real repeat-purchase story will see the post-purchase and replenishment flows underperform regardless of how well they are built, and the program will plateau in the mid-teens percent. That is a product problem, not a Klaviyo problem.

Brands with an existing strong program (already past 25 percent of revenue from email at engagement start) get a different version of this work, focused on the segment architecture, the seasonal lane, and the review cadence rather than the foundational flow rebuild. The 90-day roadmap as written assumes the foundation needs replacing. It usually does. When it does not, the engagement reshapes around what is actually missing.

What success looks like

Across the brands we run this for, total revenue attributed to Klaviyo lands between 25 and 40 percent within three months, with the first measurable uplift inside 10 to 14 days. Per-week or per-client deltas stay on the brand side of the wall. The qualitative markers matter too: the operator runs the weekly review without a strategist in the room, the deliverability layer holds without monthly intervention, and the seasonal lane is documented so the next BFCM does not start from zero.

The outcome band is the published one because we have run this program enough times to know where the work lands. The variance inside the band is mostly category, list size at engagement start, and how disciplined the weekly review stays after the engagement ends. The brands that sustain the cadence stay in the upper half of the band. The brands that do not regress toward the lower half over the following two quarters.

FAQ

How long until we see the first revenue lift from a Klaviyo retention rebuild? The first measurable uplift typically lands inside 10 to 14 days, driven by the rebuilt Welcome and Abandoned Cart flows shipping in weeks two and three. The structural lift to 25 to 40 percent of revenue takes the full 90 days because the post-purchase and replenishment flows need a few cycles of customer data to calibrate.

Why is week one not building flows? Because flows shipped onto a compromised sender domain underperform regardless of how well they are written. SPF, DKIM, DMARC alignment plus a dedicated marketing subdomain plus list hygiene is what makes the inbox-placement rate high enough for the flows to do their job. Skipping week one usually costs more than it saves.

Do we need a dedicated Klaviyo specialist on our side to run this? No. The 90-day roadmap is run by a senior strategist on the Arthea side. Brand-side, what is needed is an operator who can give the 30-minute weekly review real attention and decide on the bottom three segment actions each week. The cadence is small but it is the thing that makes the program compound.

What happens after week 12? The weekly review cadence carries the program. The flows are stable, the seasonal lane is documented, and the A/B layer is in place. Most brands move to a lighter monthly cadence with the strategist for ongoing review and for the seasonal ramps. The structural rebuild is a 90-day engagement; the maintenance is a different shape of work.

How does this connect to CRO and content work? The retention layer compounds with the CRO and content layers when they are run as one program. Brief-sharing across the three surfaces is the mechanic. See the companion piece on the retention, CRO, and content compound for how the three programs reinforce each other.

Read more

- The retention, CRO, and content compound effect: https://www.arthea.ai/article/retention-cro-content-compound - The deliverability work that comes before any retention flow: https://www.arthea.ai/article/deliverability-before-flows - Email and SMS retention engagements: https://www.arthea.ai/email-and-sms

If you want a 30-minute architecture review on Klaviyo for your brand, the calendar is here: arthea.ai/book.