Victorian planning answers, with the rule behind every one.
- Client
- Our in-house startup
- Sector
- Proptech
- Services
- AI agents, MVP, Custom software, UI/UX design
- Status
- Early access

- Note 1: Every site opens with its zone, schedule and overlays.
- Note 2: Ask in plain words. Each answer shows the planning rule it came from.
- Note 3: It measures the lot on the map and tests what fits against the zone's own rules.
The challenge
Planning answers take hours to days, and the data behind them is public but scattered.
What we built
A public AI chat with the planning rule cited on every answer, property cards, site analysis, a property finder, suburb intelligence, a developer API, and the state's planning data held in our own database.
How the automation works
Ask in plain words. The system finds the property, reads the zone, schedule and overlays, measures the lot and tests what fits against the zone's own rules. When the rules are silent, it says so.
What changed
4.1M+
Measured: count of properties in the PropyChat database, 14 September 2026 (4,187,991).
9 months
Stack
Real code, Postgres with PostGIS and 33 GB of planning data, hosted in Sydney, the Claude AI model.
What happens next
- 1Tell us the crux in a short form.
- 2We reply within one business day, with a straight answer on fit.
- 3Pick a time that suits you for a 30-minute call.