What founders get wrong when asking a developer to work for equity

A founder reached out recently. He had an AI platform concept, a domain expert as a design partner, early partnerships with major infrastructure providers, and a frontend built with a no-code tool. He needed 16 to 20 hours a week of backend work — API connectors, AI agents, a graph database, data pipelines. The offer was equity only, with salary to follow once the funding came in.

I'm a developer. I've been building software since 2000, shipped more than 30 products across my career, and I'm currently running my own pre-revenue startup while living off savings. I know both sides of this conversation.

The ask didn't work. Not because the idea was weak. It wasn't. Not because the equity offer was dishonest. It wasn't. It didn't work because 16 hours a week is not a side commitment — it is a second job — and the company had no backend, no users, and no revenue yet.

The math founders don't do out loud

At a conservative market rate of $50 an hour, 16 hours a week is $3,200 a month in unpaid work. Over six months, that's $19,200. For equity in a company that exists as a design mockup and some partnerships.

The frontend in this case was built with a no-code tool. That's fine as a prototype — it's a fast way to show what a product could look like. But it means the developer isn't joining to help finish something. They're joining to build the entire product.

For an AI-powered platform, the interface is barely 1% of what makes it work. The other 99% is everything a demo never shows:

• The AI layer — agents, prompt orchestration, retrieval, plus the evals and guardrails that keep them from producing garbage.
• The data — a graph database, ingestion pipelines, and the connectors that feed them.
• The integrations — turning those infrastructure partnerships into something that actually returns data in production.
• The plumbing — auth, billing, error handling, deployment, monitoring.

That's where the product actually lives. The mock UI is the most finished thing in the whole project.

So the honest version of the offer was: "I have a concept and a design. Help me build the real thing, 16 hours a week, and you'll get equity in something that doesn't exist yet."

That's not inherently a bad deal. But it's a very bad deal if the developer has no other income.

Equity is a bet, not deferred salary

Founders sometimes talk about equity as fair compensation, just paid later. It isn't. Equity is a bet on a future event — funding, acquisition, revenue — that may never happen.

When a developer takes equity instead of pay, they're making the same bet as an investor, except with their time and their bills. Investors spread that risk across dozens of companies. A developer going all-in on one pre-revenue startup has no diversification.

For the bet to be rational, a few things need to be true:

• The time commitment is part-time in practice. Five to eight hours a week on an interesting problem, alongside other income, is a different decision than 16 to 20 hours as your primary work. The second number describes a job, not an investment.
• The founder has real financial skin in the game. Not just time — money. If the founder is paying rent from savings and has turned down other work to pursue this, they've already made a real sacrifice. That changes the dynamic considerably.
• There is a specific near-term path to value. "We'll raise money and pay you then" is not a path. A design partner ready to pay for the pilot, a grant application under review, a signed letter of intent from a customer — those are paths. A general plan to raise funding someday is not.
• The equity percentage makes the numbers work. A 2% stake in a $5M exit is $100K — which sounds generous next to $19,200 of unpaid work, until you weight it for risk.

Weight it, then. A $5M exit is a good outcome, and good outcomes are rare — most startups return nothing. Put the odds of reaching it at a generous 10%, and that 2% stake is worth about $10,000 in expectation: roughly half the $19,200 of certain, unpaid work it's meant to offset.

And 2% rarely stays 2%. Every funding round dilutes early equity. After a seed and a Series A, that stake is often closer to 1% — or less — by the time any exit actually happens. The expected value is lower still.

None of these were fully in place in the conversation I described. The founder wasn't being dishonest — he just hadn't looked at the offer from the other side of the table.

A no-code prototype is not an MVP

It looks like a product. It is a design mockup with a working interface — and behind it, nothing that makes software run.

There's a specific pattern that's become more common with tools like Lovable, Bolt, and similar no-code builders: a founder builds a frontend, calls it an MVP, and uses it as evidence the product is "already built."

Here's what's missing behind that interface:

• No database.
• No authentication.
• No API connections.
• No error handling.
• No deployment pipeline.

Nothing that makes software actually run in production under real load. It answers "does this look like it could work?" — not "does this work?"

When a founder says "I just need someone to handle the backend," that sentence almost always describes building the entire product from scratch. The frontend is the smallest part. Saying "I have an MVP and need help deploying it" is a very different project description than "I have a design and need a developer to build the product."

This matters because the equity ask changes depending on how much of the product actually exists. Asking someone to join to help scale something that's working is a reasonable equity pitch. Asking someone to build the whole thing for equity alone is asking them to co-found the company — and the terms should reflect that.

What actually works

A small retainer. The most common fix I've seen, and not at market rate — something modest, $2K to $3K a month. It doesn't cover the full cost of a senior developer's time. But it signals that the founder treats the arrangement as a real commitment, not a hope.

A token amount of money changes the relationship. Without it, every late night and missed weekend starts to feel like exploitation, regardless of anyone's intentions. With even a small retainer, both sides have something at stake. There's a structure. The developer can plan around it.

A scoped pilot. The other option is to match the ask to what's actually possible right now. Instead of 16 hours a week across six months, ask for a defined pilot scope. Four to six weeks, a specific deliverable, a real potential customer waiting to see it. If the pilot works, revisit terms with actual evidence to negotiate from. If it doesn't, both sides learned something without anyone burning five months of unpaid work.

The founders who get this right tend to look similar. One came to me with a signed pilot customer, offered a modest monthly retainer against a four-week milestone, and left equity on the table for after the pilot proved out. The work was bounded, the money was real, and the equity became a bonus on a relationship that had already shown it could ship — not the whole bet, paid up front.

I told the founder I couldn't take on the full commitment at equity only. I'm bootstrapped, pre-revenue, and living off savings — the same position he's in. I need my time commitments to cover costs, at least at a basic level.

What I didn't say explicitly: the ask would work with a different structure. A small retainer plus equity. A smaller scope with clear milestones. A signed pilot customer before any work starts. Any of those would have changed the calculation.

Most developers who decline equity offers aren't saying they don't believe in the idea. They're saying the structure doesn't let them survive long enough to find out if it works.