If you’re planning on talking to potential investors and wondering what kinds of questions they might ask you about your startup, here are 37 likely ones. Disclaimer — this is not a comprehensive list. If there is a question you think I should add, please send it my way.
I don’t think non-technical founders should learn to code. I explained why in my last post. I also don’t think most non-technical founders need a technical co-founder.
There can be advantages to having a technical co-founder. But what if you don’t have one? Should you be actively looking for a technical co-founder? Should you put your startup on hold until you find one?
My answer is no and I’ll explain why.
I’ve been a coder for a long time and founded multiple startups. I’ve been successful, but I might have been a lot more successful if I never learned to code.
Don’t get me wrong. I love coding. That’s the problem.
When you’re a technical founder — you tend to spend almost all of your time coding. It’s what we know, love and do best. So, it’s our default mode.
The problem is, there is a lot more to building a successful tech company than writing code. …
Imagine driving a car without a dashboard. You could do it, but it would cost you. Without a speedometer you’re probably looking at a few speeding tickets. Without a fuel gauge, there might be some tow trucks bills too. The the list goes on. Thankfully, most cars have dashboards. However, too many startups don’t.
Launching a startup without a dashboard is kind of like driving a car without one — except, it’s way more costly. So, why then do so many founders do it?
I’m guessing it’s because creating a dashboard seems too technical or time consuming. Well it’s not…
Serial tech founder and professional dabbler @dabblelab. Currently dabbling seriously with Amazon #Alexa and various bot and automation solutions for business.