Two months ago, I launched a regex tester.
Why would I ever build a product around helping people with their regular expressions? The market is tiny. There are dozens of free alternatives, and only a small percentage of people I've asked said they would pay for my product.
There are a few big advantages to be had competing in a smaller market.
In a smaller market, everything happens on a smaller scale. Successes and failures are smaller in magnitude and take less time to pan out. Less effort is required to build a competitive product, since the existing ones are not as well-developed. The result is a tighter feedback loop for your learning. Debuggex is my first product, so I want to optimize for learning and profit rather than just profit.
To date, I've spent less than a month of full-time effort on Debuggex, and it's already a very competitive product. If it turns out to not make any money, I've only lost a month of effort.
Twice, my site went down for a few minutes. It was not an enormous problem - there were less than 10 users on at the time. However, I've learned valuable lessons in automating recovery.
At launch, there was a bug in my subscription code. It was a blunder, but I didn't sweat it. I only lost 30 emails, and I've learned to prioritize what gets tested earlier.
In a smaller market, you can demonstrate expertise. When you opt for a smaller market, you have a wider choice for a domain that you're skilled in. Coupled with the small scale, this lets you aim at being the absolute best in the market. You have a chance to wow your users and make them loyal to you, even as you move to new ventures.
Debuggex already (while still in beta) blows all of its online competitors out of the water. It was designed to answer the question "Why isn't my regex doing what I intend it to?" I've found that question to be by far the most frustrating and time-consuming issue with developers I've talked to, and competing products just can't give you the answer.
The way Debuggex answers this question is by allowing you to walk through an automaton step-by-step. Because it's visual, it taps into your innate spatial sense. It also offers hints as to where something may be wrong. You can inspect any portion of your string or regex and see exactly why and how that portion is (or is not) matching.
Fortunately, people have noticed. I've gotten hundreds of tweets, many of them filled with emotion (yes, emotion about regexes!). Several people have also emailed me about partnerships, and a few even wrote articles about it!
In a smaller market, you can iterate faster on non-programming skills. Since the product is small enough that I'm building it alone, I don't just program, I do everything. There is no option to pass work off to somebody else.
I wrote this article. I built a tutorial video when I found out users didn't know how to use one of the key features. I respond to every tweet, send every email, and configure everything on the server.
Consequently, my thoughts have become more coherent. I can speak more clearly. I know how to avoid audible breathing and swallowing on a microphone (much harder than it seems). I've even made new friends and reconnected with old ones.
I am learning to sell, apologize, stroke egos, manage expectations, talk to the media, and build a company.
But it's not just about the intangibles. To date, Debuggex has 120,000 pageviews. A returning user spends an average of 45 minutes(!) every time they visit, and there have been more than 800 people that have visited at least 8 times. Those 800 people have each spent a whopping 6 hours on the site in just two months! If you are one of those 800 people, it's you that I built Debuggex for. Thanks for giving me the opportunity to create something awesome!
What are your thoughts? Should your first product be aimed at a small market?
Discuss on Hacker News.