A brief guided outline to all the basics needed in establishing an early stage function, online presence, and investor readiness...
<aside> 💡 Disclosure: I don't intend to say that these are the "required steps" to have something solid or to have anything at all for that matter. The requirement documents are the way product teams in big tech co.'s set up product roadmaps, dead lines, budgets, and the like — these co.'s may have much longer product cycles and the money required to take long in releasing pieces of the product — . In other words, the documents create a thesis of sorts from which the pitch deck is decoupled. These tools get the whole team in the same page, for instance, when questions like "who are your users?" are brought up before you have users.
Think of it much like the Lean Canvas, which serves as a guide to think through the product at the early stages and results in a much more complete version. This article is not to say that these are absolutely things that must be made.
In any case, the ultimate thesis will not be a pitch deck but the creation of a product that aims to fit to the particular market that you're trying to reach, let not these docs detract from that. Instead customer's feedback - which corresponds to the prototype and insights area of the article.
At the end of the day, companies should do what works best for them, and that means, building traction.
</aside>
Let's connect! 📲
<aside> 💡 Check out more content on this outlet I call 👉🏼👉🏼Le Blog.
</aside>
right off the bat, you should read Paul Graham essays: