In this episode of The Sunny Ray Show, host Sunny Ray talks with Nathan, co-founder of Beeline Routes, a routing and scheduling platform built for field service businesses. Nathan explains how he and co-founder Michelle started by solving the classic traveling salesman problem for a real estate agent, then expanded after partnering with House Call Pro, a field service management platform that made Beeline its preferred routing integration. Nathan describes how mobile workforce companies, from pest control to power washing to home services, struggle to manually route dozens of jobs across multiple vehicles each day. He details the technical backend built in Golang, the challenges of customizing routes around real world business rules, and why growth has been steady rather than explosive due to limited discovery channels. The conversation covers customer onboarding, common failure points like invalid addresses, pricing strategy starting at 65 dollars a month, and why logistics remains one of the most underserved yet high potential sectors for practical AI and automation adoption.
A founder explains how solving the traveling salesman problem for field service crews became a real business.
What are you building and why does it matter?
We're solving the traveling salesman problem, figuring out the best route between stops to minimize cost and drive time. It's a classic math and business problem that's been around for hundreds of years, and new technology stacks let us solve it in new ways. Michelle and I started with a simple proof of concept for a real estate agent entering multiple addresses, then expanded from there.
Can you take me back to the moment you decided to build this?
I had a full time job and was a bit bored. I found Michelle through AngelList and we tried a few business ideas together. We landed on the traveling salesman problem for real estate, then Michelle found House Call Pro, who wanted us as their preferred routing partner. That demand from an existing platform of early adopters really solidified what we needed to build.
What's the growth journey right now, team size, customer count?
Growth is steady, more linear than exponential. Everyone with a mobile workforce says they need routing help, but the real question is how much. We specialize in companies doing eight to ten jobs a day, and over half our paying customers do twenty plus jobs per vehicle daily, including pesticide spray and dog poop pickup companies I didn't know existed before this.
Field service software is crowded and unglamorous. Why go there?
House Call gave us access to all their users, and I built everything API first with a Golang backend, so integrating with platforms like Pipedrive or ServicePro is plug and play. The CRM and field service market is hypercompetitive, basically a race for features, so we turbocharge platforms like House Call as their routing engine instead of competing directly.
How do you build one product for customers who all mean different things by routing?
The backend is actually the same core engine across products. We take jobs and break them into routes using a modified K means approach, then optimize for minimized drive time. Whether it's a daily route, a best fit schedule, or stacking four hundred jobs across a month, it all runs on that same underlying routing kernel.
What is the one case your optimizer cannot solve?
We built it as a no errors system, we always try to return something. If jobs are impossibly long we'll give back multiple days of driving. Invalid addresses get skipped, and airports are notoriously finicky with mapping APIs. Even islands work, we add a ferry penalty and just estimate it as a bad, time consuming route rather than failing outright.
How much of the win is time saved versus jobs added per day?
Our real value is saving the office admin's time, not necessarily drive time itself. An experienced admin's manual route is often just as good as ours, we just do it in twenty seconds instead of an hour. The bigger value add is enabling a third truck, since many customers only max out two vehicles because manual routing for more becomes impossible.
What does a customer's first week look like, and where do they churn?
We offer a two week free trial after connecting your CRM. Some users figure it out on their own, but many get overwhelmed or afraid to touch anything since they worry it'll update House Call. We only push updates after explicit confirmation. A good portion of users need one or two live demos with me, Jen, or Michelle before they start paying.
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-interview