Where every AlphaDesk number actually comes from.
AlphaDesk works with a defined set of data sources. This page lists all of them, honestly labels each one as verified, observed or modelled, and calls out what AlphaDesk does not claim access to. If a number cannot be traced back to one of these categories, it does not appear in an AlphaDesk report.
Public builder and project records maintained by Karnataka RERA. When a buyer provides a project RERA number, AlphaDesk cross-checks it against this registry.
When a buyer uploads a sale deed, khata, encumbrance certificate, RERA document or cost sheet, AlphaDesk reads only that document to answer a specific readiness question — no third-party training use.
Reference rate bands per corridor curated by AlphaDesk's research team from listing observations, past transactions communicated to us, and market snapshots. Benchmarks are versioned and dated; every corridor page shows its last-updated date.
Public information on delivery history, project count, RERA filings, and known project timelines. Sourced from RERA disclosures, publicly reported filings, and manual research.
The property details, quoted price, area, loan structure and objective a buyer types into AlphaDesk. These are treated as the buyer's stated facts and stored with the decision record.
Every derived output — fair-value band, negotiation floor, True Cost of Ownership, financial stress scenarios, IRR — is calculated by AlphaDesk's engine from the inputs above using the weights and assumptions published in the Methodology.