Most real estate platforms still lose deals on the same three things: slow listing search, a CRM that forgets follow-ups, and a tenant portal that cannot take a rent payment without a phone call. We build these systems for brokerages, property managers, and PropTech startups, and the gap between a demo that wins and one that stalls is rarely the design. It is whether the boring plumbing works.
This is a practical map of what real estate software needs to include in 2026, what each module actually does, and where the money goes when you build it.
Short answer
Modern real estate software is six connected modules: a fast listings engine with map and saved search, a CRM that automates lead follow-up, tenant and owner portals, online rent and deposit payments, a maintenance request workflow, and an analytics layer. Buyers now expect all six in one login, not stitched-together tools.
What does a real estate software build cost by module?
Pricing depends on whether you build one module or the full platform, and on integrations like payment rails and MLS feeds. These are realistic ranges for an offshore build with a Pakistan-based team, which typically runs 40 to 60 percent below US local agency rates for the same scope.
| Module | What it covers | Typical build cost | Build time |
|---|---|---|---|
| Listings and search | Map search, filters, saved searches, MLS/IDX feed sync | $14,000 to $30,000 | 5 to 8 weeks |
| Real estate CRM | Lead capture, pipeline, automated follow-up, agent assignment | $18,000 to $40,000 | 6 to 10 weeks |
| Tenant and owner portals | Lease docs, statements, messaging, role-based access | $12,000 to $28,000 | 4 to 8 weeks |
| Payments | Rent, deposits, recurring billing, ACH and card | $10,000 to $22,000 | 3 to 6 weeks |
| Maintenance workflow | Request intake, vendor dispatch, photo upload, status tracking | $9,000 to $18,000 | 3 to 5 weeks |
| Analytics and reporting | Occupancy, rent roll, lead source ROI, owner reports | $8,000 to $20,000 | 3 to 6 weeks |
A full platform that ties all six together usually lands between $70,000 and $160,000. For a deeper breakdown of what drives those numbers, see our custom software development cost guide.
The listings engine: speed is the product
Buyers judge a real estate site in the first three seconds of a search. The features that matter are not flashy.
- Map-based search with clustering, so 4,000 listings do not freeze the browser
- Saved searches with email or push alerts when a matching property appears
- Server-side filtering that returns results in under 400ms even with photo-heavy listings
- IDX or MLS feed sync that updates listings every 15 to 60 minutes without manual entry
The hard part is the MLS feed. Each regional MLS has its own RETS or RESO Web API format, field names, and licensing rules. We normalize feeds into one internal schema so the rest of the app does not care which MLS a listing came from. Skipping this step is the most common reason a PropTech build runs over budget later.
What does a real estate CRM need that a generic CRM does not?
A generic sales CRM tracks a deal once. Real estate is different because a single contact can be a buyer, a seller, and a referral source over five years. The CRM has to model that.
- Lead capture from every source: website forms, Zillow and Realtor leads, walk-ins, and inbound calls
- Automatic agent assignment by territory, price band, or round-robin
- Follow-up sequences that fire on their own, because 48 percent of leads never get a second contact when this is manual
- Property-to-contact matching, so when a new listing hits, the system flags which past buyers wanted it
- A clear handoff record when a lead moves from inside sales to a closing agent
This is where most of the revenue is recovered. A follow-up engine that nudges agents on day 1, day 3, and day 7 routinely lifts contact rates without adding headcount.
Tenant and owner portals: self-service or phone calls
Property managers drown in repeat questions: when is rent due, where is my statement, who fixes the heater. A portal answers those without a call.
For tenants, the must-haves are: view and sign the lease, see payment history, pay rent, submit a maintenance request with photos, and message the manager. For owners, it is monthly statements, occupancy status, maintenance approvals over a spend threshold, and downloadable tax documents.
Role-based access is the engineering core here. A tenant must never see another unit, an owner must only see their own portfolio, and a manager sees everything in their assigned buildings. We build this with row-level security in the database, not just hidden buttons in the UI, because hiding a button does not stop someone reading the API.
Payments: the feature buyers ask about first
Online rent collection is now the deciding feature in most property-management deals. The plumbing that matters:
- Recurring ACH for rent, because card fees on a $2,000 rent payment are too high to absorb
- Card and digital wallet for one-off charges like application fees and deposits
- Automatic late fees applied by rule, not by hand
- A clear ledger per lease so a partial payment never breaks the books
For US and Canada builds we usually integrate Stripe or Dwolla for ACH. For UAE and UK builds the gateway choice changes, and so does the compliance work. Payments touch money movement and PII, so this module needs the same care as a fintech software development project even though the app is about property.
Maintenance and analytics: the modules buyers forget to ask about
Maintenance workflow is where tenant satisfaction lives. A good flow captures the request with photos, routes it to the right vendor, tracks status from open to closed, and notifies the tenant at each step. Managers want a board view of every open ticket across buildings. Vendors want a simple mobile link, not a login they will forget.
Analytics is the module that justifies the whole platform to ownership. The reports that get used are occupancy rate, rent roll, days-on-market per listing, lead source ROI so marketing spend is defensible, and an owner-ready monthly statement. Build these as real queries against live data, not a static dashboard that someone updates by hand.
How should you sequence a PropTech build?
Do not try to ship all six modules at once. We sequence it to get revenue or retention impact early.
- Start with the one module that wins deals for your specific business, usually listings for brokerages or payments for property managers
- Add the CRM or portal that the first module feeds
- Layer payments once the portal has active users
- Add maintenance and analytics once there is real data to act on
This is a standard scoping approach for any custom software development project, and it keeps the first release small enough to launch in two to three months instead of a year. If you are still deciding whether to build at all or buy an off-the-shelf platform, the trade-off usually comes down to how unusual your workflow is.
Build notes from real projects
A few things that consistently bite teams new to the vertical:
- Photos are heavy. Serve resized variants from a CDN, never the original 8MB upload, or your listings page will fail Core Web Vitals
- Timezones matter for rent due dates across US states and international portfolios. Store everything in UTC and convert at display
- MLS licensing has display rules. You can be forced to remove listings or add attribution, so design the listing template to handle required disclaimers
- Owners and tenants need different mobile experiences. A responsive web app covers both early, then a native app makes sense once volume justifies it, which our mobile app development team scopes separately
If you are weighing whether to build a PropTech platform or extend what you already run, contact us with your current stack and we will tell you which modules are worth building first and which you can buy.