If you prefer you can watch a video version of this post.
You're taking a shower and suddenly this fully formed idea pops in your mind. A literal showerhtought. It's a culmination of years of experience, dozens of books, hundreds of videos, and many many hours of random tinkering.
This is it, you think.
This is the app that will finally make it big. This is the one that will take you out of the misery of a 9-5 job and into the glamorous space of financial freedom. Absolutely everyone will want to use this. How could they not? It's brilliant. Isn't it?
Well, it might be. But building it, bringing it to market, and generating enough revenue to sustain yourself - let alone get rich on it - that's still going to be difficult. Very difficult.
As a boostrapper, you have a few limitations:
So here's is the challenge. Your idea is for an app that can be used by millions of people, but you can't reach millions of people within your budget and timeframe.
So where do you start?
Most people start with the so called "getting the word out". They talk to some friends who might be interested. They write a tweet. They post a blog. They publish something on IndieHackers or Hacker News. They put up a landing page and maybe even put some money into an ad on Facebook or Twitter.
This seems like right thing to do. After all, this is what other successful indie hackers have done. It should work for you too, right? Unfortunately, you're falling prey to survivorship bias. The only people you see online are those who succeed in a big enough way to become popular, even iconic. You'll never hear about the ones who tried "to get the word out" but got 3 likes on their tweet. You'll never hear the stories of people who posted on IndieHacker and got 2 replies. You'll never meet the people who built a product, showed it to their friends and gave up because none of them "got" it.
To avoid the unfortunate fate of so many other well meaning hackers, you need to niche down, way down. Instead of building a product for millions, build one for thousands, even hundreds. Instead of building a flexible product that can be anything for anyone, build a specific product that solves a specific problem for a specific kind of person.
For example, instead of a nocode landing page generator that can be used for anything, build one that's specific for, say, meditation teachers in the Goenka tradition.
Instead of a habit tracking app, build an app that tracks pushups for hard core fitness fanatics who are already doing 50 pushups a day and want to push it up to 200.
Instead of another generic messaging app, build one for divorsed parents and maybe help them fight a little less.
Now, I know, niching down is hard.
It means choosing a tiny subset of the entire market you could theoretically go after. It means letting all go of the other potential customers. It feels risky. It feels scary. It's really hard to make that decision. But it's also what it may take to succeed. I assume you're not in this game to just play it. You're here to make a living. And at the risk of sounding a bit cliche, your personal and financial freedom is on the line here.
Now, not all niches are created equal. A good niche for a bootstrapped business should meet at least three criteria:
Spend a few weeks fully immersed in a niche. Talk to people, understand their problems, figure out how your app can be morphed to serve them. Pretend this is the only group of people you'll ever serve with your app. Commit. Hell, even buy a different domain. You buy one every other week anyway, right?
Your commitment to a specific narrow niche will make you intimately familiar with the people in it, their problems and the words they use to describe those problems. They'll be eager to talk to you because you understand them. And they'll be eager to buy from you - because you actually care.
The first niche you go after might not work out. In fact, it's quite likely that it won't work out. Like the first pancake you make in a batch that doesn't come out quite right because the pan isn't hot enough, your first niche will probably be too broadly defined and you won't find that kind of eager desire for your product that you're looking for.
But keep going and and keep refining. Your niche is out there.
And if you aren't sure where to start or how to do this, look me up on Twitter - my DMs are always open.
One of my strategies for growth shares a part of the same mentality: attract a few thousand users at a time with one feature at a time.
On an additional note, the same code or project could be replicated with a little bit of variation in UI for other things. (To expand one's luck.)
Like, the push-up tracker could be redesigned to be a pull-up tracker, hydration tracker, coffee tracker, etc.
Maybe pull-up fanatics have more money than push-up fanatics? Seriously.
I had to build a pull-up bar in the backyard, because where do you ever find one that's higher up than the door frame? But all one needs for push-ups is a sturdy ground.
Now you're niching! Separating pull up people from push up people is 🔥🔥
And you're right, the same core can be used for many different experiments and products, and it works well as long as you aren't trying to build one app that does all of it at once (which is what devs tend to build).
Yeah, that's definitely the tendency.
Soon, I'll release a featureful app and a watered-down version at the same time, so that they could compete.
I'm planning on posting the conditions and the basic install/retention totals on IH to share the outcome over some period. And observers can decide, on their own, whether it's been done well enough for comparison. That could be interesting.
In fact, targeting a specific niche is often how small startups beat larger rivals or create new markets. Case in point: Airbnb – the company targeted a specific niche that was once part of Craigslist's business. This approach worked for Amazon too, in its early days as a bookstore, before it expanded its inventory to include everything under the sun. Can you remember that?)
I do! And even Facebook started with helping horny college students find hookups and only then expanding to take over our entire lives.
I like this Eli, I sometimes feel embarrassed because my (future) target market is so niche (Clubs/schools running a gymnastics competition). The one think that makes me a little nervous about my niche is volumes - will there be enough volume for me to be able to make enough money for me to make it my full time job (without being unrealistic and expecting 100% market share!) It's nice to see a post like this - thanks!
Many successful businesses began from very small niches that few people believed in. E.g. Etsy started out as a way for people to sell crafts and other handmade items. eBay began in 1995 as an online auction site where collectors could buy and sell Pez dispensers. Can you imagine the pitch they must have given investors? They must have had a lot of hard passes.
Getting an investment isn't real validation 🤣. Having paying customers (and a proven way to get more customers) is.
Size of the niche is rarely a problem if your target audience has the problem you're solving, they know that they have the problem and have the ability to pay for a solution. Schools can be difficult customers. Have you talked to any yet?
I have talked to some clubs (I say "schools" as I'm used to broadening the term for countries outside Australia!) And ended up feeling overwhelming pressure to hurry up and build it! They are small businesses, but the positive thing is, they all charge gymnasts (the athletes) to enter the competition, so there is income coming in to pay for a product like mine. When I talk about volume, these businesses may host one competition a year, and some up to 20 - but most likely 2-3. So the frequency of the target market needing the product is low.
Ah that's very different from what I thought when I read the word "schools" 🤣
Sounds like a good opportunity to charge them per event instead of per month and line up a few clubs with tournaments in 1, 2, 3 months. Then get them to pay in advance and set out to build it as a rolling custom project that slowly turns into SaaS.
You can charge a % of the fee they are getting and condition it on the whole thing going without a hitch if they object to paying for something before it's built. And tell them they're getting a custom solution built to spec for 1/10th the cost because you intend to sell it to more clubs!
Exactly what I am thinking in terms of roll out & pricing. A combo of singular event purchases and SaaS once it gets going, I also eventually want to to spectator tickets - but we'll get to that later!
I don't think I am a confident enough developer to take money up front before it's ready to be honest. I learnt to code last year and only front end.... so I don't have a back end yet! I'm not very good yet at predicting how long certain parts of it will take me to build, (I am doing it on the side and have a full time job) Also - It's not just a scoring system as it will take entries as well, so a user (the host) would need the software well before the event date.
I usually push people to trust their coding abilities and focus on selling their product first. But if your skills a remote around the business side and you trust yourself to be able to sell - but are pretty new to coding - by all means, get the coding working.
And check out Do10X - it's a nocode backend platform that seems to work around a lot of the pain of building a backend yourself.
You can reach out to Mohsen on Twitter (https://twitter.com/MohsenKamranii), he's the indie founder and a super cool guy.
Thanks finereli - I haven't heard of Do10X before - I'll check it out!