Marketing & Growth

How to build lifecycle email flows as CPG Founders

Marketing & GrowthFor CPG Founders3 apps11 steps~22 min to set up

You're running a CPG brand and your lifecycle email situation is a patchwork: a Klaviyo account you set up two years ago with four flows that haven't been touched since launch, a welcome series that still mentions a SKU you discontinued, and zero visibility into whether any of it is actually driving reorders. You know your LTV math depends on repeat purchases, but you're guessing at the right cadence for a consumable vs. a seasonal SKU. You don't have a retention marketer. You have yourself, 20 minutes on Tuesdays, and a Shopify export you never have time to segment properly.

Build this on Starch → See the apps used

Marketing & GrowthFor CPG Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A lifecycle email system that triggers flows based on real purchase behavior — first-time buyers, repeat buyers, lapsed customers — segmented by SKU category, not just order date

A weekly digest from Growth Analyst that tells you which flows are actually driving reorders and where drop-off is happening, so you stop guessing and start iterating

A CRM that tracks your wholesale and DTC contacts separately, with automated follow-up reminders so a promising retail buyer doesn't go cold because you forgot to reply

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 Growth Analyst Email Agent

Data sources & config

Starch connects directly to Gmail on a scheduled sync — pulling your inbox threads, labels, and send history to power both Email Agent triage and CRM contact syncing. Growth Analyst connects to PostHog from Starch's integration catalog, querying it live each time your weekly digest runs. Shopify is connected from Starch's integration catalog; the agent queries it live when the CRM needs to pull recent purchase history or flag lapsed customers. Klaviyo is connected from Starch's integration catalog; the agent queries it live to pull flow-level open and click data into your Growth Analyst digest.

Prompts to copy

Build me a CRM for my CPG brand that separates DTC customers from wholesale buyers. For DTC, track first purchase date, SKUs purchased, reorder status, and days since last order. For wholesale, track buyer name, retailer, territory, last order value, and whether they're a deduction risk. Flag any DTC customer who hasn't reordered in 60 days and any wholesale contact I haven't emailed in 30 days.

Build me a weekly email digest that pulls from PostHog and my Gmail data. I want to know: how many new DTC customers placed a first order this week, how many lapsed customers came back, which email flows drove the most attributed revenue, and what my 30-day reorder rate looks like by SKU. Send it to me every Monday at 7am.

Triage my inbox and draft replies for any email from a wholesale buyer or retail chain. Flag anything that looks like a deduction dispute, a reorder inquiry, or a new account request. Set a follow-up reminder on any buyer email I haven't replied to in 48 hours.

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

Walkthrough

Step-by-step

1 Connect Gmail to Starch as a scheduled-sync provider. This pulls your inbox, sent history, and labels into Starch so the CRM can match threads to contacts and Email Agent can triage without you forwarding anything manually.

2 Connect Shopify from Starch's integration catalog. The agent will query it live to pull order history, SKU-level purchase data, and customer records whenever your CRM or digest needs them.

3 Connect PostHog and Klaviyo from Starch's integration catalog. PostHog feeds your Growth Analyst digest with traffic and signup data; Klaviyo feeds it flow-level email performance so you can see open rates, click rates, and attributed revenue in one place.

4 Open the CRM starter app and describe your actual sales reality — DTC reorder tracking on one side, wholesale buyer pipeline on the other. Starch builds the schema to match how you actually work, not a generic HubSpot template.

5 Tell Starch to import your existing contacts: 'Pull all customers from Shopify who have placed at least one order, and all wholesale contacts from my Gmail threads with subject lines containing purchase order or net 30. Deduplicate and tag by channel.' Starch handles the messy import.

6 Set up your lapsed-customer flag: 'Every Sunday night, query Shopify for DTC customers whose last order was 55-65 days ago. Add them to a lapsed segment in the CRM and draft a reactivation email for each one that references the specific SKU they last bought.' This gives you a personalized reactivation queue ready Monday morning.

7 Configure the Growth Analyst weekly digest with your CPG-specific metrics: new DTC customers, reorder rate by SKU, Klaviyo flow performance, top referral sources. Tell Starch which numbers you care about and it builds the digest around them — not a generic marketing template.

8 Turn on Email Agent triage for your inbox. Tell it: 'Flag emails from retail buyers, distributors, and brokers as high priority. Summarize any thread longer than five messages. Draft a reply to any reorder inquiry that includes our current lead time and case pricing.' One-click send, not start from scratch.

9 Wire a follow-up automation: 'Every Friday, check my CRM for wholesale contacts I haven't emailed in 30 days and draft a short check-in email for each one. Put them in a review queue so I can approve before sending.' You stay in control; Starch does the drafting.

10 After two weeks, ask Growth Analyst to compare reorder rates before and after your lapsed-customer flow went live. Ask it: 'Which Klaviyo flows drove the most repeat purchases in the last 30 days, broken down by SKU category? Where is drop-off highest?' Use that to tell Starch what to adjust.

11 As your brand grows SKUs, update the CRM prompt to add new fields — shelf life window, whether the SKU is FBA or DTC-only, co-packer lead time — so your lifecycle emails can account for replenishment reality, not just calendar days since last purchase.

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

Reorder Recovery: 90-Day Lapsed Campaign, April 2026

Sample numbers from a real run

Lapsed DTC customers identified (55-70 days since last order)	214
Personalized reactivation emails drafted by Starch	214
Emails sent after founder review (approved 89%)	190
Customers who reordered within 14 days	38
Average reorder value ($)	62
Incremental revenue attributed to flow ($)	2,356

In early April, the CRM flagged 214 DTC customers who had bought once — mostly the 12-pack of the oat protein bars — and hadn't reordered in 55 to 70 days. Without Starch, these contacts would have sat in a Klaviyo segment that hadn't been updated since February. Instead, Starch queried Shopify for each customer's last SKU, drafted a reactivation email referencing that specific product ('Your oat bars running low?'), and put all 190 approved emails into a send queue by Monday morning. Growth Analyst's digest the following Monday showed a 20% open rate and 38 reorders — a $2,356 return on about 45 minutes of founder time. The digest also flagged that customers who had bought the 6-pack reordered faster than 12-pack buyers, which the founder used to set a tighter 45-day trigger for smaller bundle buyers going forward.

Measurement

How you'll know it's working

30-day and 90-day reorder rate by SKU (consumables vs. seasonal)

Lapsed customer reactivation rate (orders from 60-90 day lapsed segment)

Wholesale buyer response rate and days-to-reorder from last touchpoint

Klaviyo flow attributed revenue by lifecycle stage (welcome, reorder, lapsed)

Email reply time to wholesale buyers and deduction dispute threads

Comparison

What this replaces

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

Klaviyo alone

Klaviyo handles email sending well but doesn't give you a CRM for wholesale buyers, can't triage your inbox, and won't tell you in plain English which flows are working — you have to build all the dashboards yourself.

HubSpot Marketing Hub

HubSpot has the lifecycle tooling but costs several hundred dollars a month at the tier where it's actually useful, requires meaningful setup time, and doesn't connect your ops data — so your reorder triggers still won't know about shelf life or FBA lead times.

Mailchimp + spreadsheet CRM

Works fine for a 500-customer list but breaks down when you need to segment by SKU, track wholesale contacts separately, and correlate email performance with Shopify reorder data without manually exporting CSVs every week.

Attentive or Postscript (SMS-first)

Strong for SMS-led retention on high-frequency consumables, but if you're DTC + wholesale with a mixed buyer base, you still need an email layer and a CRM — you end up paying for both instead of one platform that handles the whole stack.

On Starch RECOMMENDED

One platform — crm, growth analyst, email agent 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 send the emails, or does it just draft them?

Starch drafts and queues emails via your connected Gmail account. You can set it up to send automatically for lower-stakes flows (like a lapsed-customer nudge) or put everything in a review queue where you approve before sending — your call per flow.

Can I use Klaviyo for sending and Starch for the intelligence layer?

Yes. Connect Klaviyo from Starch's integration catalog and the agent queries it live. Your Growth Analyst digest can pull Klaviyo flow performance alongside Shopify reorder data, so you get the analysis in one place even if Klaviyo is still doing the actual sends.

Will this work if my customer list is split between Shopify DTC and wholesale orders I track in a spreadsheet?

Yes. Tell Starch where each data source lives — Shopify for DTC orders (connected from the integration catalog), Google Sheets or a CSV for wholesale contacts — and describe how you want them unified in the CRM. Starch handles the import and deduplication.

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

Starch is not SOC 2 Type II certified today. That's worth knowing before you connect a large customer list. If your compliance requirements need SOC 2 Type II, that's an honest limitation right now.

Can Starch trigger a reorder email based on a product's shelf life window, not just days since purchase?

Yes, if you store the shelf life window as a field in your CRM or product data. Tell Starch: 'For SKUs with a 60-day shelf life, trigger a reorder email at day 45 post-purchase. For SKUs with a 90-day shelf life, trigger at day 70.' Starch builds the logic around whatever fields you define.

What about wholesale buyers who aren't in Shopify at all — brokers, distributors, regional chains?

The CRM handles them as a separate contact type. You can import from Gmail threads, a spreadsheet, or type them in manually. Set up a flow like: 'Flag any wholesale contact I haven't emailed in 30 days and draft a check-in.' It works without those contacts ever touching Shopify.

Is the email data stored in Starch or just queried when I need it?

Gmail syncs on a schedule and your message data lives in Starch's database, which is what powers the CRM thread history and Email Agent triage. Klaviyo and Shopify are queried live from the integration catalog — that data isn't stored in Starch between runs.