Trading equity for software development is one of the most misunderstood arrangements in the startup world. Done well, it aligns a founder’s domain expertise with a development team’s execution capability — and both sides win. Done poorly, it creates resentment, legal disputes, and a product that never ships. The difference comes down to when equity-for-dev makes sense, how much equity is reasonable, and what protections both sides need in the agreement.
This article covers the mechanics: when to offer equity, when to decline it, typical structures that work, and the mistakes that kill these arrangements.
When equity for development makes sense
Equity-for-dev is not a hack to get free development. It is a risk-sharing mechanism that works under specific conditions:
- The founder has what the dev team lacks. Domain expertise, industry relationships, a path to the first 50 customers, or a unique dataset. If the founder brings only “the idea,” equity-for-dev rarely works.
- The idea has a credible path to revenue. Not in five years — in 6–12 months. The development team needs to believe their equity will be worth something within a reasonable timeframe.
- The founder has some cash. Pure equity deals (zero cash) almost never work. The development team has real costs — salaries, infrastructure, tools. Some cash must cover those basics.
- Both sides want a long-term relationship. This is not a transaction; it is a partnership. If either side wants to walk away after v1, use a fee-for-service model instead.
When it does not make sense
Be honest with yourself. Equity-for-dev is the wrong model when:
- You have no traction, no customers, and no distribution plan. Equity in a product nobody uses is worth zero. A development team taking 10% of zero is still zero.
- The development cost is small. If the project costs €5,000–€10,000, pay cash. Equity structures have legal costs (€1,000–€3,000 for a proper agreement) that erode the economics of small projects.
- You are not willing to share decisions. An equity holder has a voice. If you want full control, pay full price.
- The market is unproven. Equity works when there is evidence of demand. If you are still guessing whether anyone wants this product, run a validation process first.
Typical equity structures
Three structures dominate the market:
| Structure | Founder pays | Dev team receives | Best for |
|---|---|---|---|
| Cash + equity | €10,000–€30,000 | 5–15% equity (vesting) | Venture-track startups |
| Cash + revenue share | €5,000–€20,000 | 10–20% of net revenue, capped | Profitable businesses |
| Convertible note | Market-rate cash | Discount on next funding round | Pre-seed startups with investor interest |
Vesting is non-negotiable
Any equity arrangement without vesting is a red flag for both sides. Standard vesting: 4-year schedule with a 1-year cliff. This means:
- If the partnership ends in month 6, no equity has vested. Both sides walk away clean.
- After year 1, 25% vests. The remaining 75% vests monthly or quarterly over years 2–4.
- If the product fails at month 18, the dev team has earned ~37% of their equity allocation — proportional to the time invested.
Revenue share caps
For revenue-share structures, always define a cap. A common formula: the dev team receives X% of net revenue until total payments reach 2–3× the cash-equivalent value of the development work. After the cap, the revenue share ends.
Example: development work valued at €40,000, founder pays €15,000 cash, dev team takes 15% revenue share capped at €75,000 (3× the €25,000 discount). Once the dev team has received €75,000 in revenue share payments, the arrangement ends.
Cap table impact
Before offering equity, understand what it means for your cap table:
- 5–10% to a build partner still leaves room for future investors, employees, and advisors. This is the sweet spot.
- 15–20% is aggressive and may concern future investors who expect founders to retain 60–80% at pre-seed.
- More than 20% is co-founder territory. If the dev team is taking a co-founder-sized stake, they should be acting like co-founders — full commitment, not a side project.
For context on the co-founder path, see technical co-founder vs development partner.
Mistakes founders make
- Offering equity to avoid paying anything. “I have no money but a great idea” is not a pitch — it is a warning sign. Bring at least 30–50% of the project cost in cash.
- No written agreement. Every equity arrangement needs a shareholder agreement drafted by a lawyer. Budget €1,500–€3,000 for this. It is not optional.
- Vague milestones. “Build the app” is not a milestone. Define deliverables, timelines, and what happens if they are missed.
- Ignoring tax implications. Equity grants may trigger tax events depending on your jurisdiction. Consult an accountant before signing.
Mistakes development teams make
- Taking equity without evaluating the founder. The founder’s ability to sell the product matters more than the idea itself. No sales = no revenue = worthless equity.
- Not defining scope limits. Equity does not mean unlimited work. Define the scope of what is covered by the equity arrangement and what triggers additional compensation.
- Skipping due diligence. Before accepting equity, understand the cap table, existing obligations, and any legal encumbrances.
Frequently asked questions
Is equity-for-dev common in Croatia? It is growing but still less common than in the US or UK. Most Croatian dev agencies operate on a fee-for-service basis. A handful, including us, selectively take equity-based arrangements for ideas we believe in.
How do I value the equity I am offering? At pre-revenue stage, equity value is typically based on the development cost. If the work is worth €40,000 and you offer 10% equity, the implied company valuation is €400,000. This is a negotiation — there is no formula that both sides will automatically agree on.
Can I offer equity to a freelancer instead of an agency? You can, but freelancers rarely accept equity because they lack the financial cushion to absorb reduced cash. Agencies with multiple revenue streams are better positioned for equity arrangements.
Related articles
- Build partner vs paying upfront — The broader funding decision for non-technical founders.
- I have an app idea — 5 ways to actually get it built — Where equity fits among all five paths.
- How much does custom software cost in Croatia? — What the full cash cost looks like for comparison.
Considering an equity arrangement?
Book a free 30-minute Discovery call. We will evaluate the idea, discuss the right structure, and tell you honestly whether equity-for-dev makes sense for your situation — or whether paying upfront is the smarter path.
Reach out at [email protected] or via the form on our homepage.