Understanding the work
What does a real estate software development company do?
A real estate software development company plans, builds, integrates, and maintains software for the property industry: agent and brokerage tools, listing portals and IDX websites, property management and tenant portals, transaction management, and commercial real estate systems. Most of the work involves licensed MLS data, payments, and rules on fair housing and settlement services.
Real estate software development is the design, build, integration, and support of custom software for buying, selling, leasing, managing, financing, or valuing property, from consumer search portals and tenant apps to brokerage back office and lease administration systems.
What they build compared with related providers
A general firm, covered in our software development company guide, can build a web app, but may not know how MLS licensing or IDX display rules work. Website vendors that sell IDX plugins handle listing display only. Off-the-shelf property management and transaction platforms solve common workflows but limit custom processes. A real estate software development company sits between these: it builds what makes your business different and connects it to the platforms you already use.
Many brokerages start with a CRM. If client and lead management is the main need, our CRM software development guide covers that decision in more depth.
Types of software a real estate software development company builds
Common real estate software includes agent and brokerage tools, listing portals and IDX sites, property management systems, tenant portals with rent payments, transaction management, commercial real estate lease administration and portfolio analytics, valuation and market analytics, and mortgage-adjacent tools such as affordability calculators and lender handoffs.
| Type | Examples | What usually drives the effort |
|---|---|---|
| Brokerage and agent tools | Agent CRM, lead routing, commission tracking, onboarding | Brokerage rules, roster and license data, commission splits, integration with CRM and accounting |
| Listing portals and IDX sites | Property search, map search, saved searches and alerts, agent websites | MLS feeds, display rules per MLS, search performance, photo handling, SEO for listing pages |
| Property management | Residential and association management, maintenance, owner statements | Trust accounting, rent rolls, owner reporting, state-specific notices and deposit rules |
| Tenant portals and rent payments | Online applications, rent payment, autopay, lease signing, service requests | Payment processing and security, applicant screening integrations, accessibility, mobile use |
| Transaction management | Offer and contract workflows, document checklists, compliance review, e-signature | Forms licensing, buyer agreement tracking, audit trails, integration with e-signature and storage |
| Commercial real estate | Lease administration, CAM reconciliation, portfolio analytics, deal pipeline | Complex lease terms, data from many property managers, investor reporting |
| Valuation and analytics | Comparable sales tools, market dashboards, investment underwriting models | Data licensing, data quality, model transparency, refresh schedules |
| Mortgage-adjacent tools | Affordability calculators, pre-approval handoffs, closing cost estimates, title and escrow status | Settlement service rules, lender and title integrations, accuracy disclaimers |
Scroll the table sideways to see all columns.
For consumer search or tenant apps, our guide to cloud app development services covers backends and app store releases.
Requirements and rules
Rules and compliance that shape real estate software
Any real estate software development company you hire must design around MLS licensing and display rules, the Fair Housing Act for listings and advertising, RESPA and Regulation X for settlement-related features, state privacy laws, e-signature laws, and payment card security. Industry changes, such as the NAR changes effective August 17, 2024, also reshape workflows.
This is general information, not legal advice; confirm with counsel before you design features that touch these rules.
Fair housing in listings and ad targeting
The Fair Housing Act prohibits discrimination in the sale, rental, and advertising of housing. For software, that covers listing descriptions, search filters, ad audiences, chatbot replies, and any scoring of applicants or leads. HUD withdrew a set of fair housing guidance documents, including its guidance on digital advertising, effective September 17, 2025. The law itself still applies, so targeting and recommendation features need review as of October 2026.
- Do not offer search filters or ad audiences that act as proxies for protected classes.
- Screen listing text and generated content for discriminatory language before it is published.
NAR practice changes effective August 17, 2024
Following the NAR settlement, MLSs adopted policy changes effective August 17, 2024. Agents working with buyers must have a written agreement before touring a home, and offers of compensation to buyer brokers can no longer be shown on the MLS. Transaction, CRM, and showing tools need to capture and check buyer agreements, and listing displays must not reintroduce compensation fields from older data.
RESPA and Regulation X
The Real Estate Settlement Procedures Act, implemented by the CFPB's Regulation X, governs settlement services for federally related mortgage loans, including limits on kickbacks and referral fees. Features that connect buyers with lenders, title companies, or other settlement providers, especially with paid placements or lead sharing, need review before launch.
Privacy, e-signature, and payments
Many states have comprehensive privacy laws covering data from search portals, tenant apps, and lead forms. Electronic signatures rely on the federal ESIGN Act and state adoption of the Uniform Electronic Transactions Act, so software should record consent, identity, and a tamper-evident audit trail. Card payments fall under PCI DSS; a processor's hosted fields keep most card data out of scope.
MLS data, RESO standards, and integrations
A real estate software development company today pulls MLS data through the RESO Web API, a standard built on OData that has replaced the older RETS protocol, with the RESO Data Dictionary 2.0 standardizing field names. Access requires a license from each MLS, and each MLS sets its own IDX and VOW display rules.
IDX (Internet Data Exchange) lets participating brokers show other brokers' listings on their websites under MLS rules. A VOW (virtual office website) is a broker site that shows listing data to registered consumers who have a brokerage relationship, often with more data fields than IDX allows.
What to plan for with MLS data
- A data license with every MLS you pull from, often signed by the broker, with the developer approved as a vendor.
- Display rules that vary by MLS: required attribution, disclaimers, logos, refresh frequency, which fields may be shown, and how sold or off-market data is handled.
- Photo rights: listing photos are often owned by photographers or listing brokers and licensed through the MLS for specific uses only.
- Mapping local fields to the RESO Data Dictionary, since many MLSs also expose local fields outside the standard.
- Replication versus live queries: a local copy for fast search must handle deletions and status changes.
- Deduplicating listings that appear in more than one MLS feed.
| System | Used for | Watch for |
|---|---|---|
| MLS (RESO Web API) | Listings, media, agent and office rosters | Licensing, display rules, rate limits, local fields |
| CRM and marketing tools | Leads, contacts, drip campaigns | Consent records, duplicate contacts, lead source tracking |
| Accounting and trust accounting | Commissions, rent, deposits, owner payouts | Reconciliation, state trust account rules, audit trails |
| Payments | Rent, application fees, earnest money where allowed | PCI DSS scope, ACH returns, refunds and chargebacks |
| E-signature and forms | Buyer agreements, purchase contracts, leases | Forms licensing from associations, audit trail export |
| Screening and verification | Tenant applications, identity checks | Consumer reporting rules, adverse action notices, fair housing review |
Scroll the table sideways to see all columns.
Decisions
Build, buy, or extend real estate software
Buy established platforms for commodity workflows such as standard property management accounting or e-signature. Extend a CRM or transaction platform when it covers most needs. Hire a real estate software development company for a custom build when your search, lead routing, data product, or commercial reporting sets your business apart.
| Option | Good fit when | Tradeoffs |
|---|---|---|
| Buy a platform | Property management accounting, standard transaction checklists, IDX plugins for agent sites | Workflows follow the vendor; per-door or per-agent fees; data export can be limited |
| Extend a platform | A CRM or property management system covers most needs and offers APIs | API limits and vendor roadmap changes can break custom work |
| Custom build | Proprietary search, multi-MLS data products, brokerage back office at scale, CRE portfolio analytics | You own maintenance, MLS compliance, and security |
| Hybrid | Buy accounting and e-signature, build the agent or tenant experience on top | Integration becomes the main ongoing cost |
Scroll the table sideways to see all columns.
If you are testing a new proptech idea before committing to a full product, our MVP development guide explains how to scope a first release that proves demand without overbuilding. Subscription products sold to many brokerages should also follow the multi-tenant patterns in our SaaS development guide.
How a real estate software project runs
A project with a real estate software development company usually starts with data access and compliance discovery, then moves through design with agents, tenants, or property managers, MLS and payment integration, a pilot in one market or portfolio, and staged rollout. MLS approvals and compliance reviews often set the pace more than coding.
- Data and licensing discoveryList every MLS, data vendor, and forms provider, confirm who signs each agreement, and collect each MLS's display rules.
- Workflow mappingShadow agents, coordinators, leasing staff, or asset managers to see how deals actually move, including buyer agreement steps.
- Compliance reviewHave counsel review fair housing exposure in search and advertising, RESPA exposure in referral features, and privacy notices.
- Architecture and data modelMap MLS data to the RESO Data Dictionary and plan replication and deletion handling.
- Build in incrementsDeliver working slices, such as search for one MLS, and demo them to real users.
- MLS approval and testingSubmit displays for MLS review where required, test accessibility and performance, and run security testing on payment and login flows.
- Pilot and rolloutLaunch in one office, market, or building, then add markets and MLSs one at a time.
- Operate and updateMonitor feed health, track MLS rule changes, and keep integrations current.
What drives cost with a real estate software development company
Cost depends mostly on the number of MLSs and data sources, integration depth with accounting, payments, and e-signature, the number of user types (agents, brokers, tenants, owners, investors), compliance review, mobile apps, and ongoing data operations. Data licensing fees from MLSs and vendors are a separate recurring cost.
| Cost driver | Why it adds effort |
|---|---|
| Number of MLSs | Each one brings its own license, local fields, display rules, approval process, and feed quirks |
| Search and maps | Fast map search, saved searches, and alerts need indexing, geospatial queries, and caching |
| Payments and trust accounting | Money movement needs reconciliation, refunds, failure handling, and strict audit trails |
| User roles | Agents, brokers, coordinators, tenants, owners, and vendors each need permissions and screens |
| Compliance work | Fair housing reviews, RESPA review of referral features, privacy notices, and accessibility testing |
| Commercial lease complexity | Escalations, options, CAM rules, and abstracting legacy leases take specialist effort |
| Data migration | Moving tenants, leases, ledgers, or transaction files from an old system requires cleanup and validation |
| Ongoing data operations | Feed monitoring, MLS rule updates, and vendor API changes continue after launch |
Scroll the table sideways to see all columns.
The cost section of our software development company guide explains estimates, pricing models, and contingency in general terms.
Contracts, data rights, and ownership
A contract with a real estate software development company should give you ownership of custom code, keep MLS licenses, cloud accounts, and payment accounts in your name, set data processing terms for consumer data, and include a transition plan. MLS data and listing photos stay licensed, not owned, whoever builds the software.
- Code ownership: assignment of custom code to you on payment, with a list of reused libraries.
- Data rights: MLS and vendor licenses held by your brokerage or company, not the developer, so you can change vendors without losing access.
- Data processing terms: access to tenant, buyer, and lead data, breach notice duties, and deletion at exit.
- Payments: merchant and processor accounts in your name; the developer should never hold funds.
- Acceptance and warranty: acceptance tied to MLS approval and real data, plus a defect warranty.
- Exit and transition: documentation and handover help so another team can take over.
- AI-generated code: disclosure of AI tool use, since the US Copyright Office has said purely AI-generated material without human authorship is not copyrightable.
How to choose a real estate software development company
Choose a real estate software development company that has shipped live MLS integrations through the RESO Web API, understands IDX and VOW rules, can explain fair housing and RESPA risks in its features, follows secure development practices, and puts code, data licenses, and accounts in your name. Start with paid discovery.
Evaluation criteria
- MLS experienceLive products that pull from MLSs you need, with approvals completed, and references from brokers.
- Domain knowledgeThey understand brokerage operations, trust accounting, leasing, or commercial lease administration.
- Compliance awarenessThey raise fair housing, RESPA, privacy, and accessibility questions without being prompted.
- Security practicesAlignment with the NIST SSDF and OWASP ASVS, and a plan to keep card data out of scope.
- Estimate and ownershipAn itemized estimate listing each MLS and integration, plus code, licenses, and accounts in your name.
Questions to ask a real estate software development company
- Which MLSs have you integrated with through the RESO Web API, and how long did their approvals take?
- How do you handle display rules that differ between two MLSs in the same product?
- How did you update transaction or CRM workflows after the August 2024 NAR changes?
- How do you review search filters, ad audiences, and AI features for fair housing risk?
- Which referral or lender features would you flag for RESPA review?
- Where will payment card data flow, and what is our PCI DSS scope?
Red flags
- Plans to scrape listing sites instead of licensing MLS data.
- No mention of photo rights or MLS display rules.
- Offering search filters or ad targeting by neighborhood demographics.
- Holding MLS credentials or merchant accounts in the developer's name.
For a broader checklist that applies to any software project, see how to choose a software development company.
Reference
Real estate software development company FAQs
What does a real estate software development company build?
It builds brokerage and agent tools, listing portals and IDX websites, property management systems, tenant portals, transaction management, commercial lease administration, and valuation tools, and connects them to MLS data, accounting, payments, and e-signature services.
What is the RESO Web API?
The RESO Web API is the real estate industry standard for exchanging MLS data, built on the OData protocol. It replaced the older RETS standard. With the RESO Data Dictionary 2.0, it gives developers consistent field names across MLSs, though local fields and rules still vary.
Can we show MLS listings on our website?
Usually only through an IDX or VOW agreement with each MLS, typically signed by a participating broker. Each MLS sets its own display rules for attribution, disclaimers, refresh frequency, and which fields and photos may be shown, so rules vary by MLS and should be checked before design.
How did the 2024 NAR changes affect real estate software?
Since August 17, 2024, buyer agents need written agreements before touring, and offers of compensation are not shown on the MLS. Transaction, CRM, and showing tools needed new steps to capture and track buyer agreements and had to stop displaying MLS compensation fields.
Does the Fair Housing Act apply to software?
Yes. The Act covers advertising and decisions about housing, so listing content, search filters, ad targeting, and applicant scoring built into software can create liability. HUD withdrew some guidance documents effective September 17, 2025, but the law itself still applies. Confirm specific features with counsel.
When does RESPA matter for a real estate app?
RESPA and Regulation X matter when an app connects consumers with lenders, title, escrow, or other settlement service providers for federally related mortgage loans, especially with referral fees, paid placements, or lead sharing. Have counsel review these features before launch.
Who owns MLS data used in our app?
Neither you nor your developer. MLS data is licensed for specific uses under agreements with each MLS, and listing photos often carry separate rights. Keep licenses in your company's name and follow each MLS's terms on storage and deletion.
Sources and further reading
Primary sources for the standards and rules referenced in this guide.
- RESO, RESO Web API
- RESO, RESO Data Dictionary
- National Association of Realtors, Summary of 2024 MLS policy changes
- US Department of Justice, The Fair Housing Act
- HUD, Fair Housing Act overview
- Federal Register, Notification of withdrawal of fair housing and equal opportunity guidance documents
- Consumer Financial Protection Bureau, Regulation X (Real Estate Settlement Procedures Act)
- Uniform Law Commission, Uniform Electronic Transactions Act
- IAPP, US State Privacy Legislation Tracker
- PCI Security Standards Council, PCI Data Security Standard
- NIST, SP 800-218: Secure Software Development Framework (SSDF) Version 1.1
- OWASP, Application Security Verification Standard
- W3C, Web Content Accessibility Guidelines 2.2
- US Copyright Office, Copyright and Artificial Intelligence, Part 2: Copyrightability
About this guide
This guide is published by Crecso as an independent educational resource and is part of our software development guide. It names platforms, standards, and regulations as examples only, is not affiliated with any software vendor, MLS, or development firm, and does not describe services offered by Crecso. It is not legal or regulatory advice.
Last reviewed on . If you spot something that has changed, please let us know through our contact page.