How To Go From Idea To Launching With Paying Customers In 8 Steps
jasonlbaptiste.com
How To Go From Idea To Launching With Paying Customers In 8 Steps
1–10 of 44 posts
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#2Good real-world stories and inspiration, Jason!
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#3How to masquerade self-publicism as a how to?
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#4How to masquerade self-publicism as a how to?
If you know me, I could really care less about the traffic one article brings. Here's what I do care about: the comment I would have gotten - "Give us examples please" So I gave everyone examples of what we did.
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#5How to masquerade self-publicism as a how to?
Perhaps you could develop your argument a bit more before trying to tear down a substantial post on someone's experience?
I think that would be a more valuable contribution to the discussion.
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#6I really like this post.
The one thing I feel it's missing is the major step of vetting an idea. Is it WORTH doing? I literally get cold emails every day from entrepreneurs who say, "I've spent a big chunk of my life building this thing and none of the ways I've found to acquire customers is working in a scalable way" (they generally don't word it that way, but you get the gist). It's gut-wrenching.
Maybe that's a different post, but if you're building a startup for growth, you could be running that company for years (remember, avg. time to liquidity for a venture-backed startup is 8.7 years!). You should be careful to chase ideas that aren't merely viable but GREAT market opportunities (or at least products/markets that you LOVE). It's easier to swim downstream.
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#7Great list, but I don't think you need the detailed spec. Same problem as usual in developoment: the spec will be outdated by the time you're even half done, when you're finished with the first version of the product your detailed spec will be so woefully out of date (or a huge time sink to keep updated) that you'll end up rewriting it.
What you do need is a defined documentation of your internal/public API's. If the developers don't know how modules talk to one another that's a recipe for fail. Then just to keep everything coherent, a rough skeleton to keep everyone on track. Basically a mix between your step 2 and step 5.
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#8I really like this post. The one thing I feel it's missing is the major step of vetting an idea. Is it WORTH doing? I literally get cold emails every day from entrepreneurs who say, "I've spent a big chunk of my life building this thing and none of the ways I've found to acquire customers is working in a scalable way" (they generally don't word it that way, but you get the gist). It's gut-wrenching. Maybe that's a di…
I'm working on the vetting an idea post for OnStartups. It's a huge topic and a very important one. A lot of entrepreneurs seem to vet their idea like VCs. The criteria is somewhat similar, but it's not the best way to go about it. We're talking vetting an idea internally before even going after simple MVP/customer validation, correct?
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#9Great list, but I don't think you need the detailed spec. Same problem as usual in developoment: the spec will be outdated by the time you're even half done, when you're finished with the first version of the product your detailed spec will be so woefully out of date (or a huge time sink to keep updated) that you'll end up rewriting it. What you do need is a defined documentation of your internal/public API's. If the…
If you're doing a developer heavy app that requires an API, the API documentation is insanely critical. I don't think I emphasized this enough. I've been a complete lunatic (in a good way) about the API docs, response calls, etc. You can have things ghetto at first I guess, but having detailed responses is very important.
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#10Great list, but I don't think you need the detailed spec. Same problem as usual in developoment: the spec will be outdated by the time you're even half done, when you're finished with the first version of the product your detailed spec will be so woefully out of date (or a huge time sink to keep updated) that you'll end up rewriting it. What you do need is a defined documentation of your internal/public API's. If the…
If you're doing a developer heavy app that requires an API, the API documentation is insanely critical. I don't think I emphasized this enough. I've been a complete lunatic (in a good way) about the API docs, response calls, etc. You can have things ghetto at first I guess, but having detailed responses is very important.
Yes, being pedantic about responses and stuff that's flying around is vital. We can agree on that.
But keeping an insanely good db documentation and a bunch of other stuff feels like overkill.