§ W2 · Ship plan
01 / 17
CAM · Week 02 of 05

Expansion· Cross-sell Curious

4 touches across 35 days. Funday · Mar 25, 2026 → Apr 29, 2026
BrandFunday
PeriodMar 25, 2026 → Apr 29, 2026
StatusIn-flight
§ W2 · What we found
02 / 17
Restated from the audit

Why this week, this cohort.

2,100 of your one-time buyers showed signs they'd buy more than one thing. This automated sequence shows them what to get next.

You have 2,100 customers who bought once but showed multi-product cart behavior. The Camo Tee in Black and Camo Tee in White were co-purchased 19 times. This flow suggests the white tee to black tee buyers over 35 days.

The cohort

You have 2,100 customers who bought once but showed multi-product cart behavior. The Camo Tee in Black and Camo Tee in White were co-purchased 19 times. This flow suggests the white tee to black tee buyers over 35 days.

2,100 cross-sell curious buyers
One-time buyers with multi-product cart evidence
§ W2 · The campaign
03 / 17
What’s shipping this week

Expansion · Cross-sell Curious

Type
cross_sell_flow
sequence shape
Touches
4
over 35 days
Channels
email
mix
Cohort
2,100
cross-sell curious buyers

A four-email triggered flow for customers who bought once. It suggests the Camo Tee in White to those who bought the Camo Tee in Black, based on 19 observed co-purchases. No discount—product relevance drives conversion.

Strategy decision memo
Chosen play
Camo Tee in Black to Camo Tee in White cross-sell
Rev 4 · Conf 4 · Proof 4 · Risk 2 · Spec 5
Objective
revenue
Why this product now

19 co-purchases from order-line graph; 5 next-purchase paths from order-line graph; same product family or adjacent catalog path; lower friction than a cold category jump

Belief to change

The buyer needs to believe Camo Tee in White is the right product-specific next step now.

Objection

another camo tee can feel redundant without a use-case difference

Camo Tee in Black to Camo Hoodie in Black category-jump test
Rev 3 · Conf 2 · Proof 2 · Risk 3 · Spec 4

Rejected because the computed brief has a stronger product path.

Percent-off Camo Tee in White discount
Rev 3 · Conf 3 · Proof 1 · Risk 4 · Spec 2

Rejected because generic discount is blocked by the computed brief.

Camo Tee in White proof-capture pilot
Rev 2 · Conf 1 · Proof 1 · Risk 5 · Spec 3

Rejected as a launch; only proof capture is defensible.

The reasoning
01
Cross-sell mechanics

Triggered flow for one-time buyers leverages co-purchase data like Camo Tee in Black → Camo Tee in White (19 orders) with 4-touch cadence matching industry benchmarks.

02
Product anchoring

Camo Tee in Black serves as catalog anchor for product pairing claims, grounded in order-line evidence from product_graph.coPurchasePairs.

03
Incentive rationale

No discount preserves margin; value-driven copy leverages product relevance over monetary offers per offerPolicy constraints.

§ W2 · The sequence
04 / 17
4 touches · 35 days

The ship order.

Day-by-day. Each touch names the channel, the audience refinement, and the angle. Subject lines + body copy unlock once you book the kickoff.

  1. 01
    0
    EmailKlaviyo campaign
    Camo Tee in White after Black
    Introduces the paired product (Camo Tee in White) to Camo Tee in Black buyers based on co-purchase data.
    Audience
    All 2,100 Cross-Sell Curious
  2. 02
    3
    EmailKlaviyo campaign
    Why the Camo Tee in White works
    Highlights product benefits and usage context for Camo Tee in White to non-responders.
    Audience
    Cross-Sell Curious who didn't buy after T1
  3. 03
    14
    EmailKlaviyo campaign
    Camo Tee in White holds up
    Reinforces product durability as a reason to buy, using known quality cues.
    Audience
    Cross-Sell Curious who didn't buy after T1 or T2
  4. 04
    35
    EmailKlaviyo campaign
    Last chance for Camo Tee in White
    Final touch to capture remaining intent without discount pressure.
    Audience
    Cross-Sell Curious who didn't buy after T1, T2, or T3
§ W2 · Setup 01 of 03 · The parent segment
05 / 17
Build this first — once

The parent segment every touch points at.

A segment is a saved filter that auto-groups the right customers — build it carefully once and the rest of the week references it. Spend ten minutes here.

Segment name · paste exactly
W2 Cross-Sell Curious
Filter rules · add in order, joined with AND
  1. Placed Order
  2. Total orders = 1
Expected size
~2,100
Klaviyo segment should show roughly this number after you save.
✓ How to check
After saving, the segment preview should show roughly 2,100 people. If the number is zero, check the syntax for 'Total orders = 1'.
§ W2 · Setup 02 of 03 · Tag every send
06 / 17
So your reporting works

Name campaigns and tag links the same way every time.

Two short codes that turn anonymous "clicks" into "clicks from week 1 touch 2." Without them, the scorecard at the end of the week can't tell which touch did the work.

Naming convention
W2 Cross-Sell T{n}
Why
Naming them consistently (W2 Cross-Sell T1, T2, T3, T4) lets the end-of-week scorecard find all four sends and report performance as one sequence.
How
When Klaviyo prompts you to name each campaign, type 'W2 Cross-Sell T1', 'W2 Cross-Sell T2', etc.
✓Check: Go to Klaviyo → Campaigns. You should see four campaigns named W2 Cross-Sell T1 through T4.
UTM template
utm_source=klaviyo&utm_medium=email&utm_campaign=w2_crosssell_t{n}
Why
Without these, all revenue from the week appears as one number. You won't know if the first reminder or the fourth email did the work.
How
In each Klaviyo campaign editor, find the 'Link tracking' section. Paste the template, replacing {n极} with the touch number (1, 2, 3, or 4).
✓Check: Send a test email for each campaign. Hover a link — the URL should end with the correct UTM string, e.g., `?utmsource=klaviyo&utmmedium=email&utmcampaign=w2crosssell_t1`.
§ W2 · Setup 03 of 03 · Guardrails
07 / 17
Four things that quietly break the week

Pin these to the wall before you hit send.

Each guardrail is a small habit. Skip one and the week's numbers get harder to read at the end — not impossible, just noisier than they need to be.

01
Use the same from-name and reply-to address for all four emails. Inbox threading depends on consistency.
02
Schedule the campaigns in order (T1 on Day 0, T2 on Day 3, T3 on Day 14, T4 on Day 35). Don't send them all at once.
03
Klaviyo locks the audience snapshot at the time each campaign is sent. For T2-T4, you'll add filters to exclude people who bought after a previous send. This prevents selling to someone who just came back.
04
If the parent segment size is zero or wildly different from 2,100 when you build it, check the rule for 'Total orders = 1'. The syntax matters.
§ W2 · T01 · The message
08 / 17
T01
0
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Introduces the paired product (Camo Tee in White) to Camo Tee in Black buyers based on co-purchase data.
§ W2 · T01 · How to ship it
09 / 17
T01 · 0 · Email
Klaviyo campaign
Three short steps

Audience, settings, send.

The body copy on the previous page is the work product. This page is the ship list — where to paste each thing inside Klaviyo campaign.

Audience
Klaviyo flow
Segment name
W2 Cross-Sell Curious
Filter rules
  1. Placed Order
    Trigger: placed order
  2. Total orders = 1
    Filter: single-purchase cohort
Expected size~2,100
✓How to check: When selecting the audience, the estimated size should be around 2,100.
Send settings
From
Team Funday <hello@funday.com>
Why: Keep this identical across all four emails. Consistency helps inboxes thread the messages as one conversation.
Send time
Day 0 · 11:00 AM recipient timezone
UTM
utm_source=klaviyo&utm_medium=email&utm_campaign=w2_crosssell_t1
Send it

Schedule this campaign to send today. The audience is a static snapshot taken at send time.

§ W2 · T02 · The message
10 / 17
T02
3
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Highlights product benefits and usage context for Camo Tee in White to non-responders.
§ W2 · T02 · How to ship it
11 / 17
T02 · 3 · Email
Klaviyo campaign
Three short steps

Audience, settings, send.

The body copy on the previous page is the work product. This page is the ship list — where to paste each thing inside Klaviyo campaign.

Audience
Klaviyo flow
Segment name
W2 Cross-Sell Curious
Filter rules
  1. Exclude: placed order since flow entry
    Trigger: placed order
Expected size~2,100 minus T1 buyers
✓How to check: The estimated audience size will be less than 2,100. If it's still exactly 2,100, the exclusion filter wasn't added correctly.
Send it

Schedule this campaign to send 3 days after the first one. Remember to add the exclusion filter for T1 buyers.

§ W2 · T03 · The message
12 / 17
T03
14
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Reinforces product durability as a reason to buy, using known quality cues.
§ W2 · T03 · How to ship it
13 / 17
T03 · 14 · Email
Klaviyo campaign
Three short steps

Audience, settings, send.

The body copy on the previous page is the work product. This page is the ship list — where to paste each thing inside Klaviyo campaign.

Audience
Klaviyo flow
Segment name
W2 Cross-Sell Curious
Filter rules
  1. Exclude: placed order since flow entry
    Trigger: placed order
Expected size~2,100 minus T1 & T2 buyers
✓How to check: The audience size should be smaller than for T2. If it's the same, check that both exclusion filters are present and correctly linked to the T1 and T2 campaigns.
Send settings
From
Team Funday <hello@funday.com>
Why: Keep this identical across every touch. Inboxes group messages by sender — same name means the touches stack as one conversation, not four separate unread emails.
Send time
Day 14 · 11:00 AM recipient timezone
UTM
utm_source=klaviyo&utm_medium=email&utm_campaign极=w2_crosssell_t3
Send it

Schedule this campaign to send 14 days after T1. Remember to add both exclusion filters for T1 and T2 buyers.

§ W2 · T04 · The message
14 / 17
T04
35
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Final touch to capture remaining intent without discount pressure.
§ W2 · T04 · How to ship it
15 / 17
T04 · 35 · Email
Klaviyo campaign
Three short steps

Audience, settings, send.

The body copy on the previous page is the work product. This page is the ship list — where to paste each thing inside Klaviyo campaign.

Audience
Klaviyo flow
Segment name
W2 Cross-Sell Curious
Filter rules
  1. Exclude: placed order since flow entry
    Trigger: placed order
Expected size~2,100 minus T1, T2 & T3 buyers
✓How to check: The audience size should be the smallest of all four campaigns. If it matches T3's size, check that all three exclusion filters are present.
Send settings
From
Team Funday <hello@funday.com>
Why: Keep this identical across every touch. Inboxes group messages by sender — same name means the touches stack as one conversation, not four separate unread emails.
Send time
Day 35 · 11:00 AM recipient timezone
UTM
utm_source=klaviyo&utm_medium=email&utm_campaign=w2_crosssell_t4
Send it

Schedule this campaign to send 35 days after T1. Remember to add all three exclusion filters for T1, T2, and T3 buyers.

§ W2 · The math
16 / 17
Projected · 35-day flow window

What we expect, what to compare against.

Each row is a metric we'll track. Projected is what we believe this campaign will hit; benchmark is the industry-average comparison point. The gap (the lift column) is where the cohort-warming logic shows up — these aren't strangers, they're 3+ time buyers.

MetricProjectedBenchmarkLiftSource · why above benchmark
Placed-order rate
Percentage of customers who placed an order after receiving the sequence.
2.5%
0.19%
+2.31% points
Klaviyo cross-sell band (P50) vs. segmented broadcast average
Projected far above the general email benchmark because this is a sequenced cross-sell campaign targeting known buyers with relevant product pairing cues.
Revenue per recipient
Average revenue generated per customer who received the sequence.
$1.70
$0.13
+$1.57
Klaviyo cross-sell band (P50) vs. segmented broadcast average
Projected far above the general email benchmark due to elevated placed-order rate and $68 average order value.
Cohort recovery · Y1
53customers back×$68cohort LTV
Year-one
$1K
Checkpoint · Day 12 after flow launch
Pass if
Placed-order rate ≥ 1.2% (P25 benchmark) by day 12
Fallback
If ≤ 0.6%, pause sequence and pivot week 3 to social-proof subject lines.
§ W2 · Next
17 / 17
What ships next week

Up next.
W3.

64 power users can be asked for North Shore Trucker in Black review proof. W3 captures reviews/photos without claiming creator-referral performance.

Week 03

Proof Capture · Reviews

— Team Funday