Marketing & Growth

How to build lifecycle email flows as DTC Brand Founders

Marketing & GrowthFor DTC Brand Founders3 apps12 steps~24 min to set up

You built your lifecycle emails in Klaviyo — welcome series, post-purchase, win-back — and they were working fine until your SKU mix changed and your flows started recommending products you'd sold out of weeks ago. Your Shopify purchase data doesn't automatically update your Klaviyo segments, so you're manually exporting CSVs, re-uploading lists, and praying the timing is right. Your post-purchase sequence doesn't know whether someone bought a hero product or a slow-mover. Your win-back flow fires on everyone equally, regardless of margin contribution. You have the data to do this properly — it's just in five different places and none of it talks to the other.

Build this on Starch → See the apps used

Marketing & GrowthFor DTC Brand Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A lifecycle email system where Shopify purchase history, product margins, and Klaviyo engagement data feed into a single Starch view — so your flows are always firing based on current inventory and actual customer value, not stale exports.

An automated weekly digest that flags which email flows are underperforming, which segments have gone cold, and which product categories are driving repeat purchases — delivered to your inbox before Monday morning.

A customer profile layer in Starch that ties together order history, email engagement, support threads, and LTV — so when you're deciding who to target with a reactivation campaign, you're working from one number, not three conflicting ones.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Email Agent Growth Analyst

Data sources & config

Starch connects to Shopify from its integration catalog — the agent queries your orders, products, and customer records live when your CRM or automations run. Gmail is a scheduled-sync provider — Starch syncs your inbox on a schedule for email triage and follow-up tracking. Klaviyo is reachable from Starch's integration catalog for live campaign and list data. PostHog syncs on a schedule for the Growth Analyst weekly digest. Any email platform without a direct API connector — including niche ESPs — can be automated through your browser with no API needed.

Prompts to copy

Build me a customer CRM that tracks Shopify order history by SKU, total LTV, last purchase date, and Klaviyo engagement status. Flag any customer who's bought more than twice but hasn't opened an email in 60 days.

Every Monday, email me a lifecycle email performance summary: which flows had the lowest open rates last week, which segments are due for a re-engagement push, and which products appear most in abandoned cart emails but have low conversion.

Draft a re-engagement email for customers who bought our top-selling SKU 90+ days ago, haven't purchased since, and opened at least one email in the last 6 months. Pull their first-name and first product from my Shopify data.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Shopify from Starch's integration catalog. The agent queries your orders, products, customers, and refund data live whenever a flow or CRM view needs it.

2 Connect Gmail as a scheduled-sync provider so Starch pulls your inbox on a schedule — this feeds the Email Agent with incoming customer replies and support threads, not just campaign analytics.

3 Connect Klaviyo from Starch's integration catalog so the agent can pull live segment membership, campaign open rates, and flow enrollment status when building customer profiles.

4 Start the CRM app and tell Starch: 'Build me a customer view that shows Shopify LTV, number of orders, most recent SKU purchased, and Klaviyo engagement status — high/medium/cold — for each customer.' Starch builds the schema from your description.

5 Add a computed field for margin contribution: 'Add a column that multiplies each customer's order count by the average margin of the SKUs they've bought, pulling product margin data from my Shopify catalog.'

6 Set up the Email Agent on your Gmail inbox. Tell it: 'Triage incoming customer emails by priority — order issues and refund requests first, general questions second, marketing replies third. Draft a reply for anything that looks like a refund request, pulling the customer's order details from Shopify.'

7 Set up the Growth Analyst app with PostHog connected on a schedule. Tell it: 'Every Monday at 7am, email me a summary of which lifecycle email flows drove the most site visits last week, which product pages had the highest conversion after an email click, and which customer segments are underperforming vs the prior week.'

8 Build a win-back automation: 'Every Sunday night, find customers in my Shopify data who purchased 75–120 days ago, haven't ordered since, and have an LTV above $150. Pull their first name and last product, then draft a personalized re-engagement email and add them to a Starch task list for review before sending.'

9 Build a post-purchase flow trigger: 'When a new Shopify order comes in for any product in the "hero SKU" collection, create a CRM note on that customer, flag them for a 14-day follow-up email, and draft that email using their order details.'

10 Set up an inventory-aware filter: 'Before any lifecycle email automation runs, check Shopify inventory for the recommended product. If stock is below 20 units, swap the recommendation to the next best-selling in-stock item from the same category.'

11 Build a weekly refund-to-segment feedback loop: 'Every Friday, pull all refunds processed this week from Shopify, tag those customers in my CRM as "churned — refund," and remove them from any active win-back or loyalty flow segments.'

12 Review the Monday Growth Analyst digest and use the CRM to identify your top 100 LTV customers who haven't been emailed in 30 days — then tell the Email Agent: 'Draft a VIP early-access email for this segment, referencing their purchase history and offering first look at our next product drop.'

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Spring Reactivation Push — April 2026

Sample numbers from a real run

Win-back segment (90-day lapsed, LTV > $150)	847
Opened re-engagement email	214
Clicked through to site	89
Purchased within 7 days	34
Revenue recovered	6,120

In early April, the Growth Analyst weekly digest flagged that the win-back flow had dropped to a 9% open rate — down from 18% two months prior. Digging into the CRM view, the problem was obvious: the flow was recommending a SKU that had been out of stock for three weeks. Starch's inventory-aware filter hadn't been set up yet. After adding the check ('before any win-back email fires, confirm the recommended product has more than 20 units on hand — otherwise substitute the next best-seller in the same collection'), the next batch of 847 lapsed customers got a flow that actually led with something they could buy. 214 opened. 89 clicked. 34 purchased in the first 7 days, at an average order value of $180, recovering $6,120 in revenue that would have sat dormant. The Email Agent also flagged 12 customer replies to the campaign that were refund requests or sizing complaints — drafting replies for each within the hour, pulling order details from Shopify automatically.

Measurement

How you'll know it's working

Lifecycle email revenue as % of total monthly revenue (target: 25–35% for healthy DTC)

Win-back flow conversion rate by LTV tier ($50–100 vs $150+ customers convert very differently)

Post-purchase email open rate by SKU category (hero products vs slow-movers)

Days between last purchase and first re-engagement email (shorter = better retention signal)

Refund rate among customers who received a lifecycle recommendation email vs those who didn't

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Klaviyo alone

Klaviyo sends the emails but doesn't give you a unified customer view — your segment logic lives inside Klaviyo's UI and doesn't know about margin, inventory levels, or what your support inbox is seeing at the same time.

Klaviyo + Shopify + manual Google Sheets segment building

This is what most DTC founders do, and it works until the SKU count grows — then the manual export-reimport cycle eats 3–4 hours a week and the segments are always slightly stale.

Yotpo or Attentive

Solid for SMS and loyalty programs, but you're adding another platform with its own login and another monthly bill — and it still doesn't give you a single customer record that connects email behavior to order history to support threads.

Postscript + Klaviyo + Triple Whale

Triple Whale solves the attribution problem but not the workflow problem — you still have to manually act on what it shows you, and the setup cost for three platforms plus their integrations is significant for a sub-10-person team.

On Starch RECOMMENDED

One platform — crm, email agent, growth analyst all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually connect to Klaviyo, or do I need to export CSVs?

Klaviyo is reachable from Starch's integration catalog — the agent queries your segment membership and campaign data live when an automation runs. No CSV exports. If you're on a less common ESP, Starch can also automate it through your browser with no API needed.

Will Starch store all my customer purchase history, or is it just querying live?

Shopify is queried live from the integration catalog — meaning the agent pulls current data when your flows run, rather than keeping a persistent copy in Starch. If you need a long-horizon data warehouse with years of archived transaction history, Starch isn't the right fit for that specific use case. For active lifecycle email workflows and customer segmentation based on recent behavior, live querying is exactly what you want.

Can Starch actually check inventory before sending a product recommendation email?

Yes — that's a first-class pattern. Since Shopify is connected from the integration catalog and queried live, you can tell Starch: 'Before this email automation fires, check that the recommended product has more than X units in stock. If not, substitute the next best-seller in the same category.' The agent runs that check each time.

What about my existing Klaviyo flows — do I have to rebuild them?

No. Starch isn't replacing Klaviyo as your sending platform — it's adding the customer intelligence layer and workflow automation that Klaviyo doesn't have on its own. Your existing flows keep running. Starch handles the segmentation logic, the CRM-level view, the inbox triage, and the weekly performance digest.

Is Starch SOC 2 certified? I'm cautious about connecting customer data.

Not yet — Starch is not SOC 2 Type II certified today. If that's a hard requirement for your brand (especially if you're processing healthcare or financial data), that's worth knowing upfront. For most DTC brands handling purchase history and email engagement data, this is a practical consideration rather than a blocker, but it's your call.

How long does it take to get the first lifecycle flow running?

Connecting Shopify and Klaviyo from the integration catalog takes minutes. Describing the CRM schema and win-back automation in plain language to Starch takes another 20–30 minutes the first time. Most operators have their first working customer view and one automated flow live within a couple of hours — without writing a line of code or waiting for an engineer.