Every JDA is the same trade wearing different clothes: land now, in exchange for a slice of what gets built on it later. The clothes matter enormously though, because the two standard structures, area sharing and revenue sharing, distribute risk in opposite directions, and landowners routinely pick by convention what they should pick by diligence. Deshmukh's JV decision, the one this series keeps returning to, is really this article.
Key takeaways
- Area sharing: the owner receives finished units (a fixed share of built area) and sells them independently; revenue sharing: the owner receives a percentage of sale proceeds as they realise.
- Landowner shares commonly negotiate in the 25 to 50 percent band, moving with location value, funding contributions and who carries approvals.
- Area sharing transfers market risk to the owner but caps developer-conduct risk; revenue sharing does the reverse, making monitoring ability the real deciding variable.
- Under MahaRERA, the project registers regardless, and revenue-sharing owners sit inside the Master Account and disclosure machinery, use that visibility.
The two structures, side by side
| Dimension | Area sharing | Revenue sharing |
|---|---|---|
| What the owner receives | Specified finished units or built-up area | A percentage of sale realisations |
| Market risk (price, velocity) | Owner's, for their share | Shared through the split |
| Developer-conduct risk | Lower: units exist or they do not | Higher: depends on pricing, discounting and honest reporting |
| Owner's cash flow | Lumpy, after completion | Progressive, as sales realise |
| Monitoring burden | Construction quality and timelines | Everything: pricing, collections, accounts |
| Exit flexibility | Sell own units at will | Locked to the project's sales cycle |
The negotiated split moves within a wide band, 25 to 50 percent to the landowner is the commonly cited range, driven by land value relative to project cost, who funds approvals, and the market's heat. But the split's number matters less than most owners think, and the structure's fit matters more: 45 percent of revenue reported by a developer you cannot audit can be worth less than 35 percent of area you hold in your own name.
An analogy: rent the orchard or share the harvest
A farmer leasing an orchard can take a fixed number of trees' fruit (area) or a share of the crop's sale (revenue). The tree-share farmer worries about one thing: that the trees exist and fruit. The crop-share farmer worries about everything the orchardist does: when they harvest, what price they accept, whose cousin buys at a discount, and whether the ledger is honest. Neither deal is wrong; they demand different relationships. Choose the structure that matches how well you can watch the orchardist, not the one whose headline number flatters.
The diligence that decides it
- Read the developer's register record first. Delivery history, extension habits, complaint patterns, filing discipline: the full counterparty read. A revenue share with a promoter whose filings wander is a loan with extra steps. The six-check version, including why 86 percent of promoter profiles carry no delivery record under the entity that would sign with you, is in a landowner's diligence on a developer.
- For revenue sharing, wire yourself into the machinery. The Master Account structure exists precisely for multi-promoter revenue splits: your percentage should live in the bank mandate, not just the agreement, and the project's QPR booking disclosures become your independent sales audit, read them quarterly.
- For area sharing, specify like a buyer. Your units identified by number, specifications annexed, delivery timelines with the same interest machinery an allottee gets, because at handover you are one, and the model agreement's protections are the benchmark to negotiate against.
- Cover the failure modes in the document. Developer insolvency, registration lapse, stalled construction: who can step in, who controls the land's reversion, and how the project's TDR or FSI entitlements are shared if plans change.
- Price the tax and stamp events before signing. The JDA's execution, the owner's share transfer and the eventual sales each trigger their own tax and stamp duty consequences, the subject of its own guide, and structures that look identical pre-tax diverge sharply after.
The commonest landowner injury is not a bad split; it is a good split with no monitoring rights. Whatever the structure, the agreement should give you: quarterly statements reconciled to the RERA filings, audit rights on the collection accounts, consent rights on pricing below an agreed floor (revenue deals), and step-in or termination triggers keyed to objective register events like lapse or extension.
Deshmukh's fork, resolved
Deshmukh (illustrative, as ever) took both offers seriously: 42 percent revenue share from a large Pune developer, or 33 percent area share from a mid-size Nashik builder with a shorter but spotless register record. His monitoring reality decided it: living in Nashik, minding other business, with no appetite for auditing a Pune sales office's discounting, he took the area share, negotiated allottee-grade protections on his units, and keeps a calendar reminder for the project's quarterly filings. The 9 percent he "gave up" bought him a deal he can actually supervise.
ReraGenie's Rs 2,999 project analysis is built for exactly his first step: the complete register record of any Maharashtra developer, delivery, discipline, disputes, before your land meets their letterhead.
The one-line summary
Area sharing sells certainty and buys market risk; revenue sharing sells participation and buys monitoring burden: read the developer's filings first, wire your rights into the accounts and the register's machinery, and pick the structure your supervision can actually enforce.
Evaluating a micro-market or a land parcel?
The ReraGenie project analysis reads the filings around your parcel: supply, absorption and promoter records. Rs 2,999 per project; the area market report is a flat Rs 2,999 per pincode.
See the project analysis