This article is the tenth in the Startup Series on FirstPost’s Tech2 section and first appeared on January the 23rd, 2017.
A healthcare startup founder I know was in a dilemma. For a pretty sizeable chunk of the equity pie, she had agreed to take on as cofounder a tech development guy. He would in turn build the platform which would enable her business model. As delivered, the platform however was far from adequate. The tech cofounder however was not amenable to taking feedback. Lately he had gone completely quiet and was not responding to emails or picking up calls. Our healthcare founder was left with a platform that did not work as expected, with no access to the source code, and now a growing dread that the company was slipping away from her even before it was built. She had no more money left to bootstrap or to pay for legal advice to buy out his share so she could get the code and find another solution.
When I heard about it, I asked her if the equity was his outright or had a vesting schedule, whether there were ways of clawing back some of the equity as a BATNA, what checks and balances had been built into the agreement between them. What I found was not encouraging.
Through some wrangling, this particular situation somehow found a cobbled-up solution. It is, however, illustrative of why your company’s risk culture needs to be thought of right at the time of creating the startup.
Whenever I bring this up with founders, they ask if entrepreneurship is nothing but risk taking by any other name. It sure is! It is about taking those risks that advance your goals, not risks that destroy your dream. It helps to develop the ability to tell the two kinds of risks apart.
I am not recommending that instead of building your product and your customer base, you spend your time writing huge formal manuals or official policies. I am, however, strongly recommending that you give some thought to the values, beliefs, knowledge, attitudes and understanding about risk shared by a group of people with a common purpose, collectively the risk culture.
How to shape your risk culture in early days? Here are some tips to clarify your thinking.
First, ask if the risk advances your objectives, your dream. At what cost?
In early days of developing a product, building user communities for early testing of features and pricing, capturing feedback and using it to improve the product, all cofounders may use their own devices to write code, collect information and user feedback, keep essential documentation. This is a good move to avoid spending a lot of cash on buying hardware that belongs to the company, if indeed the company as a legal entity exists at all in the early days. There are of course several possible existential risks at this stage. How is the repository for what the cofounders are learning being built and accessed? Where is the essential information — source code, names of suppliers, passwords for services to name a few — kept? Can all cofounders access it? Can it be lost or tampered with easily? What is the backup plan?
Second, think of mitigation plans required, should the undesirable event you anticipated comes to pass.
What if cofounders fall out, someone wants to leave, or someone dies? Can one cofounder hold the entire venture to ransom? What if your only supplier decides not to work with you, and they have copies of your sketches which they could as easily manufacture and start selling? It goes without saying that this mitigation planning needs to happen when you are making key decisions about cofounder relationships, product development, suppliers etc. One can, of course, deal with undesirables as they arise but it is likely to cost more money and time to fix than to prevent or have other recourse.
Last but not the least, by thinking through, however uncomfortable it may be, what happens if it all goes to the wall.
This is the tricky bit. Our healthcare founder was on the verge of incurring a heavy cost for not thinking through the apocalypse scenarios regarding her cofounder. His contribution was essential to her startup but his temperament and working style could not be mitigated by writing tough contractual terms. We don’t like to imagine doomsday situations, sometimes rightly so as they can be paralysing and demotivating. But it is important to know at some level what you would do to salvage your startup if the worst things you had not planned for happened.
Our risk propensity is about that we are willing to accept for just returns. A clear framework for the risk culture makes it easier to identify, preempt, accept or reject those risks. It is wise to start early.