Skip to content

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

Comments

I generally run from non-software people wanting to be in the software business but not even want to learn or try to understand how software is built.

You might not do construction yourself but the more you know the better it will turn out being the non-technical general contractor.

I like the one rule a-lot: Ignore them if they have no expertise in the area they're wanting to startup in. Its fine if they don't program.

If you do get involved with a non-tech cofounder, don't take equity or deferred income. Startups are a little like dating in the beginning, there's no need to get married before you ever work together. Someone should pay for your time instead of expecting it for free.

If being paid for your time is working well it's easy to figure out ownership after. If the non-tech cofounder is not willing to put his money where his mouth is, it might be full of something else.

Even as a developer, when I've gotten help on an idea from a friend or colleague I always pay them and say do as much as you can for me, this is my money out of my own pocket. Since us developers are a egalitarian helpful bunch often they want to just help as friends but I make sure to pay because it's just respecting their time and saying hey, if this goes somewhere, we can always figure that out. I've never lost a friendship/colleage relationship this way.

AboutSource Built by g1lg1l

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