A chef claiming 'no time' for your food cost system usually means they're scared of change or don't grasp why numbers matter. This resistance happens in most restaurants. You can flip this situation around with the right tactical approach.
Why chefs resist systems
Most chefs are hands-on people. They'd rather cook than stare at screens. Many worry that systems will cage their creativity or turn you into a micromanager.
💡 Example:
Chef Marco says: "I've been cooking for 15 years, I know what things cost. I don't have time for computers."
What he really means: "I'm afraid you don't trust me anymore" or "I don't know how this works and that feels uncomfortable."
Start with the problem, not the solution
Skip the system pitch entirely. Focus on a shared pain point instead:
- "We're bleeding money on that steak, but I can't pinpoint why"
- "Supplier jacked up prices again—which dishes are now killing our margins?"
- "When you're out sick, nobody else can replicate your signature sauce"
Get your chef nodding about the problem before mentioning any solution.
⚠️ Watch out:
Never say: "You need to start using this." That triggers instant pushback. Try: "Can you help me figure this out?"
Make it relevant to his work
Chefs want to create amazing dishes and take pride in their craft. Frame the system as his creative ally:
- Recipe protection: "Your perfect sauce recipe stays locked in forever"
- Profit visibility: "You'll instantly spot if that new dish makes money"
- Smart sourcing: "Compare three salmon suppliers and find the sweet spot"
💡 Example:
"Marco, those fancy shrimp from supplier B cost €2 extra per kilo. Your shrimp salad jumps to 38% food cost with them. Way too steep."
Now Marco sees the system as his decision-making partner, not your control device.
Start small and build up
Don't dump everything on him at once. Baby steps work better:
- Week 1: Just your 3 top sellers
- Week 2: Toss in 2 more dishes
- Week 3: Let him input one new recipe solo
Once he realizes it's simple and actually helpful, resistance melts away naturally. Based on real restaurant P&L data, chefs who start with 3 dishes typically add 5-7 more within their first month.
Give him ownership
Transform your chef into the system's go-to expert. Have him enter new recipes and verify food costs. The system becomes his tool, not your surveillance camera.
💡 Example:
"Marco, mind checking what that new pasta dish runs? You're the only one who knows exactly how much truffle goes in."
Now Marco's the expert helping you solve problems, rather than feeling managed.
If he keeps refusing
Sometimes chefs dig in their heels despite your tactical approach. You've got two paths:
- Work around it: Input recipes yourself by watching him cook
- Set boundaries: Explain that system use becomes part of his role
But patience plus smart positioning usually transforms resistance into genuine interest.
How do you handle resistance to systems? (step by step)
Identify the real problem
Talk to your chef and find out why he's resistant. Is it fear, misunderstanding, or lack of time? Each problem needs a different approach.
Start with a shared problem
Name a concrete problem you both have (like losing money on dishes). Let him recognize the problem before you start talking about a system.
Start small and build up
Start with one or two dishes instead of everything at once. Once he sees that the system is useful and works easily, the resistance usually disappears on its own.
✨ Pro tip
Track your chef's reaction when you show him the real cost of his signature dish for the first time. Most chefs are genuinely shocked by the numbers and suddenly want to explore the system within 48 hours.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
What if my chef keeps saying he's too busy?
Offer to spend 10 minutes together after service ends. Demonstrate how quickly it actually works. 'No time' usually translates to 'I don't understand this thing.'
Should I force my chef to use the system?
Forcing backfires almost every time. Focus on explaining the why and showing how it helps his daily work. Once he grasps the value, adoption happens naturally.
What if he says systems limit creativity?
Clarify that the system documents his recipes—it doesn't handcuff his creativity. He can still experiment and adjust, but the foundation stays consistent for your business.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Give your team insight into the numbers
When your team understands what dishes cost, their behavior changes. KitchenNmbrs makes food cost visible to everyone in the kitchen. Start your free trial.
Start free trial →