Insights · 13 min read
A real estate CRM is more than a contact list. Here are the modules, MLS and IDX integrations, and commission handling that decide the build, and what it costs.
By GGP Editorial
Most real estate teams run on a spreadsheet, a shared inbox, and the one agent who remembers everything. That works until a listing goes under contract and nobody can say which buyer was followed up with and when. A real estate CRM is the system that replaces that memory with a pipeline, but it only pays for itself if you build it around how agents actually work instead of a generic sales funnel.
I write this from the vendor side. GlobeSoft is a software company founded in 2018 with 40-plus engineers and more than 300 delivered projects, and we have built property management, leasing, and client-management systems for real estate clients across several markets. This guide covers what a real estate CRM actually is, the modules that matter, the integrations that decide the project, and what it costs to build one agents will use.
If you are still deciding whether to build a CRM at all, start with our piece on custom CRM software development: when building beats buying.
A generic CRM stores contacts, deals, and activity. A real estate CRM stores listings, leads, showings, offers, and commissions, and the relationships between them are different. A lead in a normal CRM becomes a won or lost deal. A lead in a real estate CRM can be a buyer on one listing, a seller on another, and a landlord on a third, all at the same time, each with its own pipeline and its own commission math.
That one difference changes the data model. Force real estate onto a generic sales CRM and agents will keep a second system on the side, and the second system becomes the real one. The CRM has to mirror the way a brokerage already thinks, or agents quietly abandon it.
There are also three surfaces to plan for, not one. The agent surface is where a single agent manages their listings, leads, showings, and follow-ups. The broker or admin surface is where the office tracks every agent's pipeline, runs reports, and handles the commission splits. The client surface is where a buyer or seller sees saved properties, scheduled showings, and documents to sign. Most teams spec the agent screen in detail and treat the other two as afterthoughts, which is backwards. The broker surface is where you make money decisions, and the client surface is where the buyer experience lives.
The visible features are the easy part. Here is a realistic split between what a real estate CRM needs first and what can wait.
| Must have in v1 | Can wait |
|---|---|
| Contact and lead database | Predictive valuation models |
| Listing database with search and filters | Full marketing automation suite |
| Lead capture from web and portals | AI contract review |
| Lead routing and assignment | Automated CMA generation |
| Deal pipeline with stages | Team performance gamification |
| Showing scheduling and calendar | Native mobile app for clients |
| Task and follow-up reminders | Advanced analytics and forecasting |
| Email and SMS activity logging | Social media posting tools |
| Commission calculation | Open house check-in tools |
| Document storage and e-signature | Multi-language support |
| Admin console with agent reports |
The admin console is the module nobody demos and everyone needs. When an agent says a lead disappeared, or a commission split looks wrong, your office manager needs a screen that shows the lead, its owner, its stage, and who changed what. Without that screen, every dispute becomes an engineering ticket, and every dispute is about money.
Commission calculation deserves more attention than it usually gets. Real estate commissions are rarely a flat percentage. There is the listing side and the buying side, splits that change with tenure and production, referral fees, and caps. If the CRM stores only a final amount instead of the calculation, your accounting team will rebuild it in a spreadsheet on day two. Model the splits as data, not as a hardcoded formula.
A real estate CRM is only as good as the data flowing into it, and the integrations are where scope quietly grows. Here are the ones that matter.
Listing data. In the United States, listings live in multiple listing services, or MLSs. Two standards matter here. IDX, or Internet Data Exchange, lets brokers display MLS listings on their own website. The RESO Web API is the modern way to pull and sync that data; the older RETS standard is largely retired. If your product shows listings from an MLS, plan the feed integration early, because each MLS has its own access process, and the approval can take longer than the code.
Lead portals. Buyers arrive from Zillow, Realtor.com, and similar portals, often through a paid lead feed. That feed has to land in the CRM with the right routing, usually speed-to-lead matters more than anything else. A lead that sits for an hour goes cold.
Communication. Email and SMS logging, a dialer if your agents call from the CRM, and calendar sync for showings are table stakes. Plan automatic activity tracking instead of asking agents to log calls by hand. They will not.
Documents. E-signature is expected now, and the contract, disclosure, and buyer-agreement documents have to attach to the right deal. In the United States, a 2024 settlement by the National Association of Realtors changed some rules around agent compensation and buyer agreements, which is one reason a CRM now needs to track written agreements and negotiated compensation rather than assuming a standard split. The details vary by state and by market, and this is not legal advice, but the practical effect is that document and compensation tracking is no longer optional in the US.
Do not integrate everything. Pick the three or four integrations that decide whether agents adopt the product, and do those well before adding anything else.
A few things make real estate harder than a typical sales CRM build. The commission model is the real data model, and a brokerage with tiered splits, teams, referral networks, and caps cannot run on a generic CRM. The market is also fragmented: the rules, MLS structure, and document requirements in the US look nothing like those in Brazil, South Africa, or Singapore, so build the country-specific bits behind a layer you can swap rather than hardcoding them into the screens.
Most of this also applies to the adjacent property business. We wrote about the landlord side in property management software: features landlords actually use, and a real estate CRM often shares a client with that product even when the workflows are different.
There are three paths, and they suit three situations.
Buying an off-the-shelf real estate CRM gets you to market fast. You get a working product with the integrations handled, but you pay per user or per month and have little control over the roadmap. The commission and workflow rules are what the vendor decided, and that is usually where brokerages outgrow the tool.
Building custom gives you the data model, the commission rules, and the workflow exactly as your business needs them, at a higher upfront cost. This is the right call when the CRM is a product you sell, or when your commission and workflow rules are unusual enough that no off-the-shelf tool fits.
Extending an existing system means adding the real estate modules to the CRM or lead-tracking you already run. If you already use a general CRM, this is often the cheapest path: the contacts, activity, and pipeline already exist, and you are adding listings, commissions, and integrations.
The decision usually comes down to one question: is the CRM a product you sell to other brokerages, or a tool your own team uses? Answer that first and the scoping gets easier. If you are leaning toward building, how to define an MVP before hiring developers is the place to start.
Cost in a real estate CRM build is driven by four things, in rough order of impact.
Team. A real estate CRM needs a product manager, a designer, two or three backend engineers, one or two frontend or mobile engineers, and usually a part-time QA lead. Where the team sits changes the bill a lot. A senior engineer through a China-based team runs roughly $5,000 to $8,000 a month, against around $12,000 to $16,000 for the same role on a US salary. We break those numbers down in software development cost in China.
Integrations. The MLS or IDX feed, the lead portals, the e-signature, the dialer, and email all add real time, and each is a place where scope quietly grows. Feed approval timelines are the part nobody budgets for.
Commission and workflow rules. The more unusual your splits, teams, and referral structure, the more time goes into modeling them. This is the difference between a two-week CRM and a three-month one.
Data migration. If you are moving off an existing CRM, you have to map and clean years of contacts and deals, and it always takes longer than anyone expects.
As a rough guide, a focused real estate CRM with listings, lead capture, pipeline, showings, documents, and basic commission handling typically lands between $60,000 and $140,000. A full platform with MLS/IDX feeds, an agent and client portal, advanced commission engine, and reporting runs $150,000 to $350,000 or more. These are ranges, not quotes, and the only number that matters is the one from a scoped proposal. We wrote about getting a real number in how to estimate a custom software project.
A focused real estate CRM runs four to six months from kickoff to a limited launch. A full platform with listing feeds, client portal, and the commission engine to support a multi-office brokerage runs seven to eleven months. Plan a discovery phase before anyone writes code, a feed-approval process started early enough that it does not block launch, and a pilot with a small group of real agents before you roll it out office-wide.
Agents adopt or abandon a CRM in the first two weeks. If the pilot group is not using it by then, the product has a workflow problem, not a training problem.
AI has real uses in a real estate CRM, but they are narrower than the pitch decks suggest.
The useful ones are follow-up and routing. A model that scores leads and tells an agent which one to call first is valuable, and so is a system that drafts a follow-up message the agent can send. Transcribing a call and attaching the notes to the deal saves real time. Automated property recommendations are a standard feature buyers now expect.
The risky ones are anywhere a model makes a decision about a transaction or a contract. A valuation or a summary of a legal document that an agent relies on without reading is where harm happens. Keep the AI on routing, drafting, and matching, and keep a person in the loop for anything that touches the deal. If you want to understand where AI actually pays for itself in business software, start with how to add AI to existing business software.
Building the agent app before the data model. The commission and listing model is the product; the screens are a feature.
Treating MLS/IDX as a checkbox. Feed access and approval take calendar time, not coding time. Start the process before you write the first line of code, or launch slips by weeks.
Hardcoding the commission formula. Splits change. Put the rules in data and let an admin edit them, or your accounting team will keep a shadow spreadsheet forever.
Assuming agents will log activity manually. They will not. Build the integrations and the automatic tracking, or the CRM looks empty and gets abandoned.
Skipping the client portal. Buyers and sellers expect to see their saved listings, showings, and documents. If you force them to email for everything, you give the experience away to a competitor.
A focused CRM typically lands between $60,000 and $140,000. A full platform with MLS/IDX feeds, a client portal, and an advanced commission engine runs $150,000 to $350,000 or more. See where the money goes in a custom build for the breakdown.
Buy if you need to launch fast and can live with the vendor's commission and workflow rules. Build if the CRM is a product you sell, or your brokerage's splits, teams, and referral structure do not fit an off-the-shelf tool.
IDX lets brokers display MLS listings on their own website. If your product shows listings from an MLS, you need it, and the RESO Web API is the modern way to sync that data. Plan the approval process early, since it often takes longer than the code.
Four to six months for a focused CRM, seven to eleven for a full platform with listing feeds and a client portal. MLS feed approval and data migration are the two things that usually stretch the timeline.
Usually, and it is often the cheapest path. Adding listings, commission, and integrations to a CRM that already has contacts and a pipeline is a smaller job than building from nothing.
Listings, lead capture and routing, a deal pipeline, showing scheduling, document storage with e-signature, basic commission handling, and an admin console. Skip valuation models, contract AI, and gamification until you have real usage.
GlobeSoft is a software development company founded in 2018, with 40-plus engineers and more than 300 delivered projects for over 100 clients across the US, Brazil, South Africa, and Singapore. We build custom software, mobile apps, SaaS platforms, FinTech systems, ERP and CRM, and AI products on a stack that includes Java, Spring Boot, Go, Python, React, Vue, and Node. Our real estate work includes property management and leasing systems, so we know the workflows a brokerage product has to handle.
If you are planning a real estate CRM, a property platform, or a client-management system for your brokerage, talk to us about your project. Send us the rough idea and we will help you work through the build-versus-buy call, the integrations, the commission model, and what to ship first.
Tell us what you are building and where you are today. We typically reply within 24 hours.
