Skip to content

Comment on Warning signs in a non-technical cofounder (can you spot them?)

Comments

Are there any signs for non-technical co-founders that we should take as 'positives' - like this guy knows what he's talking about ??

I guess the one that springs to mind for me is someone who has previously launched some startups and had some success ...

I look for "guy in some field thinks app/site is desperately needed by that field." This implies domain knowledge and existing relationships for target customers.

That's actually pretty rare, in my experience. But, it's how I've seen several non-tech companies start, basically.

The non-technical co-founder should BE that guy. Not know that guy. I get THAT one a lot.

I actually WAS that guy, but I couldn't find my technical co-founder - so I just became a technical founder ... took me a few years, but I'm there now ;)

Same here... I had domain expertise but wasn't technical so I just sucked it up and learned. It's taken me a few years, but it's well worth it.

Looking back, I think that's the only way to go. That, or at least learn enough to have a decent conversation with technical people so when you ask them to do something, you know how big of a pain in the ass you are being.

Even without experience, a very good sign is that they know and are passionate about the market they want to enter.

Sure, it will be a bigger risk if that person has no startup experience, but if they've been working in the X-industry for years, are passionate about said industry and believe they've identified a major (and preferably disruptive) opportunity, that significantly improves the odds.

Trust. If they don't trust you to make decisions, they are looking for "An IT Guy". Not a co-founder.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.