I'll start: the possibility that I've simply chosen a bad problem to solve.
The IH podcast (specifically @arvidkahl 's interview) talks about the importance of choosing a good problem/market and I'm increasingly convinced I didn't do this well.
I definitely don't solve the #1 most important problem of my users. Maybe top 5. Does this mean I should quit? If not, how should this affect how I proceed?
If you're not solving #1 for everyone in the niche, maybe find a smaller sub-niche where it's not just #5, but maybe #2.
It's like how there are tools for podcasters, and then there are tools for podcasters who want to automate their marketing. A mp3-to-video SaaS will sell pretty well to "all podcasters", but it will sell insanely well to "podcasters with automation aspirations".
Niche down in your niche, and as long as the resulting market is still big enough for you, you'll be good.
Otherwise, just solve their #1 problem ;D
Thanks! I'm struggling with estimating the size of the market, do you happen to have any tips for that?
I have written about that particular topic here: https://thebootstrappedfounder.com/determining-the-size-of-your-saas-market/
thanks!
I wonder what I should prioritize or what steps given my current project situation I should focus on.
I really identify with all of these! Especially the "something else I don't know" and "just be happy".
I’m an 18 yo starting out this journey building stuff that my friends and I need (occasionally mom and dad). My biggest doubt is whether I would be taken seriously 😬
Please comment on my post to help me out!
https://www.indiehackers.com/post/high-school-student-here-feedback-on-a-product-idea-282beafabd
Cheers!
My biggest hurdle/self-doubt is worrying about whether or not a specific track is worth my time. I have a great job that I love, pays me well, and requires a lot of mental and emotional investment...so my spare time is quite valuable.
I spend my time doing user discovery, then never actually transition into building a solution for the problem I uncover. It's a silly problem.
That's probably the right order to do things, doing research before building :)
I would generally agree with you...if I ever actually built anything!
The doubt is if businesses are that interested to the product. As a user who accesses a website (from a business), it is a lifesaver.
I'm pretty confident I've chosen a good problem to solve - it's an itch I myself want to scratch and there are some good competitors already in the market, but aside from some initial marketing to prove my assumptions, I'm worried I won't be able to follow on and build actual traffic/buyers.
This has always been my weakness, though, so I also have historical data to be worried about. =)
If you have a good problem I wouldn't be too worry about that :)
part of the process of figuring it out is asking these questions.
so, you're doing it "right"...
but, at the same time, you will need to eventually commit to an approach and a market. the way that i've landed on this is realizing if i've "fallen in love" with the problem... not the solution.
that way, despite the changes in solution (iterations of the product), i've not fallen out of love (or interest) in the problem i'm trying to solve for my customers and community!
Thanks John. I do feel passionate about the problem and the users/community, so I think that's good at least!
that'll get you through the tough times.