Chef Robotics had millions of dollars in contracted revenue from fast-casual restaurant chains.

Rajat Bhageria still chose to walk away.

The demand was real. The model was not viable. Restaurants only operate at peak production for a few hours a day, while a useful robot may need to handle as many as 90 different ingredients. The economics and technical reality did not support the company Rajat wanted to build.

In this episode of Automated, Brian Heater speaks with Rajat, founder and CEO of Chef Robotics, about the difficult decision to leave restaurants behind as the company’s starting market and focus on high-mix food manufacturing instead.

Rajat explains how the team assumed food factories were already automated until it visited plants where hundreds of people were still portioning meals by hand. Unlike a restaurant, these facilities can run production for as many as 16 hours a day. A robot on a high-mix assembly line may also need to handle four or five ingredients instead of every ingredient on a restaurant menu.

The conversation reveals why so much fresh-food production remains manual. Low-mix products such as soup, cereal, or bagged vegetables can justify dedicated automation. Fresh meals, wraps, salads, and prepared foods require constant changeovers across hundreds or even thousands of SKUs. That flexibility still often comes from people working in refrigerated production rooms.

Brian and Rajat also examine the robotics graveyard. Rajat argues that many robotics startups do not fail because their technology is poor. They fail because they choose the wrong customer, solve the wrong problem, or never make the unit economics work. That same tension now hangs over the humanoid market, where capital runway may determine which companies survive long enough to reach commercial scale.

They also discuss what it takes to win a manufacturer’s trust when a startup has no track record. Chef structured early deployments around clear acceptance tests, embedded its engineers at customer sites, and spent a year sending team members into plants before sunrise to find bugs, release new software, and test it again the next morning.

Finally, Rajat explains why Chef’s lack of food-industry insiders became an advantage only because customers acted as true design partners. The team learned food safety, production planning, and line operations directly in the field. It also discovered that the hardest robotics problems were often the least obvious, including clear trays on white conveyors, sloped floors, changing line speeds, and placing food without spilling it.

The result is a candid conversation about product-market fit, customer pull, real-world robotics, and why shipping a useful system requires much more than building impressive technology.

Connect with Rajat Bhageria

https://www.linkedin.com/in/rajatbhageria

Learn more about Chef Robotics

https://www.chefrobotics.ai/

We’d love to hear from you. Have thoughts or guest suggestions?

Reach us at podcast@automate.org

You can find the transcript and more episodes of Automated at https://automated.fm

Unlock full access to Automated and explore everything automation.

Subscribe today and leave a review on YouTube, Apple Podcasts, Spotify, and the Automated Newsletter.

https://www.youtube.com/@automatedpodcast

https://podcasts.apple.com/us/podcast/automated-with-brian-heater/id1837762221

https://open.spotify.com/show/60olq6brlBEIJWggx2fMR6

https://www.automate.org/automation/automated-newsletter

LinkedIn
https://www.linkedin.com/showcase/automated-podcast-by-a3/

Instagram
https://www.instagram.com/automatedpod/

Rajat Bhageria on Why Chef Robotics Walked Away From Restaurants

Automated with Brian Heater

Rajat Bhageria on Why Chef Robotics Walked Away From Restaurants