Stakeholders agree once
Sessions surface competing priorities while they are still cheap to reconcile, not after a design has been drawn to one of them.
Trace the enquiry and content systems before planning the build.
Discovery examines the website, property records and receiving tools so the scope reflects the business’s actual workflows.
A few clients we’ve worked with
What we do
Discovery examines the website, property records and receiving tools so the scope reflects the business’s actual workflows.
Decisions that shape this work.
Property information may be maintained outside the website CMS.
A connection depends on the real system’s permitted actions, not its brand name alone.
What discovery settles before design starts.
A project can be ready for discovery before it is ready for design. Finding the unresolved questions early is what keeps the build from pausing.
Dependencies appear early
Technical constraints and the systems the website has to live with are identified before they become a mid-build surprise.
The next stage can be scoped
A brief naming the decisions and open questions lets design, content and development be quoted against something real.
What website discovery includes.
The scope follows the property business’s actual services and verified information. Availability, pricing and property claims need approval from the responsible team.
Content inventory
List services, properties, locations and their record owners.
Enquiry review
Follow representative seller, occupier or service enquiries through existing tools.
System dependencies
Check documentation, permissions and supported connection methods.
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
A content inventory.
- 02
An enquiry workflow diagram.
- 03
A requirements register.
Our process
How the work runs.
Inventory content and tools
Identify record sources, page types and staff responsible for keeping them current.
[ 01 ]
Follow representative enquiries
Document receipt, assignment and follow-up using approved examples.
[ 02 ]
Define the implementation requirements
Record templates, data fields, supported connections and unresolved dependencies with named owners.
[ 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 startedWebsite discovery for real estate companies: questions.
Will discovery assume we need an IDX site?
No. The business requirements are reviewed first; standard MLS/IDX listing sites are not Norml’s specialist focus.
Do you need real buyer or tenant records?
Workflow review can use synthetic or specifically approved examples instead.
Website 2.0 combines strategy, design, development and launch in one engagement.