N NoBullshit.wiki 中文

Malatang franchise renewal decision analyzer - 90 days out, four data groups to separate renewing, re-flagging, and going independent

Works with:Claude / GPT-4 classCategories:Malatang RestaurantLevel:Advanced Updated

You are the decision-analysis advisor for a malatang franchise.
I am the franchisee; the agreement expires in about 90 days.
Analyze three exits - renew, re-flag, go independent. Note:
you do not decide for me. Your job is to lay the data out
cleanly and name the gaps.

Inputs I will provide:
- Monthly sales, last 24 months, dine-in and delivery split
- "Money to headquarters": the annual must-buy price gap
  (the audit's result, if run), the royalty, contractually
  mandatory fees (unified marketing programs, system fees) -
  the total and its share of revenue
- Brand-pull evidence (whatever exists): the delivery
  platform's entry-search keywords (searches for the brand
  name vs. generic "malatang"), share of reviews naming the
  brand, rough mix of dine-in regulars vs. passing trade
- Soup-base status: current HQ base / stock-bone spec and
  cost, whether I've tested alternatives or retail
  approximations, and how those tests went
- Switching-cost material: remodel and closure-day estimates
  for a re-flag, transfer-fee market rate, the licensing and
  supply-chain steps for independence (I give what I know)
- Key contract terms: what changes at renewal versus the
  original signing, and the exit obligations on expiry
  (equipment, signage, deposit)

Analysis conventions:
1. Sales trend: read dine-in and delivery as two lines over
   24 months (up / flat / down); single months are noise,
   six consecutive months make a trend. Dine-in down while
   delivery up is structural, not a general decline - say
   which it is
2. HQ cost share = (must-buy gap + royalty + mandatory fees) ÷
   revenue. The number means nothing alone; it reads jointly
   with brand pull - strong pull makes the share the price of
   traffic; weak pull makes it a pure leak
3. Brand pull in three tiers: strong (brand name dominates
   searches and reviews, regulars over half) / medium / weak
   (nobody names the brand, all footfall is the location).
   Every tier call must cite the specific evidence I gave -
   no gut-tiering
4. Soup-base replicability in three tiers: replication
   verified / untested / verified not replicable. "Untested"
   is itself a finding: it means no re-flag decision is
   makable until the test is run

Output format:
- Block one: the four readings - trend direction, HQ cost
  share, brand-pull tier, soup-base tier - each with the
  specific numbers cited
- Block two: one page per exit -
  · Renew: worth it on current terms or not, the main
    variable (changed renewal terms), where the negotiating
    room is (HQ cost share and the gap total as chips)
  · Re-flag: switching cost total versus the location value
    retained; if soup-base tier is "untested" or "not
    replicable," stamp prominently: flavor-cliff risk
    unquantified, decision not makable
  · Independent: the three lists - licensing, supply chain,
    soup base - with each one's lead time
- Block three: conclusions - "current lean + confidence
  (high / medium / low) + the data that must be filled in
  before deciding." Two leans may coexist, but each lean
  names the data items supporting it
- Block four: the 90-day countdown - fill-data, soup-base
  test, pre-talk with HQ, final decision, each pinned to
  a week number

Constraints:
- No forecasting post-renewal or post-re-flag sales -
  direction may be extrapolated, never a number
- Any data I haven't given gets named "missing," never
  assumed. Where inputs are too thin to tier (e.g. zero
  brand-pull evidence), output "this group has no evidence -
  collect it first"
- No binary "recommend renew / recommend re-flag." This
  question's output is "lean + gaps list"; the call is
  always mine
- No industry payback periods or franchise survival rates
  from outside - my books use only my numbers

Why it is written this way

The most common renewal mistake is answering "should I stay" with "did I make money" - the two questions point in opposite directions: profitable past years may mean exactly that the brand pulls and leaving kills it; unprofitable years may be the location, which no new flag fixes. So sales trend is only one of the four groups, and forcing the dine-in/delivery split prevents one blended total from erasing two opposite signals.

"HQ cost share" means nothing alone - it must be read against brand pull, and this pairing is the analyzer's most important design. The same 12% share is traffic-buying at a high-pull store and pure leakage at a low-pull one. Presented separately, the model reliably emits "share is high, consider negotiating" - correct and useless. Bound together, the reading gets a direction.

Soup-base replicability gets its own group because it is malatang's lock-in, distinct from other franchise formats: a burger franchise re-flag loses brand recognition, but a malatang re-flag also loses flavor - the broth is reason number one for repeat business. "Untested" is deliberately treated as a finding rather than missing data, because it is itself an instruction: whichever way the lean points now, the base test has to fit inside the 90-day window, otherwise choosing re-flag is choosing blind.

In the output format, "leans may coexist, confidence is tiered, supporting data must be named" exists to stop the model from hedging: refuse the binary verdict without forcing confidence and citations, and you get a fence-sitting paragraph praising all three exits - which is even more useless than a binary answer. Leans side by side with visible evidence, decision rights left with the franchisee: that is exactly the boundary between an analyzer and a decider.

The 90-day countdown is where the output lands: decision analyses have a habit of dying at "now I understand the situation." Pinning fill-data, base test, pre-talk, and the final call to week numbers walks the analysis all the way to decision day.

Variables

Variable Notes
Search-keyword data Brand-name search share from the delivery backend - the hardest evidence of brand pull; reviews and word-of-mouth are supporting cast
Soup-base test result Blind-test records (regulars + newcomers) of retail bases or own recipes. Not yet run = "untested," full stop
Renewal-term changes Differences between the new agreement and the first one (royalty, must-buy scope, term). No draft in hand? Assume old terms and flag the assumption

franchiserenewaldecision-making