There are so many obvious pitfalls, and the lessons learned are not particularly good. It should have been summed up as:
> Discuss the core business product and idea with a technical person mostly capable of understanding the details it entails. Understand the market, end product you want to envision, and evaluate if there is a fit for it.
But then again, pick any "startups for dummies" book, and it'll explain exactly that.
A technical person should be able to give pointers on stuff you might be missing, and then knowing if there is a market for it... If you don't know, then, what's the point?
For example, "lesson #1" should be met with ">... What do you mean? Of course it is. Also... what do you mean? Who's the middle man here?".
"Lesson #3": Build an mvp
"Lesson #4": If developing your MVP is 90%-95% development costs, you better know how to do this, or have deep enough pockets to not care.
"Lesson #5". What are you talking about?
"Lesson #6": See lesson 3.
"Lesson #7": See lesson 3, also, talk to potential customers, heck, even before mvp.
"Lesson #8": See lesson 7, i.e. lesson 3.
"Lesson #9": I would argue a founder's job is to establish the business and product to a point where one can evaluate the extent it fits a market that was assumed to exist, then tested to exist, then proved to exist. None of this is necessarily related to sales, or cannot be handled by dedicated sales people.
In any case, kudos for writing a post mortem on this. Most would be too embarrassed by it.