Building Never86. I write about restaurant ops leaks: POS exceptions, labor drift, voids/comps, third-party margin loss, and the stuff operators catch too late.
๐จ Restaurants getting VARโd by DoorDash, Uber Eats & Grubhub โฝ๐ด
30-40% real cost after hidden fees.
One $50 order = $15โ20+ gone before ingredients.
https://t.co/ldAY5ARaeu = The VAR that actually helps operators keep the W.
Drop your worst 3P horror story ๐
#FIFAWorldCup #BRAvNOR #WeAre26
@daryljwilson@Larryjamieson_ Direct pickup helps, but the operator leak is bigger: menu prices, 86'd items, and modifiers have to match across POS, website, and 3P. One stale item online turns into refunds, bad reviews, and wasted labor before anyone sees it on a report.
@markproduct hard agree
linkedin is where you find out what someone used to do. x is where you find out what they're shipping today. one is a resume. one is the tape
restaurant tech is 80% consultants who never ran a shift and 20% operators who never shipped code
the operators are miserable using the tools the consultants built
the consultants keep raising off it
i'm in the second 20%. that's why we've moved
multi-unit chef-led restaurant group. last 7 days. $904K net sales
27% of it went through doordash, uber eats, grubhub
every single store is down 4 to 17% versus its own 30-day average
nobody at the group knows this yet. reports haven't been pulled
that's the gap. that's what we're building for
@sysprompter better late than never
Never 86'd = we tell restaurant operators every night which shift just cost them money and why. not the software. the receipt
that describes it in one line without capital letters
@markproduct hard agree
linkedin is where you find out what someone used to do. x is where you find out what they're shipping today. one is a resume. one is the tape
@sridharfyi step 5 checking in
real problem: restaurant groups can't see across toast, r365, and delivery
users: chef-led multi-unit paying pilot
keep coming back: daily active
money: yes
raising: now
most founders skip 1 through 4. i wish more didn't
@christophersaum Never 86'd
restaurant intelligence for chef-led multi-unit groups
ex-operator, ran a group i now sell into
one thing: we cross-vendor toast + r365 + delivery into one operator pane. nobody else has the operator's read on the data because nobody else has ever run the shift
@MCovBrown restaurant tech is the worst offender for this
every food cost reel we post gets saved by operators who then never hear from us. we started DMing every save last month. our reply rate is embarrassing for the rest of the category
@businessbarista curious how many operators are in that room vs execs
i'm running the same ai stack live inside a multi-unit chef-led restaurant group right now. toast iq, r365, ops floor. the potholes on the operator side are not the potholes on the enterprise side
would trade notes for a seat
@RestaurantNews1 Field execution is where franchise systems win or bleed out. A COO can matter if the cadence turns strategy into store-level checks: labor by daypart, menu availability, prep misses, guest recovery, and what GMs fix before it hits comp sales.
@sysprompter Restaurant operators don't usually lose margin in one big miss. It bleeds through bad counts, stale prep, missed 86s, menu drift, and labor drag. Never86'd turns those leaks into a manager action before the P&L tells you a month late.
@JaimeOikle Food cost leaks are usually boring before they get expensive. Bad counts, loose prep, substitutions nobody logs, and 86'd items not tied back to purchasing. If an operator only sees the leak on the P&L, the kitchen has already been training the problem for weeks.
I almost deleted my account.
Not because I hated creating.
Because it felt like I was talking to nobody.
170 days laterโฆ
2,900 followers.
5M+ impressions.
$485 earned.
Funny how quickly things change when you refuse to quit.
Happy to connect with more Founders .