I'm going to preface by saying that I've been very happy tinkering away on my SaaS app Be Inclusive, and have had some wonderful conversations with subscribers that I'd consider to be "power users" who really enjoy it.
Those two reasons are why I keep going at it and have no plans of stopping, but I do sometimes wonder if I took the "find your niche" advice a bit too seriously and ended up targeting an exceptionally small group of people (Freelancers and Small Agencies) with a specialized need (managing accessibility audits).
Have you experienced this before? How'd you rationalize a decision one way or the other?
I actually think being "too niche' to start out plays into your benefit. There's so much competition out there that niching down to hyper-specific targets will benefit you. If there's enough targets in the niche to support the saas, great, if not, you can always branch out horizontally
Thanks for the reply! Yeah that's a good point about initially being a benefit, "who is my target audience?" becomes a very easy question to answer too which I would consider another benefit.
Ohh now that's an interesting prospect, when you drill down to a hyper-specific niche like this what options are available to start branching out? I suppose that's a question that can have many different answers depending on the niche but curious if you have further thoughts here.
Maintaining relationships and networking becomes critical. I've been able to open new customer accounts simply because they were employees of a former customer account.
I have started a few projects that have been too niche. Firstly, it was hard to reach my prospective customers. And when I did, the audience was so small that converting even 5% of them wouldn't create a big enough company.
So if you have a good idea of how to reach your niche audience, that's a good start. Then figuring out how niche it is, so you don't make my mistake.
Thanks for the response! I do have some fairly good avenues to reach prospects but absolutely need to do more to put myself out there and start conversations. Getting going on that now and am crossing fingers.
I'm curious about your "big enough company" comment, how do you quantify that? Do you have certain MRR/ARR expectations or is it more than that?
Well one thing could be to just do a realistic MRR expedition. Here’s an example:
So in your dream scenario your company will turn over $600k per year. Which I think is too little, considering it’s pretty unlikely. A dream scenario should contain revenues of $1B+, so if you reach 1/100th or that, you’ll still have a nice company.
Whew I've not considered numbers that high but I totally see your point about estimating a dream scenario and then getting realistic with actual reach. I'll give this some more thought. Thanks again Johan!
No problem, hope it helps!
I have experienced this before, in similar circumstances in the past, particularly in dealing with funding providers. When considering business proposals for possible untapped markets, they often used the expression: “There may be a gap in the market, but is there a market in the gap?” In other words, “Can your idea make enough money to satisfy all stakeholders, including yourself?”.
But, if you enjoy the niche, and you are happy with whatever income it generates, and you have no particular desire to expand hugely, then just carry on enjoying it!
When you feel you’ve reached the maximum size of businesses you want Be Inclusive to be, you could consider whether you can either run that business in a passive way, or sell the business, or have someone else run it on a part-time basis, while you explore possible new niches to work on.
I can't imagine taking on funding only to realize the market is too small for the investment. It seems the happiest pairing is going hyper-niche + bootstrapped so there is less concern about turning a significant profit.
Thank you for that, sometimes it's easy to get carried away with "how do I make this worthwhile?" It's nice to pause and reflect on the journey it took to get here, and realize that I do enjoy the feedback I get from a small but mighty group of subscribers that say it helps them get their job done.
Great quote, surprised I've not heard that one before!
It definitely yes. My product is a tool to send web articles and newsletters to Kindle (https://ktool.io). It’s too niche that it’s quite hard to acquire new paying customers.
I was aware of this since the beginning but was too busy to take action.
Going to pivot soon to broaden the target customer
Thanks for commiserating in our hyper-niche startups! KTool looks really neat, what do you have in mind for pivoting? Offering more than Kindle as a destination for articles?
I do not believe this is a problem of being 'too niche'. Niche is specialised process for a set group. Kindle device users are not a niche for me. Even owning a kindle I would never use such a service as my ipad mini can do it as part of standard operating system 1 click. Very pleased to hear you did get paying customers for your effort!
This is exactly why it's a "niche". A very small amount of people would need this solution.
Kindle users are not a niche: true. I never say it was.
BUT, Kindle users who don't just use it to read books, but instead wanted to read all kinds of web content on their Kindle, because they value e-ink screen & zero distraction reading experience.
Now that's is a niche.
Firstup, your LP is fantastic! Adding to myCollection.
Typically in a niche business, you master a very particular process for a set group of people. That does not mean you only ever have to master that 1 process. Most niche processes can be replicated out.
That is in fact how CRM grew from basic lead generation thru to opportunity management and the full CRM, then duplicated that and popped it into B2B context.
so for me, at the. mo, focus on mastering the niche process.
Get it sooo slick, people looove to use it. Like Apple standard of beauty and elegance.
Cant emphasis how critical usability and enjoyment is when dealing with a tedious process. The best apps I have seen in this domain, make it so the users dont have to capture anything, just point and click their iphone/android for evidence capture.
Once it is that slick, the citizens experienced to be 'that easy'... citizens will find ways to use your so-called niche process in other ways. Citizens in my experience can't stand anything tedious and when they realise benefit using your app, it wont take them long, to go.. hey.. we could also use it here (sure there will be some tweaks to adapt, but not many).
I hope this makes sense.
Forgive my ignorance, but what is LP? I appreciate your kind words but want to understand what in particular was fantastic :D
I like that mindset of focusing on the user experience to be as easy as possible, I think I've been doing similar and my small but mighty list of subscribers agree. Hoping to continue to grow based on that positive response. Wishing you luck on your product as well!
LP = Landing Page
To communicate the 'how it works' to others, outside your small and mighty subscribers, a GIF is best. People can scroll to that and it is ok.
I even love how you describe your subscribers. Communicates kindness and regard.
Thankyou for your well wishes. Hope the detail helps. Feel free to reach out if you ever what some process aspect tested from a UX perspective.
I'm actually intentionally going "too niche" with my first product. Not sure if it's going to work, but my thought is to use it as a wedge to acquire my first ~100 or so customers before expanding the feature set and going more broad.
In my view being "too niche" is beneficial when there is so much saturation & Duplicted Software Features.
On the Flip Side, It is difficult to generate sufficient interest & sales to sustain a business. Finding the right balance between a product that addresses a specialized market & appeals to a larger audience is difficult.
Yes, it is possible to be too niche. If you focus on a very small group of people with a specialized need, you may find it difficult to generate enough interest and sales to sustain your business. It's important to identify the right balance between a product that is specific enough to meet the needs of a particular market, while still being broad enough to appeal to a large enough audience. Doing some market research can help you determine the size of the potential market and if your product will be viable in that market. Additionally, make sure you are staying up-to-date with emerging trends and technologies so you can adjust your product accordingly.
I don't think so
Nikita Bier has a good tweet that says:
"The only way to push through the noise of the App Store is to be unapologetic about marketing to your first users. If your first users are Berkeley students, go ahead & call the app Berkeley Memes. It's hard enough to get the flywheel spinning without being obnoxiously relevant."
I like what you're offering and you're genuine in helping your market solve a problem; so no, I don't think being too niche is a problem. Besides, you can always expand your services in the future, especially after feedback from clients.
Thanks for the kind words, yeah I've considered expanding the offering some and have been weighing the pros and cons. It's a tough decision! Focusing now on gathering that feedback you mentioned, we'll see where 2023 takes me!
Perhaps you can re-use that tech / UX design and domain knowledge and apply it to something that is closely related to it. This way you can re-use most of what you have and grow your potential audience that way.
This is a great point, I've considered a couple other app ideas but had held off (so far) because I'd prefer to work more on making this one the best it can be. But you're right I do have (what I consider to be) a decent starting point for something new as well. Thanks for the comment!
Happy to be able to help!
Be sure the spin-off projects are also something you care about, so it doesn't become a chore :)
Well, it is about the TAM(total addressable market). Too niche is never a problem, but the market size is. Let's say, you build a chrome extension that helps indiehackers filter posts. Now it is as niche as it can be, but the community is a growing one. With that you can find the number of people you can serve to. With that you make an assumption that how much share of the market you can take and how much money that can make you. If that money is a profit that you desire, then "too niche" it great. Having said that, you can expand you market by spreading awareness.
Being "too niche" in business has both pros and cons. On the positive side, specializing in a specific market allows for tailored products/services and reduced competition. However, downsides include limited market size, dependency on a narrow segment, and potential scalability issues. Perhaps broaden the niche as your company grow?
It depends a bit on your goals.
I think especially for indiehackers the smaller the niche the easier it gets but obviously you'll hit limits in terms of earning potential and outside investment.
Having said that from your description your market doesn't sound all that niche at all tbh.
What makes you think you are "too niche"?
"Freelancers" and "small agencies" is actually NOT niche enough. "Managing accessibility audits" does seem to be somewhat MVP, although I'd need to actually see it to "audit" it myself. From the sounds of it, you may not be experiencing growth in terms of numbers or revenue. If that's the issue, you'd really need to conduct research to understand "What problem does managing accessibility audits really solve?" Once you have your core problem defined, you'd next need to take a look at what industry is either needing it the most and ignorant, or already actively buying accessibility audits? (Blue vs Red ocean.) B2B is the fastest to revenue, but you've chosen the businesses with the least amount of profit margin. Finding one behemoth in an un-catered-to industry, or that spends quite a lot of time and money on accessibility audits would immediately turn the tide for you. Just 3 enterprise clients paying you $10K ea per month subscription would be $30K MRR. This gives you the overhead to scale and grow your business. Thereafter, you can create a smaller, cheaper offering catering to the freelancers, and small agencies. You can never be too niche, and in your case it sounds like your NOT niche enough. Pick an industry, pick a problem, pick a bigger client. Then scale. Cheers!
I think there's a high chance that once a niche starts working, it starts spreading making it no longer a niche. I think the chances are low for a good niche to stay a niche, or niches to be "too niche" - I think this means the product will burn out in a couple of years.
DISCLAIMER: just my thoughts!
Thank you for your thoughts! I think this is good general advice on the subject, though I've learned over the years that some verticals just trend a bit low in terms of growth year over year. Unfortunately, none more pronounced than with accessibility.
I do see an overall increase in awareness, and a desire to do more to bake in accessibility best practices earlier in the product development cycle so I continue to be hopeful. I think another factor that keeps me going is in knowing this app I built contributes (in its own small way) towards a more accessible experience, and that's enough for me to continue to support it and look for more freelancers and agencies that aspire to build accessible digital experiences.
"Too niche" can mean a few things:
There may be people who love your product, but no reliable place where those people gather that you can tell them about your product. IMO, the fellow in the comments making a product that sends web articles and newsletters to Kindle falls into this category: even if find a way to find just readers or Kindle users, only a small slice would find that product useful. I'll call this "unreachable customers".
Your product works great for an easily findable slice of people, but there aren't really any "adjacent" groups that it would also work well. The overall addressable market just isn't large enough for what you built to support a business. When I was younger, I built a super useful tool for an online game... with 20 players. I would never try to turn that into a business. I'd call this "too small of a TAM (total addressable market)".
The ideal is that you target a very small niche, build a great product for it, and then find adjacent niches that your product also works for. That's a much easier way to earn a large market than approaching it head-on.
Yes, but that's not a bad thing. Finding the right sized niche is hard (and I'm still learning by trial and error), but if you have some customers and feel your niche is too small, to me that's a good signal to try expanding the scope a bit.
I think I heard Adrian from PyImageSearch talking about this on his recent podcast. He focused on a really specific Python library (if I remember correctly), got a bit of traction but not much, and then branched out into other Python image-related stuff and that took off. To me, that seems easier than starting too broadly and not knowing where to focus.
Having said that, maybe there are other ways of gaining traction for you. I certainly wouldn't try to reduce your pricing (if anything, increase it!), but if you have some power user customers then a couple of suggestions are:
Some great and thoughtful points here, thank you so much! I am actually planning on reaching out to existing customers with a (hopefully short) questionnaire already, I'm going to try to frame some of the questions this way. The handful I've spoken to directly have been enthusiastic so I'm hopeful I can glean more information (and help) from them.
It's crossed my mind, but I've held firm here because I really want to give freelancers and individuals at smaller agencies an affordable way to get this kind of work done more quickly. The hope is that making it affordable may be a difference-maker in their ability to make the time for this important work.
Is this the podcast you're referring to? https://infoproductmastery.com/
You're welcome!
Yes, that's the podcast. I think it was one of the first two or three episodes where he talked about niches.
And regarding chatting with customers, I found this talk by Joanna Wiebe insightful (starting around 25:50): https://www.youtube.com/watch?v=F_urkVueszI&t=1490s
Thank you for confirming, and also for that video of Joanna Wiebe! The name sounds familiar so I must have heard/read some of her content in the past. It's a great reminder to listen to customers.
Possible, but the more niche you become, the more money you have to charge for the product.
Ah this is an interesting take, is it coming from an angle of "I need to charge more to make this niche project worthwhile" or "this niche project is perfect for my unique situation so I'm willing to pay more for that". Both?
It can be too small, if it's so small the number of potential customers is only in the double digits and the value of the product isn't in the five to six digit range.
Beyond that, I think it depends on your goals?
If you're trying for a side income, and the project doesn't require a huge investment, then a relatively small niche could make sense.
It's all about cost/benefit analysis, right? If it costs a lot of money to build the product and the return is too low, then you will likely lose money. If it only costs you time to build the product, and the return is low but consistent over time, then you've built an income stream.
If you're looking to go big, though, then you really need to carefully choose your niche and ensure it's large enough to support your goals.
Your example seems potentially problematic though. I'm a freelancer who has worked on a decent number of startup sites, and I've never been asked to do anything at all about accessibility. My thought is that very few startups think about accessibility in their initial product design. It's not a part of an MVP; it's what you do once you've gotten traction. Maybe agencies would see more requests for accessibility?
But a tool to help manage the audits? I've seen a lot of tools that will perform an audit, but I have a hard time wrapping my head around what managing the audit would even look like or how it would help me. I mean, why wouldn't I just use a tool to validate the site and add any problems the tool identifies to my normal task tracking list? Or better, just keep running the tool and use the list of problems in the tool as my to-do list? There are a ton of free tools, after all.
So considering I would be a potential customer if I had a client ask me to ensure a site was accessible, at least your description, phrased in that manner, doesn't sound like something I would need. Maybe you have a better elevator pitch that you didn't employ above?
But if I'm right, then your niche isn't just small as much as nearly nonexistent. And you do need to have some customers.
I like that you narrowed down your niche; that's actually pretty hard to do, at least for me. But I think you might have a difficult sell for that product.
This is a great way to frame it, thanks for that! Right now I'm happy with staying small and treating it as a side income. Thinking of it that way does help reduce the stress a bit.
This is a great, and somewhat depressing, point about the lack of focus on accessibility early in product lifecycles when it could potentially be a whole lot easier - and thus less expensive - to incorporate into the build. Truth is, accessibility isn't a priority until it very much is either by regulation or by getting sued, and then companies are stuck paying off that tech debt and have to do so quickly because they're reacting. I think the freelancers I have in mind aren't necessarily working on these kinds of startups, there are freelance accessibility auditors for example. Might be something I can try clarifying on the site, will consider that!
Aha, this is a rather common misconception about accessibility testing. Automated tools (like browser plugins from Wave, SiteImprove, Axe, etc.) will absolutely give you a whole list of potential accessibility problems, but by virtue of being automated there is no way they can find all potential blockers. There is also a good chance there are going to be issues flagged that are "warnings" that need to be manually validated (or invalidated), for example text overlayed on top of a background image.
I really appreciate this thought process you shared here, I think adding a bit more high-level education on the benefits of a manual (even quick keyboard & screen reader testing) audit could be helpful. There might be a way to convey that quickly to folks that are scanning the homepage "why would I want help managing audits?" or "how is this better than running an a11y validator?". That question could link to a succinct page that outlines the pros and cons. As a potential customer, would that help you make a more informed decision?
You brought up a good point. I'd say the SaaS that I'm considering doing is pretty niche (Online portal for scholarship managers & donors), but it's comforting to know that this can just be side income to support my main project, scholarship management & consulting (old-school trade in your time for money). Thanks!
I am currently struggling with this concept myself. We built an end-to-end encrypted data storage network that uses a Cosmos blockchain for user permissions and making sure our storage providers continue to have all the data. Its called Jackal: https://jackalprotocol.com/
We live and die by the unique TBs that will be stored on this network.
We are still pre-product, but our options are;
Continue to double down on the Web3 niche that would use Jackal as an active cloud storage environment with their crypto wallets. These users enjoy the values of self-custodial storage, ownership, self-sovereignty, geo-redundancy, and other classic crypto ideologies.
Generalize into an auxiliary data backup for disaster recovery with the Web2 markets. They want a custodial solution without the crypto wallet UX, email and password login, fiat currency payments, and other values that oppose the web3 peeps.
Do both and risk spreading our marketing and engineering efforts too thin with 18 months of runway left.
Would love to hear what everyone thinks.
Hey Patrick, took a peek at the site and I'm going to be completely honest and admit that - even though I have a technical background and have no trouble around new technologies in general - I struggle quite a bit with the crypto/web3 niche. That's already going to cloud any feedback I could personally provide so please take the following with that in mind as I don't think I'm your (current) target audience.
When I clicked the link my first question was "what's the Jackal Protocol?" and I struggled to really get an answer to that at first. The terminology sounds impressive but I read the tagline "Jackal Protocol is the purpose-built blockchain for the everyday user. No more choosing between security or user-experience. With Jackal, protecting your valuable data has never been easier." a few times and still didn't really get what is offered. After clicking around a bit it seems to be a few things - cloud-based storage, a Retriever Name Service, and a token.
Again, full transparency, I have no idea what a Retriever Name Service is even after looking at https://jackalprotocol.com/rns-2/. It's some sort of domain registration to identify blockchain addresses? The token part is a bit more clear to me, though I don't fully understand the benefits of utilizing it.
At a high level there seems to be a few offerings for consumers, as well as a couple ways for folks to participate more deeply via the Storage Providers & Opportunities pages. Maybe both of those pages should be under the "Participate" dropdown? Otherwise I don't really understand why there's a dropdown with a single option.
Finally, there are a lot of great CTAs that I excitedly clicked on hoping to learn more, but most redirected to the app with a password field. If someone were interested in signing up, how do they go about doing that?
--
TL;DR - All the above is to say, if you're at all leaning towards pursuing a more general audience I would suggest some explainers to help plebs like me grok what's offered and how it's better than other data backup providers. It seems you've already gone all-in on the crypto/web3 crowd so swapping to generalize would be quite the pivot, option #3 seems more palatable even if it starts as offering a helpful leg up on understanding some of this more easily. Hope this helps!
Unrelated, but wanted to say the site has a beautiful layout and I really like the illustrations too! It went a long way towards me continuing to explore even though I was struggling initially.
Hey Steven, this is awesome. This is the long form feedback we need.
My key take away from this is to reduce web3 jargon, which I agree is a barrier to entry. Also cleaning up the menu by moving Storage providers to the dropdown with the other opportunities.
Regarding the CTA's were still pre-product so the dashboard is password protected. Swapping that for a sign-up is definitely the right thing to do for the time being.
Thanks for this, when we launch I would love to give you a free TB of storage for the year so you can try it out.
Glad it proved useful, all these takeaway planned changes you mentioned sound great to me!
I'll take you up on that offer too, thanks! Let me know if you're interested in a similar extended trial of Be Inclusive. As you probably could already tell I'm big on advocating for accessibility and early in a product lifecycle is an ideal place to start building with best practices in mind and testing what you've already completed.
Sure. If the need is so overtly specific, then it's possible. If you're catering to a group (freelances and small agencies), then it seems likely there is enough of an audience. Every focused need beyond that is going to make it less accessible.
It sure is, if you have relatively big costs and a very niche product it's going to be hard to profitable.
I am facing the same problem. We are developing a file version control software for mechanical engineers, and on the one hand it is actually harder to develop than git, but on the other hand it turns out that the group of engineers who can accept the git concept is perhaps smaller. So it's hard to break even financially when doing commercialization. When the potential user group is relatively small, too expensive people are not willing to buy, too cheap and especially low revenue.
Going very niche is great for learning and another source of income but you will plateau very quickly.
I think that starting from a niche is good practice because it gives confidence and feedbacks. However, once you realize that a niche is too limited for growth, you should definitely pivot.
Starting with a small niche is often key to getting off the ground. It allows you to refine your offering and build a loyal customer base. From this strong foundation, you can gradually expand to other niches.
There are 8 billion people in the world. If you can build something that just one in a hundred thousand people want (that's pretty niche--just 22 people in my hometown of Houston) and charge $10/month for it, that's nearly a million a year in revenue.
Accessiblity is a niche space and it works out well for you as companies are starting to be more inclusive. My company finally appointed a head of accessiblity to get a top down directive on accessiblity and inclusivity.
I guess how niche you can go also depends on which sector you are in. Like for us, @fastsociety and I are building in the AI space which is so broad and emerging every day. We have kept our scope pretty broad and we are trying to narrow down our niche based on user feedback.
Great questions!
I've struggled with this before as I built my first venture (IWL Translate). At some point, we were using something like 37 demographic and psychographic parameters to segment our audience to the point that we only had around 150 accounts that fit our criteria.
Ultimately, the key driver of any decision was the profitability of the venture.
Aside from exploring cost optimization plays, I also looked into whether I could find some upsell or cross-sell opportunities to increase the average buy per customer. This way, we could leverage our existing customer relations and increase our total revenues with 0 marketing spend.
In our case, after building a financial model with few scenarios, we decided to stay niche, leveraged some upselling opportunities and managed to increase the average customer spend by 150% in 6 months.
Looking back at this experience, I'm very happy with how things turned out for us. However, if I'd find myself in the same situation today after +9 years of venture building, I'd make two minor adjustments to my decision-making formula:
If, after all the calculations and introspection, it turns out that the business is sustainable, runs with very little intervention from me and allows me to do something I like, I'd keep it going.
Not every business can or needs to be a gazillion-dollar mammoth. As long as it is an economic and emotional value-add in your life, why shut it down?
P.S. Your product really looks great! I was not even aware of the existence of accessibility audits. Thanks for introducing me to this ✌️
Presumably being in a niche is only a problem if you can't grow existing accounts or find enough users.
But, just because you started in a niche does not mean you must stay that way.
Use the niche need to spearhead into specific, additional users and then grow the product scope based on the next logical thing they will need (and without ruining your core service)
If you have a dedicated customer base you're miles ahead already.
Anybody can be too niche but what will also be too niche is your revenue. Then one way to increase revenue when you're very niche is to dominate that niche be an expert at it increase the value/offerings and own that market which is easier that owning a market that's very packed with the big boys.
While it can certainly help to be great at a specific thing, you put yourself at risk. Being too niche means that you won't have room to pivot into something related or similar, should there be any economic changes impacting your target audience. Or a new law, regulation, new tech.
It's definitely possible to be "too niche," but it's important to remember that niche products can still be successful. The key is finding the right balance between being niche enough to attract a specific audience and having a large enough audience to sustain a business. It sounds like you have a loyal user base and are happy with your progress, so it may not be necessary to broaden your target audience. However, it may be worth exploring other ways to monetize or expand your offering within your niche market. Ultimately, it's up to you to weigh the pros and cons and make the best decision for your business.
Hey Steve, I think it would help to start with that very small niche and then see if you want to scale later. If you are already ready with this audience then it doesn't matter right now how big or small the niche is.
While it's essential to find your target audience, it's also important to consider the potential size of that audience.
Targeting a specific niche can have its advantages. For example, a small but dedicated group of power users can provide valuable feedback and help shape the app's direction. Additionally, a niche market can be less crowded, making it easier to stand out from the competition.
However, it's also essential to consider the market's potential growth. For example, if the need for accessibility audits is not growing, it may be challenging to develop your app. It's also important to consider if there are other potential markets or use cases for your app that could expand your target audience. With my website that provides complete design services, I cater to a specific niche of people looking for such services.
Ultimately, it's a balance between finding a niche that is small enough to be manageable but large enough to sustain your business. Evaluating if your place needs to be bigger and if there are other opportunities to expand your target audience is always worth considering.
This is my product.. you can check it out here: https://www.bubblewrap.design/ For better understanding..