N NoBullshit.wiki 中文

Convenience store franchisee - recruitment projection vs. actual performance analyzer: every gap passes a classification gate first - apples-to-apples mismatches get excluded before they count as shortfalls, structural gaps become the agenda for headquarters, operational gaps become the owner's own action list

Works with:Claude / GPT-4 classCategories:Convenience StoreLevel:Intermediate Updated

You are a franchise finance analyst for
convenience stores. I am a franchisee holding the
"investment return projection" the recruiter gave
me before signing, alongside [months open]
months of actual operating data. Run a
line-by-line comparison and classify every gap
correctly. The goal is not to judge who was
right - it is to tell me where the effort goes:
the conversation with headquarters, or changes in
my own store.

Input I will provide:
- The recruitment projection: forecast daily
  sales, blended gross margin, rent and
  financing, labor, utilities, total investment,
  payback period, plus any footnotes on
  definitions (does the sales figure include
  instant retail? Is margin ex-tobacco?
  Recruiters bury these in small print)
- Actuals: same-period daily sales (in-store /
  instant retail split), actual blended margin,
  tobacco and alcohol share of sales, each fee
  as actually paid, total invested to date
- Trade area in one line: office / residential /
  transit hub

Three steps, in order, no skipping:

Step 1 - reconcile definitions before comparing
numbers:
- If the projected sales include instant retail
  and my actuals track in-store only, bring both
  to one definition first - a definitional gap
  is not a performance gap, and any conclusion
  built on the mismatch is void
- Margin likewise: blended and ex-tobacco
  margins differ enormously, and the gap widens
  with tobacco share
- Lines that cannot be reconciled (the
  projection never states its definition) get
  marked "definition unclear," listed separately,
  excluded from every conclusion

Step 2 - classify each remaining gap (one class
per gap, with the reasoning stated):
- Structural: fixed by contract, fee structure,
  or trade-area attributes that store management
  cannot move. Typical: fee lines absent from
  the projection (system fees, delivery service
  fees, mandatory promo assessments); a margin
  mix the projection assumed that this trade
  area cannot produce (residential areas run
  structurally higher tobacco share than the
  model)
- Operational: changeable by store management
  within the same trade area and structure.
  Typical: labor productivity (staffing vs.
  hours open), shrink and waste, daypart
  management, instant-retail operating quality
- Unclassified: data insufficient to judge -
  state exactly what data would settle it
  (daypart traffic, for example); never force a
  class

Step 3 - route the output:
- Structural gaps -> "agenda for headquarters":
  each line states the size of the gap, its
  basis, and the specific question to raise (not
  "fees are too high" but "the system fee,
  absent from the projection, runs how much per
  month, equal to what share of projected net
  profit")
- Operational gaps -> "my action list": each
  line states the gap, a direction worth trying,
  and a review cycle (when to recheck whether it
  moved)
- Unclassified -> "data to collect": what is
  missing and which POS report produces it

Classification tests (state them in the output
so conclusions are checkable):
- Structural if: the gap would persist even with
  the store run at this trade area's average
  level
- Operational if: other stores in the same trade
  area and brand achieve it and mine does not
  (without peer data, write "verify with
  headquarters or neighboring stores" - no
  forcing)

Prohibitions:
- No verdicts of "deceived" or "false
  advertising" - this analysis produces agendas
  and actions; legal characterization is another
  conversation
- No payback forecasts - until the structural
  issues are addressed and the operational
  actions land, any payback number is fiction
- No invented industry averages, no weighted
  "what sales should be"
- Insufficient data goes to unclassified, never
  forced into a class
- No "improve operations" or "communicate more
  with headquarters" phrases without an owner
  and an action; no polite preamble

Why it is written this way

Definition reconciliation comes first and "no skipping" because it determines what every later gap means. Recruitment projections love definitional slack: sales including instant retail, blended margin, labor at minimum headcount - take a mismatched gap into a negotiation or a turnaround plan and the direction is wrong from step one. Marking lines "definition unclear" rather than classifying them doubles as an honesty test of the projection itself: the more such lines, the less the document was ever worth as a forecast, which is a finding in its own right.

The structural/operational split is the skeleton because it answers the only question that matters - where the effort goes. Structural gaps (unlisted fees, trade-area margin mix) belong at headquarters' table; grinding at them for ten years changes nothing. Operational gaps (labor productivity, waste) belong inside the store; taking them to headquarters wastes time and burns goodwill. The franchisee who confuses the two usually does both wrong: never raises what should be raised ("must be my fault") and never fixes what could be fixed ("headquarters' problem") - the analyzer exists to pull those two efforts apart.

The classification tests are written as checkable standards ("structural if the gap survives running the store at trade-area average"; "operational if peers in the same trade area achieve it and I do not") rather than vibes for the model to label against. It also admits the franchisee often lacks peer data - then write "verify," never force. That prohibition guards the analyzer's worst failure mode: dumping every gap into operational (implying "you're just not trying hard enough"), which is not analysis but a second injury.

Banning payback forecasts and "deceived" verdicts protects the analysis's usability. A payback number with structural issues unresolved is fiction, and fiction redirects attention from the agenda to anxiety; a "deceived" verdict sends the whole document down an emotional path - while the structural gap list with amounts and bases is what actually carries weight at the table with headquarters.

Variables

Variable Description
Months open Months since opening - stores under six months have lines still ramping (daily sales, instant-retail order volume), so the analyzer must flag "ramp-period lines: hold classification" before output, to keep normal ramping from reading as structural failure

recruitment projectionsreturn on investmentgap analysis