I spent five years building a webapp and got my first $1 (2022)
11–20 of 101 posts
Re: I spent five years building a webapp and got my first $1 (2022)
#12Estimated Cost to Develop (organic) $1,023,233
Estimated Schedule Effort (organic) 13.87 months
Estimated People Required (organic) 6.55
Re: I spent five years building a webapp and got my first $1 (2022)
#13Light text on light background for max pain. Still I will read it though. Frankly, I commend anyone who is willing to work long-term on massive projects by themselves like this. I find it inspiring since all my projects are like this tbh. Seems like frameworks were a major problem for the project. I get it. Sometimes if you're too early you end up having to build not only your project but a small ecosystem of things…
Re: I spent five years building a webapp and got my first $1 (2022)
#14Re: I spent five years building a webapp and got my first $1 (2022)
#15Re: I spent five years building a webapp and got my first $1 (2022)
#16then Ai education: https://pub.education
then Ai healthcare: https://codify.healthcare
I used to think my goal was to do this and that and change the world etc... I am starting to think that I just like building things and maybe thats OK.
Re: I spent five years building a webapp and got my first $1 (2022)
#17Spent last year working on a side project and assumed I would need this and that in order to launch. But after it was ready to launch, I found out there was no product market fit. I have known about the importance of quickly finding out pmf but still made the mistakes. knowing != doing. We just love building stuff and mistakenly convince ourselves that if I add one more feature, this thing would be ready for launch a…
Even non-technical founders make this error. Everyone wants to believe that "just one more feature" is the difference between make and break.
In my experience reducing features is better to begin with.
Re: I spent five years building a webapp and got my first $1 (2022)
#18Spent last year working on a side project and assumed I would need this and that in order to launch. But after it was ready to launch, I found out there was no product market fit. I have known about the importance of quickly finding out pmf but still made the mistakes. knowing != doing. We just love building stuff and mistakenly convince ourselves that if I add one more feature, this thing would be ready for launch a…
> mistakenly convince ourselves that if I add one more feature, Even non-technical founders make this error. Everyone wants to believe that "just one more feature" is the difference between make and break. In my experience reducing features is better to begin with.
This is right approach. Lean. If you don’t have PMF, reduce your features until you find it. Pivot. Maybe pivot again. Eventually you’ll find a market to serve. Just don’t fall into the sunken cost fallacy. Time box your market exploration.
Re: I spent five years building a webapp and got my first $1 (2022)
#19Light text on light background for max pain. Still I will read it though. Frankly, I commend anyone who is willing to work long-term on massive projects by themselves like this. I find it inspiring since all my projects are like this tbh. Seems like frameworks were a major problem for the project. I get it. Sometimes if you're too early you end up having to build not only your project but a small ecosystem of things…
Is that Signal Vercel MIDI thing something people can use to make music for free?
Re: I spent five years building a webapp and got my first $1 (2022)
#20Light text on light background for max pain. Still I will read it though. Frankly, I commend anyone who is willing to work long-term on massive projects by themselves like this. I find it inspiring since all my projects are like this tbh. Seems like frameworks were a major problem for the project. I get it. Sometimes if you're too early you end up having to build not only your project but a small ecosystem of things…