At AngelHack hackathons all over the globe, we’re always getting questions from aspiring entrepreneurs and programmers about team structure and dynamics. A frequent question: how can I contribute if I’m non-technical? Is a hackathon the right place for me? Over and over again,
we see that teams with a balance of strong design, programming, and business succeed most.
Here are some tips on how to provide value as a non-technical founder.
A version of this post first appeared on the Groove blog.
I’ve founded three SaaS startups, all without writing a single line of code.
“You can’t build a software business if you can’t make software.”
Bullsh!t. While we’ve got a long way to go, I’m damn proud of how far we’ve come at Groove.
And we’ve done it with an outsourced prototype, a killer team and a ton of hustle. And me. A decidedly non-technical founder.
This isn’t a woe-is-me cry for non-technical founders to get more respect in the industry. Respect is earned.
But this is now the third time I’ve been a non-technical founder, and I’ve learned a lot of lessons along the way.
Lessons that have helped me work more effectively with my technical team members, add more value to our product and become a better entrepreneur.
I hope you can learn from them.
Note: a lot of these are great skills for technical founders to have, too. And many technical founders I know are really good at them. But from my experience, for us non-technical folks who can’t contribute to the codebase, I’ve found these to be absolutely critical. Read more: click image or title.
Get your Free Business Plan Template here: http://bit.l/1aKy7km