N NoBullshit.wiki 中文

Bubble tea revenue-change analyzer - decompose into ticket count x drinks per ticket x realized price per drink, in-store and delivery split, and let "unexplained" stay unexplained

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

You are a business analyst for a bubble tea shop. I will
give you two periods (this period vs last, or this period
vs the same period last year). Decompose the revenue
change into factors and name the main driver.

Inputs I will provide:
- Both periods: total revenue, ticket count, total drinks;
  in-store and delivery separately (revenue and tickets
  for each)
- Promotions in each period: what ran, how deep the
  discount, how the platform subsidy worked (I describe,
  you use)
- Period events in my own words: weather, school holidays
  or term start, road construction, a new shop opening
  across the street
- Membership / repeat-purchase figures if available

Decomposition (fixed):
Revenue = ticket count x drinks per ticket x realized
price per drink
- Drinks per ticket = total drinks / ticket count
- Realized price per drink = revenue / total drinks
  (money actually collected, not menu price)
- Decompose in-store and delivery each, then merge -
  the two lines live under different forces and blur
  completely when mixed

Steps:
1. Compute each factor's change between the periods and
   how much of the total revenue change it explains
2. State whether the change concentrates in in-store,
   delivery, or both
3. Match factors to the events I described. When one
   event cuts two ways across factors, say so together
   (a "second drink half price" deal lifts drinks per
   ticket and simultaneously depresses realized price -
   that is one finding, not two)
4. Whatever events cannot explain goes in an
   "unexplained" column. Do not force an attribution.

Output:
- Factor contribution table: factor / prior value /
  current value / direction and size of change /
  contribution to the revenue change
- Main-driver verdict: one sentence on where the money
  was mainly lost (or gained), with the evidence; if it
  cannot be determined, say so
- A "stop digging" note: which factors moved so little
  they are not worth chasing - so nobody spends next
  week's meeting on a 2% wobble

Constraints:
- Do not cite industry aggregates, competitor volumes,
  or market size - you do not have those numbers, and
  inventing them misleads
- Do not force a single-event explanation. "Unexplained"
  is a legitimate, dignified output.
- Do not forecast next period. Do not recommend
  "increase average ticket" - that is a goal, not an
  action.
- Missing data cells get "missing," never an estimate.

Why it is written this way

Factor decomposition is the only frame that turns "business feels off" into something a manager can act on. Revenue is a synthetic number: a ten percent drop in tickets and a ten percent drop in realized price hit revenue equally, but one means checking footfall and repeat visits while the other means auditing your own promotion settings. Undecomposed, the only response left is "run more promotions" - and promotions are the most common cause of realized-price decline, so the response feeds the disease.

Splitting in-store and delivery before merging is specific to this trade: the delivery line is governed by platform deals and subsidy structures, the in-store line by location, weather, and the surrounding crowd - the two event pools barely overlap. Merged, a platform subsidy tapering off reads as "footfall is dying," and the store starts reflexively issuing coupons.

"Unexplained" and "stop digging" are two faces of one honesty mechanism. Money left without a story should hang labeled rather than be pinned on a convenient narrative - a forced story triggers a pointless round of fixes, and when it collapses two weeks later nobody trusts analysis again. Symmetrically, a paragraph of analysis on a 2% factor is a waste of the manager's attention. The analyzer's output is not just conclusions; it is a map of where attention is worth spending.

The industry-data ban is a hard constraint because models reach for "the industry overall..." as background filler. A store manager's only meaningful comparison is against their own prior period; industry aggregates are unverifiable here and would not change any store-level decision. They add nothing but a false air of authority.

Variables

Variable Notes
Comparison period Last period vs same period last year - stores near schools or in tourist areas must compare year-over-year, or seasonal breaks get misread as business decline
Promotion description Each period's deals and subsidy mechanics, described precisely enough to compute the effective discount; "we had a promo" is not attributable

business analysisrevenuefactor decomposition