Not to be overly glib, but the #1 "Startup CTO mistake" you can make is having a CTO. Even on paper, the CTO is an architect's role --- which you don't have time for. In practice, it's a place to put founding developers out to pasture when they burn out.
I think I have some of the same problems,I thought it was a good write up and hopefully will make me more aware when I am making a common mistake...<p>Spending to much time on the technology over the people seemed very relevant to me, as it might pay off in the short term but as the company grows it surely hurts it.