The Marketing Line
How a decision becomes a post, how a post becomes a bookable night, and how a bookable night becomes a room that delivers what was promised. Six stages, ten seats, ten surfaces.
What actually breaks
Bloom does not have a marketing problem. The nights are good, the creative lands, the room fills. What Bloom has is a handoff problem — decisions get made and then stop travelling halfway.
Every item below is from the platform audits run between 2 and 3 August 2026. None of them is a failure of taste or effort. Each one is a decision that was made correctly and then didn't finish moving.
| What was decided | Where it landed | Where it didn't | What the guest saw |
|---|---|---|---|
| Wednesday renamed Wine Wednesday → Hustle and Bloom |
Tablelist, website | Tock, ManyChat, IG creative | Two different names for the same night depending on where they looked |
| Tuesday, Thursday and Friday renamed to canonical names | Website, Tablelist | Tock — three retired names still live a day later | Booked "Live Music Tuesdays," arrived at The Bloom Sessions |
| Sunday = Chandon & Croissants | Tock | Tablelist (17 instances still "Sunday Brunch"), website (absent entirely) | No Sunday on the site at all |
| Bloom Brunch Experience runs Saturdays | Website, with a Sept 5 start date | Four August Saturdays were invisible | A brunch that looked like it didn't exist yet |
| Wednesday is a dining-led night offer vs path |
The offer: half-off pizza, half-off wine, $1 wings | No Tock dining experience for Wednesday at all | A food-and-wine night with no way to book a table |
| 1 Year Anniversary Weekend — a tentpole | Tablelist only | Website, /events | The biggest night of the year, invisible to anyone not already booking |
| Nobody decided this at all | SpotHopper auto-generated "national day" events | — | National Drink Beer Day on a Monday. The building is closed Mondays. |
| ManyChat answers the basics | Built, then paused | Still factory placeholder text: Mon–Fri 9–6, "delivery," a pricing link | Nothing — it was off |
| Somebody answers the DMs | Cleared once, 554 → 0 | No shift owner, no reply standard | 554 people who asked a question and got silence |
Look down the third column. Tock appears four times. ManyChat appears three times. The website appears three times. These are not random — they are the surfaces at the end of the chain, the ones nobody is named on, updated last or not at all.
A change that reaches two surfaces out of five is worse than no change, because now the surfaces contradict each other and the guest has to guess which one is true.
The line
Everything marketing does runs through the same six stages, whether it's a standing Tuesday or a tentpole weekend. The stages don't change. The lead time does.
Decide
The night, the offer, the price, the talent, the canonical name. Written down once, in the fact sheet. Nothing downstream may contradict it.
Build
Make the night buyable and deliverable. Booking path live on the right platform. Offer built in the POS. Kitchen and bar told. Talent contracted. This is the stage that gets skipped.
Dress
Flyer, reel, caption, story frames, email and SMS copy. Everything reads from the fact sheet, not from memory or from last month's flyer.
Publish
Out to every surface in the fixed order, inside one window, by one named seat. Half-published is not published.
Deliver
The floor gets the night brief before the night, not during it. Whatever the post promised, the room does — or somebody knew in advance that it couldn't and the post changed.
Count
Covers, sections, spend, saves, DMs, reviews, content captured. One page, Monday. It sets the next Decide.
A stage cannot start until the one before it is signed off. The most expensive version of this business is the one where creative is beautiful, the post performs, four hundred people see it, and the night it points at cannot be booked, isn't in the POS, and the kitchen didn't prep for it.
The two clocks
Two kinds of thing run through the line, and they run on different clocks. Confusing them is why tentpoles get announced late and standing nights get announced twice.
The weekly clock
STANDING NIGHTS- Covers
- The seven recurring identities — Tue through Sun, plus Saturday day.
- Locks
- Programming for the month locks on the 15th of the month before. Themes and guests for a given week lock 14 days out.
- Cycle
- Decide monthly, dress weekly, publish weekly, brief weekly, count weekly.
- Fails as
- Drift. Nothing dramatic — a name changes and three surfaces never hear about it.
The tentpole clock
ONE-OFFS- Covers
- Memorial Day Weekend, Summer Kickoff, Father's Day, Juneteenth, the anniversary, any booked headline talent.
- Locks
- Concept 60 days out. Talent contracted 45. Booking paths built 30. Announced 21.
- Cycle
- Runs once, front-loaded, with a countdown — section 12.
- Fails as
- Compression. Announced too late for anyone to plan around, so it sells like a normal night.
Anything that is not one of those two is an interrupt — a last-minute guest, a weather call, a viral moment worth chasing. Interrupts are allowed. They skip the calendar but they do not skip the gates, and the promise test in section 07 still applies.
Marketing seats
Ten seats. Positions only — names go on a roster, not in this document. At Bloom's current size one person holds several of these; that is fine and expected. What is not fine is a seat nobody holds, because the work still exists and simply stops happening.
Marketing Lead
OWNS THE LINE- Owns
- The whole line, end to end. The calendar, the budget, and the number the month is judged on.
- Decides
- What gets programmed, what gets spent, what gets killed. Signs the gate between every stage.
- Hands to
- Everyone. This is the only seat that touches all six stages.
- Measured by
- Covers and sections sold per night against the same night last month. Not reach.
- Covered by
- Ownership. There is no acting version of this seat.
If this seat is empty, the line has no gates and every other seat works to its own clock. That is the current state.
Listings Owner
STAGE 2 — BUILD- Owns
- Every place a guest can book or read about a night: website and /events, Tock, Tablelist Pro, Google Business Profile, the SpotHopper event calendar.
- Decides
- Nothing about what the night is. Everything about whether it is actually live and correct.
- Hands to
- Social Manager — and the handoff is a green light: "this night is buyable, you may post."
- Measured by
- Zero drift on the weekly sync check. Every night bookable on the right platform before its creative goes out.
- Covered by
- Marketing Lead, for a single night only. Not for a week.
This is the missing seat. Six of the nine failures in section 01 land here. It is unglamorous and it is the highest-leverage seat in marketing.
Content Lead
STAGE 3 — DRESS- Owns
- Creative direction, shoot planning, the shot list for every night, the edit, the look. Guards the brand against flyers that read like someone else's club.
- Decides
- What gets shot and what ships. Can refuse creative that is off-brand.
- Hands to
- Social Manager, as finished assets with copy attached.
- Measured by
- Assets delivered on time against the weekly lock. Saves and shares on published work.
- Covered by
- Marketing Lead or an outside creative on retainer.
Reads from the fact sheet, never from last month's flyer. The flyer that still said "LIVE MUSIC TUESDAYS" a week after the rename came from copying the previous one.
Social Manager
STAGE 4 — PUBLISH- Owns
- The feed, stories, the posting schedule, comments, tagged content, the propagation order in section 06.
- Decides
- Timing and sequencing within the published week. Not what the night is.
- Hands to
- Inbox Lead, for anything that turns into a conversation.
- Measured by
- Publish completeness — every surface, every week, in order. Then saves and shares.
- Covered by
- Content Lead.
Cannot publish a night that the Listings Owner has not green-lit. That refusal is the job.
Inbox Lead
STAGE 4 — CAPTURE- Owns
- ManyChat flows and keywords, Instagram DMs, comment replies, the response standard, and the handoff of anything that isn't marketing.
- Decides
- What gets automated and what a human answers.
- Hands to
- Lifecycle Lead, as captured contacts. The floor or ownership, for complaints and non-marketing inquiries.
- Measured by
- Reply time against the standard in section 13. Unassigned conversations at end of shift — target zero.
- Covered by
- A named person per shift, not "whoever sees it."
11,851 contacts sit in ManyChat. The inbox is not a chore attached to social — it is the top of the middle funnel and it is where group decisions get made.
Lifecycle Lead
STAGE 6 — RETURN- Owns
- SMS and email, the list, segmentation, win-backs, the habit loop in section 14. Owns the Toast → SpotHopper migration of SMS and email.
- Decides
- Who gets messaged, how often, and about what.
- Hands to
- Reporting seat, as repeat-visit data.
- Measured by
- Repeat visit rate inside 30 days. List growth net of opt-outs.
- Covered by
- Marketing Lead.
Blocked today on A2P 10DLC registration, which has not been started. Until it is, retention texting is not legally sendable at scale.
Talent & Events Coordinator
STAGE 1–2- Owns
- DJs, hosts, live acts, podcast and takeover partners. Contracts, call times, tech needs, payment terms.
- Decides
- Nothing about spend without the Marketing Lead. Everything about logistics once booked.
- Hands to
- Content Lead (name and handle for creative), Listings Owner (for the event listing), the floor (call times).
- Measured by
- Talent confirmed in writing before creative is briefed. Zero day-of surprises.
- Covered by
- Marketing Lead.
"Confirmed" means a signed agreement with a date, a fee and a call time. A text saying "I'm in" is not a booking.
Partnerships Lead
STAGE 1 — DEMAND- Owns
- Promoters, outside hosts, brand partners, group and corporate leads, sponsor relationships.
- Decides
- Which outside parties get a night, on what terms, with what minimum.
- Hands to
- Talent Coordinator for logistics, Listings Owner for the booking path.
- Measured by
- Revenue from partner-driven nights. Group and buyout leads worked to a close.
- Covered by
- Marketing Lead.
This seat is also where off-premise and catering demand lands. Today it lands nowhere.
Reputation Lead
STAGE 6 — ADVOCACY- Owns
- Google reviews — generation and response. The post-visit ask. Yelp and any other public review surface.
- Decides
- The response, within the reply playbook. Escalates anything about safety or staff conduct.
- Hands to
- Ownership, for anything that names a person or an incident.
- Measured by
- New reviews per month and rolling average. Response rate and response time.
- Covered by
- Inbox Lead.
Reviews are not reputation management, they are the top of the funnel for everyone searching "Southfield lounge" who has never heard of Bloom.
Reporting Seat
STAGE 6 — COUNT- Owns
- The Monday page. Pulls from Toast, Tock, Tablelist, ManyChat and the platforms, and puts one page in front of the room.
- Decides
- Nothing. Reports.
- Hands to
- Marketing Lead, as the input to the next Decide.
- Measured by
- The page exists every Monday and the numbers reconcile to the POS.
- Covered by
- Finance, if marketing cannot hold it.
Separate from Marketing Lead on purpose. Nobody should grade their own night.
One person can reasonably hold Content Lead + Social Manager. One can hold Inbox Lead + Reputation Lead. One can hold Talent Coordinator + Partnerships Lead. Listings Owner should be held alone or by the Marketing Lead — it is the gate, and gates held casually are not gates. Reporting should never sit with the Marketing Lead.
That is ten seats held by four or five people. What matters is that each seat has a name against it, and that the person holding it knows which of their hats they are wearing when they refuse to let something through.
Who owns which surface
Ten surfaces face the guest. Each gets exactly one owning seat. "Everyone can post" is how three surfaces end up disagreeing about what Wednesday is called.
| Surface | What it is for | Owning seat | Update cadence |
|---|---|---|---|
| bloomsouthfield.com | The centre. Everything a guest needs to decide, in one place. | Listings Owner | Weekly |
| /events page | The organic SEO asset. Ranks for day-of-week and "things to do in Southfield" searches. | Listings Owner | Weekly |
| Tock | Dining and brunch reservations. One experience per dining night. | Listings Owner | On change |
| Tablelist Pro | Sections, tables and bottles, all six nights. | Listings Owner | Weekly |
| Google Business Profile | Hours, photos, reviews. The first thing a stranger sees. | Reputation Lead | Weekly |
| Instagram @bloomsouthfield | Awareness, proof, and the group-chat decision. | Social Manager | Daily |
| ManyChat | Follower capture, FAQ, and routing to the right booking path. | Inbox Lead | On change |
| SMS — JOIN to 1-833-239-1387 | Retention and the habit loop. | Lifecycle Lead | Weekly |
| Retention and segmented campaigns. Migrating from Toast to SpotHopper. | Lifecycle Lead | Weekly | |
| SpotHopper event calendar | Feeds the site and the SEO page. Generates filler if left alone. | Listings Owner | Weekly |
The website is the centre, not Instagram. Ads, bio links and DM flows should all end at a page on the site that shows everything Bloom offers and routes to the right booking path. Instagram is rented ground and it does not rank.
SpotHopper generates events nobody asked for. National Drink Beer Day, Labor Day and National Prosecco Day were all sitting on the public calendar, two of them on Mondays when the building is closed. Somebody owns deleting those. Today nobody does.
One fact sheet, one order
There is one document that says what is true — the confirmed brand fact sheet. Names, hours, prices, addresses, which night routes to which booking platform. Every surface reads from it. Nothing overrides it, including a flyer that already went to print.
The propagation order
When anything changes, it moves in this order and only this order. The order exists because the surfaces at the end are the ones that get forgotten, so they go on a list instead of being remembered.
The fact sheet
Change it here or it did not happen. Nothing else moves until this line reads correctly.
The booking platform
Tock for dining, Tablelist for sections. The path has to exist before anyone is invited down it.
Website and /events
Both. The SEO page is a separate surface from the homepage and it is the one that ranks.
Bio links, highlights, pinned posts. Not just the next flyer.
ManyChat
Keywords, FAQ answers, the AI knowledge base, and every automated reply that names a night.
Re-check the map
Walk the sync map and confirm all five moved. A change is not done until this step is done.
A change gets 48 hours to complete the full order. If it cannot be finished in 48 hours, it does not start — the old name stays live everywhere until there is time to move it everywhere. A half-propagated rename is the single most common failure in section 01 and it is entirely self-inflicted.
The promise test
Before anything goes public — a flyer, a reel, an email, a story, an ad — it passes eight checks. Any single failure holds the post. This is the gate between stage 2 and stage 4, and it is the whole point of this document.
| # | The check | Who confirms | What happens if it's skipped |
|---|---|---|---|
| 1 | The name matches the fact sheet | Content Lead | Two names for one night. Guests book the wrong thing. |
| 2 | The date, day and time match the real hours | Listings Owner | An event on a Monday. A brunch that ends two hours before it closes. |
| 3 | The booking path is live on the right platform | Listings Owner | A dining-led night with nowhere to book a table. |
| 4 | Every dated instance is live, not just the first one | Listings Owner | A start date four weeks out hides the next four weeks. |
| 5 | The offer is built in the POS with a button | Floor manager | Bartenders improvise the discount. The number is unrecoverable afterwards. |
| 6 | Kitchen and bar know, and have the stock | Kitchen Manager / Bar Lead | The promoted item 86s at 9pm on the night it was promoted. |
| 7 | Talent is confirmed in writing | Talent Coordinator | A name on the flyer who never agreed to the date. |
| 8 | Somebody owns the shot list for that night | Content Lead | No proof the night happened. Nothing to post on Monday. |
Marketing's job is not to get attention. It is to make a promise the building can keep. A post that fills the room with people expecting something the room does not deliver is worse than no post — it converts strangers into one-star reviews, and it does it at scale.
The night brief
One page, per night, issued to the floor before the week starts. This is the artifact that crosses the line from marketing to operations. Without it the floor finds out what was promised from the guest who shows up holding a screenshot.
Night and canonical name
Exactly as the fact sheet has it. No shorthand, no old name in brackets.
The promise, verbatim
The actual words that went out. Copy and paste the caption. Not a summary of it.
Offer, price, minimum
Every number a guest could quote back. What it includes and what it does not.
POS build
Which button. Confirmed built, not "should be there."
Talent and call times
Who, when they arrive, when they start, what they need, who greets them.
Booking paths live
Tock experience and Tablelist packages named and confirmed live for this date.
Expected volume
Reservations on the book, sections sold, last month's same night. What to staff to.
Prep implications
What the kitchen and bar need extra of because of what was promoted.
Shot list
The three to five specific things to capture tonight, and who is holding the phone.
Manager on duty
The one person who can make a call if the promise and the room collide.
Recap owner
Who files the numbers and the content by Monday morning.
Known risks
Anything already wobbly — a talent who hasn't confirmed, stock that's tight, a short shift.
Marketing Lead drafts it, Listings Owner confirms fields 04 and 06, floor manager receives it. Thursday, for the week starting Tuesday. Twelve fields, ten minutes a night.
After the night
Stage 6 is where most hospitality marketing quietly stops. The night happened, everyone is tired, and the only record is a camera roll nobody edits. Three things happen after every night, and they are small.
Within 12 hours
- Content off the phone. Whoever held the shot list dumps it to the shared folder before the next shift. Footage that stays on a personal phone is footage that does not exist.
- The review ask goes out. Post-visit SMS or email to anyone on the book, pointing at the Google review link. This is the single highest-yield retention action Bloom is not doing systematically.
- Story reposts. Tagged content and story mentions get reshared while the night is still live in people's feeds.
Within 48 hours
- The recap post. Proof the night was good, aimed at everyone who didn't come. This is stage 3 of the funnel and it is what makes next week's decision easier for a group chat.
- Reviews answered. Every one, good and bad, inside the playbook.
By Monday
- The numbers filed. Covers, sections sold, spend per head, comps, DMs, new followers, new list subscribers, reviews. Against the same night last month.
- One line on what to change. Not a report. One sentence that goes into the next Decide.
Tock knows what people came for. Toast knows what they spent. ManyChat knows what they asked about. Put together, those three tell you who to invite back and to what. Separately they tell you nothing. Joining them is the Lifecycle Lead's standing job and it is the difference between a mailing list and a customer base.
Stage, owner, number
Eight funnel stages. Each one gets a seat and one number. If a stage has no number, nobody can tell whether it is working, and it quietly becomes optional.
| # | Stage | Owning seat | The one number | State |
|---|---|---|---|---|
| 1 | Awareness | Content Lead + Social Manager | New reach and new followers per week | working |
| 2 | Interest | Inbox Lead | Conversations started per week | working |
| 3 | Social proof | Content Lead | Tagged posts and story mentions per night | thin |
| 4 | Group decision | Social Manager | Saves and shares per post | thin |
| 5 | Conversion | Listings Owner | Reservations plus sections booked per night | leaking |
| 6 | Experience | Floor — not marketing | Spend per head and comp rate | working |
| 7 | Retention | Lifecycle Lead | Repeat visit inside 30 days | not running |
| 8 | Advocacy | Reputation Lead | New reviews per month and rolling average | ad hoc |
Stages 1 and 2 are the ones Bloom is good at — the reach is real and 11,851 people are sitting in ManyChat. Stages 3 to 5 are the middle, and the middle is where a stranger turns into a booking. Stage 7 is where a booking turns into a habit.
Stage 5 is marked leaking for a specific reason: every failure in section 01 happens exactly here. Somebody decided to come and then could not find a way to book, or booked the wrong thing. That is the cheapest revenue in the building, because the demand already exists.
The weekly rhythm
The line only works if it has a clock. This is the proposed week — fixed days, fixed outputs, so nobody has to ask what happens next.
| Day | What happens | Owning seat | Output |
|---|---|---|---|
| Monday | Last week counted. Numbers filed, reviews answered, recap posts out, one line on what to change. | Reporting + Reputation | The Monday page |
| Tuesday | Capture day. Shoot for the week after next. Content bank topped up while a night is actually running. | Content Lead | Raw assets |
| Wednesday | Build day. Listings Owner walks every surface, fixes drift, confirms next week's nights are buyable. Creative reviewed and approved. | Listings Owner + Content Lead | Green light per night |
| Thursday | Publish and brief. Next week's posts scheduled, email and SMS built, night briefs issued to the floor. | Social Manager + Marketing Lead | Scheduled week + 7 briefs |
| Friday – Sunday | Execute. Stories live, inbox worked inside the standard, shot lists shot. | Social + Inbox | The nights |
| 15th of the month | Programming for the month after next locks. Themes, guests, offers, tentpoles. | Marketing Lead | Locked calendar |
Note what Wednesday is. It is not a content day — it is the day somebody walks every surface and refuses to green-light nights that are not actually bookable. That single recurring hour is what stops section 01 from happening again.
The tentpole countdown
For Memorial Day Weekend, Summer Kickoff, Father's Day, Juneteenth, the anniversary, and any booked headline. Days before the night.
| Day | What must be true | Owning seat |
|---|---|---|
| T−60 | Concept locked. Target talent named. Budget ceiling set. | Marketing Lead |
| T−45 | Talent contracted in writing. Fee, call time, tech rider, payment terms. | Talent Coordinator |
| T−30 | Booking paths built and tested. Tock experience live, Tablelist packages priced with minimums. Creative briefed. | Listings Owner |
| T−21 | Announced. Every surface, same day, propagation order followed. Presale opens. | Social Manager |
| T−14 | Email one out. Promoter and partner seeding begins. Influencer list confirmed. | Lifecycle + Partnerships |
| T−7 | SMS one out. Daily story cadence begins. Night brief circulated to the floor. | Lifecycle + Marketing Lead |
| T−3 | Staffing confirmed against the book. Prep and par levels set. POS built and tested. | Floor manager |
| T−1 | Final push. Day-of assets queued. Talent contact confirmed. Shot list assigned. | Social + Content |
| Night | Shot list executed. Sections and covers tracked live. | Content Lead |
| T+1 | Recap out. Review asks sent. Tagged content reshared. | Social + Reputation |
| T+7 | Result against the number. New contacts segmented and folded into the list. One line on what to repeat. | Reporting + Lifecycle |
The anniversary weekend lived only on Tablelist. A tentpole that is announced at T−7 on one surface performs like a normal night, because nobody who needed to plan around it found out in time. Twenty-one days is the minimum for a night people are expected to organise their weekend around.
The inbox
Eleven thousand eight hundred and fifty-one contacts. Instagram's reply window is 24 hours — after that you cannot message a person back without them writing again. The inbox is not admin, it is the most direct conversion surface Bloom has, and it is the one with the hardest deadline.
The standard
| Type | Reply inside | Handled by | Routes to |
|---|---|---|---|
| Booking question — table or section | Automated, instant | ManyChat keyword | Tock or Tablelist |
| Hours, address, menu, happy hour | Automated, instant | ManyChat FAQ | Fact sheet answers |
| Birthday, group, large party | 4 hours, open hours | Inbox Lead | Partnerships Lead |
| Anything free text the bot can't route | 4 hours, open hours | Inbox Lead | — |
| Complaint about a visit | 2 hours | Inbox Lead | Floor manager, then ownership |
| Press, partnership, vendor | Next business day | Inbox Lead | Partnerships Lead |
| Job applications | Next business day | Inbox Lead | Hiring seat |
Rules
- A named person per shift. Not "whoever sees it." The shift ends when the inbox is at zero unassigned.
- The bot handles the top five questions, a human handles the rest. Automation that tries to answer everything answers nothing well and produces the placeholder problem.
- Nothing routes to a link that does not work. Every automated reply that names a night or a booking path is on the propagation list in section 06.
- Non-marketing inquiries have a destination. Today this is unresolved in the responsibility record and it is why things sit.
The ManyChat FAQ is still factory placeholder copy and is paused — guests get nothing. The Default Reply that catches free text is built but still sits as a draft, never set live. Both are one decision away from working, and both have been one decision away since early August.
The habit loop
The goal is not a busy Friday. The goal is a person who says "I go to Bloom on Thursdays" without thinking about it. That sentence is worth more than any single campaign, and it is built deliberately.
What makes a night a habit
- It never moves. Same night, same name, same offer, indefinitely. A night that changes identity every few months cannot become a habit.
- The promise is identical every week. The variable is the guest, the host or the theme — never the format.
- Somebody notices they came. Recognition at the door, a held table, a name remembered. This is a floor job that marketing depends on.
- They get one message between visits. One. Timed to the night they already come to.
The segments worth building
Three systems hold pieces of the same person. Joined, they produce a list worth messaging.
Tock
WHAT THEY CAME FOR- Gives
- Which experience they booked — brunch, dinner, a themed night. Party size. How far ahead they book.
- Segment
- Brunch people are not nightlife people. They want different messages on different days.
Toast
WHAT THEY SPENT- Gives
- Spend per head, what they ordered, bottle versus cocktail, frequency.
- Segment
- Bottle buyers get section offers. Everyone else gets the night, not the upsell.
ManyChat
WHAT THEY ASKED- Gives
- Keywords triggered, questions asked, what they nearly booked and didn't.
- Segment
- Someone who asked about sections twice and never booked is the warmest lead in the building.
None of this sends at scale until A2P 10DLC registration is done. It has not been started. It takes weeks. Every week it is not started is a week the retention stage in section 10 stays marked not running, regardless of how good the segmentation plan is.
Who can say yes
Marketing decisions stall not because they are hard but because nobody knows who is allowed to make them. This is the shortest possible version.
| Decision | Decided by | Consulted | Cannot be decided by |
|---|---|---|---|
| What a night is called | Ownership | Marketing Lead | Anyone making a flyer |
| Killing or replacing a night | Ownership | Marketing Lead, floor, kitchen | Marketing Lead alone |
| Weekly themes and guests | Marketing Lead | Talent Coordinator | — |
| Talent fee inside budget | Marketing Lead | Finance | Talent Coordinator alone |
| Talent fee above budget | Ownership | Finance | Marketing Lead |
| A new offer or discount | Ownership | Finance, kitchen, bar | Marketing, on its own |
| Holding a post that fails the promise test | Listings Owner | — | Nobody — this refusal is not overridable except by ownership, in writing |
| Ad spend inside budget | Marketing Lead | — | — |
| Responding to a review that names a person | Ownership | Reputation Lead | Reputation Lead alone |
| Comping to fix a marketing mistake | Floor manager on the night | Marketing Lead after | — |
Row seven gives a junior seat the power to hold a post that ownership wants out. That is deliberate. If the gate can be waved through by whoever is loudest that afternoon, it is not a gate and section 01 repeats. If ownership overrides it, that is fine — it just gets written down, so that when the night goes wrong the reason is on the record rather than in dispute.
Unowned right now
Straight from the responsibility record and the platform audits. These are not proposals — they are jobs that exist, are being done badly or not at all, and have nobody's name against them.
| The job | Seat it belongs to | Cost of leaving it |
|---|---|---|
| Non-marketing DMs and inquiries | Inbox Lead | Named in the record as unresolved. Messages sit past the 24-hour window. |
| An inbox owner per shift, and a reply standard | Inbox Lead | Open since early August. 554 unanswered once already. |
| Master calendar — events, deliveries, inspections, renewals | Marketing Lead + Admin | Nobody. Tentpoles collide with deliveries and nobody sees it coming. |
| Guest list and comp list management | Partnerships Lead | Nobody. Comps are untracked and unattributable. |
| Version control and naming conventions | Marketing Lead | Nobody. This is the direct cause of the drift in section 01. |
| Deleting SpotHopper's auto-generated events | Listings Owner | Nobody. Off-brand filler on the public calendar, some on closed days. |
| A2P 10DLC SMS registration | Lifecycle Lead | Not started. Retention cannot run. |
| Setting the ManyChat FAQ and Default Reply live | Inbox Lead | Built, drafted, paused. Guests get silence or placeholder text. |
| Off-premise and catering demand | Partnerships Lead | No owner, no path, no pipeline. Inquiries arrive and die. |
| Bloom / Vice revenue attribution | Reporting + Finance | One building, one POS, two concepts. Without a rule you cannot tell which one makes money. |
Take Listings Owner, an inbox owner per shift, and A2P 10DLC registration. The first stops the leak at stage 5, the second stops it at stage 2, and the third unblocks stage 7 — which cannot start until the paperwork is weeks old. Everything else on this page can wait a month. Those three cannot.
Tell us what's wrong
This is a draft, and the people who know whether it's accurate are the people doing the work. If a seat doesn't match what you actually do, if a lead time is unrealistic, or if something you handle every week isn't on any page — say so here.
The feedback form is directly below this document — scroll to the end of the page.