In 2026, BDO Australia counted around 51,000 build-to-rent apartments in the national pipeline, worth about $40.1 billion. A year earlier those numbers were 39,300 and $30.1 billion. Whatever else is true about Australian housing, this asset class is no longer an experiment.
A sector that grew up fast
The trajectory matters more than the totals. Victoria leads the country with 24,855 apartments across 65 projects. New South Wales is the growth story, now at 17,465 apartments and climbing fastest. These are not scattered one-off developments; they are portfolios being assembled deliberately, by institutions, with decade-long horizons.
Growth of this shape changes what operations means. A sector made of one-off projects can improvise: a spreadsheet here, a part-time building manager there, a box of fobs in a drawer. A sector with a $40 billion pipeline cannot. The gap between how these buildings are funded and how they are run is now the most interesting problem in Australian proptech.
The operator model changes the software question
Around 80 per cent of the pipeline is run by dedicated operator platforms. That single number explains why build-to-rent needs different software. BTR is institutional ownership of professionally managed communities: the owner keeps the asset for decades, and the operator is accountable for occupancy, resident experience and compliance across a whole portfolio.
That is a different business from managing tenancies on behalf of scattered landlords. The accountable party is different, the time horizon is different, the resident relationship is different, and the compliance surface is portfolio-wide rather than per-property. It needs different software, in the same way an airline needs different software from a travel agent.
Repurposed tools carry the wrong assumptions
Most Australian residential software was built for two models: strata and agency. Strata software assumes an owners corporation, levies and quarterly cycles. Agency software assumes a landlord, an agent and a tenant, arranged in a triangle around individual properties.
Neither has a concept of a building as a product, a resident as a member, or an operator as accountable for the whole stack from the front door to the rent ledger. When a BTR operator runs on these tools, the mismatch is structural, not a missing feature. You cannot configure your way from a landlord-agent-tenant triangle to a portfolio operating model.
Access and operations are the least served layer
Leasing tools exist. Finance tools exist. The layer with the least purpose-built software is the operational one: doors, credentials, visitors, amenities, and the audit trail behind all of it. It is where operators are stitching together the most vendors with the least governance, and it is also the layer residents actually touch every day. The front door is used more often than the lease.
What purpose-built looks like
A platform built for this model starts from one resident record, treats every operator and resident action as a governed event on one audit trail, and gives residents a single app they actually use. It assumes a portfolio, not a property. It treats compliance as a property of the system rather than a filing obligation.
This is the gap we built BTR OS for, and we are open about that being the lens here. But the argument stands on the BDO numbers alone: a $40 billion sector run by dedicated operators will not run indefinitely on software borrowed from a different industry.
Source: BDO Australia, A Changing of the Guard in Australia's Living Sector, 2026.