I get asked this question so often that I could hang the answer on the office door. Someone comes with an idea, there is no money for development, and they ask where to find a programmer who will build the product "for equity" or "for the idea". Sometimes they ask hopefully, sometimes with a slight challenge, as if checking whether I will say it is impossible. I will not. It is possible. But the answer begins with an unpleasant truth: free developers do not exist. There are developers who are paid in something other than money. And if you do not understand what exactly you are paying with, you will find nobody, and if you do find someone, you will lose them within two months.
The pirate contract
Pirates of the seventeenth and eighteenth centuries had a surprisingly democratic system that few people know about. Before a voyage the crew signed an agreement, the so-called articles: who gets which share of the plunder, how much is due for losing an arm or a leg, how the captain is elected and removed. Sailors went on a dangerous voyage without wages, but not for free. They knew their share exactly, the rules were written down, and a captain who broke them risked ending up overboard. This is exactly what a healthy "work for equity" model in a startup looks like. It is not a request for a favour but an honest agreement between people who set out together for treasure that does not exist yet.
Now look at what the offer usually sounds like: "I have a brilliant idea, build me the whole product and I will give you five percent." Translated into pirate: a captain with no ship and no map asks a carpenter to build the ship single-handedly for a handful of coins from future treasure. No wonder carpenters say no.
What people are really paid with
I see four currencies you can pay a developer with when there is no money. Usually a combination of them works.
- Real equity. Not symbolic but a partner's share. If a person builds the product without which there is no project, they are not a hired hand but a co-founder, and the share should reflect that. With vesting, meaning the share is earned gradually over time worked, so both sides are protected.
- Meaning. Projects that solve an important problem, in medicine, ecology, education, attract people willing to work for the result. Open source has lived on this currency for decades.
- Growth. The chance to try a new technology, to take on an architect's role that a salaried job would only offer five years later, to build a portfolio. For strong young developers this is real value.
- Your contribution. This is the currency people forget most often. If you come not with an idea but with your first customers, with an agreed pilot, with market research, you pay by reducing risk. The developer sees that their work will not vanish into the void.
An idea without execution is worth about as much as a lottery ticket before the draw. A developer understands this perfectly well, even if they politely say nothing.
Where to look
The best partners are almost never found through job ads. They are found in environments where people have already seen each other at work. Former colleagues you went through difficult projects with. Hackathons, where a single weekend shows who can see things through. Communities around technologies and open source projects, where a person has been showing the quality of their work in public for years. Industry conferences and meetups. All these places have one thing in common: you can see a person in action before tying the fate of your project to them. It is like the army: trust goes not to the one who speaks well on the parade ground but to the one you have already shared a trench with.
Why "free" projects fall apart
Even if you have found an enthusiast, the main danger is still ahead: work without money has no deadlines. The person has a day job, a family, fatigue. For the first two weeks the enthusiasm burns, then a quarterly report hits at the day job, then the child gets sick, and two months later the project has stalled. Nobody is to blame, unpaid work simply has the lowest priority in anyone's life. I have seen dozens of such projects slowly dissolve in chats without a single conflict: the messages just became rarer and rarer.
What to do about it. First, write the agreements down, like the pirates did: who does what, what the share is, what happens if someone leaves. Second, cut the scope to the minimum so the first version can be finished before the enthusiasm cools. A huge product cannot be built on enthusiasm, a small one can. Third, work at least as hard as your partner. Nothing kills a developer's motivation faster than a founder who "generates ideas" while others write code at night.
An alternative worth considering
Sometimes it is more honest not to look for a free developer but to bring the cost of the first version down far enough that you can pay for it. Today this is more achievable than ever. At Ingello we use Fractal to build working prototypes in days, because the system is described rather than typed by hand. A small prototype budget often costs less than six months of persuading people and a project that never gets finished. And with a working prototype and first users, both the conversation with an investor and the offer to a strong developer to become a partner look completely different. You are no longer a captain without a ship, you already have a boat that floats.
What to do tomorrow: write on a single page what you personally bring to the project besides the idea. If the list is short, start by making it longer: find your first customers, run interviews, put together a prototype. After that, looking for a partner stops being a request and becomes an offer.
