§ W3 · Ship plan
01 / 13
CAM · Week 03 of 05

Proof Capture· Reviews + UGC

2 touches across 7 days. Funday · Mar 25, 2026 → Apr 4, 2026
BrandFunday
PeriodMar 25, 2026 → Apr 4, 2026
StatusIn-flight
§ W3 · What we found
02 / 13
Restated from the audit

Why this week, this cohort.

64 of your top customers have bought 5+ times. They’re your most authentic source of social proof.

This group of 64 people represents your most valuable customers. They’ve spent over $480 each on average. A personal, founder-led request for a review or a photo of their gear will feel like a conversation, not a marketing ask.

The cohort

This group of 64 people represents your most valuable customers. They’ve spent over $480 each on average. A personal, founder-led request for a review or a photo of their gear will feel like a conversation, not a marketing ask.

64
Power users eligible for review/UGC capture
§ W3 · The campaign
03 / 13
What’s shipping this week

Proof Capture · Reviews + UGC

Type
review_ugc
sequence shape
Touches
2
over 7 days
Channels
email
mix
Cohort
64
targeted

A two-email sequence to collect reviews and user-generated photos from your 64 most loyal customers. The first is a founder-led request for a review on the North Shore Trucker in Black. The second is a follow-up for a photo.

Strategy decision memo
Chosen play
North Shore Trucker in Black review capture
Rev 3 · Conf 3 · Proof 3 · Risk 2 · Spec 4
Objective
proof capture
Why this product now

2 public reviews in review feed

Belief to change

The buyer needs to believe North Shore Trucker in Black is the right product-specific next step now.

Objection

buyer may not know the brand needs product-specific proof from them

Camo Hoodie in Black to Camo Tee in White 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 North Shore Trucker in Black discount
Rev 3 · Conf 3 · Proof 1 · Risk 4 · Spec 2

Rejected because generic discount is blocked by the computed brief.

North Shore Trucker in Black 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
Why reviews matter

Power-user review requests can carry more trust than generic claims. Anchoring on North Shore Trucker in Black leverages existing review sentiment.

02
Cohort-specific relevance

Power users purchased 5+ items including North Shore Trucker in Black. Their authentic advocacy carries disproportionate weight versus broad requests.

03
Minimal incentive design

Avoiding monetary offers preserves review authenticity while founder-led framing keeps the ask focused on reciprocity instead of discount-seeking.

§ W3 · The sequence
04 / 13
2 touches · 7 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
    A quick favor for your North Shore Trucker in Black?
    Founder-led request for a review, anchored to a specific product they own, leverages reciprocity without offering a discount.
    Audience
    All 64 Power Users
  2. 02
    3
    EmailKlaviyo campaign
    Got a photo of your North Shore Trucker in Black?
    Follow-up touch for a photo (UGC), sent only to those who didn't click the review link. Focuses on visual proof and community recognition.
    Audience
    Power Users who didn't click the review link
§ W3 · Setup 01 of 03 · The parent segment
05 / 13
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
W3 Power Users (5+ Orders)
Filter rules · add in order, joined with AND
  1. Placed Order ≥ 5 times
Expected size
~64
Klaviyo segment should show roughly this number after you save.
✓ How to check
After saving, the segment preview should show roughly 64 people. If the number is zero, check the syntax for 'Placed Order at least 5 times'.
Matches the power_user cohort from the audit.
§ W3 · Setup 02 of 03 · Tag every send
06 / 13
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
W3 Proof Capture T{n}
Why
Naming them consistently lets the end-of-week scorecard find both sends and report performance as one sequence.
How
When Klaviyo prompts you to name each campaign, type 'W3 Proof Capture T1' and 'W3 Proof Capture T2'.
✓Check: Go to Klaviyo → Campaigns. You should see two campaigns named W3 Proof Capture T1 and T2.
UTM template
utm_source=klaviyo&utm_medium=email&utm_campaign=w3_proofcapture_t{n}
Why
Without these, all link clicks from the week appear as one number. You won't know which email drove the review submissions.
How
In each Klaviyo campaign editor, find the 'Link tracking' section. Paste the template, replacing {n} with the touch number (1 or 2).
✓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=w3proofcapture_t1`.
§ W3 · Setup 03 of 03 · Guardrails
07 / 13
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 both emails. Inbox threading depends on consistency.
02
Schedule the campaigns in order (T1 on Day 0, T2 on Day 3). Don't send them at the same time.
03
Klaviyo locks the audience snapshot at the time each campaign is sent. For T2, you'll add a filter to exclude people who clicked the review link in T1. This prevents asking the same person twice.
04
If the parent segment size is zero or wildly different from 64 when you build it, check the rule for 'Placed Order at least 5 times'. The syntax matters.
§ W3 · T01 · The message
08 / 13
T01
0
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Founder-led request for a review, anchored to a specific product they own, leverages reciprocity without offering a discount.
§ W3 · T01 · How to ship it
09 / 13
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 segment
Segment name
W3 Power Users (5+ Orders)
Filter rules
  1. Placed Order ≥ 5 times
    Power user cohort: 5+ historical orders
Expected size~64
✓How to check: When selecting the audience, the estimated size should be around 64.
Send settings
From
Cody at Funday <hello@funday.com>
Why: Using 'Cody at Funday' personalizes the founder-led request. Keep the reply-to address consistent.
Send time
Day 0 · 2:00 PM recipient timezone
Why: Mid-afternoon is a typical time for checking personal email, which fits a non-urgent, personal request.
UTM
utm_source=klaviyo&utm_medium=email&utm_campaign=w3_proofcapture_t1
Send it

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

§ W3 · T02 · The message
10 / 13
T02
3
EmailKlaviyo campaign
Rendered as it lands in the inbox · paste copy verbatim
Why this one
Follow-up touch for a photo (UGC), sent only to those who didn't click the review link. Focuses on visual proof and community recognition.
§ W3 · T02 · How to ship it
11 / 13
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 segment
Segment name
W3 Power Users (5+ Orders)
Filter rules
  1. Placed Order ≥ 5 times
    Power user cohort: 5+ historical orders
  2. Did not click email 'Review Link' in last 3 days
    Exclude touch 1 responders
Expected size~64 minus T1 responders
✓How to check: The estimated audience size will be less than 64. If it's still exactly 64, the exclusion filter wasn't added correctly.
Send settings
From
Cody at Funday <hello@funday.com>
Why: Keep this identical to the first email. Consistency helps inboxes thread the messages as one conversation.
Send time
Day 3 · 2:00 PM recipient timezone
UTM
utm_source=klaviyo&utm_medium=email&utm_campaign=w3_proofcapture_t2
Send it

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

§ W3 · The math
12 / 13
Projected · per_cycle

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
Click rate
Percentage of customers who click a link in the email.
8.5%
1.24%
+7.26% points
Projected vs. Klaviyo segmented broadcast average
Projected far above the general email benchmark because the audience is your most engaged buyers and the ask is a direct, personal request from the founder.
Placed-order rate
Percentage of customers who placed an order after receiving the sequence.
1.4%
0.19%
+1.21% points
Projected vs. Klaviyo segmented broadcast average
Projected above the general email benchmark because this warm cohort is familiar with your brand. Some will buy incidentally while submitting proof.
Cohort recovery · Y1
1customers back×$68cohort LTV
Year-one
$27
Checkpoint · Day 7 post-send
Pass if
UGC submission rate ≥ 6.25% (4+ assets captured)
Fallback
If <2 submissions, supplement with incentivized review capture in product education flows
§ W3 · Next
13 / 13
What ships next week

Up next.
W4.

2,100 customers bought one thing from you. An automated email sequence shows them what to buy next.

Week 04

Cross-Sell · The Curious

— Team Funday