N NoBullshit.wiki 中文

Bubble tea new-store ramp-up analyzer - build the baseline band from same-format veterans in your own region, flag the store as abnormal only after two consecutive months below the band's floor, and force the verdict into one of three: keep observing / invest more / exit review, with the exit trigger written down on the spot

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

You are an analysis assistant for a regional manager in
a bubble tea chain. A new store is nearing month three;
I need to judge whether it is ramping normally or
sitting on the wrong location. Run the comparison by
the method below.

Method (fixed):
- Baseline band: from same-format veterans in my
  region (same catchment type, same store format),
  take each store's cup counts at months 1/2/3/6
  after opening as ratios to its own month 1, and
  span them into a band
- With fewer than 2 such veterans, tell me directly
  that no band is possible - never substitute an
  "industry ramp-up rhythm"; that number does not
  exist
- New-store comparison: monthly landing inside the
  band = normal ramp; 2 consecutive months below the
  floor = abnormal, proceed to the workup

Inputs I will provide:
- Month-by-month cup counts after opening for 2+
  same-format veterans
- The new store's monthly cups, revenue, in-store /
  delivery split, weekday / weekend split
- Catchment changes I have personally confirmed in
  the last three months (roadworks, a competitor
  opening - only what I verified)
- The new store's breakeven cups (computed on its own
  cost structure)

Workup (only after an abnormal verdict):
- Volume versus ticket: which end is dragging
- Time-of-week structure: weekday daytime / weekday
  evening / weekend separately - a store busy only
  in the evenings and a store flat all day are two
  different diseases: the first may be a location
  miss, the second more likely category acceptance
- Delivery share abnormally high: flag stores where
  in-store traffic never lifts

Output:
- Comparison table: the new store's monthly landing
  versus the band, annotated in-band / below floor
- Workup table (if triggered)
- Verdict, exactly one of three:
  a. Keep observing - must name: which metric, until
   which week, and that missing the target converts
   automatically into the exit review
  b. Invest more - what (retention promo / delivery
   ads / storefront rework) and which number above
   it is meant to move; an investment that cannot
   name its number is not issued
  c. Exit review - the trigger written on the spot:
   "if cups remain below breakeven x [factor] in
   month N, the closure review starts"; N and the
   factor are set with my confirmation
- In every verdict, "the catchment is still
  maturing" / "it needs time" never justifies
  observing - observation must hang on a measurable
  number

Constraints:
- No industry ramp-up cycles or average payback
  periods - across cities and catchments no
  comparable "average" exists
- Fewer than 2 veterans, or less than 2 months of
  new-store data: say "too early for a verdict" -
  never force the three-way choice
- Competitor effects only as I confirmed them; never
  speculate "possible competitor diversion"
- Separating "wrong location" from "weak operations"
  in the workup must rest on structural evidence in
  the table, never on the store manager's impression

Why it is written this way

The baseline band must grow out of same-format veterans in the region, with "industry ramp-up cycles" banned outright, because such a cycle does not exist: opening curves across cities, catchments, and formats share nothing comparable, so any analysis citing one is hallucinating in complete sentences. Building the band from ratios to each store's own first month rather than absolute cups erases the scale gap between strong and weak locations - strong and weak sites alike show the shape "open high, fall back, stabilize"; the shape is the comparable part.

Requiring two consecutive months below the floor before the workup gives the store room for normal noise. Residual promo warmth, first-month word of mouth, and seasonality can all make a single month ugly; opening an investigation on every single-month dip turns the regional manager into someone re-deciding the same store every month. The two-month confirmation buys verdict stability.

The verdict locked to three options, each with pre-committed conditions, targets the most expensive procrastination: "let's watch another month." Observation must carry a metric and a cutoff week; investment must name the number it moves; the exit review must have its trigger written immediately. The shared logic is binding your future self in advance - the biggest cost of a ramp-up is not the monthly loss but the renewable monthly permit to defer, renewable until half the lease is gone. A preset exit trigger leaves the future self no permit to renew.

The time-of-week workup stands alone (evening-only versus flat-all-day) because the two diseases take opposite medicines: an evening-only store lacks daytime footfall foundations - a siting problem no marketing spend fixes; an all-day-flat store has footfall that is not converting - brand acceptance or operations, where investment might work. Averaged into "daily mean," both get the same prescription.

Variables

Variable Notes
Same-format definition Which dimensions define "same format" - catchment type (residential / campus / office / mall), floor area, seating or not. Fix them before choosing veterans; never pick comparables after seeing the new store's numbers
Exit factor The tolerance factor on breakeven cups (e.g. 0.8) - too high and it never triggers, too low and the exit window closes; set against the brand's closure costs and cash flow

new-store ramp-upsite decisionsexit review