Intern
What you actually do
Day one: define unengaged. Write the finite length. Write sunset. Do not buy a tool to 'wake the list'. Clean lists beat big lists. Look at complaints first.
Library / DTC brands / List reactivation
Hardware buyers respect useful sequences more than lifestyle copy.
Read it once, then stop negotiating with it. List reactivation for tools and hardware DTC is a wiring job: see it → spec it → install it → review it. 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.
Tools and hardware DTC do not have a List reactivation problem because they lack Email systems. They have it because the list is large. The list is not alive.
Wire these objects first: Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list.
Then these edges, in order: Unengaged N days → enter finite reactivation; not infinite 'we miss you' · No response → sunset suppression; they leave campaigns and most flows · Complaints during reactivation → halt; list was too cold or too bought · Clean list → campaigns to engaged only; vanity list size demoted
Done looks like a test you can repeat: Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak.
Start here: Post-purchase consumable path. Cart without coupon-first. List hygiene.
Tools and hardware DTC already have Email systems. The leak is not a missing feature. The list is large. The list is not alive. 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: Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list. Then connect these edges, in order: Unengaged N days → enter finite reactivation; not infinite 'we miss you' · No response → sunset suppression; they leave campaigns and most flows · Complaints during reactivation → halt; list was too cold or too bought · Clean list → campaigns to engaged only; vanity list size demoted. If you skip an edge, the next one is decoration. If you add a Email systems feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak. How you know it worked on the board: Owner is named (or it will not run). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Post-purchase consumable path. Cart without coupon-first. List hygiene. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: define unengaged. Write the finite length. Write sunset. Do not buy a tool to 'wake the list'. Clean lists beat big lists. Look at complaints first.
Operator
You already feel the list is large. the list is not alive. Hardware buyers respect useful sequences more than lifestyle copy. Protect one sequence for 90 days. The four moves are see it → spec it → install it → review it. The edges are Unengaged N days → enter finite reactivation; not infinite 'we miss you' then No response → sunset suppression; they leave campaigns and most flows. Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional.
CEO
This is a money leak, not a preference about tools. Broadcasts feel like work. Until owner is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Unengaged N days → enter finite reactivation; not infinite 'we miss you'.
Before
Tuesday. Someone among tools and hardware DTC. Hardware buyers respect useful sequences more than lifestyle copy. Email systems 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. Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional. Unengaged N days → enter finite reactivation; not infinite 'we miss you' The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in tools and hardware DTC already paid for Email systems. Hardware buyers respect useful sequences more than lifestyle copy. 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. Nurture is a spine with manners: a short sequence, a human on replies, a stop rule, and segments that match relationship — not 'everyone who ever opted in'. Prove write-in: Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak. This week is one move: Post-purchase consumable path. Cart without coupon-first. List hygiene. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Broadcasts feel like work. Sequences feel like a project. So the list gets another campaign while nobody has a 5-email spine with one job per letter. Replies go nowhere. Unengaged contacts never sunset. Deliverability pays the bill.
The system
Nurture is a spine with manners: a short sequence, a human on replies, a stop rule, and segments that match relationship — not 'everyone who ever opted in'.
Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
Sunset is real. Reactivation is a finite sequence.
Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional.
The list is large; the list is not alive. Reactivation is a finite sequence with a sunset, not a personality. Complaints are watched because this is how you damage the domain. Sunset is real — they leave the sending universe except legal and transactional if required. Vanity list size is how founders refuse sunset: size is not a KPI; deliverability and RPR are.
Wire engagement as a defined object (open/click/purchase in N days — pick, and do not worship opens alone). Purchasers can be engaged even if they do not click. Never-buyers who also never engage are the first sunset. Do not mix win-back of buyers with reactivation of never-buyers. Those are different jobs and different offers.
Two databases: a 'master list' CSV you are afraid to touch and Klaviyo. The intern builds the unengaged segment and a 50-person test. They do not send to 200k on a Friday. If someone wants to keep the dead names 'for Facebook matching', that can be a suppressed segment, not a sending list. Names that cannot be sent to are not a list. They are a file.
Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list.
Unengaged N days → enter finite reactivation; not infinite 'we miss you'
No response → sunset suppression; they leave campaigns and most flows
Complaints during reactivation → halt; list was too cold or too bought
Clean list → campaigns to engaged only; vanity list size demoted
Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak.
Day one: define unengaged. Write the finite length. Write sunset. Do not buy a tool to 'wake the list'. Clean lists beat big lists. Look at complaints first.
Sunset is real
Reactivation is a finite sequence
Complaints are watched
Clean lists beat big lists
On one line, for tools and hardware DTC: The list is large. The list is not alive. 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.
Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Sunset is real Then wire: Unengaged N days → enter finite reactivation; not infinite 'we miss you'
Why: Tools and hardware DTC cannot skip this edge. The list is large; the list is not alive. If it is not true, Email systems is already a second database.
Done when: Unengaged N days → enter finite reactivation; not infinite 'we miss you' is true on a test.
Reactivation is a finite sequence Then wire: No response → sunset suppression; they leave campaigns and most flows
Why: Tools and hardware DTC skip this and the leak returns as a private language. Wire engagement as a defined object (open/click/purchase in N days — pick, and do not worship opens alone). Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: No response → sunset suppression; they leave campaigns and most flows is true on a test.
Complaints are watched Then wire: Complaints during reactivation → halt; list was too cold or too bought
Why: Tools and hardware DTC feel this as the list is large. The list is not alive. Two databases: a 'master list' CSV you are afraid to touch and Klaviyo.
Done when: Complaints during reactivation → halt; list was too cold or too bought is true on a test.
Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Owner (Or it will not run), then weekly number (Or reporting is theatre). 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.
Post-purchase consumable path. Cart without coupon-first. List hygiene.
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.
Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list.
If objects aren't named, software invents a second database.
Hardware buyers respect useful sequences more than lifestyle copy.
Sunset is real Then wire: Unengaged N days → enter finite reactivation; not infinite 'we miss you'
Tools and hardware DTC cannot skip this edge. The list is large; the list is not alive. If it is not true, Email systems is already a second database.
On Email systems, this means the data model matches how tools and hardware DTC actually work — not the snapshot demo. Edge: No response → sunset suppression; they leave campaigns and most flows
Reactivation is a finite sequence Then wire: No response → sunset suppression; they leave campaigns and most flows
Tools and hardware DTC skip this and the leak returns as a private language. Wire engagement as a defined object (open/click/purchase in N days — pick, and do not worship opens alone). Spec tags, fields, and states have to be the same objects the next workflow will read.
Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional.
Complaints are watched Then wire: Complaints during reactivation → halt; list was too cold or too bought
Tools and hardware DTC feel this as the list is large. The list is not alive. Two databases: a 'master list' CSV you are afraid to touch and Klaviyo.
post-purchase consumable path. Cart without coupon-first. List hygiene.
Because the login already exists. Broadcasts feel like work. Sequences feel like a project. A new feature on a missing spec is a second database. Finish this edge first: Unengaged N days → enter finite reactivation; not infinite 'we miss you'.
Day one: define unengaged. Write the finite length. Write sunset. Do not buy a tool to 'wake the list'. Clean lists beat big lists. Look at complaints first. 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. Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak. 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. Stop rule (Or you will scale the leak) is how you stop the leak returning dressed as a new feature. Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
More leads into a leak is a more expensive leak. Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional. Watch owner 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. Post-purchase consumable path. Cart without coupon-first. List hygiene. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Email systems is “set up”.
Do this
Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Unengaged N days → enter finite reactivation; not infinite 'we miss you'
Skip this
Calling it done because a screenshot looks busy.
Do this
Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak.
Skip this
Leaving “Review it” to chance.
Do this
Clean lists beat big lists
The usual miss
Calling Email systems “set up” because someone logged in and imported a snapshot.
Do this instead
Sunset is real Then prove write-in: Move a test profile to unengaged.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Unengaged N days → enter finite reactivation; not infinite 'we miss you' 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
Owner: Named. Or it will not run. 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.
Owner
Named
Or it will not run
Weekly number
Believed
Or reporting is theatre
Stop rule
Written
Or you will scale the leak
This week
post-purchase consumable path. Cart without coupon-first. List hygiene.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
Sunset is real
Reactivation is a finite sequence
Complaints are watched
Clean lists beat big lists
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.
Tools and hardware DTC do not have a List reactivation problem because they lack Email systems. They have it because the list is large. The list is not alive. Wire these objects first: Sunset definition, finite reactivation sequence, complaint watch, suppression after fail, deliverability, remaining live list. Then these edges, in order: Unengaged N days → enter finite reactivation; not infinite 'we miss you' · No response → sunset suppression; they leave campaigns and most flows · Complaints during reactivation → halt; list was too cold or too bought · Clean list → campaigns to engaged only; vanity list size demoted Done looks like a test you can repeat: Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak. Start here: Post-purchase consumable path. Cart without coupon-first. List hygiene.
Broadcasts feel like work. Sequences feel like a project. So the list gets another campaign while nobody has a 5-email spine with one job per letter. Replies go nowhere. Unengaged contacts never sunset. Deliverability pays the bill. Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional.
Before: Tuesday. Someone among tools and hardware DTC. Hardware buyers respect useful sequences more than lifestyle copy. Email systems 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. Project-based second purchase (blades, bits, consumables) is a flow. Lifestyle campaigns are optional. Unengaged N days → enter finite reactivation; not infinite 'we miss you' The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because Email systems is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: see it → spec it → install it → review it.
Owner: Named — Or it will not run. Then weekly number (Or reporting is theatre). If those are folklore, do not add another Email systems workflow.
post-purchase consumable path. Cart without coupon-first. List hygiene.
Because the login already exists. Broadcasts feel like work. Sequences feel like a project. A new feature on a missing spec is a second database. Finish this edge first: Unengaged N days → enter finite reactivation; not infinite 'we miss you'.
Day one: define unengaged. Write the finite length. Write sunset. Do not buy a tool to 'wake the list'. Clean lists beat big lists. Look at complaints first. 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. Move a test profile to unengaged. Run the finite sequence. Confirm sunset. Confirm they no longer receive a campaign. Watch complaint rate on a small slice before a big reactivation. Big list, dead list is the leak. 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.