Chapter 01 of 04
The brief
An instant Dubai property valuation that shows its working.
A three-step wizard turns an address into a value range, and every figure on the result names its source and the month it was read. When the evidence is thin, the range visibly widens instead of hiding behind a number nobody measured.
The property portals already answer "what is my flat worth" in seconds, and they answer it as a black box: a figure, sometimes a range, and no way to see what produced it. For an owner that is a guess with a logo on it. For a valuer it is unusable, because the first question a professional asks of any number is where it came from.
The tool started as a page inside the BARNES Dubai innovation portal and was carved out into its own repo, then rebuilt from a plausible demo into something a valuer could read closely. The earlier version printed a confidence score and a range that contradicted each other, on a bar drawn at a fixed position. It looked like a measurement and was decoration.
Chapter 02 of 04
The problem
Give a Dubai owner an instant valuation where every figure on the screen says where it came from, and where thin evidence shows up as a wider range instead of a confident number.
Chapter 03 of 04
The build
- Frontend Engineering
- A three-step wizard (address, property details, contact) and a results screen in Next.js 16's App Router: a range bar drawn to scale from the band, an itemised price-adjustment breakdown, an evidence table, a trend-extrapolation panel, comparable sales, a twelve-month trend chart, and location signals from public open data (RTA metro stations, KHDA school inspections, OSM Overpass). The five result surfaces were extracted into shared components so the wizard and the saved report cannot drift apart.
- Backend Engineering
- Five API routes on Vercel. Estimate runs the pricing engine; lookup resolves a deed or Makani number; lead writes to Vercel Blob and notifies through Resend; email-report sends the result; report persists one to Turso and serves it back at its own URL. The report route recomputes server side and never accepts a client-supplied price, so nobody can publish a fabricated figure on a branded page. Every integration no-ops cleanly rather than erroring when its env var is unset, including the database: with no Turso URL the save button does not render at all, rather than rendering and failing.
- Data Pipelines
- A hand-curated benchmark table, 15 communities, where each row records the published index it was read from and the month. Automated ingest from the Dubai Land Department is closed off (its transaction search is captcha-gated per query and the bulk portal is unreachable), so curation with recorded provenance is the model rather than a stopgap. One row is flagged in place because its villa index does not state whether its per-sqft denominator is built-up area or plot, and the two differ enough to matter.
- Product Strategy
- The positioning is the valuation that shows its working. Bayut and Property Finder are black boxes; the differentiator is that every displayed number produces an evidence row inside the engine rather than in the page, which is what stops a figure reaching the screen without provenance. Where a number cannot be sourced the surface says so out loud rather than quietly deriving it from the figure it was meant to explain. Net yield is the sharpest case: it is the number the portals do not publish, and it needs a service charge, which is published in no feed at all. So the charges are curated by hand as a band per community, and the yield is published as a range, because the sources make a single figure indefensible: Downtown Dubai runs from AED 21 per square foot in one tower to 67.88 in another. Three of the fifteen communities have no cited source and therefore no net yield, which the evidence table states plainly.
Build notes. How it came together and the decisions on the record.
Chapter 04 of 04
What it did
A public test build where no figure reaches the screen without a source.
The four benchmark rows that once read 'unverified' now each cite a published index and month. Checked against the live production API in September 2026: a mid of AED 3,210,000 on a band of AED 2,889,000 to 3,531,000, exactly the curated-benchmark tier's plus or minus 10 percent.
The tool is deployed as a standalone prototype, the Dubai Real Estate Valuation Toolkit, with no BARNES branding and a banner saying plainly that nothing submitted reaches a broker. The live production API returns a band that matches its evidence tier exactly, and every figure on the result card carries a row naming its source and the period it covers.
- 15
- Dubai communitieshand-curated, a source recorded per row
- 5
- API routesestimate, lookup, lead, email-report, report
- ±6-15%
- range widthset by the evidence tier, not by a score


