How to Structure a Fair Equity-for-Build Deal: Vesting, Cliffs, and Valuation
The mechanics of a fair equity-for-services arrangement, from the valuation basis to vesting schedules to IP and exit terms, so the deal survives contact with reality.
Whether an equity-for-services arrangement succeeds is decided almost entirely by its structure. A good idea with a sloppy structure turns into a dispute the moment either side feels the deal drifted. These are the mechanics that matter, in the order you should settle them.
Anchor the number to something defensible
The percentage should not come out of a negotiation. It should come out of arithmetic. Take the cash value of the work at market rate, divide it by a company valuation you could defend to an investor, and then discount for the risk the partner is carrying by taking equity instead of cash.
That discount is real. A partner accepting equity is taking on the same downside your other stakeholders carry, so the equity should be worth more than the cash it replaces. A number built this way is one both sides can still stand behind in two years. A number pulled from the air is one someone will resent.
Vest on delivery, never grant on day one
Equity should be earned, not handed over at signing. A lump grant on day one turns a build partner into a passive shareholder with no reason to stay for the hard part, which always comes later than anyone plans.
Tie vesting to milestones that map to real progress: a shipped MVP, a working integration, a production launch, a performance target. Milestone vesting rewards the thing you actually want, which is shipped software, rather than mere presence on the calendar.
Use a cliff to protect both sides
A short time-based cliff at the start, commonly a few months, protects everyone against an early bad fit. If the partnership is clearly wrong within the first stretch, no equity has changed hands and both sides walk away clean. If it is working, the cliff passes and milestone vesting takes over. The cliff is not a trust issue. It is a cheap insurance policy that lets both sides commit with less fear.
Write the scope like it is the deal, because it is
The single biggest source of equity-for-services disputes is an ambiguous scope that lets each side remember the arrangement differently. Define what is being built, what "done" means for each milestone, and, critically, what happens when scope expands. Scope expansion is normal and expected. Pretending it will not happen is the error. Agree in advance how new work is valued, whether in additional equity, cash, or a reset of the milestone schedule.
Settle IP, control, and the divorce clause up front
Three questions have to be answered before anyone writes code, while everyone is still optimistic:
- Who owns the IP. The company should own the code outright. The equity is the compensation for building it. Write this down.
- How decisions get made. Equity without a voice breeds resentment; a voice without limits creates gridlock. Define where the partner has input and where they do not.
- What happens if it ends early. How much equity is vested, what happens to the unvested portion, and who keeps what. The time to agree on the divorce is before the wedding.
Keep a cash floor if you can
A blended arrangement, reduced cash plus equity, is usually healthier than pure equity. It keeps the partner's team funded enough to do the work properly and signals that both sides have skin in the near term, not only the eventual exit. Pure equity can quietly starve the very work it is meant to pay for.
An illustrative example
To make the arithmetic concrete, here is an illustrative example, not a quote or a real engagement. Suppose a build is worth roughly 300,000 dollars of senior work at market rate, and the company can defend a 4 million dollar valuation. That work is about 7.5 percent of the company before any risk discount. Because the partner is taking equity risk, both sides agree on 9 percent, vesting over a three-month cliff and then four delivery milestones, with a reduced cash fee covering the team's costs along the way. Your real numbers will differ. The method is what carries over.
Where this fits
Structure only matters once you have decided equity is the right instrument at all. If you are still weighing it, read the equity-for-services playbook and the comparison of equity against a cash retainer and a fractional CTO first. And before you sign anything, pressure-test the partner itself: how to vet an equity build partner covers what to look for.
This is a framework for thinking through structure, not legal or financial advice. Structure any actual arrangement with your own counsel.
Frequently asked questions
How much equity should a software build partner receive?
Anchor it to a defensible number: the cash value of the work divided by a valuation you could justify to an investor, then discounted for the risk the partner is taking. For a meaningful build this usually lands in a single-digit to low-double-digit percentage, always on a vesting schedule rather than a lump grant.
Should equity for services vest over time or on milestones?
Milestones tied to real delivery are usually better than pure time-based vesting for a build partner. Time-based vesting rewards presence; milestone vesting rewards shipping. A common structure blends the two: a short time-based cliff to protect against an early bad fit, then milestone-based vesting for the rest.
Who owns the code in an equity-for-services deal?
The company should own the IP outright, with that ownership written into the agreement before work begins. The equity is the partner's compensation for building it. Leaving IP ownership ambiguous is one of the most common and most damaging mistakes in these arrangements.