Starting a SaaS business is challenging, but I did it! In this video, I break down my journey from idea to launch. We are now generating revenue with customers and improving our back end infrastructure to scale. If you’re thinking of launching your own SaaS startup, this video is for you.
💬 What’s your biggest challenge in starting a SaaS business? Let me know in the comments below!
📖 Chapters 0:00 - Starting my freight logistics company 0:42 - Talking to my co-founder about my app idea 1:06 - Noticing the gap in the market 1:39 - Describing the problem (drivers, trucks, routes) 2:38 - How to write good software (ft. Moses) 3:01 - Building the Minimal Viable Product 4:09 - Building the Team (ft. Jeremy) 5:35 - Measuring risk vs success
Here's the situation. I've worked in corporate America all of my life at companies like Apple
and Amazon, but I left all of that to start a freight company. At first, it was all good.
I felt like a free man escaping the nine-to-five and my business was growing fast. We were hiring
drivers left and right, adding more trucks to our fleet weekly, but before I knew it,
I was working 60 hours a week to run this company. One thing I missed from my corporate nine-to-five
was having access to the best tools and software that money can buy.
This is a story of how Laminar CoPilot started a year ago during a random car ride to Santa Barbara.
The first time we talked about CoPilot was actually during our drive up to Santa Barbara.
So we had a cycling event and on the way up, we were just talking about business ideas and one
of the business ideas he had was to have some sort of app for the company that he runs.
We both thought there was a lot of potential and so yeah, that's kind of the first time we
talked about Laminar CoPilot. That entire morning, I had actually spent scheduling my team for my
freight company. Even though I was coming from all this experience in operations, I was still
having to do a lot of this manually. A lot of Excel, a lot of spreadsheets, and a lot of just
manual maneuvers until you can make it work. And I knew that there had to be some sort of tool
that can do this automatically for me. But when I googled it, I found none. And that was a complete
shocker to me and that's when I realized, hey there's something here and potentially if we
can code this, it could be huge. Imagine this. You have x number of drivers and let's just say
you have y number of trucks. And every week, you want to fulfill z number routes optimally
and efficiently. In theory, you can just go down this list and assign each driver to a truck.
But what happens when you add different variables to the story? Suddenly, a driver only wants to
work Monday, Tuesday, and Wednesday. And let's just say this truck is actually out on a trip
and only becomes available Monday through Thursday now. What happens if you have z number of routes
but not enough trucks? On that drive up to Santa Barbara, I looked at Moses and I asked him,
is it possible to create an algorithm that can do all of this for us automatically? The first step,
I think, to writing great software is just having the context necessary to write the software,
understanding the problem, right? The second thing is just starting to write the software.
You just figure things out as you go and there's always going to be roadblocks that come up,
but step by step, that moves the process along and allows you to
iterate and build something that ends up being used, right?
So I know that on Wednesday, you have 521.30, right? Yes. Yeah, there's not really a good way
to infer. We were testing Dynamic Scheduler and this had been a weekly thing that we were doing.
So every week we would get an export of the routes that needed to be fulfilled
and we would try to run my code, right? Insufficient drivers.
We got to 55. Wow. This was the first time that it actually worked and it was a huge deal for us.
There were 60 routes in total and given different driver constraints and truck constraints,
our algorithm was able to automatically schedule 55 routes. A person manually scheduling 55 routes
would take a couple hours. In like two or three seconds, we did 55. We realized that
maybe our idea could actually be something. Once we knew that the logic and algorithm
actually worked, it was time to actually build the app. And for that, we needed a team.
First flow is with Dynamic Scheduler. Start to the dashboard module. Kevin shot me a text
saying like, I'm currently working on this app and I really need a designer. I was like,
oh shoot, another opportunity? Like, I'm down. Let's do it. He sent me a screenshot of here's
what we got so far. And I was expecting at least sort of like a browser window with some buttons,
but it was literally just like an input button and upload form thing. And I was just like,
oh, okay. There's a lot we can work with here, but honestly that meant I had a lot of
impact to the team to help out. I would describe design as the glue that holds sort of the form
and the function together. Form being sort of the ideations that Kevin has and the function,
which is the developmental code that Moses has. Once you just have a design in front of you,
it really just brings this personable feel to the product rather than everything just in your head.
You have this, it'll take you to that. So that way right now.
I'm just so blessed to be a part of a team where everyone is so talented. I would never have
imagined Copilot to make so much progress now. And I'm so excited to see where it's going to be
the next year and even future years to come. It's always fun when you're like kind of trying
to do things alone or you're trying to build something. But I think the moment when you
actually add people into it and they have now invested hundreds of hours into it is when the
risk transitions from the risk of the business failing to the risk of you actually letting your
team down. Right now, the most important thing and success to me means Laminar Copilot succeeds,
not just for myself and for my freight company now, but for the team members that have invested
hundreds of hours into the product. The team is extremely proud of where Copilot is today.
We've proven out that the algorithm works and the logic works and that customers love the product.
Going forward, we're now focused on scaling the backend infrastructure.
We're really excited to get Copilot into the hands of customers all across the nation.