Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design the steps between property interest and the right enquiry.
We map visitor tasks and design the screens, filters and form states that support actual property services.
A few clients we’ve worked with
What we do
We map visitor tasks and design the screens, filters and form states that support actual property services.
Decisions that shape this work.
Filters cannot reliably offer attributes that the property records do not contain.
Contact, booking and transaction commitments need distinct interface wording.
What interface decisions cost when nobody makes them.
Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.
Development stops guessing
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
The product survives its next feature
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
What UX/UI design includes.
The scope follows the property business’s actual services and verified information. Availability, pricing and property claims need approval from the responsible team.
Audience journeys
Separate seller, occupier, buyer or existing-customer tasks where relevant.
Browsing interactions
Design useful filtering and empty states using the data genuinely available.
Enquiry flow
Specify question order, validation and next-step messaging for each route.
Selected projects across our wider practice
All case studies
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
What you receive.
The agreed engagement includes the relevant outputs below.
- 01
Journey maps.
- 02
Interactive Figma flows.
- 03
A form and filter specification.
Our process
How the work runs.
Map the visitor decisions
Define browsing and contact tasks using the business’s actual audience groups.
[ 01 ]
Prototype the interactions
Connect filter states, detail pages and enquiry screens with representative records.
[ 02 ]
Test the proposed flows
Walk through desktop and mobile scenarios and document behaviour for empty results, errors and completion.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedUX/UI design for real estate companies: questions.
Can the interface include map-based workflows?
Yes, when the user tasks, data rights and map capabilities are defined for the scoped product.
Should every visitor use the same contact form?
Only if their information needs and receiving workflow are genuinely the same.
Website 2.0 combines strategy, design, development and launch in one engagement.