Every non-technical founder eventually asks the same question: should I pay a developer in cash, equity, or some mix of both? The honest answer is that it depends on what role they’re playing — a true technical co-founder, an early hire, an advisor, or a contractor building your MVP — and how much risk they’re actually taking on alongside you.
Table of Contents
This guide breaks down realistic equity and cash ranges for each scenario, how vesting protects both sides, and the mistakes founders make most often when they try to pay in “exposure” instead of real compensation.
Quick Answer
A true technical co-founder joining at the idea stage typically gets somewhere in the range of 15% to 50% equity (often split close to evenly with the business co-founder), vested over time. An early technical hire who isn’t a co-founder usually falls in the 1% to 10% range, while a part-time technical advisor typically gets a much smaller slice, often well under 1%. A freelance developer or agency building your app should almost always be paid in cash — if they take any equity at all, it should be a small bonus on top of a fair hourly or project rate, not a replacement for pay.
How Much Equity Makes Sense, by Role
The right number depends heavily on what stage you’re at and what the person is actually risking. A developer joining pre-revenue, pre-funding, with nothing but your idea and a handshake is taking on far more risk than one joining after you’ve already got paying customers — so the earlier and riskier the join, the more equity is justified.
True technical co-founder (joining at idea stage, no product yet): this person is effectively building the company’s core product from scratch and should be treated like a founder, not an employee. Splits here commonly land close to even between the business and technical sides, adjusted for who came up with the idea, who’s putting in more hours, and who has prior relevant experience.
Technical co-founder joining with some traction (a working MVP, a few pilot customers, early investor interest): because the risk is already partially de-risked, equity offers in the roughly 15% to 35% range are more typical, scaled to how real that traction actually is.
Founding engineer or early technical hire (not a co-founder, but one of the first few people in): offers commonly fall between about 1% and 10%, decreasing as the company matures, raises funding, and hires more people. A developer joining right after a seed round will expect less equity than one joining pre-seed with nothing built yet.
Technical advisor (someone giving periodic guidance, code review, or architecture input, not building day-to-day): grants here are much smaller than for co-founders or hires, often well under 1%, scaled to how engaged and senior the advisor is.
Freelancer or agency building a one-off app or MVP: this is a service relationship, not a partnership. Cash is the default. If you genuinely can’t afford to pay market rate, a hybrid of discounted cash plus a small equity stake (sometimes calculated by taking their normal rate, the hours worked, and your startup’s current valuation to back into a fair percentage) can work — but expect most experienced developers to decline equity-only deals, since most ideas never turn equity into real money.
Vesting, Cliffs, and Protecting Both Sides
Never hand over equity all at once, no matter how much you trust the person. For co-founders and early employees, the near-universal standard is a four-year vesting schedule with a one-year cliff: no equity vests at all until the person has been involved for a full year, at which point 25% vests immediately, with the rest vesting monthly over the remaining three years.
Advisors are treated differently, since an advisory relationship is lighter-touch and often doesn’t stay useful as long as a full-time role. The common structure for advisors (formalized in the widely used Founder/Advisor Standard Template) is a shorter two-year vesting period with just a three-month cliff — the advisor vests nothing if the relationship ends in the first three months, then vests monthly over the remaining time.
This protects you if the relationship doesn’t work out early (someone who leaves right away walks away with little or nothing), and it protects the other side by guaranteeing their stake accrues steadily and isn’t subject to being revoked on a founder’s whim. Put this in writing from day one, even with a friend or someone you trust completely — handshake equity deals are one of the most common sources of founder disputes down the road.
If you’re offering cash alongside equity — say, a reduced hourly rate plus a stake — put both halves of the deal in the same written agreement: the rate, the payment schedule, the equity percentage, the vesting schedule, and what happens to unvested equity if either side walks away. A short contract drafted with a lawyer or a solid template is far cheaper than the alternative.
Tips and Common Mistakes
Don’t offer equity instead of cash to someone doing contract work just because you’re short on money — most skilled developers have seen too many ideas go nowhere and will discount their rate for a real company at most, not work for free on a promise. If you truly can’t afford to pay, be upfront about that and look for a genuine co-founder relationship instead of dressing up unpaid work as a job offer.
Don’t offer a flat dollar amount of equity (“$10,000 worth of equity”) on a company with no real valuation yet — equity should be expressed as a percentage, since a pre-revenue startup’s “value” is mostly guesswork and a dollar figure can mislead both sides.
Don’t use a co-founder-style four-year vesting schedule for an advisor, and don’t skip vesting altogether for anyone, even a close friend or spouse. Matching the vesting structure to the role (longer for people building the company day-to-day, shorter for advisors giving occasional guidance) keeps the deal fair to both sides.
Do reassess equity grants over time. A developer who joined as employee #2 and is still your lead engineer three years later, after multiple funding rounds, may reasonably deserve a refresher grant — equity isn’t a one-time conversation.
Do get everything in writing, including what happens to equity if the company is acquired, if the person is let go, or if the company shuts down. Verbal promises about equity are extremely common and extremely hard to enforce later.
Explore more: more app development guides.
Equity vs. cash for developers FAQs
Should I ever pay a developer in equity only, with no cash?
Only if they’re truly a co-founder sharing in the company’s upside and risk the same way you are. For contract or freelance work, equity-only arrangements are rare and risky for the developer, since most startups never generate a return — expect to pay at least a reduced cash rate.
What’s a fair starting point if I want to offer a hybrid of cash and equity?
A common approach is to pay a reduced hourly or project rate in cash, then calculate an equity percentage based on the developer’s normal rate, the hours they’ll put in, and your company’s current valuation (hours × rate ÷ valuation), so the equity roughly represents what the discount is worth.
How long should a developer’s equity take to fully vest?
For a co-founder or early technical hire, the standard is four years with a one-year cliff, meaning nothing vests until year one (when 25% vests at once), with the rest vesting monthly over the following three years. A technical advisor is different — the common structure is a shorter two-year vesting period with just a three-month cliff, since advisory relationships are lighter-touch and tend not to stay relevant as long as a full-time role.
Does a freelance developer or agency ever take equity?
Occasionally, but it’s the exception, not the norm — most freelancers and agencies are running a business that needs steady cash flow, so equity is more often offered as a small bonus on top of a paid engagement rather than as the main form of payment.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Photo by krakenimages on Unsplash.