N NoBullshit.wiki 中文

Community supermarket marketing planner - neighborhood pop-up booth checklist; written property permission first, booth clear of fire lanes and curb cuts, gift log to stop repeat claiming, and the first group message sent within 24 hours of joining

Works with:Claude / GPT-4 classCategories:Community SupermarketLevel:Intermediate Updated

You are the marketing planner of a community
supermarket. The store will run a pop-up booth
in a nearby residential compound (join-the-
group gift + special-offer vouchers + tasting
samples). Write me an execution checklist
covering before, during, and after.

One week before:
- Property filing: spot, hours, power - get it
  in writing. Without this line every line
  below it is void; file first
- Spot selection: inside the main entrance, by
  the parcel lockers - wherever foot traffic
  actually flows. Red-line self-check: never
  on the fire lane, never on the curb cut,
  never blocking a building entrance. One
  complaint and this compound never approves
  you again
- Materials count: tables and chairs, canopy,
  gifts (planned headcount x 1.2), QR stands
  (group code and voucher code on separate
  stands), event poster, tasting stock and
  hygiene kit (gloves, masks, picks, sealed
  trays)
- Roles: who hands out gifts, who walks people
  into the group, who restocks and holds the
  cash (if vouchers are sold on-site, one
  person takes money, a different one hands
  out vouchers)
- Rain plan: canopy enough? File a backup date
  with the property office in the same request

Event day:
- On site 30 minutes early; scan every QR code
  yourself first (group joins, voucher
  redeems)
- Gift log: record phone digits or group
  nickname to stop repeat claiming; when
  taking numbers, say what they are for
  ("we'll send the weekly specials") - state
  the use before collecting
- One joining line for everyone: "Join and
  tomorrow 8 a.m. you get the day's specials
  list" - a concrete post-joining expectation
  retains far better than "scan for a gift"
- Tasting rules: gloves and masks, samples
  sealed and portioned, name-brand product
  with full manufacturer and date labeling,
  nothing open left out past noon
- Voucher sales on-site: log every transaction;
  reconcile before packing up
- Leaving: trash out, site restored,
  photographed. That photo is exactly what
  the property office checks - and what
  decides the next approval

48 hours after:
- Numbers review: group joins / vouchers
  redeemed / new-store customers (ask at
  redemption, "how did you hear about this?")
  / gift cost
- Group handoff: first group message within 24
  hours of the event (next day's specials list
  or a joiners-only perk). New members' warmth
  lasts a day or two; finalize that first
  message a day ahead
- One thank-you note to the property office
  with the site-restored photo attached -
  paving the way for next time

Constraints:
- No samples without manufacturer and date
  labeling, ever
- No "mind the store image" filler - every
  line is an action, a check, or a red line
- Whatever the joining line promises (daily
  specials list) must actually keep going -
  posting for one week and then stopping hurts
  more than never promising; confirm someone
  owns the group long-term before promising

Why it is written this way

Written property permission sits in the first box because it is the only single-veto item on the sheet: the best spot and the best gifts die to one sentence - "you never filed" - and the incident follows you; property managers across compounds talk, and a black mark here travels to the next compound. The three red lines (fire lane, curb cut, building entrance) get their own line because they are the three most-complained-about placements: occupy any of them, one resident photo in the compound chat reframes the whole event.

The gift log takes phone digits or group nicknames, not full numbers, as a deliberate compromise: a complete record prevents repeat claiming perfectly, but a queue that sees "leave your phone number" loses a slice of people on the spot. Digits plus nickname stops the large majority of double-claiming while keeping the registration threshold invisible. And stating the use before collecting is both good practice and, in practice, the thing that lowers refusal.

"A concrete post-joining expectation" is the dividing line of the joining script: "scan for a gift" defines the group as a bin (claim and leave); "tomorrow 8 a.m. you get the specials list" defines it as a service (there is something here tomorrow). Join count is the vanity metric - retention on day three is the booth's real output, and the script decides which one you get in the first second.

"First message within 24 hours" leads the after-event block because it carries the most time pressure of anything on the sheet: joiners are warmest that same evening; a group that goes quiet for two days gets eaten by exits and mute-taps. The closing constraint is the mirror check - the worst booth outcome is not an empty group but two thousand members watching the specials list die after a week, which proves to two thousand people, in writing, that the store does not keep its word.

Variables

Variable Description
Gift buffer How many multiples of expected headcount to stock - 1.2 by default; 1.5 where foot traffic is a guess. Running out mid-event hurts more than leftovers

pop-up eventsgroup recruitmentevent execution