A property-management website serves several audiences. A landlord may be comparing management services; a renter may be checking an available property; an applicant may need a separate application system; and an existing tenant may need the approved support route. The design should make those differences clear.
This agency-authored guide from Auckland-based No Brainer Creative explains how to scope that website. It does not establish portfolio-size thresholds, recommend unverified named packages or promise a particular enquiry rate. Costs and deliverables are agreed for the actual project.
1. Map the four visitor journeys
Start with the route and responsible person for each audience. A separate page or form can be useful when it clarifies the task, but it is not automatically proven to convert better than another layout.
- Landlords: understand the actual management service, coverage, approved fee information and how to discuss their property.
- Prospective renters: find current listings, viewing information and the appropriate question or application route.
- Applicants: use the authorised application process and understand its next step.
- Existing clients and tenants: reach the intended portal, contact person or approved support process.
Make navigation labels descriptive. An application submitted is not an approved tenancy, and a landlord enquiry is not a signed management agreement. Confirmation messages should reflect the state actually reached.
2. Explain the management service accurately
Use the firm’s actual service scope, people, coverage and contact information. Have the responsible manager approve statements about fees, inspections, maintenance and other processes. A web editor should not invent claims about compliance or imply that attractive design proves professional capability.
Use genuine examples and testimonials with appropriate permission. Distinguish service descriptions from measured client results. If the business wants to publish a performance claim, agree the evidence and period before adding it to the page.
For landlord enquiries, collect the information needed for the next conversation and explain who will respond. Avoid adding fields simply because a generic website template includes them. Decide how the enquiry reaches the correct branch and how absence or routing failures are handled.
3. Scope listing feeds and portals before building
Identify the software or provider that holds the current listing information. Ask which feed, embed or public links are available, what requires a subscription and who can authorise implementation. A proposal should distinguish a designed mockup from a working integration.
Check the actual update process: when the source listing changes, which website fields change, how long the update normally takes and who handles a failed sync? Keep listing status, viewing details and contact information aligned. Do not assume a successful import establishes reliable future updates.
A link to an existing provider page can be a sensible route. Test whether it opens the intended listing or branch and remains usable on a phone. A template can also be suitable when it supports the agreed requirements; custom work should solve a documented need rather than satisfy an arbitrary property-count threshold.
4. Keep applications and private records in the right process
A public marketing form and a tenancy application have different purposes. Agree the application provider, collection fields, privacy information, recipients and record-handling responsibilities before implementation. Do not copy private applicant or tenant records into a public website or general marketing report.
The Office of the Privacy Commissioner’s rental guidance for landlords and property managers addresses information handling through the rental process. Have the responsible business reviewer confirm what applies to the proposed forms and systems. Website design does not replace that review.
Keep existing-client and maintenance routes distinct from new-business marketing. Show the property manager’s approved instructions and avoid inventing an emergency route, after-hours promise or acknowledgement that implies a human has already reviewed a request.
5. Agree practical launch checks
Use the real pages and integrations on phone and desktop. Check navigation, text readability, form labels, listing filters where supplied and the return path from external services. Measure technical problems rather than assuming a platform always meets or fails a universal speed threshold.
- Check each audience reaches the correct destination.
- Verify the selected listing or branch and its current status.
- Check that application and enquiry labels describe the actual result.
- For authorised controlled tests, verify the intended record and notification receipt.
- Record test identities and remove their activity from demand reporting.
- Document unavailable access or unverified delivery instead of calling the journey complete.
Do not submit surprise applications, maintenance reports or bookings. Tests can create work and transmit personal information, so agree their scope and cleanup with the receiving business first.
6. Plan editing, search and measurement
Assign responsibility for service copy, staff information, listing updates, portal links and approved contact details. Include training, support and software costs in the handover. Keep access limited to the agreed people and systems.
For local visibility, use real locations and useful coverage information. Avoid pages that merely swap suburb names or imply an office the business does not have. Our Auckland SEO service can be scoped separately from the build.
Report landlord enquiries, rental questions, applications and support requests separately. Where the evidence allows, identify suitable opportunities and accepted management work. A button click, form success message or Maps interaction is not proof of a new client.
Prepare a website scope discussion
Bring the current website, software provider, audience routes and known problems to a scope discussion with No Brainer. Our website design service can address the agreed pages, integrations and checks. Wider CRM and follow-up automation should have its own defined workflow and verification.
Frequently asked questions
What should a property-management website do first?
Make it clear where each visitor should go: a landlord considering the service, a renter looking for a listing, an applicant and an existing tenant may need different routes. Agree ownership of each route before designing the pages.
Do we need a live listings feed?
It depends on the operation and provider. A maintained feed, embedded listing view or a clearly labelled link to a provider can each be appropriate. Confirm availability, update responsibility, costs and what happens when a listing is removed.
Should tenants apply through the public enquiry form?
Do not assume a marketing contact form is suitable for full tenancy applications. Agree the authorised application system, required information, privacy wording and handling responsibilities with the business. Keep simple enquiries distinct from applications.
Is a custom site required above a certain portfolio size?
No threshold is established by this guide. Choose the platform and build scope from integration needs, editing, usability, maintenance and the customer journeys. Portfolio size alone does not establish the right package.
Can an external portal be a good website route?
Yes, when it is the intended and verified route. Label it clearly, send visitors to the right place and check its use on phones and larger screens. An embedded portal is not automatically better.
How should maintenance requests be handled?
Use the property manager’s approved support process and distinguish routine messages from its stated urgent procedure. Confirm who receives requests and what the acknowledgement means. Do not invent emergency instructions or promise an unverified response time.
What will the website cost and how long will it take?
Request a proposal for the actual pages, content, integrations, migration, tests and handover. Separate software subscriptions and wider marketing costs. This guide does not define No Brainer packages, prices or a fixed launch timetable.
How should the business measure website performance?
Separate landlord enquiries, rental questions, applications, maintenance requests and accepted opportunities. Record the source and reporting period where reliable, exclude internal tests and document any gaps in delivery or CRM evidence.
