Real estate software can mean a public listing website, a brokerage CRM, or a private maintenance portal. These serve different users and need different data. A useful agency brief starts by choosing which job you are commissioning rather than asking for every property feature in one platform.
This guide focuses on property information, inquiry handling, and operational coordination. The examples do not represent Catapult client projects. Screening decisions, legal documents, regulated advice, and jurisdiction-specific requirements need their own qualified review and should not be casually added to a website or automation scope.
Related service: Property workflow and portal development- 01Resident reports an issue
- 02Property team confirms the record
- 03Manager assigns approved work
- 04Contractor records progress
- 05Manager reviews closure and updates the resident
SECTION 01
Separate property discovery from ongoing operations
A prospective buyer or renter needs accurate property information and a clear inquiry path. A resident needs access to their own requests. An owner may need an approved summary across selected properties. A contractor needs only enough information to complete assigned work. One shared login screen does not make these the same product.
Choose the first audience and outcome. A brokerage might begin with website inquiries connected to an existing CRM. A manager might need a request queue spanning properties already recorded elsewhere. Both can use custom software, but their data model, permissions, acceptance tests, and operating responsibilities differ.
| Audience | Possible implementation | Important boundary |
|---|---|---|
| Prospective customer | Property pages and inquiry-to-CRM connection | Display only licensed, current information. |
| Resident | Private request portal with attachments and status | Show only the resident's permitted property records. |
| Property manager | Assignment queue and exception dashboard | A person owns priority, access, and completion decisions. |
| Owner | Approved operational summary | Limit visibility to the properties and fields they may access. |
SECTION 02
Confirm listing access before designing around a feed
If the project includes U.S. listing feeds, ask who provides the data, which uses are permitted, and who owns the credentials. RESO publishes standards for exchanging real estate information; it does not supply MLS listing data. Its documentation directs data recipients to the relevant MLS and its licensing process.
Have the agency inspect an authorized sample and document field coverage, update behavior, removed listings, and display requirements. Avoid assuming that a standard field exists in every provider response. A connection is only in scope once your access and the provider's supported interfaces have been confirmed.
SECTION 03
Example: a resident reports a leaking appliance
In this illustrative workflow, a resident selects their unit, describes an appliance issue, and submits a photo. The portal displays the property's approved urgent-contact guidance without trying to diagnose the fault. It records the request and lets the property team confirm the right category and response process.
The manager assigns a contractor and shares only the required visit information. The contractor records an attempted visit but cannot complete the repair because access was unavailable. The request moves to 'visit needs rearranging', not 'completed'. The resident receives a verified status update, while the manager decides the next action.
A later completion note enters a review queue. The manager checks the record before closing the request. AI could organize the original description or suggest a category, but it should not make safety assessments, approve work, or invent an arrival time. Preserve the source message beside any suggested summary.
SECTION 04
Test permissions when people and properties change
A resident moving out, a new owner, or a contractor finishing an assignment should change what those users can access. Document those transitions. Historical records may need to remain available to the manager without remaining visible to the previous resident or contractor.
OWASP's authorization guidance is relevant here: permissions must be checked on requests, including access to individual resources. In practical terms, testing should try another property's record ID and a previously valid attachment link. Hiding a button is not enough. Keep the test dataset fictional or safely prepared for development use.
SECTION 05
Prove one workflow, then decide what to expand
Keep the first release to a manageable property group and one process, such as maintenance intake and review. Configure the current management product if it already supports the journey. Use custom portal development where a distinct user experience or supported cross-system connection is needed.
For an agency engagement, supply the current workflow, sample records, access approvals, and a property-team reviewer. Agree the launch checklist, data export, backups, integration monitoring, and who updates guidance after handoff. Catapult can plan the technical scope remotely for U.S. or international teams; local operational and legal decisions remain with your responsible advisers.
SECTION 06
Frequently asked questions
Can an agency add MLS listings to any website?
Not without the appropriate data access and display permissions. Confirm the MLS or provider agreement, credentials, supported API, and implementation requirements before including a listing feed in scope.
Is a custom tenant portal a replacement for property-management software?
It can be a connected interface rather than a replacement. Keep the existing system of record where it works and build only the resident or staff workflow that needs improvement.
Can AI automatically prioritize maintenance?
AI can suggest a category from an approved input, but the property team should own urgency and safety-related decisions. Provide an explicit urgent-contact route and a review path for uncertain requests.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- RESO Web APIReal Estate Standards Organization
- Authorization Cheat SheetOWASP
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy