Why I'm Betting My Career on Fleet Software
Fifteen years of running fleets, and one problem that never got solved — a letter on why FleetStream exists.
After nearly fifteen years in fleet management, I left the safety of a full-time role to build FleetStream. I was excited, and honestly a little nervous, the first time I said that out loud. I still am.
Those fifteen years are where the idea came from. Every fleet tool on the market seems to start the vehicle's story at the first repair order. But by then, the most expensive decisions have already been made: what you spec'd, who you assigned it to, what you paid. Nobody was tracking the whole life of the asset in one place — so I spent a career stitching it together by hand.
FleetStream is the system I wish I'd had: one record from the purchase requisition to the day the truck gets sold. Spec, assign, maintain, monitor, optimize, plan, dispose. All of it, connected.
We're building it in Minneapolis, with a team I'd trust with my own fleet. We're already talking with last-mile delivery operators, municipalities, and contractors running a few hundred units who are tired of managing million-dollar assets in a dozen tabs.
If that sounds like your fleet, I'd love to talk.
And to the leaders, colleagues, customers, and friends who sparked this passion and challenged my thinking: FleetStream exists because of what I learned from you.
Who FleetStream Is Not For
I sat through too many vendor demos that should never have been booked. If any of these describe your operation, we'll both be happier if you know now.
Built for fleets of 50–1,000 assets; the sweet spot is 100–500. Compliance obligations, capital assets, operational accountability — that's the fleet this system was built for.
If That Sounds Like Your Fleet, Let's Talk
A walkthrough personalized to your fleet — and if you want to help shape the product, the Founding Fleets beta is open.