PropTech
Technology applied to property — listings, transactions, management, investment — across a market where the user and the buyer are rarely the same person.
PropTech spans listing marketplaces, transaction and conveyancing tools, property and tenancy management, construction technology, and investment platforms. The common thread is an industry where transactions are infrequent, high-value and involve many parties — buyer, seller, agent, lender, surveyor, solicitor — each with their own systems and none with an incentive to make the others' work easier.
Two design consequences follow. First, the person using the software is often not the one paying for it: an agent's tool is bought by the brokerage, a tenant portal is bought by the landlord. Designing for the buyer produces software the daily user resents. Second, infrequent use means nothing can rely on familiarity — someone buys a home a handful of times in their life and will not learn your interface, so every screen has to work for a first-time user under financial stress.
In practice
A conveyancing platform designed its client portal around the solicitor's workflow, because solicitors bought it. Buyers, who used it once, could not tell which of eleven documents needed their signature and which were informational. Splitting the view into “needs you” and “for reference” cut chase-up calls by about half.
Where teams get it wrong
- Designing for the buyer of the software rather than the person using it daily.
- Assuming familiarity in a transaction most people go through a handful of times.
- Ignoring the other parties in the chain, whose delays surface as your product failing.
- Listing data treated as clean when it arrives from many sources with different conventions.
- Mobile as an afterthought in a market where viewings happen on a phone.
( Learn more )
Related terms
All terms- Customer PortalAn authenticated area where customers handle their own account — the cheapest support channel a business has, when it covers the right things.
- User FlowA diagram of the path a user takes through an interface to finish one task, including every decision point, branch and error state.
- Form DesignDesigning the fields, sequence, validation and error handling of a form so people can finish it without stopping to think.
- File UploadThe control for getting a file from a person's machine into a product — and the place where most products lose the work silently.