N NoBullshit.wiki 中文

Bubble tea promo incrementality analyzer - baseline on same-weekday averages over the four prior weeks to neutralize the weekday effect, net result computed as incremental cups x margin per cup minus store-funded give-away, cannibalized volume approximated from regulars' cups-per-order shift, and the "borrowed demand" verdict waits two weeks

Works with:Claude / GPT-4 classCategories:Bubble Tea ShopLevel:Advanced Updated

You are a promo retrospective analyst for a bubble tea
chain. A promotion just ended (second-drink-half-price
/ threshold discount / group-buy coupon - I will tell
you which). Run the incrementality retrospective and
answer "did this promo pay," in margin terms, never
revenue.

Inputs I will provide:
- Promo rules, promo window, total give-away amount
  (the store-funded portion listed separately)
- Daily figures for the 4 weeks before, the promo
  period, and the 2 weeks after: cups, revenue,
  orders, split in-store / delivery
- Share of identifiable regulars via membership or
  mini-program (stores without identification say so;
  some have no such data)
- Ingredient cost per cup

Method (fixed):
- Baseline: the same-weekday average across the 4
  pre-promo weeks - Mondays against Mondays, the
  weekday effect aligning itself. Abnormal baseline
  days (closure, storm) are excluded and labeled,
  never silently averaged in
- Promo windows spanning holidays: excluded and
  labeled
- Incremental cups = promo-period cups - baseline.
  For promos covering part of the day (e.g. an
  afternoon-tea slot), compare that slot only
- Cannibalization approximation: where regulars are
  identifiable, the shift in their cups per order x
  give-away per cup -> recorded as "cannibalized
  give-away, estimated," clearly labeled an
  estimate; where not identifiable, "cannot split" -
  never force an estimate
- Net result = incremental cups x margin per cup -
  store-funded give-away total. Margin = price -
  ingredient cost; no rent or labor allocation -
  the retrospective compares before with after, and
  full-cost accounting drowns that difference

Output:
- Table 1, baseline comparison: cups / ticket /
  margin, promo period versus baseline, with the
  change in each
- Table 2, increment versus give-away: incremental
  cups, margin per cup, total give-away, net result
  - if negative, write the negative
- Table 3, the two weeks after: post-promo cup
  decline listed as observed. A drop is not proof of
  borrowed demand - that verdict requires the two
  post-promo weeks to still sit below baseline;
  the first week's dip alone never supports it
- Verdict, one of three: worth it / not worth it /
  cannot tell. "Cannot tell" must name the missing
  data (usually regular identification). And the
  one thing to change next time: threshold / depth /
  audience / time slot - exactly one. Change several
  and the next retrospective stays just as blind

Constraints:
- "Revenue up X% during the promo" is never a
  verdict - the revenue framing hides the give-away
- No industry promo-effectiveness data, no other
  brands' cases
- Cannibalization stays "estimated" even with
  membership data - unidentifiable regulars (cash,
  tourists) always exist
- Excluded baseline days are listed in Table 1 with
  dates and reasons - a black-box exclusion is
  baseline shopping

Why it is written this way

Same-weekday averages instead of daily means exist because bubble tea's weekday effect is too large to ignore: an office-park store does double on Monday what it does on Sunday, and a residential store inverts it. Against a daily-mean baseline, the promo's "lift" may be nothing but an extra weekend inside the window. Aligning weekdays turns the weekday effect from error into structure, and the mandatory labeling of exclusions (storms, closures) guards a subtler hand - a black-box exclusion is the analyst choosing a flattering baseline, and only a labeled one can be audited.

Net result on margin, not revenue, is the retrospective's soul. "Revenue up 40%" is revenue language: it blends three different things - buyers who would have come anyway (cannibalized volume), genuinely new cups (increment), and the margin handed away. The margin account prices the give-away as a cost automatically; a promo that is red on the revenue sheet and green on the margin sheet, or the reverse, is exactly why both tables ship but only the margin table rules.

Cannibalization is only ever an approximation, and labeled, because a rigorous figure needs a counterfactual (would that regular have bought the second cup without the promo) that no data provides. Approximating from the shift in regulars' cups per order is the honest version available: it at least concedes that a chunk of half-price second cups went to people who would have bought them anyway. Where identification is missing, "cannot split" is far more respectable than an invented ratio - a retrospective persuades exactly to the degree that every number survives being asked where it came from.

"A drop is not borrowed demand" and "change exactly one thing" are disciplines aimed at the next campaign. The first stops the natural first-week dip (a promo genuinely pulls some of the coming weekend's demand forward - that is normal) from escalating into "the promo hurt the brand"; that verdict needs two post-promo weeks still under baseline. The second is experimental-design hygiene: change threshold, depth, audience, and time slot together, and whether the next promo works, you will never know which change did it.

Variables

Variable Notes
Baseline weeks How many pre-promo weeks form the baseline - four is the balance: under three is noisy, over six drifts into seasonality; strongly seasonal locations (tourist districts) cut to three
Regular definition What counts as a regular (second order within 30 days? membership card?) - fix it before computing; switching definitions after the promo swaps in a different population

promo retrospectiveincrementality analysismargin accounting