Benchmark data licence
The derived tables, in your own systems
230 communities and 676 developers with medians AND the full quartile columns as one clean table rather than 906 separate pages, the 2,924 off-plan project index with exact coordinates we publish nowhere else, 3,315 payment plans decomposed stage by stage, and the handover pipeline by quarter. Joinable on stable ids, refreshed with every build, delivered as CSV and JSON.
Built for agencies with a CRM, portals that want a benchmark badge, and analysts who would rather not scrape. If you need a live endpoint instead of files, say so at checkout or by email and we switch you to it.
What is in the bundle
| Table | What it holds | Grain |
|---|---|---|
| communities.csv / .json | Median, p25, p75 AED per sqft, median price, project and unit counts, payment plan medians, pipeline by year, per bedroom breakdown | one row per community, 230 rows |
| developers.csv / .json | Same measures per developer plus the communities they build in and their share of the Dubai pipeline | one row per developer, 676 rows |
| projects.csv / .json | Project index with developer, community, city, exact coordinates (published nowhere else, the free pages carry none), delivery quarter, sale and construction status, starting price, price range, median AED per sqft, unit and plan counts | one row per off-plan project, 2,924 rows, plus 1,087 delivered comparables flagged as such |
| payment-plans.csv | Every published plan decomposed into booking, construction, handover and post-handover shares, with pre-handover total and step count | one row per plan, 3,315 rows |
| pipeline.csv | Projects and priced units by delivery quarter and community, 2020 through 2032 | quarter by community |
| bedroom-benchmarks.csv | Median AED per sqft, price and size per bedroom count, per community and per developer | community or developer by bedroom |
Sources read to 30 July 2026, corpus merged 18 August 2026, tables built 2 September 2026. Every figure traces to a query over developer-published inventory; the method is public at /methodology, what we will never ship is at /data-policy, and what you may do with the tables is at /licence.
How often it moves. Builds are dated, not scheduled. This one was assembled from sources read to 30 July 2026 and computed on 2 September 2026. A listings watcher reads new launches continuously and the newest of them was read on 1 September 2026, but a handful of fresh records is not allowed to move the “as of” date of everything around them. We do not promise a fixed refresh interval, because the build is run by a person and a promise nobody schedules is not a promise. Instead the licence carries the term below: a calendar month with no newly dated bundle is credited on request.
The first rows, before you ask for them
slug,name,city,n_projects,n_units,psf_median,psf_p25,psf_p75,price_median,pre_handover_median
al-safa,Al Safa,Dubai,4,29,5398,5242,5532,25878000,60.0
sheikh-zayed-road,Sheikh Zayed Road,Dubai,11,138,3691,1881,6929,4585472,50.0
world-of-islands,World of Islands,Dubai,10,68,3000,2800,4506,3389304,80.0
jumeirah,Jumeirah,Dubai,32,227,2738,2199,4465,5643000,60.0
saadiyat-island,Saadiyat Island,Abu Dhabi,49,336,2440,1816,3645,4218820,65.0The head of OffplanIndex-sample-communities.csv, printed from the same sample file linked below. The licensed table has the same columns and every community row, not a slice. An engineer can load it before anyone in your firm has to approve a card.
Sample files
Four sampled CSVs so your team can test the schema before subscribing: rows are taken evenly across each table, so they span the ranking rather than the top of it. Same columns as the licensed bundle, a fraction of the rows.
Why you can check us instead of trusting us
We have no customers to quote, and we are not going to invent one.
This is a new product. There is no logo wall here, no “trusted by” strip and no testimonial, because there is nothing true to put in one yet. What follows is the argument we would rather you judged us on anyway: you can check the numbers instead of trusting them.
Load the schema before you pay for it.
The sample files on this page carry the licensed columns, so the shape is testable in ten minutes.
Most of the corpus is already published, free, on this site.
168 community pages and 391 developer pages are built from the same tables the paid products ship. Pick a community you know well and check the median against your own comparables before you spend anything.
Every figure states the base it was computed on.
A median taken over thirty records and a median taken over three thousand are not the same claim, so the count sits next to the number rather than being left out of it. A thin sample is visible instead of hidden, and anything under the evidence floor is not ranked at all.
The method is written down, including what is wrong with it.
Methodology names the validation bands, the exclusions and the known gaps. The data policy names what we will never publish and why. Both were written to be argued with.
The corpus is countable, and its dates are on the page.
4,011 records across 230 communities and 676 developers, of which 52,882 priced unit records clear every plausibility check and are allowed inside a published benchmark. Sources read to 30 July 2026, merged 18 August 2026, built 2 September 2026.
What you are risking
- The schema is testable before the first charge. The sample files on this page are the licensed columns on a slice of the rows, taken evenly across each table rather than off the top of it.
- First month refunded in full, for 14 days. If the bundle does not match the published schema, or the tables are materially not as described here.
- A month with no new build is credited if you ask for it. The data build is run by hand, so we do not promise a fixed refresh interval. Instead: if a calendar month passes and no newly dated bundle appeared, tell us and we credit that month. Every bundle carries its three dates, so this is checkable from your side rather than ours.
- Cancel any month. Access to new bundles ends at the end of the paid month. What you may keep doing with bundles you already hold is written down on the licence page, in full, for the person in your firm who has to read it.
- Who answers. One person reads hello@offplanindex.com and answers within one business day. There is no ticket system and no queue.
The same terms in legal form are on the terms page, and the licence itself is at /licence. If the two ever disagree, the more generous one applies.
Questions
What exactly do we receive?
The six derived tables listed on this page as CSV and JSON, delivered as a dated bundle you download the moment checkout completes, from a receipt page that serves the newest build there is. The bundle currently served is the 2026-08 build. An HTTPS endpoint returning the same JSON is available on request at no extra cost.
How often is it refreshed?
Builds are dated, not scheduled. The corpus is rebuilt by a person rather than by a cron job, so we will not claim a fixed interval we have nothing to enforce. Every bundle carries the date its sources were read, the date the corpus was merged and the date the tables were computed, so you can always see what you are holding. If a calendar month passes with no newly dated bundle, tell us and we credit that month.
Is this a copy of a portal database?
No. Every table is an aggregate or a project-level fact table computed by us. There are no listing records, no descriptions, no images and no portal URLs in the bundle. See the data policy.
Can we publish the numbers?
Use inside your organisation and inside your own products is included, with attribution. Redistributing or reselling the tables as data is not, and neither is serving them row by row through your interface until someone outside your organisation holds the table. The full terms, including what survives cancellation, are on the licence page.
What if the data is not what we need?
Check before you pay: the sample files on this page have the same columns as the licensed tables, so your engineer can load them and see the shape in ten minutes. If you subscribe and the delivered bundle does not match that schema, or the tables are materially not what this page describes, write to hello@offplanindex.com within 14 days of the first charge and we refund that month in full. After the first month, cancel any time from the billing portal: access to new bundles stops at the end of the paid month, and the licence to use bundles you already hold is set out on the licence page rather than being left to a sentence in an FAQ.
How do we cancel?
Any time from the Stripe billing portal link on your receipt. Access to new bundles ends at the end of the paid month. What you may keep doing with bundles you already hold is clause 8 of the licence.
Only need the numbers once? The Q3 2026 report ships the same tables as a one-off CSV bundle with the PDF, 79 USD. The full terms for the licence are at /licence.