Intern
What you actually do
Day one: everyone gets everything — that is the leak. Write RFM buckets. Write VIP. Write suppressions. Do not buy AI clustering. A segment you cannot explain is a mood.
Everyone gets everything. VIP is a feeling. Suppressions are a single unsubscribe. Campaigns use the full list because it is easier.
Read it once, then stop negotiating with it. Klaviyo segmentation for DTC brands is a wiring job: grid → vip → layers → campaigns. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
DTC brands do not have a Klaviyo segmentation problem because they lack Klaviyo. They have it because everyone gets everything.
Wire these objects first: RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required.
Then these edges, in order: RFM (recency, frequency, monetary) → named segments you can explain · VIP → definition in dollars/orders/time; not 'people we like' · Suppressions layered → unsub, never-engage, recent purchasers as appropriate · Campaign send → uses a segment; 'all subscribers' is an exception with a reason
Done looks like a test you can repeat: Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names.
Start here: RFM or equivalent exists
DTC brands already have Klaviyo. The leak is not a missing feature. Everyone gets everything. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required. Then connect these edges, in order: RFM (recency, frequency, monetary) → named segments you can explain · VIP → definition in dollars/orders/time; not 'people we like' · Suppressions layered → unsub, never-engage, recent purchasers as appropriate · Campaign send → uses a segment; 'all subscribers' is an exception with a reason. If you skip an edge, the next one is decoration. If you add a Klaviyo feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names. How you know it worked on the board: Full-list sends is rare (or fatigue is earned). If that number is a vibe, do not add traffic.
What to do this week, and only this week: RFM or equivalent exists An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: everyone gets everything — that is the leak. Write RFM buckets. Write VIP. Write suppressions. Do not buy AI clustering. A segment you cannot explain is a mood.
Operator
You already feel everyone gets everything. Everyone gets everything. Protect one sequence for 90 days. The four moves are grid → vip → layers → campaigns. The edges are RFM (recency, frequency, monetary) → named segments you can explain then VIP → definition in dollars/orders/time; not 'people we like'. RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments.
CEO
This is a money leak, not a preference about tools. Everyone gets everything. Until full-list sends is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: RFM (recency, frequency, monetary) → named segments you can explain.
Before
Tuesday. Someone among DTC brands. Everyone gets everything. Klaviyo is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments. RFM (recency, frequency, monetary) → named segments you can explain The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in DTC brands already paid for Klaviyo. Everyone gets everything. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. RFM or equivalent exists. Prove write-in: Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names. This week is one move: RFM or equivalent exists If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Everyone gets everything. VIP is a feeling. Suppressions are a single unsubscribe. Campaigns use the full list because it is easier.
The system
RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments.
Recency, frequency, monetary — or a simpler grid you will actually keep. Best buyers should not get the same 15% as a 2022 one-time. That is how you train your best people to wait.
Layer suppressions: bought recently, in a flow, complained, sunset, in-conversation. Unsubscribe is the floor, not the system.
RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments.
Everyone gets everything when campaigns use the full list. RFM or an equivalent is enough: who bought recently, who buys often, who spends. VIP is defined. Suppressions are layered so you do not have one mega-filter nobody understands. Campaigns use segments. Predictive tools are optional; they are not a substitute for a definition you can audit.
Wire properties that make segments true: last order date, order count, revenue, preferred category if you have it. If those properties are stale, the segments are theatre. Flows still own state; segments feed campaigns and some flow filters. Do not build twenty micro-segments you will not send to. Five that are used beat twenty that are pretty.
Two databases: Shopify tags 'VIP' and Klaviyo VIP with different thresholds. One definition. The intern documents the definition and samples ten profiles per segment. Misfiles become property bugs. If marketing wants 'all subscribers because it's a brand moment', brand moment is still a segment (engaged 90 days, for example) or it is a deliverability incident wearing a cape.
RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required.
RFM (recency, frequency, monetary) → named segments you can explain
VIP → definition in dollars/orders/time; not 'people we like'
Suppressions layered → unsub, never-engage, recent purchasers as appropriate
Campaign send → uses a segment; 'all subscribers' is an exception with a reason
Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names.
Day one: everyone gets everything — that is the leak. Write RFM buckets. Write VIP. Write suppressions. Do not buy AI clustering. A segment you cannot explain is a mood.
RFM or equivalent. Simple enough to run.
Defined in numbers, not vibes.
Suppressions stacked. Not one toggle.
On segments. Full list is a last resort you regret.
On one line, for DTC brands: Everyone gets everything. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
RFM or equivalent. Simple enough to run. Then wire: RFM (recency, frequency, monetary) → named segments you can explain
Why: DTC brands cannot skip this edge. Everyone gets everything when campaigns use the full list. If it is not true, Klaviyo is already a second database.
Done when: RFM (recency, frequency, monetary) → named segments you can explain is true on a test.
Defined in numbers, not vibes. Then wire: VIP → definition in dollars/orders/time; not 'people we like'
Why: DTC brands skip this and the leak returns as a private language. Wire properties that make segments true: last order date, order count, revenue, preferred category if you have it. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: VIP → definition in dollars/orders/time; not 'people we like' is true on a test.
Suppressions stacked. Not one toggle. Then wire: Suppressions layered → unsub, never-engage, recent purchasers as appropriate
Why: DTC brands feel this as Everyone gets everything. Two databases: Shopify tags 'VIP' and Klaviyo VIP with different thresholds.
Done when: Suppressions layered → unsub, never-engage, recent purchasers as appropriate is true on a test.
Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Full-list sends (Or fatigue is earned), then vip (In numbers). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
RFM or equivalent exists
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required.
If objects aren't named, software invents a second database.
Everyone gets everything.
RFM or equivalent. Simple enough to run. Then wire: RFM (recency, frequency, monetary) → named segments you can explain
DTC brands cannot skip this edge. Everyone gets everything when campaigns use the full list. If it is not true, Klaviyo is already a second database.
On Klaviyo, this means the data model matches how DTC brands actually work — not the snapshot demo. Edge: VIP → definition in dollars/orders/time; not 'people we like'
Defined in numbers, not vibes. Then wire: VIP → definition in dollars/orders/time; not 'people we like'
DTC brands skip this and the leak returns as a private language. Wire properties that make segments true: last order date, order count, revenue, preferred category if you have it. Spec tags, fields, and states have to be the same objects the next workflow will read.
RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments.
Suppressions stacked. Not one toggle. Then wire: Suppressions layered → unsub, never-engage, recent purchasers as appropriate
DTC brands feel this as Everyone gets everything. Two databases: Shopify tags 'VIP' and Klaviyo VIP with different thresholds.
RFM or equivalent exists
Because the login already exists. Everyone gets everything. VIP is a feeling. A new feature on a missing spec is a second database. Finish this edge first: RFM (recency, frequency, monetary) → named segments you can explain.
Day one: everyone gets everything — that is the leak. Write RFM buckets. Write VIP. Write suppressions. Do not buy AI clustering. A segment you cannot explain is a mood. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Suppress (Unsubscribe is not enough) is how you stop the leak returning dressed as a new feature. If Placed Order is dirty, every metric is theatre. If browse collides with cart, you trained people to ignore you. Discount-first abandon trains the wrong buyer — especially when consideration is long. Score the system. Then ship the two worst gaps. Not another brand story.
More leads into a leak is a more expensive leak. RFM or equivalent exists. VIP is defined. Suppressions are layered. Campaigns use segments. Watch full-list sends before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. RFM or equivalent exists That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Klaviyo is “set up”.
Do this
RFM (or equivalent) segments, VIP definition, layered suppressions, campaign audience = segments not full list, profile properties, predictive optional but not required.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
RFM (recency, frequency, monetary) → named segments you can explain
Skip this
Calling it done because a screenshot looks busy.
Do this
Open three campaigns from last month. If any went to all subscribers without a reason, fail. Define VIP in a sentence and find that segment. Check a recent buyer is not in a lapsed segment. RFM does not need a PhD — it needs names.
Skip this
Leaving “Campaigns” to chance.
Do this
On segments. Full list is a last resort you regret.
The usual miss
Calling Klaviyo “set up” because someone logged in and imported a snapshot.
Do this instead
RFM or equivalent. Simple enough to run. Then prove write-in: Open three campaigns from last month.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect RFM (recency, frequency, monetary) → named segments you can explain first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Full-list sends: Rare. Or fatigue is earned. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Full-list sends
Rare
Or fatigue is earned
VIP
Defined
In numbers
Suppress
Layered
Unsubscribe is not enough
This week
RFM or equivalent exists
RFM or equivalent exists
VIP is defined
Suppressions are layered
Campaigns use segments, not the full list
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
Working notes
Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Home décor has long consideration. Flows have to respect that without going quiet.
Read ↗Candle brands win on replenishment and scent stories, not one welcome coupon.
Read ↗Apparel lives on returns, second purchase, and segments that are not 'all subscribers'.
Read ↗Pet buyers are loyal when post-purchase is useful, not cute.
Read ↗Outdoor is seasonal. Lifecycle still has to work in the off-months.
Read ↗B2B-on-Shopify still needs lifecycle. Wholesale is not a reason to skip flows.
Read ↗Furniture is slow. Flows should educate, not nag.
Read ↗The same leak shows up for coffee brands, fashion accessory brands, haircare brands, home fragrance brands, tabletop brands, pool and outdoor living brands, tools and hardware DTC, toy brands, gifting brands, DTC food brands, sporting goods brands, footwear brands. The stack does not change because the niche does — the language does.
Email and WhatsApp stay open. A call is for installing the system.