Intern
What you actually do
Day one: name the interval from real use, not from a blog. Split subscribers and one-time. Do not guess 30 days if the product is 90. Do not duplicate subscribe-and-save coupons onto people who already subscribe.
Library / DTC brands / Replenishment flows
Toys are gifting plus seasonality. Segmentation is the strategy.
Read it once, then stop negotiating with it. Replenishment flows for toy brands is a wiring job: clock → split → before empty → stay on. 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.
Toy brands do not have a Replenishment flows problem because they lack Klaviyo. They have it because you reacquire people who would have reordered.
Wire these objects first: Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU.
Then these edges, in order: Ordered Product X → replenish clock starts using the real use interval · Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions · Reminder → lands before empty; after empty is reacquisition wearing a mask · Campaigns → do not pause this flow in peak without a written exception
Done looks like a test you can repeat: Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill.
Start here: Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
Toy brands already have Klaviyo. The leak is not a missing feature. You reacquire people who would have reordered. 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: Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU. Then connect these edges, in order: Ordered Product X → replenish clock starts using the real use interval · Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions · Reminder → lands before empty; after empty is reacquisition wearing a mask · Campaigns → do not pause this flow in peak without a written exception. 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. Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill. How you know it worked on the board: Interval is real (not a campaign mood). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: name the interval from real use, not from a blog. Split subscribers and one-time. Do not guess 30 days if the product is 90. Do not duplicate subscribe-and-save coupons onto people who already subscribe.
Operator
You already feel you reacquire people who would have reordered. Toys are gifting plus seasonality. Segmentation is the strategy. Protect one sequence for 90 days. The four moves are clock → split → before empty → stay on. The edges are Ordered Product X → replenish clock starts using the real use interval then Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions. January is hangover. If win-back is not booked before peak, you will invent it while tired.
CEO
This is a money leak, not a preference about tools. They would have reordered. Until interval is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Ordered Product X → replenish clock starts using the real use interval.
Before
Tuesday. Someone among toy brands. Toys are gifting plus seasonality. Segmentation is the strategy. 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. January is hangover. If win-back is not booked before peak, you will invent it while tired. Ordered Product X → replenish clock starts using the real use interval The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in toy brands already paid for Klaviyo. Toys are gifting plus seasonality. Segmentation is the strategy. 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. The interval matches real use. Prove write-in: Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill. This week is one move: Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
They would have reordered. You paused the flow for a campaign. Or you guessed 30 days for every SKU. Or you couponed subscribers. Then you paid acquisition again for a refill you already earned.
The system
The interval matches real use. Subscribers and one-time buyers are split. Reminders land before empty, including ship time. Flows stay on during peaks.
Name the clock from the product — burn, bag, tin, filter — not from marketing's mood. If you do not know it, learn it from reorder data or one post-purchase ask.
Do not acquire-coupon people who already pay you monthly. Keep the email useful: what they bought, how to refill. Do not pause replenishment because there is a drop.
January is hangover. If win-back is not booked before peak, you will invent it while tired.
You reacquire people who would have reordered when replenishment is not a clock. The interval matches real use. Subscribers and one-time are split — subscribers already have a billing object. Reminders land before empty. Flows stay on during campaigns. If you only run a 'stock up' campaign, you do not have replenishment. You have a sale.
Wire Ordered Product filters per SKU or category. People who bought a one-off gift SKU may not belong. People who still have inventory because they bought two should not be nagged on the same clock — quantity can adjust the interval if you are willing to do the math. Exit on repurchase. RPR is the score.
Two databases: subscription app reminders and Klaviyo replenish both hitting subscribers. Exclude. The intern maps SKU → interval on a sheet. They do not write cute 'running low?' puns until the clock is true. If the interval is a guess, survey or reorder data first. A wrong clock is a trust leak.
Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU.
Ordered Product X → replenish clock starts using the real use interval
Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions
Reminder → lands before empty; after empty is reacquisition wearing a mask
Campaigns → do not pause this flow in peak without a written exception
Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill.
Day one: name the interval from real use, not from a blog. Split subscribers and one-time. Do not guess 30 days if the product is 90. Do not duplicate subscribe-and-save coupons onto people who already subscribe.
A number of days you can defend, including ship time.
Subscribe vs one-time. Different journeys.
The reminder lands while they still need you.
Campaigns pulse on top. The clock does not pause.
On one line, for toy brands: You reacquire people who would have reordered. 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.
Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
A number of days you can defend, including ship time. Then wire: Ordered Product X → replenish clock starts using the real use interval
Why: Toy brands cannot skip this edge. You reacquire people who would have reordered when replenishment is not a clock. If it is not true, Klaviyo is already a second database.
Done when: Ordered Product X → replenish clock starts using the real use interval is true on a test.
Subscribe vs one-time. Different journeys. Then wire: Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions
Why: Toy brands skip this and the leak returns as a private language. Wire Ordered Product filters per SKU or category. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions is true on a test.
The reminder lands while they still need you. Then wire: Reminder → lands before empty; after empty is reacquisition wearing a mask
Why: Toy brands feel this as You reacquire people who would have reordered. Two databases: subscription app reminders and Klaviyo replenish both hitting subscribers.
Done when: Reminder → lands before empty; after empty is reacquisition wearing a mask is true on a test.
Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Interval (Not a campaign mood), then subscribers (From acquire coupons). 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.
Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
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.
Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU.
If objects aren't named, software invents a second database.
Toys are gifting plus seasonality. Segmentation is the strategy.
A number of days you can defend, including ship time. Then wire: Ordered Product X → replenish clock starts using the real use interval
Toy brands cannot skip this edge. You reacquire people who would have reordered when replenishment is not a clock. If it is not true, Klaviyo is already a second database.
On Klaviyo, this means the data model matches how toy brands actually work — not the snapshot demo. Edge: Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions
Subscribe vs one-time. Different journeys. Then wire: Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions
Toy brands skip this and the leak returns as a private language. Wire Ordered Product filters per SKU or category. Spec tags, fields, and states have to be the same objects the next workflow will read.
January is hangover. If win-back is not booked before peak, you will invent it while tired.
The reminder lands while they still need you. Then wire: Reminder → lands before empty; after empty is reacquisition wearing a mask
Toy brands feel this as You reacquire people who would have reordered. Two databases: subscription app reminders and Klaviyo replenish both hitting subscribers.
gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
Because the login already exists. They would have reordered. You paused the flow for a campaign. A new feature on a missing spec is a second database. Finish this edge first: Ordered Product X → replenish clock starts using the real use interval.
Day one: name the interval from real use, not from a blog. Split subscribers and one-time. Do not guess 30 days if the product is 90. Do not duplicate subscribe-and-save coupons onto people who already subscribe. 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. Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill. 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. Second order (The number that matters) 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. January is hangover. If win-back is not booked before peak, you will invent it while tired. Watch interval 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. Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back. 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
Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Ordered Product X → replenish clock starts using the real use interval
Skip this
Calling it done because a screenshot looks busy.
Do this
Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill.
Skip this
Leaving “Stay on” to chance.
Do this
Campaigns pulse on top. The clock does not pause.
The usual miss
Calling Klaviyo “set up” because someone logged in and imported a snapshot.
Do this instead
A number of days you can defend, including ship time. Then prove write-in: Order a test SKU.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Ordered Product X → replenish clock starts using the real use interval 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
Interval: Real. Not a campaign mood. 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.
Interval
Real
Not a campaign mood
Subscribers
Suppressed
From acquire coupons
Second order
From flow
The number that matters
This week
gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
EU operators · EU hours. Consent and entities are real. They are not a substitute for exit rules.
The interval matches real use
Subscribers and one-time are split
Reminders land before empty
Flows stay on during campaigns
Want the longer lesson, not the page for this niche? Replenishment is a clock ↗
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.
Toy brands do not have a Replenishment flows problem because they lack Klaviyo. They have it because you reacquire people who would have reordered. Wire these objects first: Use-interval (days) on SKU or profile, Klaviyo flow, subscriber vs one-time split, reminder before empty, campaign exclusion, Placed Order of that SKU. Then these edges, in order: Ordered Product X → replenish clock starts using the real use interval · Subscriber to X → different flow or skip; they already have a clock in Recharge/subscriptions · Reminder → lands before empty; after empty is reacquisition wearing a mask · Campaigns → do not pause this flow in peak without a written exception Done looks like a test you can repeat: Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill. Start here: Gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
They would have reordered. You paused the flow for a campaign. Or you guessed 30 days for every SKU. Or you couponed subscribers. Then you paid acquisition again for a refill you already earned. January is hangover. If win-back is not booked before peak, you will invent it while tired.
Before: Tuesday. Someone among toy brands. Toys are gifting plus seasonality. Segmentation is the strategy. 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. January is hangover. If win-back is not booked before peak, you will invent it while tired. Ordered Product X → replenish clock starts using the real use interval The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because Klaviyo is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: clock → split → before empty → stay on.
Interval: Real — Not a campaign mood. Then subscribers (From acquire coupons). If those are folklore, do not add another Klaviyo workflow.
gifting vs parent-buy segments. Peak calendar. Post-peak finite win-back.
Because the login already exists. They would have reordered. You paused the flow for a campaign. A new feature on a missing spec is a second database. Finish this edge first: Ordered Product X → replenish clock starts using the real use interval.
Day one: name the interval from real use, not from a blog. Split subscribers and one-time. Do not guess 30 days if the product is 90. Do not duplicate subscribe-and-save coupons onto people who already subscribe. 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. Order a test SKU. Confirm the flow would time for that interval (even if you shorten delays in a clone). Confirm a subscriber profile is excluded. Confirm a campaign can send without killing the flow. You reacquire people who would have reordered — that is the leak to kill. 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.
Posts go live. Search still does not know you.
Read ↗GSC and GA4 sit in silos. Nobody sequences the work.
Read ↗Roadmaps are annual. Execution is weekly panic.
Read ↗You have access. You do not have a Monday ritual.
Read ↗You write better emails into a worse inbox.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.