Context
The demand side of a feasibility
Feasibility software handles costs, finance and margins well. The demand case can rest on a paragraph from a council profile, written for a different boundary, from a Census that may be ten years old.
The questions behind a product mix are simpler than that: who lives within a few kilometres of the site, how big their households are, whether they rent or own, what they earn, and whether the area is growing. The Census answers all of them once the tables are joined and carried onto today's boundaries, which is the work Censible has already done.
An example
Marsden Park, in Sydney's north-west
Marsden Park had about 940 residents at the 2016 Census and about 14,700 in 2021. Censible's projections put it near 30,000 in 2026 and above 42,000 by 2031.
In 2021, 69% of its families were couples with children, 30% of residents were under 15 and the average household had 3.4 people, almost all of them living in separate houses.
Marsden Park's boundary has changed since 2016, so its earlier figures are estimates and its 2026 and 2031 figures are projections rather than Census results, and both are labelled that way.
Limitations
Demand evidence, not a valuation
Censible doesn't hold sale prices, listings, development approvals or construction costs, and it doesn't value land. Its rents and mortgage repayments are what households reported to the Census, not current market rates.
Use it for the demand side of a feasibility, alongside your cost model and your agents' sales evidence. The latest results are from the 2021 Census; results from the 2026 Census arrive from June 2027.