Sunny Ray welcomes Omar Abdul-hadi of Adeeb Robotics back for part two of a conversation about leaving a senior engineering role at Apple to build industrial robots. Omar explains why he wanted a clean slate after years at Yaskawa, how his team wrote its own EtherCAT master stack from scratch in about seven months, and why the company started with a Delta robot instead of a robotic arm. He describes a settings-first software philosophy built in Rust, with a web-based interface and 3D simulation, and credits his father's decades of machining experience. The discussion covers four years of bootstrapping, supply chain and shipping hurdles, and a robot priced around 16,000 dollars. Omar also explains why small and mid-sized factories value responsive support above nearly everything else, and how a young hardware company earns trust through trade shows and detailed answers. His first customer, who found the company online, assembled the robot in two or three hours. The episode closes with where listeners can learn more.
A former Apple engineer explains how he and his machinist father bootstrapped a robot company by writing their own EtherCAT stack from scratch.
What made you leave Apple to build industrial robots?
I always had a passion for robotics. I spent years at Yaskawa watching how slowly the automation industry moves. I wanted a clean slate, to do things differently and use the latest technology. Older companies get bogged down in large code bases that can't be refactored easily, and they struggle to adopt new technology.
What was one of the biggest early hurdles?
EtherCAT. It is extremely time-sensitive, with timing measured in nanoseconds and synchronization to microseconds. We didn't want to license it from a third party, and the open-source options were poor, so we wrote it from scratch. That alone took about seven months, and once it worked, I felt we could build our own motion controller software.
Why did you build a Delta robot first instead of a robotic arm?
Delta robots are cheaper, faster and easier to make. The joints support each other in parallel, so the structure is stronger, while an arm's first joint carries all the others. A Delta has roughly half the joints, so half the motors, servo drives and gearboxes, and no cable routing inside an arm. We'd love to revisit arms later.
How did you design the robot so your first customer could assemble it so quickly?
We used IKEA-style exploded view instructions with everything labeled. The customer said it felt like putting together Lego. Four people did it in two or three hours. Every part is a manageable weight, so no crane is needed, and the box is layered so each foam layer reveals the next set of parts to install.
What do you build in-house that most robot makers buy from someone else?
The EtherCAT master stack. I worked at Yaskawa, Applied Materials and Apple, and none of them developed it themselves. We own it and can modify it quickly. We also used Rust for the back end, and our web-based UI with 3D simulation, jogging and calibration ships as a single integrated binary.
What surprised you about how small factories decide to automate?
It's always about support. These projects are expensive, and they don't want a vendor to disappear a year after the sale or leave them with downtime when something breaks. The economics also work, since labor costs keep rising. At about 16 grand, our robots pay for themselves within a year or two.
How do you earn trust as a new robot company?
It's been the most challenging part, because our product costs as much as a car. We go to PACK Expo every year, and this is our third in a row. Everyone in this industry knows everyone. My seven years at Yaskawa also lends credibility, and our first customer trusted us because I answered their questions thoroughly.
Building something daring? Sunny talks to founders like this every day. Fifteen minutes to see if your story belongs on the stage.
Claim your pre-interviewSend a founder here and we will know it was you.
One email a week. The best ideas from the show, read through bitcoin, AI and robots, and what founders should do about them.