What to Look for When a Training-Software Vendor Pitches You
Hey Team!
Let me tell you something I've heard about a hundred times. An operator sits across from me, arms crossed, and says "I've already bought three pieces of software that were supposed to fix my problems. I don't need another subscription." And you know what? They're right to be skeptical. Most software sold to restaurants has been oversold, underdelivered, and quietly abandoned by March. The graveyard of restaurant tech is enormous.
So if you're trying to get a skeptical owner to listen, whether you're a GM pitching your boss, a consultant working with a client or an operator yourself trying to talk a partner into something new stop leading with features. Nobody cares about your feature list. They care about Saturday night.
Here's what I mean by that. Picture a Saturday at 8pm. You've got a packed house, two servers who started this week, a bar running four deep, and someone at table twelve just asked your new hire what's in the walnut cream sauce. We ran into this exact situation at Fat Tommy's. The new server froze. Not because she was bad at her job. Because nobody had trained her on the allergens in that dish in any meaningful way. She'd been shown a menu PDF on someone's phone during onboarding and told "learn this." That's not training. That's hoping.
When you pitch a skeptical owner, that's the moment you paint. Not "our platform generates quiz questions from your menu." Who cares. The question is: what does Saturday look like when your staff actually knows the menu cold? What does it look like when a guest asks about a nut allergy and your server answers confidently instead of saying "let me go ask the kitchen"? That's a table you keep. That's a review that doesn't say "staff seemed clueless."
The skeptical owner isn't skeptical of training. They believe in training. They're skeptical of the friction. They've seen the binders that nobody opens. They've sat through the vendor demos where everything works perfectly on a Tuesday afternoon in a conference room and falls apart the moment a real cook tries to use it on a Monday before service. They've been sold "easy" before and gotten "another thing I have to manage."
So when you're having this conversation, acknowledge the graveyard first. Say it directly: "You've bought stuff that didn't stick. I get that." Because until you say it, they're just waiting for you to stop talking so they can say no. Once you name the thing they're thinking, the conversation actually starts.
Then talk about what frictionless actually means in practice. Not frictionless in the demo. Frictionless when you're short-staffed and trying to onboard two people before a Friday rush. The bar for "easy enough to use" in a restaurant is not the same bar as in a corporate office. Your staff is on their feet, moving fast, maybe English isn't their first language, and they've got about seven minutes between tasks. If the training tool doesn't work in that context, it doesn't work, period.
At Black Barrel Tavern, we noticed something that honestly surprised me. Staff started retaking quizzes on their own phones, voluntarily, before their shifts. Nobody told them to. Nobody built that into a policy. It happened because the format was short, it was on their phones, and it felt more like a game than a chore. That's the detail I'd share with a skeptical owner. Not a feature. A behavior change. Because behavior change is what they actually need. That's what puts money in the register.
Here's another thing worth saying directly in this conversation: don't over-promise the timeline. A skeptical owner has been burned partly because someone told them "you'll see results in two weeks." Maybe you will. Maybe it takes a full quarter before the new training culture sticks with a rotating staff. Honest expectations build more trust than optimistic ones. If you go in and say "this will solve everything fast and it's totally painless," you sound like every other vendor who burned them. If you say "here's what to expect in the first 30 days and here's what takes longer," you sound like someone who's actually done this.
The strongest version of this pitch isn't really a pitch at all. It's you saying: here's what my Saturday looks like now, and here's what it looked like before. Real, specific, no exaggeration. If you've got data, use it. If you don't yet, use the data that exists — Cornell's research put the cost of replacing a single restaurant employee at about $5,864 when you account for recruiting, onboarding, and lost productivity. If better training keeps two people from quitting, that's not a small number. That's real money a skeptical owner understands because they've felt it.
The last thing I'd say is this. Let the operator drive their own discovery. Don't spend forty minutes walking through every screen. Ask them: what's the hardest thing to train right now? What's the thing that keeps going wrong even after you think someone's ready? Let them talk. Their answer tells you exactly which problem to solve, and it's almost always something specific, something embarrassing, something that happened on a Saturday night. Your job is to connect that moment to a better outcome. The features are just the mechanics of how you get there.
Operators trust operators. Lead with the real story, stay specific, and never promise what you can't actually deliver.
Have a great day! — Terry
Your AI Restaurant Guy
