For developers
Screen a site before you commit hard costs. Model residual land value and margin against your own assumptions while the site is still on the market.
See the feasibility softwareOne record takes a site from the map to the feasibility. Search a Victorian or New South Wales address and read its planning context, controls and property data right now.
No account needed to search. Create a free account to save sites and run feasibility.
Developers, agents, valuers, architects and planners read the same site from the same data, so their numbers finally reconcile.
Screen a site before you commit hard costs. Model residual land value and margin against your own assumptions while the site is still on the market.
See the feasibility softwareOpen a site and surface every control that governs it, on a record you can cite and date. The conversation starts with what is actually permissible.
Read the planning libraryFind any Victorian or New South Wales parcel by address or lot and plan, and open its record in seconds.
Learn more →Every zone and overlay on the site on one screen, with how much of the lot each one covers and the date the data was loaded.
Learn more →Setbacks, height and related controls resolve into a buildable volume on supported typologies, before concept hours start.
Learn more →Profit, margins, residual land value and sensitivity on the same record, with every assumption visible and dated.
Learn more →Export the study as a PDF, an Excel workbook with its assumptions sheet, and a lender pack with the site’s planning status and sensitivity.
Learn more →The developer's view, the valuer's view and the planner's view never reconcile, because none of them were built on the same record.
Zone and overlay wording lives in council PDFs. You read it, paraphrase it into an email, and hope you caught the clause that matters.
Lot dimensions, easements and encumbrances sit in a second platform, on a different basemap, with no link back to the constraint.
Comparables come out of a separate subscription, then get retyped into a spreadsheet where the adjustment logic is invisible to everyone but its author.
Every feasibility starts from someone's old file. Assumptions are buried in cells, versions fork, and nobody can audit the number that mattered.
Each layer is marked by what it is now, not what it will be.
See the roadmapSite pipelines are commercially sensitive. Primary databases are hosted in Australia, and your project content is never sold.
Read our privacy policy