Flow · Forge & Grind · Premium coffee and gear, subscription-first

Getting new subscribers to their second box.

A welcome flow for two high-ticket buyers, the espresso machine owner and the monthly bean subscriber, built around one number: how many are still subscribed when charge #2 runs.

Keep new subscribers past the second charge: answer every early reason to cancel before it's felt.

Projected24% → 14%Projected share of subscribers who cancel before charge #2, generic welcome vs this flow.
ShopifyKlaviyoRecharge
Forge & Grind: Unboxing and subscription welcome

If this sounds like your store

Subscribers cancelling before their second charge?

The first box didn't fit their week, and cancel was the only button. The audit looks at where subscribers drop off in Recharge or Skio.

Problem, strategy, execution

Unboxing and subscription welcome

"It doesn't taste like I expected."

Usually the grind, not the beans.

Answered by the dial-in guide on day 6, when the first bag is half gone and frustration peaks.

"Bags are piling up."

Wrong frequency, so cancelling feels like the only fix.

Answered on day 12: change frequency, swap roast or skip, one click each.

"It's just coffee."

Premium coffee needs a reason to pay more.

Answered on day 0 by the founder's letter on where the beans began. Surprise charges are handled by a heads-up 10 and 3 days out.

The flow

Every step, and who goes where.

  1. triggerSubscription started or machine orderedRecharge / Shopify
  2. splitWhich buyer?

    Bean subscriber

    1. emailS1 · Day 0 · Why these beansfounder letter on the origin
    2. emailS2 · Day 3 · Your first three cupsbrew guide + brew-method tap
    3. emailS3 · Day 6 · Dial in your grindvisual grind-size guide
    4. emailS4 · Day 12 · Make it fit your weekfrequency, swap or skip
    5. splitDay 19 · next charge still on schedule?

      Yes

      1. emailS5 · Meet your next roastswap it before it roasts

      No

      1. emailS5b · See you on [new date]no pitch
    6. emailS6 · Charge −3 days · Roasting Mondayits own flow, on Order upcoming

    Machine buyer

    1. emailM1 · Day 0 · Why we chose this machinefounder letter, machine edition
    2. emailM2 · Day 1 · Unbox and set upsetup video, warranty sign-up
    3. emailM3 · Day 4 · Dial in your grindstarting settings for their model
    4. emailM4 · Day 10 · Care for itbackflush and descale schedule
    5. splitDay 16 · subscribed yet?

      No

      1. emailM5 · Beans built for your machinefirst bag free

      Yes

      1. exitJoins the subscriber track

Rules on every touch: cancelled subscribers are out at the next step; paused subscribers only get content, nothing about the next box; anyone who skipped or pushed a delivery gets S5b instead of S5; and the Recharge portal link sits in every footer from day 0. Bought both? They run the subscriber track, with machine setup and care blocks swapped in.

The emails

What customers actually receive.

Desktop and phone, with the job each email does and how it's built.

Forge & Grind email: The founder letter, desktop
The same email on a phone

S1 · Day 0

The founder letter

From: Eli at Forge & GrindWhere your first bag beganA farm, a folding table, and a harvest we bought on the spot.

A/B subject: The farm behind your first bag

The job
Make a high-ticket purchase feel justified before the first bag arrives.
Why it works
Story and liking. People stay loyal to a person and a place, not a price list.
How it's built
The origin card is dynamic: conditional blocks keyed to the product in the subscription event show that roast's producer, altitude, process and tasting notes. Two compressed images, live serif text, under 102KB. The Recharge portal link is in the footer from day 0.
Forge & Grind email: The dial-in guide, desktop
The same email on a phone

S3 · Day 6

The dial-in guide

From: Forge & GrindDial in your grind in three shotsSour? Go finer. Bitter? Go coarser. Here's the whole map.

A/B subject: Sour or bitter? Here's the fix

The job
Break the most common early-churn path: bad cup, blame the beans, cancel.
Why it works
Competence. When people succeed with the product, they credit the product.
How it's built
An infographic built in live HTML from tables and text, not one big image, so it's readable with images off and dark-mode safe. The brew_method property from S2 picks the recipe card and the highlighted stop. Replies go to a barista, tagged "dial-in".

Every other touch, and the job it does

S2 · Day 3Your first three cupsAn early win, and a one-tap brew-method question every later touch reads.
S4 · Day 12Make it fit your weekHand them the release valve before they reach for cancel. A skip keeps a subscriber.
S5 · Day 19Meet your next roastMake the next charge feel like an arrival, not a bill. Skipped or pushed? S5b instead.
S6 · Charge −3 daysRoasting MondayNo surprise charges. Fires only before the first renewal.
M2 · Day 1Unbox and set upTurn a $1,200 box on the counter into a working ritual on day one.
M4 · Day 10Care for itProtect the investment. Fewer breakdowns, fewer angry tickets.
M5 · Day 16Beans built for your machineTurn a one-time machine order into recurring revenue.

Projected impact

What it should be worth.

14%Cancel before charge #2, down from 24%
15%Machine buyers who subscribe within 30 days, up from 4%
+$32kFuture revenue per monthly cohort
MetricControlWelcome flow
Founder letter open rate61%72%
Brew-method tap rate (S2)n/a31%
Dial-in guide click raten/a18%
Skipped or changed frequency instead of cancelling3%9%
"Tastes wrong" support ticketsbaseline−35%
Cancelled before charge #224%14%

The maths: Per monthly cohort of 1,000 subscribers and 150 machine buyers: 100 more subscribers reach charge #2, plus about 16 more machine buyers subscribe. At 7 more charges × $40 each, that's about $280 per saved subscriber.

How we would measure it: Hypothesis: if every early reason to cancel gets answered before it's felt (bad cups, piling bags, surprise charges, "it's just coffee"), more subscribers are still there when charge #2 runs. Validated with a 50/50 hold-out on new subscribers, read at charge #2.

How it's built in Klaviyo and Shopify

The catch: Recharge doesn't send Klaviyo a "skipped" event. A skip moves the next charge date, so the flow watches the date instead.

  1. Flow filters on the subscriber track, checked before every send: Subscription cancelled on Recharge zero times since starting the flow, and rc_active_subscriber is true.
  2. Day 19 split one: Subscription paused at least once since starting? Yes goes to content-only touches.
  3. Day 19 split two: Next charge date changed zero times since starting, and the date is within 12 days? Yes gets S5; no gets S5b with their new date.
  4. S6 is its own flow, triggered by Order upcoming on Recharge and filtered to rc_customer_charge_count = 1, so it only fires before the first renewal. Recharge's default notice is switched off to avoid a duplicate.
  5. The machine track skips anyone who started a subscription in the last 30 days, so nobody gets two welcomes.

What Recharge syncs to Klaviyo, and how it's used

SignalTypeUsed for
Subscription started on RechargeEventSubscriber track trigger
Subscription cancelled on RechargeEventFlow filter: out at the next step
Subscription paused on RechargeEventSplit: content-only path
Next charge date changedEventThe skip signal
rc_next_charge_dateProfile propertyDate check before S5
rc_active_subscriberProfile propertySubscriber filter; M5 only if not true
rc_customer_charge_countProfile propertyS6 fires only before renewal #1
Order upcoming on RechargeEventS6 trigger, 3 days ahead

S5b · the new date

See you on {{ person|lookup:'rc_next_charge_date'|format_date_string|date:'M j' }}

The 48-Hour Repeat Revenue Audit · free

Which of these is your store missing?

The free audit shows where your customers stop buying after order #1, which flows are missing or mistimed, and our estimate of what it's likely costing you. Back in 48 hours.

Get your free 48-hour audit