Building a Robotics Company in Ohio: Path Robotics and Drive Capital on Midwest Venture, AI, and Manufacturing

Open on YouTube ↗
Overview

This live episode of Manufacturing Happy Hour, recorded in front of a packed room in Columbus, Ohio, asked whether the Midwest can build world-class technology companies, and what that looks like in practice. Host Chris brought together Andy Lonsberry, CEO and co-founder of Path Robotics; Nima Gard, Path's Director of AI; and Nils Root, who runs marketing at the venture firm Drive Capital. The guests agreed on the main point: Ohio is not "the next Silicon Valley," and it doesn't need to be. Their case is that the region can produce serious technology businesses on its own terms, drawing on its manufacturing base, its talent, and a startup culture that is slowly maturing. Along the way, the Path founders explained how their technology works, why they treat data as their most valuable asset, and how they think about automation and jobs.

24 min read

"Absolutely not": why Ohio isn't the next Silicon Valley

Chris opened by asking Root directly whether Ohio is the next Silicon Valley. Root first gave context on Drive Capital. He described it as the largest venture capital firm between the coasts. It is about 12 years old and was founded by two Silicon Valley VCs on the thesis that more great technology businesses would be built outside Silicon Valley than inside it over the next 20 years. Drive invests in places such as Columbus, Chicago, Atlanta, Toronto, Denver, and Austin. Root's view is that technology companies will increasingly be built where people and industry already live. Root has been at Drive for six years and handles PR, content, and events.

His answer to the question was "absolutely not." He compared it to calling Atlanta the next Hollywood because films are made there, or calling Montgomery the next Detroit because it builds cars. By his account, Silicon Valley was a special historical case. Building technology companies once required specific infrastructure and a talent pool that could manage it, and both were concentrated within a 10-to-20-mile radius around San Francisco. That changed around 2007–2008 with cloud computing. With an internet connection and a credit card, anyone could rent storage and compute from AWS. What remained scarce outside the coasts, in Root's telling, was venture capital to fund those companies.

So Ohio's opportunity is not to copy Silicon Valley but to become "the best version of Ohio possible." As evidence, Root pointed to Path Robotics and Root Insurance, which he said was started in Drive's office and is now public. He also noted that established tech companies such as Anduril and Intel are coming to the state. He credited Ohio and Columbus with being business-friendly and said he doesn't know whether there will ever be another Silicon Valley, just as there isn't another Hollywood. Chris said he had deliberately set up the question after hearing the "next Silicon Valley" framing elsewhere, and he endorsed Root's reframing.

Path Robotics' origin story: a garage fab shop, humanoid robots, and a $300,000 first customer

Asked why Ohio was the right place to start Path, Lonsberry told the company's story. He was born and raised in Ohio in what he called a standard Ohio manufacturing family. All of his grandparents and great-grandparents worked in manufacturing, and many were welders. His father has spent roughly 40–45 years in manufacturing and turned the family garage into a fabrication shop with a mill and a lathe. Lonsberry started building off-road vehicles there at age seven. When he was ten, his father quit his job to start a company building two- and four-wheel off-road vehicles. For about four years they ran it out of a roughly 5,000-square-foot facility in Warren, Ohio, with just the family and a handful of employees. Lonsberry said the experience showed him firsthand how hard it is to manufacture a product, and how hard it is to find and keep good people to scale a business. That lesson stayed with him.

In college he was studying mechanical engineering when he first saw Boston Dynamics. It made him want to make mechanical systems intelligent. He interned at the Institute for Human and Machine Cognition, which he described as a facility of MIT PhDs working with Boston Dynamics on bipedal robots and exoskeletons. He then spent six years on a PhD in deep reinforcement learning for humanoid robots, essentially teaching robots to walk. He noted the irony that Path doesn't work on humanoids. His brother was doing a PhD in computational neuroscience at the same time. Drawing on their robotics background and their manufacturing upbringing in Ohio, the two decided to build a company around machine intelligence and computer vision for robotics. The goal was to make manufacturing, which Lonsberry called one of the oldest and hardest businesses to scale, easier to grow.

They talked to about a hundred U.S. manufacturers in Ohio. One, Corsa Performance, agreed to pay about $300,000 for what Lonsberry described as the first fully autonomous welding cells. He stressed that these were genuinely autonomous. An operator put in a part and pressed a single "go" button. The system then had to 3D- and 2D-scan a generic area, recognize what should be welded, decide how to weld it, collect data during and after the weld to judge whether it was good or bad, and feed that data into a reinforcement learning algorithm to keep improving.

With that customer in hand, Lonsberry flew to Silicon Valley expecting to be dismissed. He said people there asked where Ohio was, and some assumed Ohioans "ride cows and chew tobacco." Still, the two PhDs found a first investor who gave them seed money. Back in Ohio they met Drive Capital. Lonsberry described Nick, Path's board member from Drive, as relentless, constantly texting and calling to be part of the company. After closing the deal with Drive, the founders moved to Columbus, reincorporated as Path Robotics, and set out to be a machine learning company that makes robots smart enough to help manufacturing.

Not a welding company: welding as the "heartbeat," assembly as the next task

Chris said Path seems to have become more than a welding robot company. Lonsberry agreed that people usually label Path as welding automation, and said that isn't entirely accurate. Welding is the first product. What defines the company, in his account, is its technology stack: using data and machine learning to get systems to learn tasks. He called welding "the heartbeat of the company," the thing Path wants to be the best in the world at. But the ambition is to handle the tasks before and after welding as well, giving manufacturers the labor capacity they need to scale.

The main task Path is working on beyond welding is dexterous assembly: putting parts together, using tools, and fitting physical components. Lonsberry said large OEMs and small and mid-sized manufacturers alike have a big need for this. It also sits directly upstream of welding, because two or more parts have to be assembled before they can be welded. Path is expanding into assembly using the same intelligence stack it built for welding.

Chris asked how Path chose assembly as the next application out of many possibilities. Lonsberry tied the choice to the company's business model and its focus on customers. Path sells robots as a service, so it only gets paid when customers use the systems every day. He contrasted this with purely capex robotics sales. In that model the vendor delivers a system once for one use case, and it's up to the customer to adapt it to the next one. Path, by contrast, has to keep providing value even when customers switch parts. He said that happens constantly in metal manufacturing through change orders, SKU changes, and shifts in demand. So the company asked what would give its existing customers the most additional value. Assembly was the step before welding that most relieved their labor pressure and could feed the welding cells.

The technical approach: one network, world models, and the long tail

Gard described Path as a modern AI robotics company. It doesn't think of itself as doing welding or assembly but as helping manufacturers automate what they need. To do that, tasks have to be broken into abstractions that apply across applications. First there is infrastructure that can handle various tasks and move robots around, whether the job is painting, grinding, or welding. Then there is perception: robots need to see what they are looking at and where they are going. Gard said this is handled by a single network that learns across application types. Finally the robot performs the task itself, which might be welding or dexterous assembly.

The team's current focus, Gard said, is building a world model. He explained why. Data is the bottleneck in robotics, and in his view the reason robotics hasn't had a "GPT moment" is that there is no internet-scale dataset for physical tasks the way there was for text. That matters in manufacturing because of edge cases. Gard described a small number of common problems and a large number of rare ones. He estimated, with uncertainty, that the rare ones add up to maybe 20–30% of situations. Manufacturing also sets a high bar for accuracy, quality, first-pass yield, and cycle time. To handle this long tail, models need to encounter edge cases and learn from the mistakes of other robots.

Gard laid out two ways to get that data. One is simulation. In his account, simulators take a lot of money and time to build, and even then the data isn't accurate enough because of the "sim-to-real gap" between a digital twin and what actually happens on the shop floor. So simulation alone won't be enough. The alternative, which Gard said Path believes is the answer, is a world model. It is trained on real data, learns to predict the next step, and can be controlled. He described it as a neural network acting as a physics-based engine that learns the laws of physics and can be used to perform different tasks. Path sees this as its future "data engine." When Chris summarized this as needing both simulators and next-step models, Gard corrected him: these are two alternative routes, simulation versus training networks on real data.

What's changed recently: from task-specific models to generalization

Chris mentioned that a Path colleague had said the company may be moving faster than Moore's law, and asked what had improved most in the last quarter or six months. Gard described a change in mindset. A year or two earlier, the standard approach was to collect data and train a model for one specific task, and to repeat that for every new task, customer, or part. After GPT, the thinking shifted to training on many tasks at once so the model generalizes. Path has made the same shift. Gard said that on the perception side, the model no longer depends on which customer, state, country, part, material, joint type, temperature, or lighting it faces; it can handle all of them. Similarly, for assembly, it doesn't matter whether the parts are two flat pieces or cylinders; the system can pick them and put them together. He attributed this to moving toward generalization with one large network.

Lonsberry added that the biggest change is the volume of data as more cells go into the field. Every deployed system collects data every day, which he said has an exponential effect. The data spans time zones, lighting conditions, countries, and ambient temperatures from 0°C to around 40°C across North America. Path combines all of it to train one large foundational network. He said the company is growing about 3x per year, and that this figure covers data as well as revenue. He called data "the gold mine that we care about the most right now." Chris highlighted that framing as a concrete version of the common claim that data is a company's most valuable asset.

What excites the team: embodied AI and real deployments

Asked what excites them most, Gard first named the team. He said he gets emotional and gets goosebumps seeing everyone aligned on a mission. Second was the work itself. He said large models for text, image diffusion, and video generation are great, but what excites him is embodied AI: putting machine intelligence into a real, physical robot. He said Path is at the forefront of that.

Lonsberry's answer was deployment in the real world. He said the robotics hype cycle is "through the roof" and that much of what circulates online is hype rather than reality. His rule of thumb is that any demo that hasn't gone to a customer site is three to ten years from being real. He said Path lived through this three to four years ago. The company had an incredible demo, but when it delivered to a customer, "everything breaks." He said anyone who has delivered a real robot knows it's the most painful process. Path went through what he called the pit of despair and came out the other side. It is now scaling real systems aggressively. Lonsberry said he thinks there are maybe two or three companies in the world, adding that he isn't sure, that actually deploy neural networks trained with reinforcement learning to customers who use them every day.

Standing out when everyone claims to be an AI company

Chris noted that every company now calls itself an AI company and asked why an outsider, whether a customer or a prospective employee, should care. For hiring, Lonsberry said people should come meet the team, which he described as electric and motivating and said he learns from daily. For customers, his answer was also "come see it." Send the parts and watch the technology run. He said many demos lead to a signed contract within 30 days.

He credited Heather, Path's chief revenue officer, who had left early to catch a flight. According to Lonsberry, the current sales cycle is about 80 days from first meeting to close, with deal sizes of roughly $5–10 million. Asked what other manufacturers could learn about shortening deal cycles, he joked that the answer is to hire an amazing CRO. He then described her approach. She aligns Path with a prospect's three major strategic initiatives for the next three to five years and shows where Path fits. She also disqualifies prospects faster than anyone he knows, so the team focuses only on companies with a real need that Path can deliver value to. He gave an example. For one prospective customer, she researched their biggest customer, that customer's growth rate, and the prospect's most pressing need. She then walked the prospect through their own strategic initiatives and built a case for how Path could accelerate them. In Lonsberry's words, "it's not about the tech, it's about the value," measured in revenue, growth, and profitability. He admitted the sales process was about five times worse when he ran sales himself.

Chris, a former salesperson, pulled out three lessons: tie the pitch to the customer's strategic initiatives, disqualify quickly instead of chasing poor fits, and have the self-awareness to recognize when someone else does a job better than you.

What other regions can learn: the ecosystem around startups

Chris asked Root what other regions could learn from Columbus. Root said he wasn't sure how actionable his answer was for individuals. His main point was that building an innovation economy takes more than startups. It needs a supporting culture. That includes law firms that know a term sheet doesn't need to be 100 pages or take six months, and landlords who will offer one- or two-year leases because a startup won't sign a five- or ten-year lease. More broadly, people have to understand startup risk. Root said that today in Columbus, if you told your spouse you were joining a venture-backed startup, the reaction would be enthusiasm and a question about which one. Ten or fifteen years ago, he said, the reaction would have been worry about risking your career with kids heading to college. He described this as a cultural shift that takes time and open-mindedness. He also saw it happening across America, not just in Columbus, and said he didn't think Columbus was ten years ahead of, say, Dayton.

He added a distinction Drive uses: scary versus dangerous. Joining Sears in 1995 wasn't scary, but it was dangerous for your career because Sears is gone. Joining Amazon in 2010 was scary, a fast-moving company that would intimidate someone coming from a company like Nationwide, but it wasn't dangerous, because of the experience and skills you gained. Root put Path Robotics in the same category: a startup may feel scary, but it gives people the skills for where the economy is heading.

Are the coasts changing their view of the Midwest?

For the last main question, Chris asked whether attitudes toward the Midwest are changing on the coasts. Root went first and said, "absolutely not." Nobody in San Francisco is asking how Illinois is doing, and he said that's fine. The coasts play their own game, and the Midwest doesn't need to worry about how it's perceived. He said people should be bullish on Columbus and Ohio because a world-class technology company can be built anywhere. Asked why the Midwest needn't worry, he pointed to a growth mindset and the amount of innovation left to do. Social networking has been figured out, he said, but industries such as hospitals, manufacturing, and transportation still need modernizing, and that is where the opportunity lies.

Lonsberry agreed. He said coastal investors still routinely ask Path when it will move to Silicon Valley or the East Coast, and the answer is always that the talent is here. He cited Ohio's population of roughly 22 million, by his estimate, and research institutions such as Case Western, where he and his brother studied, Ohio State, and Carnegie Mellon. He recalled a statistic, which he said he couldn't remember precisely, that more software engineers graduate in the Midwest than on the coasts. He contrasted the cultures. He described coastal engineers as moving from company to company, pointing to LinkedIn profiles listing ex-Twitter, ex-Meta, and ex-Google. By contrast, he said the Columbus talent pool is bought in, teachable, willing to grind, and wants to win, and that "there is no IQ test" showing Ohio below the coasts.

He also made a strategic argument. Path is one of very few AI robotics companies in the Midwest, while many are forming on the coasts, yet their customers will mostly be in the Midwest. Path chose to stay close to where its equipment is deployed so it can respond quickly, work in the weeds with customers, and learn from them. He said he wouldn't build the company anywhere else.

Audience Q&A: other rising startups and what's really advanced in AI

An audience member who has been a supplier to Path asked which other promising companies or industries in Columbus and Ohio deserve attention. Root suggested Lonsberry might know the manufacturing startup scene better. He said Drive constantly looks at companies automating work, whether in manufacturing or back-office healthcare tasks, and that many come out of Columbus. His explanation was that a critical mass of people working on related problems starts to feed off each other, as happened in Silicon Valley. He noted someone in the front row wearing a Ready Robotics sweatshirt, a past Drive investment that no longer exists, but said he couldn't name a current Columbus manufacturing investment on the spot. Lonsberry said he didn't know of other AI robotics companies in Columbus specifically, only one in Pittsburgh a few hours away. Chris joked that Pittsburgh may not like being called Midwestern.

Another attendee asked Gard what real advance, beyond the buzzwords, he had seen in AI over the past 12 to 24 months that Path is applying. Gard repeated the main theme: larger datasets and larger models that generalize across more tasks instead of being specialized. He said Path doesn't plan to stop at welding and assembly. It will keep expanding to the processes before and after, and it doesn't want to reinvent the wheel every time it onboards a new product, task, or customer. The goal is to make that onboarding frictionless.

Automation and jobs: displacement, new roles, and the labor gap

Leslie, from the event's sponsor, asked how humans and robots will keep interacting as AI extends what robots can do, given the common claim that nobody loses their job and workers simply upskill. Gard didn't fully accept that framing. He said it's fair to admit that some jobs will be eliminated by any new technology. He gave the example of the person who fed and cared for horses before cars. He also noted that barbers 200 years ago also pulled teeth, which seems absurd now. He paraphrased an idea he attributed to Steve Jobs: when a new technology arrives, people first apply old problems to it, and only over time learn how to really use it. His conclusion was that there will be some displacement, but new jobs will be created, and that humans are poor at thinking about exponential change but will adapt and create new possibilities.

Chris offered his own view. He said the "GPT moment" shifted the automation story from lower-wage manual jobs to highly paid knowledge work. Automating a $20–30-an-hour job saves that much per worker, while automating a lawyer billing $300–400 an hour is a completely different calculation. He pointed to uploading a contract and asking an AI how it's unfair as the kind of task that changed the conversation, and suggested we're only beginning to see who will be automated. Gard agreed that, from a manufacturing perspective, physical jobs are much harder to automate than legal or medical work. He suggested regulation is one of the main things protecting the medical field. Chris summed it up: the more your job lives on a screen rather than in the physical world, the more exposed you are.

Lonsberry, leaving for a 7 p.m. call, took a different angle. He said the gap between jobs needed and workers available is still very large and growing. In Path's experience, no one at any company it works with has been laid off or replaced by a robot; the robots have always been an addition. He expects that to hold for a long time. He also said there will be plenty of opportunity in learning to work with these systems to become more efficient as the economy and population grow. He said he doesn't see it as "tomorrow it's robots, goodbye humans," but as filling a gap so manufacturers can accelerate. Chris added that he had heard there are around 2 million manufacturing jobs open or about to open as workers retire, and said he sees automation as repurposing jobs, as has happened for centuries.

Closing: building the next workforce

The evening ended with two short segments on the workforce pipeline. Josh from A3, the Association for Advancing Automation, a former K–12 teacher who joined the trade association the previous November, described its education push around the Automate show in Detroit. He said the show will include an education pavilion and an educators day, and that nearly 400 students were expected, with the number still growing. A3 works with programs such as VEX and FIRST to get young people interested in automation and manufacturing, which he called the next workforce.

Finally, Adrisu, founder of a Columbus nonprofit that the tour supported with a portion of its proceeds, described its mission: getting underserved and underrepresented youth interested in STEM careers through hands-on, project-based workshops in schools, libraries, and community centers. Adrisu studied mechanical engineering at Cleveland State and then built and tested rocket engines in the California desert. Speaking with kids at STEM outreach events there showed Adrisu how eager they were to learn. After returning to Ohio to raise a child, Adrisu started the organization to show that interesting career paths exist and that STEM is for anyone who is curious, not only students in wealthy school districts.