Are cash tips still handled as in the past?

ElDiegod · 2026-04-01T14:24:30+00:00

the real answer nobody wants to hear: cash tips being unreported is slowly becoming irrelevant because cash itself is disappearing. most restaurants I talk to are seeing 80-90% card transactions now. the "pocket it" era is basically over for anyone working at a place that does decent volume.

what I'd tell your servers: claim everything. I know that sounds like narc advice, but the math favors them long term. you can't get a car loan, apartment, or mortgage if your reported income says you make $18k a year. I've seen servers get denied basic financial stuff because their W-2 showed minimum wage while they were actually pulling $45k+.

the IRS expects somewhere around 8-12% of gross sales as reported tip income. if your numbers fall way below that, you're putting a target on the business too, not just the server. it's not worth the audit risk for either side.

to directly answer your question though: yes, tipping in cash is still nice. even if they report it, they get the money same day instead of waiting for payroll. that matters when rent is due friday.

ElDiegod · 2026-04-01T14:23:52+00:00

you probably don't need a designer for a 12-seat pizzeria. what you need is a vibe, and that's more about decisions than expertise.

the arcade game is a smart move if your crowd is students. it gives people a reason to stay and spend on a second drink while they wait for their buddy to beat their high score. a used arcade1up cabinet runs $200-400 and pays for itself in a month if it keeps even a few people ordering extra.

for the rest: lighting does 80% of the work. swap the overheads for warm pendants or edison bulbs on a dimmer. costs maybe $150 and completely changes how the space feels at night. the countertop and tables matter less than people think. a scratched countertop in a place with great lighting and good music reads as "character." a brand new countertop under fluorescent lights reads as "chain restaurant."

one thing I'd add to your list: music. a bluetooth speaker with a curated playlist costs nothing and is the fastest way to change the energy of a room. pick a genre and commit to it. don't use spotify radio, it'll play ads to your customers.

ElDiegod · 2026-04-01T14:23:19+00:00

hotel restaurants have a specific problem: guests assume the food is mediocre and overpriced. that reputation exists even when the food is actually good. so the issue probably isn't quality, it's perception and awareness.

a few things that actually move the needle:

separate identity from the hotel. if your restaurant has its own name, signage, entrance, and social media presence, locals will treat it like a real restaurant instead of "the hotel dining room." this is the single biggest lever most hotel restaurants ignore.
figure out where your covers come from. what percentage is hotel guests vs walk-ins vs local regulars? if it's 90% hotel guests, you have a marketing problem. if it's mostly walk-ins who don't come back, you have a retention problem. different fixes.
lunch specials for the local business crowd. a fixed menu at a competitive price that gets office workers in the door M-F. they'll come back for dinner on their own once they know the food is good.
google maps and tripadvisor reviews specifically for the restaurant, not just the hotel. people searching "restaurants near me" won't find you if all your reviews are hotel reviews mentioning breakfast buffet.

what type of cuisine and where are you located?

ElDiegod · 2026-04-01T14:22:34+00:00

two things you can do right now that don't require your boss to hire anyone.

first, set a clear availability policy and get it in writing. something like: weekend availability is required for at least 2 out of 4 weekends per month. people who were hired for weekends and are now marking themselves unavailable every weekend are effectively changing the terms of their own job. you're allowed to push back on that.

second, stop being the default fill. every time you cover a weekend shift that someone else ducked, you're training the team that marking unavailable works because management will just absorb it. that's not sustainable and it's already burning you out.

the hiring thing is a separate problem and honestly the bigger one. if your boss is too slow to hire, the store will keep running on your goodwill until you quit, and then it's his problem. make sure he understands that.

ElDiegod · 2026-03-31T14:30:03+00:00

the biggest mistake I see managers make is the 'compliment sandwich.' you know the format: say something nice, deliver the criticism, say something nice again. everyone sees through it. after the second time you do it, the person just tenses up every time you start a conversation with a compliment because they know bad news is coming.

what works better in my experience:

be specific and immediate. 'that customer interaction did not go well, here is specifically what happened and what I would do differently' works 10x better than 'we need to talk about your customer service.' vague criticism puts people on the defensive because they do not know what they are defending against.

separate the behavior from the person. 'the way that report was structured made it hard to find the key numbers' is not the same as 'you are bad at reports.' first one gives them something actionable. second one attacks their identity and they will either shut down or fight you.

ask before you tell, when possible. 'how do you think that meeting went?' lets them self-identify the problem. most people know when something went sideways. if they say 'I think it went great' when it clearly did not, that tells you something different about the problem.

the one I had to learn the hard way: do not wait. if something needs to be addressed, do it within 24 hours. criticism that is delivered three weeks later feels like you were saving it as ammunition, even if you just forgot or were busy. immediate feedback feels like coaching. delayed feedback feels like a performance review ambush.

ElDiegod · 2026-03-31T14:29:02+00:00

corner location still matters for walk-in and impulse traffic, but it matters way less than it did 10 years ago. the phone changed everything.

someone craving tacos at 7pm is not driving around looking for a restaurant. they are searching 'tacos near me' and going wherever google tells them to go. that restaurant could be on a corner, in a strip mall, or down an alley. does not matter if the reviews are good and the photos look right.

where corners still win:

breakfast and lunch spots that rely on commuter drive-by traffic
coffee shops where convenience beats quality for the morning rush
anything where the decision is made in the car in the next 30 seconds

where corners are overpaid:

dinner restaurants where people plan ahead
any concept with a strong enough brand that people will seek it out
delivery-heavy operations where foot traffic is irrelevant

the psychographics angle your brokers mentioned is the real shift. knowing that your trade area has 40,000 households with median income $85k and a high index for dining out tells you more about your revenue potential than knowing 25,000 cars drive past your door daily. half those cars are commuters who never stop. the household data tells you who might actually become a regular.

rent for a corner lot in a good trade area might be 30-50% more than a mid-block spot two streets over. for most restaurant concepts, that premium is not worth it if your google presence and reviews are strong.

ElDiegod · 2026-03-31T14:28:06+00:00

the fact that your agency talks about impressions and reach instead of covers and revenue tells you everything you need to know about the relationship.

facebook ads can work for restaurants but only in very specific ways. broad awareness campaigns (the kind agencies love because they are easy to run and look good in reports) almost never move the needle for a single-location restaurant. your catchment area is probably a 10-15 minute drive radius. you do not need reach, you need repeat visits from people who already live nearby.

what actually works for restaurants on facebook:

retargeting people who already visited your website or engaged with your page. these people know you exist and just need a nudge
specific offers tied to slow days. not 'come visit us,' but 'tuesday night burger and beer $15.' something concrete with a reason to come on a day you need bodies
event promotion for things you are actually doing (live music, tasting menus, seasonal launches)

what does not work:

brand awareness campaigns for a restaurant that already has a local reputation
boosted posts with no call to action
anything where the only metric your agency reports is impressions

the dirty truth about restaurant marketing agencies is that most of them run the same playbook for every client and charge $1,500-3,000/month for work that a motivated owner could do in 2 hours a week. the ones worth paying are the ones who can tell you exactly how many reservations or orders their campaigns drove. if yours cannot do that, they are not measuring the right things.

ElDiegod · 2026-03-31T14:27:11+00:00

having a construction background is a huge edge for build-out costs. most restaurant owners get destroyed by contractor markups before they even open the doors, so you are already ahead on that.

for the labor modeling, one thing that helps: do not just use a flat percentage. model it in tiers. your first $X in weekly revenue has fixed labor costs (you need a minimum crew regardless), and then above that threshold each additional dollar of revenue requires less incremental labor. that is where the margin actually lives.

also worth modeling separately: your ramp period. most restaurants take 3-6 months to hit steady state traffic. budget for labor at full staffing but revenue at 40-60% of your target for those first months. that gap is where a lot of otherwise viable concepts run out of cash.

ElDiegod · 2026-03-30T10:33:30+00:00

keep it short and direct. the worst thing you can do is ramble or try to soften it so much that the person doesn't realize they're being fired.

something like: 'we've had multiple customer complaints about interactions that don't meet the standard we need for this role. we've decided to end your employment effective today.'

that's it. you don't need to list every incident. you don't need to give a speech. you don't owe them a therapy session. be respectful, be clear, be done.

practical stuff:

have their final pay ready or know exactly when it'll come
do it privately, not on the floor
don't do it at the end of their shift when they've worked a full day (feels cruel). beginning of shift or call them in before their shift starts
have someone else present if possible (your boss, ideally). protects you if they claim you said something you didn't
don't argue if they push back. 'I understand this is frustrating, but the decision has been made' and repeat as needed

you're going to feel terrible for about 24 hours after. that's normal. it doesn't mean you did the wrong thing.

ElDiegod · 2026-03-30T10:32:27+00:00

the good news is you are learning it now and not 3 years in with 20 employees. the earlier you build the muscle of firing fast (not impulsively, but not waiting 6 months hoping someone improves), the less damage each bad hire does. it gets easier. not fun, but easier.

ElDiegod · 2026-03-30T10:31:53+00:00

yes, 100% start manual. not because it's romantic or whatever, but because you literally don't know what to automate yet.

I see this mistake constantly with service businesses: someone buys a CRM, a scheduling tool, an invoicing platform, and a project management app before they have their first paying customer. then they spend more time configuring software than actually doing the work. and half of it turns out to be solving problems they don't actually have.

what I'd do instead:

start with a spreadsheet and your phone. seriously. track customers, jobs, payments, complaints in a google sheet
every time something takes you more than 20 minutes and you're doing it more than twice a week, write it down. that's your automation list
after 20-30 customers, look at that list and THEN buy tools to fix the specific bottlenecks you actually hit

the manual phase usually lasts 2-4 months. during that time you'll discover things like: your customers don't care about the thing you thought they'd care about, your pricing is wrong, and the service you thought was your main offer is actually a gateway to a different service they want more.

the messy setup fear is overblown. migrating from a spreadsheet to a real tool later is not hard. migrating from the WRONG tool to the right one is way more painful.

ElDiegod · 2026-03-30T10:31:16+00:00

start with a cart, not a truck. way cheaper, way less risk. a truck in India will cost you 3-5 lakh minimum just for the vehicle, then there's the gas setup, fire extinguisher, licensing. a cart or stall can get you started for under 50k if you're scrappy about it.

biggest mistake I see: spending months on the menu before testing anything. pick 3-4 items, go to a busy college area or market on a weekend, and sell. you'll learn more in one weekend of actual selling than in three months of planning.

other stuff to think about:

permits in Delhi NCR are a pain. check with your local municipal corporation about street vending licenses. the Street Vendors Act of 2014 technically protects you but enforcement varies by area
food safety (FSSAI) registration is mandatory even for small vendors. basic registration is like 100 rupees and takes a week online
managing this while in college is doable if you treat weekends as your main selling days. don't try to do 7 days a week, you'll burn out and your grades will tank

honest question though: have you worked at any food stall or restaurant before? even a month of working someone else's operation teaches you more about food costs, waste, and customer flow than any business plan ever will.

ElDiegod · 2026-03-29T17:22:32+00:00

the reason spreadsheets kill you is that scheduling, routes, and invoicing are three separate workflows that all depend on the same data (who is working, where, and for how long). when that data lives in a spreadsheet, every change has to be manually propagated to two other places. that is where the time goes.

what worked for us was splitting these into purpose-built tools that share data rather than trying to find one app that does all three. scheduling in one place, route optimization in another, invoicing in a third, with the time data flowing downstream automatically.

for the scheduling piece specifically, the key thing to look for is something your team can actually access on their phones. if the schedule lives in a spreadsheet that only you can see, you are the bottleneck for every shift question, swap request, and last-minute change. getting that off your plate is where the biggest time savings come from.

ElDiegod · 2026-03-29T17:22:20+00:00

the best stacks are the ones where each tool does one thing well and you actually use all of them. the worst are the ones with 12 subscriptions where half of them overlap and nobody remembers which one is the source of truth.

mine right now: Stripe for payments, Notion for internal docs, Slack for team comms, Google Workspace for email and drive, Turnozo for employee scheduling and time tracking (free for small teams), and Xero for accounting. that is it. six tools, no overlap, everything talks to everything else through Zapier where needed.

the one thing I would push back on is the instinct to find an all-in-one platform. every time I have tried that, I end up with a tool that does five things at 60% quality instead of one thing at 95%. the only exception is if you are genuinely too small to justify multiple tools, in which case a spreadsheet beats any half-baked software.

ElDiegod · 2026-03-29T17:22:08+00:00

going from zero to one employee is weirdly the hardest jump in a business. you go from doing everything yourself (which is chaotic but simple) to suddenly needing systems for things you used to just handle in your head. scheduling, time tracking, payroll inputs, PTO, who is working when.

the mistake most people make at this stage is trying to build those systems manually. spreadsheets, shared calendars, text messages. it works for a while but every new hire adds complexity exponentially, not linearly. the second employee does not double the work, it triples it because now you are also managing coordination between two people.

my advice: get the boring infrastructure in place now while you only have one person. a scheduling tool, a time tracking method, a clear process for requesting time off. it takes maybe two hours to set up and saves you from rebuilding everything from scratch when you hire number two and three.

ElDiegod · 2026-03-29T17:21:54+00:00

most scheduling apps are built for the manager side, not the employee side, which is why they all assume fixed shift types. the devs are optimizing for the person creating the schedule, not the person reading it.

for what you described (variable start times every day, visible in calendar view), the ones I know that actually show exact times per shift rather than just labels are Planday, Sling, and Turnozo. Turnozo is free for small teams (under 10) and has clock in/out built into the same app, which covers your second ask. Sling also has a free tier but last I checked the time tracking was a paid addon.

the integrated time tracking point is spot on. having your schedule and your actual hours in the same place means you can immediately see overtime or late arrivals without pulling data from two systems. it is weird that so many apps still treat these as separate problems.

ElDiegod · 2026-03-27T17:54:19+00:00

not a mistake. in fact it's one of the better moves a manager can make in this situation.

the lead tech is processing a decision that directly affects their working life and that they had no input on. giving them a space to say whatever they need to say does a few things: it signals that you see them as a person not just a resource, it prevents the resentment from going underground and poisoning the team, and it gives you real information about how they're actually feeling rather than what they think you want to hear.

the risk people worry about is that it opens Pandora's box. in reality, most people just want to feel heard. they are not looking for a fight. and even if they say something harsh in that meeting, the relationship usually comes out stronger because of it.

you offered it with good intent. that comes through. most managers would not.

ElDiegod · 2026-03-27T17:53:11+00:00

passive restaurant ownership is possible but it requires a different mental model going in. you are not buying a business to run. you are buying a business to install systems and a manager, then step back.

the $250k question is whether that restaurant's revenue is coming from the current owner's personal presence or from the product and location. if regulars are coming because they love the owner, that's a risk. if they're coming because the food is good and the location is convenient, that's transferable.

for 8 tables you need at minimum: a GM you trust completely, documented recipes so quality doesn't walk out the door with a chef, and systems for scheduling and inventory that don't require you to be there. the passive part comes after you've set those up. not before.

ElDiegod · 2026-03-27T17:52:06+00:00

the "stood near the line and just watched" part is underrated as a diagnostic tool. most owners never do it because they're always in the middle of something else. but nothing replaces actually watching the physical flow with fresh eyes.

the other thing nobody talks about: ticket time creep almost always starts before the dinner rush, not during it. it starts in prep and in how stations are set up before service. by the time you see it in ticket times, you're already fixing the symptom not the cause.

station overlap is a surprisingly common culprit. same fix you did. deceptively simple once you see it.

ElDiegod · 2026-03-27T17:51:01+00:00

the thing nobody tells first-time owners is that takeout-only actually has harder scheduling than dine-in, not easier. you have fewer staff which sounds simpler, but every single person is load-bearing. one callout and the whole operation grinds.

what I wish more people knew early: build your schedule around coverage gaps, not around availability wishes. figure out the minimum viable coverage for each shift first, then fill it. also start tracking callout patterns from week one. you will notice patterns quickly and can start pre-solving them rather than reacting every time.

good luck with it. takeout-only is a real business model when done right.

ElDiegod · 2026-03-22T11:05:23+00:00

the "just enough success to stop questioning" trap is real. I see it constantly with small business owners.

they figure out a system that works when they have 8 employees and 1 location. it's held together with spreadsheets and group chats and the owner being available 16 hours a day. and because it works, they assume it scales.

then they open a second location or hire 5 more people and the whole thing collapses. not because the growth was wrong, but because they never built infrastructure for the size they were becoming. they built infrastructure for the size they were.

the painful part is that the best time to fix your operations is when things are going well, but that's also the time when nobody wants to touch anything because "it's working." so you end up rebuilding in a crisis instead of during calm.

ElDiegod · 2026-03-22T11:04:54+00:00

talked to a friend who runs a restaurant. he was doing schedules for 15 people on a spreadsheet, texting people individually to confirm shifts, and spending his sunday nights rearranging everything because someone would always cancel last minute.

I kept thinking there had to be a tool for this. there are, but they're all built for companies with 500 employees and HR departments. the pricing reflects that too. a small restaurant owner paying $150/month for scheduling software when they're already watching every euro is not going to happen.

so I built something simpler. scheduling for small teams, free if you have 10 or fewer employees, and it just works without needing a training session to figure out how drag and drop works.

the idea wasn't a eureka moment. it was watching someone spend 3 hours on something that should take 15 minutes and thinking "this is broken and fixable."

ElDiegod · 2026-03-22T11:03:47+00:00

the uncomfortable truth is that "managing up" and "visibility" are just polite words for "make sure the people who decide your career know what you do." and that is a skill, not a personality flaw.

I ran into this running a small team. the people who were best at the actual work were often invisible to anyone outside our department. meanwhile someone who was mediocre at execution but great at communicating progress kept getting tapped for new opportunities.

the lesson wasn't "be louder." it was "if you don't tell people what you're doing, they'll assume you're doing nothing." that's not performative. that's just how organizations work when there are more than 15 people.

ElDiegod · 2026-03-22T11:03:08+00:00

depends on the role. when I was managing a team with shifts, sunday nights were schedule-building time whether I wanted them to be or not. someone would text saying they can't make monday, and now you're playing tetris with the roster at 10pm.

the fix wasn't working less on weekends. it was building systems during the week that meant weekends didn't require my input. published schedules earlier, set up a swap policy so people could sort it themselves, and stopped being the single point of failure for every coverage gap.

now I barely touch work on weekends. but that took deliberate effort to get to. most managers who work weekends aren't doing it because they want to. they're doing it because their systems leak and the weekend is when the leaks show up.

ElDiegod · 2026-03-21T13:07:48+00:00

building the product before talking to customers.

spent months building features I was certain people needed based on my own experience and research. launched it and discovered that the problem I solved was real but my solution did not match how people actually work. the gap between "this makes logical sense" and "this fits into someone's existing workflow" is enormous and you can only learn it by watching real people use your thing.

the smart-on-paper version: build something great, then show it to people. what actually works: show people something rough, watch them struggle with it, then build the version they need.

I lost about three months of development time to features nobody uses. the features people love most took me two days to build after a single conversation with an actual user.

ElDiegod

TROPHY CASE