Building a SaaS from Scratch: Idea to First Customers
Kevin Park left corporate jobs at Apple and Amazon to start a freight company, then discovered a gap in scheduling software. He partnered with a developer (Moses) and designer to build Laminar Co-Pilot, an algorithm-driven scheduling app that automates route assignment for logistics companies. Their first real test scheduled 55 routes in 2-3 seconds versus hours of manual work, proving the concept and attracting a team.
The Problem: Manual Scheduling Chaos
Corporate escape led to operational pain
Kevin left Apple and Amazon to run a freight company, initially enjoying freedom but quickly hitting 60-hour work weeks. Despite his operations background, he spent entire mornings manually scheduling drivers and trucks using Excel and spreadsheets, with no existing software solution available.
The scheduling complexity multiplies fast
Assigning drivers to trucks and routes seems simple until constraints pile up: drivers only work certain days, trucks have availability windows, and route counts don't match vehicle capacity. This combinatorial explosion is why manual scheduling becomes impossible to optimize.
The Idea: A Chance Conversation
Inspiration struck during a car ride
On a drive to Santa Barbara for a cycling event, Kevin and Moses (a developer) discussed business ideas. Kevin mentioned needing an app to automate his company's scheduling, and both recognized the potential immediately—this casual conversation became the seed for Laminar Co-Pilot.
Building the Algorithm
Two-step approach to software development
Kevin identified the core steps: first, deeply understand the problem and context; second, start coding and iterate through roadblocks as they arise. This pragmatic method allowed the team to move forward despite uncertainty.
First successful algorithm test
Testing their dynamic scheduler on real freight routes, the algorithm successfully scheduled 55 out of 60 routes automatically in 2-3 seconds. Manual scheduling of the same 55 routes would take a couple of hours, proving the concept worked and validating the business idea.
Building the Team
From solo idea to three-person team
After proving the algorithm worked, Kevin needed a designer. He texted a designer friend showing just a basic input form and upload interface. The designer saw potential and joined, recognizing there was significant impact to be made on the product.
Design as the bridge between vision and code
The designer described their role as glue holding form (Kevin's ideation) and function (Moses's code) together. Design transforms abstract concepts into a tangible, personal product experience that brings the team's vision to life.
Team investment shifts the risk equation
Once team members invested hundreds of hours, Kevin's perspective changed: the risk shifted from the business failing to letting the team down. This psychological shift made success feel more urgent and personal.
Proof of Concept and Next Steps
Algorithm and customer validation achieved
The team proved the algorithm logic works and that customers love the product. They've moved past the concept phase and are now focused on scaling backend infrastructure to handle growth across the nation.
Notable quotes
I knew there had to be some sort of tool that can do this automatically for me but when I Googled it I found none. — Kevin Park
The moment you add people and they've invested hundreds of hours, risk shifts from business failing to letting your team down. — Kevin Park
Design is the glue that holds the form and the function together. — Designer