About HobbsMate
A small team chasing a big idea
The Team
Lance
Founder and Engineer
Pilot and software engineer. Started HobbsMate to scratch his own itch and give back to the General Aviation community. Handles everything from engineering to UX to customer support — alongside his wife Christen who helps with marketing and support.
Jacob
Engineering
Aviation enthusiast and engineer. When he isn't spending time with family or perfecting the art of pizza making, he's getting nerdy on the details that make HobbsMate tick. You'll find Jacob obsessing over latency and the finer engineering details that make the platform stand out.
Brandon
Sales
Family man and pilot. Co-owner of a plane with Lance, Brandon has been there since the beginning of HobbsMate. He's excited to help share the vision with the General Aviation community.
Our Story
The Spark
It started with a spreadsheet. The existing aircraft management software had price gates that didn't match the value. Lance — a pilot and veteran — realized he had the skills to build something better for himself and his co-owner Brandon. A nice change from building software for big tech and DoD. That was the spark.
The Ah-Ha Moment
As we dug in, we got nerdy on what GA pilots actually do every day: snap a photo of the hobbs or tach, record the times, note where we started and ended. The question hit: what if we just leaned into the pictures? What could we glean from that?
A lot, it turns out. That's when HobbsMate went from "just another tracking app" to something different. HobbsMate Intelligence™ was born.
Innovation Didn't Stop There
Another owner asked for an oil sample export feature. We were ready to build a button — then the second epiphany hit: what if you could just *ask* HobbsMate Intelligence™? We tested it. It worked. Now we lean hard into that approach — letting features find themselves from feedback, and not doing what's already been done.
Built Because We Use It
We're a small team — two pilots and an engineer who geeks out on aviation. We use HobbsMate ourselves. If something sucks, we note it and fix it. Every feature exists because one of us needed it.
We ship fast, listen to feedback, and keep improving. This is just the beginning — and we invite you to join us on this adventure.
How We Think
We don't build features just because others have them. We study the problem, find the friction, and ask: what if we approached this differently? That's how photo-based logging was born — and we're just getting started.
Ready to try photo-based flight logging?
Snap a photo. Get a log entry. It's that simple.
Get Started