I have been describing to a friend how we distribute equity in elexu and I thought it might be interesting for others as well so I decided to share it here.
what’s the problem?
Imagine you have a great idea for a web startup and you realise you can’t do it on your own. You start looking for a co-worker. You obviously start with a person you need the most – if you are a business/marketing person you search for a developer and vice versa. As you don’t have money to pay them right away you reward them with equity. But how much do you give them?
Let’s say you believe it’s a really great idea and the person’s contribution won’t be worth more than 10% but your first coworker will very likely see it differently – she will see that there are two of you, both spending roughly the same amount of time so from her perspective it should be more like 50-50 or at least 75-25. You agree with that and start working.
It all goes well until you realise you need more human resources. So you find new people and offer them equity but that means that both you and your first colleague have to give up a part of your equity which as you can imagine usually doesn’t go down well. You can easily end up arguing about whether you need new people at all and why you have to give them so much equity. And this gets worse with every new person coming on board as you have more people with a stake in the company whose share you want to dilute.
how we do it in elexu?
We work for sweat equity which means that the salary we would have earned is converted into equity. Each of us has a set salary level. As we don’t pay ourselves any cash at the moment we can afford to set the salary levels relatively generously. Rather than setting the salary based on previous experience of a person we can look at it from the future perspective – either elexu achieved success which in itself justifies the higher salaries (we had to be quite good to suceed) or it didn’t achieve success in which case the higher salaries are irellevant as the equity is worth nothing.
Great feature we use is a deferred payment bonus – in order to make up for the fact that money are not being paid out immediatelly we put a premium of 50% on top the basic salary. The beauty of this is that we can use the same approach for external collaborators (contractors, key advisors, etc.) – if they are willing to postpone their reward until the company can afford it (i.e. after the first investment round) they will get a 50% bonus.
The key ingredient to all of this is the valuation of the company. This is the value stakeholders (founder, employees, investors) believe the company has at a certain point in time. A typical startup doesn’t set their valuation until a meeting with the first investor. That’s too late. It gives too much power to the investor to impose a valuation benefitial for her (as low as possible). What you as a founder should do is set a valuation of your company yourself on the first day you start working on it and then review it with after every major event (e.g. team expansion, demo version created, product launched, first paying customers, etc.)
Here are some ideas how to evaluate an early stage startup:
- Ask yourself: “If an investor would come today and wanted 20% of my business how much would she have to pay me?” Take into account the current stage of the startup.
- Or you could be more scientific about it and calculate it from bottom up. Estimate how much work (in monetary terms) has to be done by your employees before they will stop earning sweat equity and start being paid normal salary (e.g. first investment round). Set a sufficient buffer for unexpected circumstances. Decide what percentage of shares you want to own at the time you will start paying your employees (the rest will be owned by your employees). And now just calculate the valuation as (work to be done + buffer) / % to be owned by employees.
It is important to set the valuation right. You have to be able to justify the valuation in front of your colleagues and investors, if the valuation is too high they won’t work with you. On the other hand if the valuation is too low you might run out of equity for distribution before you reach your goal.
Now, going back to sweat equity – the salary gets converted into the percentage stake in the company by using the valuation of the company at the time the money was earned. I created a simple illustration.

The table shows an employee who worked two days a week (40% of a work week) between July and September, when the company had valuation of $1 million. And jumped on board full time since October when the odds of success increased (which is demonstrated in a higher valuation). Although the employee worked for only two days a week in the first three months she earned a bigger stake (1.2%) than in the second period (0.6%). The monetary value of the sweat equity from the first period copied the increase of the valuation so the $12k worth of sweat equity from the first three months are now worth five times more, i.e. $60k.
what are the benefits?
The key benefit of this method is that founder doesn’t have to give equity away cheaply. By operating with real monetary figures (as opposed to using only percentages) it’s easier for coworkers to see the value of their stake.
This gives the founder higher flexibility to get more people involved which subsequently inreases the likelihood of success of the startup.
There is one more perspective I’d like to mention. This approach sends a strong message to your potential investors. It demonstrates that you really value your equity. In other words, if you’ve just given 30% to a developer for 3 months worth of work, why should an investor pay hundreds of thousands of dollars for 20%?
I really like this approach, it is transparent, easy to understand, it increases the chances of success and reduces chances of internal arguments about shares and allows people to focus on what really matters – getting work done.
what do you think?
Please let me know what you think. Do you see some key aspect I have overlooked? Do you have any ideas how to further improve this? Have you successfully used a different approach? Was the article helpful or at least interesting?