6
2 Comments

Did I create a cheaper competitor to my product?

New Product: GoPro GPS Quick Fix.

While providing support to the GoPro community as part of the activities I do with the GoPro Telemetry Extractor, I realized many GoPro users arrive at the forums in search of a solution to a common problem: The GoPro video editing software would not display their performance gauges (GPS and forces). My software solved the needs of a fraction of those users by converting the telemetry data into a series of formats that can be read by a myriad of other software, video editing or not.

Still, most users would like to keep using GoPro software, so I decided to redirect my learnings on the matter and create a smaller tool that modifies the video files to artificially "amplify" the GPS signal, so that the official software reads and displays it.

http://goprotelemetryextractor.com/#fix

Just three months ago I was releasing my flagship product after two years of it being a pet project. I wasn't sure this was a viable idea. Now I'm unexpectedly releasing the 4th product in the series, and looking forward to more of them.

And answering to my own initial question, I believe each tool meets a different need. GPS Quick Fix tries to ease the workflow of consumer users, while the Telemetry Extractor is a Swiss army knife that empowers prosumers and pofessionals to do much more with their videos and data. So hopefully I'm expanding the market.

  1. 1

    Yeah, sometimes people are used to software they already use and it might be hard to convince them to use something else.

    You did nice in overcoming that.

    1. 1

      Thanks. The first sale came in just a few hours after the (pretty discreet) launch, which did not happen with the other products

Trending on Indie Hackers
Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 19 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments How I Launched FrontendEase 13 comments