Interview with a Successful Startup Founder

MotoBox: The Story of 2 Technical Co-Founders

Joe Stech
Joe Stech
March 17, 2018
Category of startup
Transportation
Country of startup
United States
Revenue of startups
Interview with a Failed Startup Founder

MotoBox: The Story of 2 Technical Co-Founders

Joe Stech
Joe Stech
March 17, 2018
Category of startup
Transportation
Country of startup
United States
Cause of failure of the startup
Bad Marketing

Simple, WiFi-enabled, OBD-II vehicle data logger and cloud services creating a platform for custom software development, which couldn’t reach customers.

Ad

No Code MBA Logo

No Code MBA teaches you how to build powerful apps, websites, and automations using the most popular ‘no-code’ tools. Learn how to build real-world projects like Product Hunt, Tinder and Zillow. Get 50% off with code FAILORY.

Hello Joe! What's your background, and what are you currently working on?

Hi! I have a fairly eclectic background – I started out in physics,  eventually getting a degree in biochemistry. While working in the lab I started creating data analysis programs for other researchers and got hooked on programming. I ended up becoming a firmware engineer and getting a graduate certificate in software engineering while working. After five years of that, I transitioned to professional data science, which is my current day job.

My current side project is Compelling Science Fiction, a digital science fiction magazine. I work with several volunteer editors and advisers to print high-quality science fiction stories and pay authors professional rates. The magazine is now considered a SFWA qualifying market (one of only 36 worldwide). The project is quite a bit different from my last startup, which was focused on automotive telematics.

What was MotoBox about?

My friend and I created MotoBox because we wanted to help developers create an ecosystem of applications built on vehicle data. The best description of the project can be found on our old Kickstarter project page.

The project involved three components:

  • An OBD-II reader with a wifi chip,
  • A set of servers to collect vehicle data, and
  • APIs that served the data to developers (and to our internal app).

The idea was that we'd allow developers to build applications that use vehicle data (things like speed, fuel use, RPM, sensor data, braking data, etc.) and also allows consumers to view their driving data through the app. At the time (2013) the idea seemed novel, but over the next few years, several other similar products were released.

Our Kickstarter ended up failing, but we made some interesting connections. There was a guy in Denmark who really wanted our product to put in his fleet of rental cars. Unfortunately, since we didn't get the funding we needed, we scrapped the project, and it wasn't until years later that I really internalized how bad I was at finding initial customers.

How did you grow MotoBox?

This is the part we were really terrible at, and I learned the most from. Our entire strategy revolved around posting to automotive forums and trying to get articles written about the product, which didn't really work out.

Ad

No Code MBA Logo

No Code MBA teaches you how to build powerful apps, websites, and automations using the most popular ‘no-code’ tools. Learn how to build real-world projects like Product Hunt, Tinder and Zillow. Get 50% off with code FAILORY.

Which was the problem with MotoBox? How did you realize?

The problem was reaching customers. When we didn't reach our Kickstarter goal, but all the backers that had heard of us were super excited, we realized that we hadn't done enough outreach.

 

What were the mistakes you made?

We really needed to refine our message and get better at succinctly communicating. The project was a fairly complicated one, and it was easy to lose people when describing it.

More than anything else, though, we should have consulted with a marketing pro to get the word out better.

                                                                                                                                            

What were your biggest disadvantages?

I and my co-founder were both highly technical (he was a firmware/hardware engineer and I was more focused on software), so we didn't have the business side covered as well as we should have. It was also our first real foray into startups, so we were a little trepidacious. If we had been a little more willing to jump in all the way, and if we were better at outreach, we would have done a lot better. We had a lot going on, and weren't willing to fully commit without funding.

If you had to start over, what would you do differently?

I would have spent way more time validating the market and gathering a potential customer base. To this day I don't know how big the market was for our product (although based on the success of other similar startups, it looks like it would have worked out). This was a huge learning experience for me – you hear a lot about finding product/market fit and doing validation before starting, but this project really helped me internalize that concept.

 

What's your advice for someone who is just starting?

Validate your idea first, and if you're not taking funding, make sure you have large margins. I cannot emphasize this enough. If your margins are too small you'll never be able to bootstrap. Specifically, your cost of customer acquisition has to be smaller than your expected lifetime customer value. This is simple stuff, but you really have to always keep it in mind.

 

Where can we go to learn more?

You can check out Compelling Science Fiction, and I occasionally post to Twitter as @joe_stech. If you're interested in embedded systems development you should really check out my MotoBox co-founder's blog at Electron Vector.

The All-In-One Newsletter for Startup Founders

Every week, I’ll send you Failory’s latest interviews and articles, curated resources for founders, and updates on how I’m growing the site to $10k/mo. Join other +6,000 startup founders!