The Equity Question: Should You Give Developers Stock?

What you actually need to know

• Equity is not a discount on your engineering bill. It is a share of the company. Treat it like one.
• A freelancer who asks for equity instead of cash is either deeply committed to your mission or cannot find enough cash clients. You need to know which one.
• The right equity conversation is always about commitment and timeline, not about budget constraints.
• Standard vesting is four years with a one year cliff. Anything shorter than that is a gift to someone who might leave before they have proved themselves.
• Most developers who are genuinely good at their job have enough cash clients that they do not need equity. The ones who push hard for it early deserve a careful read.

The core argument

The equity question sounds simple on the surface. Should the developer get stock? In practice it is three questions in one. How long are they staying. What are they giving up to be here. And what does the company actually need to get done before that equity means anything.

I have seen founders give two percent to a freelancer who built a landing page and a login screen. I have seen founders refuse equity to a developer who worked for eighteen months at thirty percent below market. Both were mistakes. The first confused gratitude with ownership. The second lost a good person who had already proven themselves. Neither conversation started with the right frame.

The right frame is commitment and risk. An employee who signs a four year vesting agreement, takes a salary cut, and bets their career on your company's survival is taking real risk. Equity is the right return for that risk. A contractor who invoices you monthly, works three other clients simultaneously, and has no interest in your long term product direction is not taking that risk. Cash is the right return for that arrangement. The currency should match the commitment.

What makes this harder is that the line between contractor and early employee is blurry on purpose. Some developers start as contractors and end up being the most important person in the company. The clean version of that story is that the equity conversation happens when the relationship changes, not when it starts. You pilot in cash, you confirm fit, and then you have the equity conversation with evidence on the table.

The dangerous version is the founder who offers equity in the first meeting to close the deal. That almost always ends with either a developer who leaves at month eleven and takes nothing, or a developer who stays and owns a meaningful chunk of something they contributed to for only the first six months.

The vesting structures that actually work

Standard four year, one year cliff. This is the default for a reason. One year of real work before anything vests. Then monthly vesting over the next three years. Clean, understood by most lawyers, defensible in any later round conversation. I would not deviate from this without a specific reason.

Early employee accelerator. Some founders add a "double trigger" acceleration clause for key early hires. If the company is acquired and the employee is terminated within twelve months of the acquisition, all remaining shares vest immediately. This is not free. The acquirer will price it into the deal. But for a developer who has been there from the beginning, it is the right protection.

Milestone based vesting. Occasionally used for a very specific scope engagement where the developer is doing critical foundational work but not joining full time. A percentage vests on launch, another percentage on hitting a retention metric, and so on. This is harder to administer and requires a lawyer to set up correctly, but it aligns the equity with the actual value delivered.

The cliff only structure. Some very early founders give a small grant with a two year cliff and no monthly vesting after that. Not standard. Not recommended unless the relationship is genuinely ambiguous. The problem is that anyone who hits the cliff and vests the whole grant on day seven hundred and thirty has less incentive to stay on day seven hundred and thirty one.

When to say no to the equity ask entirely

A contractor who asks for equity instead of cash on a three month project is telling you something. It might be that they believe in the company and want skin in the game. It might be that they have cash flow pressure and equity feels like a way to defer the conversation. The way to find out is to offer to pay them in full in cash and see if the equity ask disappears. If it does, you have the answer.

The other case to decline is when the developer has the wrong kind of interest. They want equity because they want to influence product direction without doing the daily work. That is a board seat, not an option grant, and it is a conversation that should happen at the cofounder level or not at all.

What it requires

The legal setup is not optional. Issuing equity without the right structure creates tax exposure for the developer and cap table problems for the company. The cost of doing it right at the start is small compared to the cost of cleaning it up before a Series A.

What to look for before making an equity offer

• A developer who has already turned down another offer to work with you. Commitment shows before the conversation.
• Clear evidence they can carry the technical direction without supervision. Equity partners need to make good decisions on their own.
• A willingness to talk honestly about the company's risk. Someone who expects equity to be worth something soon has misread your stage.
• At least three months of working relationship before the equity conversation. Trial periods reveal more than interviews.
• An understanding of dilution. If they do not know what happens to their two percent in a Series A, they need to understand that before signing.

Expert opinion

The founders who give equity too early almost always do it to close a deal they were not sure they could close on merit. The founders who give equity at the right time do it because the developer has already proved they are irreplaceable. The second version almost never requires a hard conversation. Everyone knows what they are agreeing to.

>

Yashveer Singh, founder of Yashveer Labs

How this played out on a real project

One of my clients came to me six months into a working relationship with a developer who had pushed hard for equity at the start. The founder, not wanting to lose the hire, gave one and a half percent with no cliff. The developer shipped for four months, then started missing deadlines, then quietly reduced hours. By month six, they were doing two days of work a week and still holding the equity. There was no legal way to claw it back.

The fix was a long and uncomfortable conversation about redefining the arrangement. We restructured the relationship as a contractor agreement, moved the equity into a new grant with a proper cliff, and the developer agreed because the alternative was walking away from something. That conversation cost three weeks and a lawyer's bill. The original equity offer cost the company a point and a half of cap table with no real work to show for it.

The lesson I gave that founder afterward: the equity conversation is a trust test as much as a compensation decision. If you are giving equity because you are afraid someone will leave, they probably will. If you are giving it because they have already proven they are in it for the long run, then the vetting framework for real experience has already done its job. The related conversation about early team structure is in the two person team post, which covers who to hire first and what commitment should look like.

Common mistakes founders make with developer equity

1. Offering equity in the first meeting to close the deal. The signal you are sending is that you are not confident the cash offer is competitive.
2. Skipping the cliff because it feels harsh. The cliff is not punishment. It is the minimum bar for proving that someone is in the relationship.
3. Not modeling dilution before the grant. One percent at seed is roughly half a percent after a Series A. Know what you are actually giving.
4. Issuing equity without a 409A valuation. This creates immediate tax exposure for the developer and is a red flag in any due diligence.
5. Giving equity to contractors who will not be around for the journey. They will hold a slice of your cap table with no ongoing accountability.
6. Treating equity as a salary substitute for a role that should be salaried. If you cannot pay a fair salary, the company may not be ready to hire full time.
7. Not including a double trigger acceleration clause for key early hires. It protects the people who built the thing if the thing gets acquired.
8. Letting the equity conversation drift without a specific vesting agreement signed. A verbal equity promise is worth less than you think and more complicated than you want.

A 90 day plan

1. Week one. Get the legal structure right. If you do not have a Delaware C-corp and an option pool, talk to a startup lawyer this week. The cap table cleanup later is expensive.
2. Week two to four. Run a proper trial with any developer you are considering for equity. Four weeks of real work. Pay them in full in cash. Observe the commitment and the communication.
3. Month two. If the trial was clean and the developer is clearly staying, have the equity conversation with numbers on the table. Show them the cap table. Explain dilution. Give them time to review with their own counsel.
4. Month three. Sign the vesting agreement with a four year cliff structure. Get board approval. Send the grant notice. And then return to the actual work, which is what will make the equity worth something.

For the hiring decisions that come before the equity conversation, the 10 questions every non technical founder must ask before hiring covers the interview and trial structure. For the cost side of early hiring decisions, why cheap developers cost the most long term covers the math on what the wrong hire actually costs.