
4.1M
PropyChat: talk to your property
Our flagship product connects 4.1 million Victorian properties and their planning to AI, so anyone can ask about a property and get an answer in seconds.
UI/UX design
UI and UX design for web and mobile applications, by the people who then build them. Research, flows, a design system and working prototypes before a line of code.

The problem
It looked fine in the demo. At four on a Friday it is three screens too many, every button means something different, and on a phone it is a desktop squeezed into a rectangle.
Impressive in a pitch, painful in daily use, so the team keeps the spreadsheet.
Three designers, no system, and buttons that mean different things on different pages.
A desktop layout squeezed onto a phone, used once and never again.
The solution
We start with the people who will use it and finish with a system the engineers in the next room build from. Nothing is lost in a handover, because there is no handover.
We sit with the people who do the work, map the real flow, and design for the day, not the demo.
Tested with your team before we build, so the arguments happen on a prototype, not in production.
One set of components for web and mobile, so every screen feels like the same product.
What we have done
Our own products are the proof: designed here, built here, running today.

4.1M
Our flagship product connects 4.1 million Victorian properties and their planning to AI, so anyone can ask about a property and get an answer in seconds.

Live
Our own practice management system for Australian accounting firms: client files and onboarding, task tracking on ATO cycles, invoicing and collections, documents and team chat, multi-tenant per workspace.
Up to 80%
less admin work for the teams we build systems for
4.1M
Victorian properties, with their planning, that our flagship PropyChat connects to AI and answers about in seconds
FAQ
Yes. You own the source files and the design system either way. Most of the value comes when the same team builds it, but that is your call.
Research notes, the mapped flows, clickable prototypes tested with your team, a design system, and the source files.
Paper and Figma, and we hand over the source files at the end. The design system is written so engineers can build from it directly.
Yes. One set of components serves both, so every screen feels like the same product on a phone and on a desk.
One call, no deck. We will tell you what we would redesign first, and whether it is a design problem or a system problem.