Skip to main content

Finding a co-founder for a "mature" early-stage startup

Often, you hear about how two or three or four friends/colleagues got together and launched a hi-tech startup ... and lived happily ever after.

You might also have heard about how VCs "help" a single founder put together the right team- sometimes without the need for the quotes around "help".

I have come across several founders of hi-tech startups lately. Maybe it's because they're all bootstrapping, and maybe it's because the cost of doing a software startup has gone down so dramatically. But the fact is that more and more startups are being launched and bootstrapped all the way to Angel/VC funding, until they become cash flow positive or until they die.

Many of these solo-founders don't want to go it alone. But once you're bootstrapping, you are on a roll, and it's not easy to find someone at a later stage who comes along, say a year later, and shares your passion and vision.

On the flip-side, I see wanna-be co-founders on the sidelines much like the way Angels and VCs do, waiting to see how far you can go it alone before they decide to join you. In other words, they are trying to maximize their contribution to risk ratio - and reap the rewards of being co-founders.

What is the best way to find a good co-founder for a startup that's "early-stage" by the Venture industry's definition, but has come a long way bootstrapping?

I don't know, I'm still looking for an answer. But I've started 'Agile Entrepreneurs' specifically to help founders find answers to questions like this.

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint:

Manage Unfinished Work - Split user stories (new link)

Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):
This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying acceptance criteria, in response to t…

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is.

Allow me to explain.

The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with.

Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria.

Describing all the requirements as User Stories for a decent sized product is rigoro…

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams.
Between the bigger things you cannot do,and the smaller things you don't want to do,you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded".

I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day.

Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add yours to the list…