Intern
What you actually do
Day one: welcome is a discount code with a logo on top — that is the leak. Write brand and proof first. Write the coupon policy (if any) and who is excluded. Do not launch five emails of merchandising.
Welcome is a discount code with a logo on top. Preference is never captured. The next email is already a sale. Welcome fights cart and campaigns because exclusions were never written.
Read it once, then stop negotiating with it. Welcome series for operators is a wiring job: orient → preference → first order → exclusions. 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.
Operators do not have a Welcome series problem because they lack Klaviyo. They have it because welcome is a discount code with a logo on top.
Wire these objects first: List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source.
Then these edges, in order: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon · Preference / quiz → writes properties; later campaigns use them · First-order CTA → one path; not five merchandising blocks with no hierarchy · Other flows → welcome does not fight cart/post-purchase the same hour
Done looks like a test you can repeat: Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1.
Start here: Brand and proof before coupon
Operators already have Klaviyo. The leak is not a missing feature. Welcome is a discount code with a logo on top. 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: List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source. Then connect these edges, in order: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon · Preference / quiz → writes properties; later campaigns use them · First-order CTA → one path; not five merchandising blocks with no hierarchy · Other flows → welcome does not fight cart/post-purchase the same hour. 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. Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1. How you know it worked on the board: Coupon in email 1 is usually no (price later, if at all). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Brand and proof before coupon An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: welcome is a discount code with a logo on top — that is the leak. Write brand and proof first. Write the coupon policy (if any) and who is excluded. Do not launch five emails of merchandising.
Operator
You already feel welcome is a discount code with a logo on top. Welcome is a discount code with a logo on top. Protect one sequence for 90 days. The four moves are orient → preference → first order → exclusions. The edges are New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon then Preference / quiz → writes properties; later campaigns use them. Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows.
CEO
This is a money leak, not a preference about tools. Welcome is a discount code with a logo on top. Until coupon in email 1 is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon.
Before
Tuesday. Someone among operators. Welcome is a discount code with a logo on top. 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. Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows. New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in operators already paid for Klaviyo. Welcome is a discount code with a logo on top. 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. Brand and proof before coupon. Prove write-in: Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1. This week is one move: Brand and proof before coupon If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Welcome is a discount code with a logo on top. Preference is never captured. The next email is already a sale. Welcome fights cart and campaigns because exclusions were never written.
The system
Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows.
The job of welcome is to make the list a relationship, not a coupon vault. Teach what you are, capture a preference if you can, show one proof, then a single path to first order. If email one is 20% off, you taught price before ritual.
Welcome should suppress against people who already bought. It should not also be the cart flow. Those collisions are why operators say 'email doesn't work' while four flows shout at once.
Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows.
Welcome is often a coupon with a logo. Brand and proof belong first so the list is not trained to wait for 15% off. Preference is captured if you will actually use it — a dead question is a field you will ignore. First-order path is clear: one merchandising story, one CTA. Welcome does not fight other flows: a new subscriber who immediately carts should get cart logic, or a written exception. Buyers who join the list are not new to the brand.
Wire the trigger: list, or a form that also exists in Shopify/Klaviyo. Source property on the profile. Exclusions: already purchased in X days, already in welcome (do not restart on every list add unless you mean to). SMS welcome if used honors 10DLC/opt-in separately. Deliverability: welcome to a dirty popup list will hurt the domain — hygiene still applies.
Two databases: a popup tool's list and Klaviyo's list, double-opting or double-sending. One form, one list, one flow. The intern subscribes twice with two emails (buyer vs not). They do not pick a 'fun' GIF until branches are true. If email 1 is a coupon, you do not have a welcome series. You have a discount dispenser.
List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source.
New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon
Preference / quiz → writes properties; later campaigns use them
First-order CTA → one path; not five merchandising blocks with no hierarchy
Other flows → welcome does not fight cart/post-purchase the same hour
Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1.
Day one: welcome is a discount code with a logo on top — that is the leak. Write brand and proof first. Write the coupon policy (if any) and who is excluded. Do not launch five emails of merchandising.
Who you are. What this list is for. No coupon required.
Ask if you can. Stage, product, use-case — something to segment.
One clear path. Proof, then ask.
Buyers out. Cart out. Welcome is not a megaphone.
On one line, for operators: Welcome is a discount code with a logo on top. 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.
List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Who you are. What this list is for. No coupon required. Then wire: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon
Why: Operators cannot skip this edge. Welcome is often a coupon with a logo. If it is not true, Klaviyo is already a second database.
Done when: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon is true on a test.
Ask if you can. Stage, product, use-case — something to segment. Then wire: Preference / quiz → writes properties; later campaigns use them
Why: Operators skip this and the leak returns as a private language. Wire the trigger: list, or a form that also exists in Shopify/Klaviyo. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Preference / quiz → writes properties; later campaigns use them is true on a test.
One clear path. Proof, then ask. Then wire: First-order CTA → one path; not five merchandising blocks with no hierarchy
Why: Operators feel this as Welcome is a discount code with a logo on top. Two databases: a popup tool's list and Klaviyo's list, double-opting or double-sending.
Done when: First-order CTA → one path; not five merchandising blocks with no hierarchy is true on a test.
Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Coupon in email 1 (Price later, if at all), then preference (Or every send stays generic). 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.
Brand and proof before coupon
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.
List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source.
If objects aren't named, software invents a second database.
Welcome is a discount code with a logo on top.
Who you are. What this list is for. No coupon required. Then wire: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon
Operators cannot skip this edge. Welcome is often a coupon with a logo. If it is not true, Klaviyo is already a second database.
On Klaviyo, this means the data model matches how operators actually work — not the snapshot demo. Edge: Preference / quiz → writes properties; later campaigns use them
Ask if you can. Stage, product, use-case — something to segment. Then wire: Preference / quiz → writes properties; later campaigns use them
Operators skip this and the leak returns as a private language. Wire the trigger: list, or a form that also exists in Shopify/Klaviyo. Spec tags, fields, and states have to be the same objects the next workflow will read.
Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows.
One clear path. Proof, then ask. Then wire: First-order CTA → one path; not five merchandising blocks with no hierarchy
Operators feel this as Welcome is a discount code with a logo on top. Two databases: a popup tool's list and Klaviyo's list, double-opting or double-sending.
Brand and proof before coupon
Because the login already exists. Welcome is a discount code with a logo on top. Preference is never captured. A new feature on a missing spec is a second database. Finish this edge first: New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon.
Day one: welcome is a discount code with a logo on top — that is the leak. Write brand and proof first. Write the coupon policy (if any) and who is excluded. Do not launch five emails of merchandising. 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. Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1. 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. Collisions (Welcome ≠ cart ≠ campaign) 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. Brand and proof before coupon. Ask what they came for. First-order path is clear. Welcome does not collide with other flows. Watch coupon in email 1 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. Brand and proof before coupon 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
List-trigger or added-to-list flow, brand/proof before coupon, preference capture, first-order path, exclusion vs other flows, profile source.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon
Skip this
Calling it done because a screenshot looks busy.
Do this
Subscribe a never-buyer. Confirm proof before any coupon. Subscribe a recent buyer; confirm they are not treated as a stranger with 15% off. Submit a preference if you have one; see it on the profile. Check they are not also in a blast that duplicates email 1.
Skip this
Leaving “Exclusions” to chance.
Do this
Buyers out. Cart out. Welcome is not a megaphone.
The usual miss
Calling Klaviyo “set up” because someone logged in and imported a snapshot.
Do this instead
Who you are. What this list is for. No coupon required. Then prove write-in: Subscribe a never-buyer.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect New subscriber → welcome flow; existing buyers who subscribe get a different branch or skip coupon 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
Coupon in email 1: Usually no. Price later, if at all. 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.
Coupon in email 1
Usually no
Price later, if at all
Preference
Captured
Or every send stays generic
Collisions
None
Welcome ≠ cart ≠ campaign
This week
Brand and proof before coupon
Brand and proof before coupon
Preference is captured
First order path is clear
Welcome does not fight other flows
Want the longer lesson, not the page for this niche? Welcome is not a coupon with a logo ↗
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.
Email and WhatsApp stay open. A call is for installing the system.