One company, two kinds of R&D
Many proptech companies are software businesses with a foot in the physical world. That gives them two distinct kinds of technical uncertainty, and they should not share a core activity.
The software side (valuation, plan analysis, search and matching) is judged against what an experienced data or software engineer could predict from published methods. AusIndustry's software guide treats building dashboards and integrating services by following vendor documentation as routine, which covers most property management and listings features.
The physical side (energy, comfort, materials, construction methods) is judged by a building services engineer or building scientist against engineering literature, codes and standards. Here the question is whether calculation and established practice could predict the result. If an engineer could model it confidently, there is no experiment.
The building can host the experiment, but its cost stays out
Construction claims are closely watched. Taxpayer Alert TA 2017/2 targets claims that treat a whole building project as R&D, claims where the "novel" element in effect just delivers the building contract, and claims that include building expenditure. A proptech pilot in a real building inherits the same scrutiny.
A building can still be the subject or the test site of a qualifying activity. What can qualify is a narrow question inside it: does this control strategy hold comfort while cutting energy, does this facade panel meet a thermal target in this climate. AusIndustry's built environment guidance notes that the "application of existing technology in a different context or location" can be core R&D, depending on the circumstances, so a known approach in a new building type is not automatically out.
Three separate rules then apply, and they answer different questions. Whether the activity is R&D is the ordinary core test. Whether a cost counts is a different matter: s 355-225(1)(a) stops expenditure to acquire or construct a building, or to extend, alter or improve one, being notionally deducted, even when an experiment runs inside it. And because the building keeps producing a service while the trial runs, work on it can only be supporting if its dominant purpose is the experiment.
Who the software is for
Section 355-25(2)(h) excludes software developed for the dominant purpose of internal administration by the company or a connected or affiliate entity. That matters for proptech businesses that sit inside property groups. A leasing or asset management platform built mainly to run the parent's own portfolio is internal administration for the group, even if it lives in a separate company. The same platform sold to unrelated agencies and landlords is a product. See internal administration software.
Group structures raise a second question. Where the parent funds the work and keeps the results, the R&D may be conducted for the parent. Taxpayer Alert TA 2023/4 describes a related pattern, where a group's R&D entity claims for work that an associate in substance funds, controls and exploits.
How proptech registrations usually split
- Separate core activities for software questions and building science questions.
- Supporting activities for pilot instrumentation, data labelling and test rigs, with any building that keeps operating apportioned.
- Left out: construction and fit-out, compliance and ratings, property operations software, and pricing experiments.
Keep the pilot agreement with each building owner with the trial records. It is the document that shows your company controlled the work, paid for it and kept the results.
For physical prototypes and test panels, see prototypes and tooling and materials testing.