The Pitch We Hear Every Week
"We don't have much budget right now, but we'd love to offer you equity in exchange for building the app."
We hear some version of this at least once a week. And we get it. You're a founder with a great idea, limited capital, and a genuine belief that this thing is going to be huge. Offering equity feels like a win-win: the developer gets a piece of the upside, and you preserve your cash for marketing and operations.
Here's the reality: pure equity deals almost never work out for either side. We've been building apps since 2012, and we can count on one hand the number of equity-only arrangements we've seen end well. But that doesn't mean equity should be off the table entirely. The key is understanding when it makes sense, when it doesn't, and how to structure it if you go that route.
Why Pure Equity Deals Fail
The Math Problem
Let's run real numbers. Say you're offering a developer 10% equity to build your app. For that to be worth their time, your company needs to eventually be worth enough to make that 10% meaningful.
A typical app build costs $40,000-$80,000 in cash. So the developer is effectively investing $40K-$80K of their time. For that investment to return even 3x (a modest target), the company needs to reach a valuation where their 10% stake is worth $120K-$240K. That means a company valuation of $1.2M-$2.4M.
Sounds achievable, right? Except:
- 90% of startups fail. That 10% equity has a 90% chance of being worth exactly zero.
- Dilution happens. By the time you raise a Series A, that 10% is probably 4-6%. By Series B, it's 2-3%.
- Liquidity takes years. Even if the company succeeds, the developer can't sell that equity for 5-10 years. There's no market for shares in a pre-revenue startup.
For the developer, this is a terrible risk-adjusted return. They could spend those same 3-4 months building for paying clients at $150-$250/hour and guarantee $60K-$100K in income.
The Alignment Problem
Equity implies partnership, but the developer's incentives and the founder's incentives aren't actually aligned.
The founder wants to move fast, iterate based on user feedback, and potentially pivot. The developer-turned-equity-holder wants to minimize their time investment (since they're not being paid) and may resist changes that extend the timeline. This creates friction that cash-paid relationships simply don't have.
We've seen this play out dozens of times: the developer does the initial build, the founder wants revisions, the developer says "that wasn't in the original scope," and now you have a partner dispute instead of a client-vendor conversation.
The Legal Problem
Equity arrangements require proper legal documentation. You need:
- A vesting agreement (typically 4-year vest with a 1-year cliff)
- Clear IP assignment language that transfers code ownership to the company
- A shareholder agreement defining rights, responsibilities, and exit provisions
- Potentially an 83(b) election filing with the IRS within 30 days
This legal work costs $3,000-$8,000. If you're trying to avoid spending cash, you've already undercut the premise.
When Equity Actually Makes Sense
Despite all of the above, there are situations where equity in a developer arrangement works:
1. You Have a Technical Co-Founder, Not a Contractor
If someone is joining as a true co-founder — making strategic decisions, attending investor meetings, working full-time on the product — equity is appropriate. But this is a co-founder relationship, not a vendor relationship. They should get 15-40% equity with standard vesting, and they should be involved in the business well beyond writing code.
2. You're Doing a Hybrid Deal
The arrangement that actually works is cash plus a small equity kicker. The developer gets paid a reduced (but still meaningful) cash rate, and receives a small equity stake as upside.
A typical structure:
- Cash: 50-70% of the developer's normal rate
- Equity: 1-5%, vesting over 2-4 years with a cliff
- Milestone-based: Equity vesting tied to product milestones, not just time
This works because the developer isn't bearing all the risk, you're still preserving some cash, and the equity stake is small enough that dilution doesn't feel punitive.
3. You've Already Proven Traction
If you have paying customers, meaningful revenue, or a signed term sheet from investors, equity has tangible value. A developer can look at your $20K/month in recurring revenue and make a reasonable assessment of what 2% equity might be worth. That's a fundamentally different conversation than "we have an idea and a pitch deck."
How to Structure a Hybrid Deal That Works
If you're going the hybrid route, here's the framework we recommend:
Phase 1: MVP (Cash-Heavy)
- Pay 60-75% of normal development rates in cash
- Offer 1-3% equity with a 1-year cliff
- Define clear deliverables and a fixed timeline
- All IP transfers to the company regardless of equity outcome
Phase 2: Post-Launch (Performance-Based)
- Additional equity (0.5-1%) tied to specific metrics: user growth, revenue milestones, uptime targets
- Cash rate adjusts based on funding status
- Quarterly vesting after the cliff period
Phase 3: Scale (Market-Rate Transition)
- Once funded, transition to market-rate cash compensation
- Existing equity continues to vest
- Relationship shifts from partner to vendor or employee
Non-Negotiable Terms
Regardless of the equity structure, these provisions must be in the agreement:
- IP assignment: The company owns all code, period. Equity or no equity, the code belongs to the business.
- Vesting with cliff: Standard 4-year vest, 1-year cliff. If the developer walks after 3 months, they don't keep equity.
- Buyback rights: The company should have the right to repurchase unvested (and sometimes vested) shares at fair market value if the relationship ends.
- Anti-dilution clarity: Be transparent about expected dilution from future funding rounds.
What We Tell Founders Who Ask
When a founder asks us to work for equity, here's our honest response:
We don't do pure equity deals. Our team has salaries, health insurance, and rent. We can't pay those with shares in a pre-revenue startup.
But we do work with founders who have limited budgets. Options include:
- Phased development: Build the MVP for $15K-$25K in cash, prove traction, then fund the next phase with revenue or investment
- Reduced scope: Strip the feature set down to what you can afford to build properly with cash
- Deferred payment: In select cases, we'll defer a portion of our fee until a funding milestone, with a premium for the risk
The founders who succeed aren't the ones who find a developer willing to work for free. They're the ones who figure out how to fund even a small cash engagement and use that first build to generate the traction that attracts real investment.
The Bottom Line
Equity is a tool, not a substitute for cash. Used correctly in a hybrid structure with proper legal agreements, it can align incentives and stretch a tight budget. Used as a replacement for payment, it almost always creates misaligned expectations, legal complications, and a product that never ships.
If you can't afford to pay anything for development, you're not ready to build yet. Focus on validating your idea with no-code tools, building an audience, or raising a small pre-seed round. The app can wait. Getting the financial foundation right can't.