Lead capture and routing
Portal leads, IDX inquiries, open house sign-ins, referrals and website chats land in one queue. Your rules assign them by area, price band, language or who is on duty, and reassign when nobody answers.
For brokerages, agent teams and property managers whose lead flow, listing data and closing steps no longer fit a subscription CRM. We check first whether you should buy one instead, then build what a product cannot: MLS data, routing rules, deal steps and commission splits.
A custom real estate CRM is a contact and deal system written for one brokerage, team or property manager. It takes leads from your sources, routes them by your rules, tracks each deal through your steps to closing and reads listing data from your MLSs. You own the code and the records, with no fee per seat.
Most agents should not build one. Between them, Wise Agent, Follow Up Boss and Zoho CRM already sell lead routing, drip email, deal tracking and commission reports by the month. A build earns its cost only when the way your office works is what those products cannot hold, so this page starts with the arithmetic.
One sign means configure your current product harder. Two or more means a build deserves a written scope.
Three products cover most of what a brokerage asks for. The table uses only what their own pages said when we read them on 13 October 2026. Firms that build one to order are compared in our ranking of custom CRM development companies.
| Option | What its own site offers | Published price | Fits when | Watch for |
|---|---|---|---|---|
| Wise Agent | Lead rules, drip campaigns, transaction checklists and portals, commission reporting | $49 a month for up to five people on a shared login; custom from 15 agents | A solo agent or small team that wants one tool this week | Separate logins cost $20 a month each |
| Follow Up Boss | Lead distribution by round robin, price or ZIP code; more than 250 integrations | $69 per user a month; $499 for 10 users; $1,000 for 30, then $20 per user | A team that lives on fast follow-up | On the per-user tier, calling costs $39 per user extra |
| Zoho CRM, configured | Lead scoring, territory assignment, drip email, lease expiry tracking, add-ons such as IDX Broker and commission management | Not read for this page | You want a general CRM shaped to your office, without owning code | Zillow leads arrive through Zapier, one more service to run |
| Custom build | A firm such as Digital Heroes builds it to your written scope | Our focused first versions typically cost $40,000 to $150,000 | The workflow is your edge, or seat fees pass the build | Months before first use; you fund hosting and upkeep |
Zoho's real estate page shows a middle path: its customer stories include an estate agency that shaped Zoho into a bespoke agency CRM, and a brokerage whose CRM a partner built on top of Zoho.
Follow Up Boss prints every tier, so it is the cleanest test. For each team size we took its lowest list price on monthly billing over five years. On the custom side we added the 10 to 20 percent a year that the GoodFirms 2026 cost survey puts on upkeep after launch.
| Agents | Lowest tier a month | A year | Five years |
|---|---|---|---|
| 10 | Pro, $499 | $5,988 | $29,940 |
| 25 | Platform, $1,000 | $12,000 | $60,000 |
| 40 | Platform, $1,200 | $14,400 | $72,000 |
| 100 | Platform, $2,400 | $28,800 | $144,000 |
| 250 | Platform, $5,400 | $64,800 | $324,000 |
| Custom, $40,000 build | No seat fee | $4,000 to $8,000 upkeep | $60,000 to $80,000 |
| Custom, $150,000 build | No seat fee | $15,000 to $30,000 upkeep | $225,000 to $300,000 |
Our reading: seat fees alone pay for a build at the bottom of our range somewhere between about 20 and 50 agents, and for one at the top only between about 170 and 230. Yearly billing takes two months off each Follow Up Boss year, which pushes both points higher.
The custom figures also leave out hosting and the services you still pay for, such as texting, e-signature and any MLS fee. Below those sizes, build for the workflow, never to escape the subscription. Our build vs buy calculator runs the same comparison on your own seat count.
A real estate CRM is three systems behind one sign-in: a lead engine, a listing layer and a deal tracker. Leave one out and agents go back to the spreadsheet for it. Here are the parts to scope, in the order a lead meets them; our custom CRM development page covers the same ground for any sales team.
Portal leads, IDX inquiries, open house sign-ins, referrals and website chats land in one queue. Your rules assign them by area, price band, language or who is on duty, and reassign when nobody answers.
Every call, text, email, showing and saved search on one timeline, duplicates merged on arrival, so the next agent knows what the last one promised.
Drip email and text triggered by what a contact does, such as viewing a listing again, and halted the moment they reply, book or opt out.
Your own stages from offer to closing, dated tasks for each contingency and document, and reminders before a deadline rather than after it.
Splits, caps, team overrides and referral fees worked out from the closed deal, so disbursement and the agent's statement share one number.
Pipeline value, lead source return, speed to first contact and agent production, read from the records agents work in, not a Monday export.
Agents see their own leads, team leads their team, the broker every office, and every change is logged with who made it and when.
Owners, tenants, renewals and maintenance requests on the same contact records, so a landlord who later sells is already known. Scoped only when you manage property.
Agents judge a CRM by whether it already knows what they know, and that starts with the MLS. The RESO Web API is the standard way listing data now moves. It runs on OData, RESO no longer supports the older RETS, and RESO says MLSs owned and operated by REALTOR associations must offer production access through the Web API under National Association of REALTORS rules.
The data does not come from RESO or from us. Each MLS grants access once your brokerage agrees to its data use and licensing policies, and its software provider or staff issue the credentials. File that application during discovery: the MLS's approval time is the one date nobody on the build controls.
| Connection | What it gives agents | Who has to approve it | Build note |
|---|---|---|---|
| MLS listing data | Live status, price and photos on each contact's saved listings | Each MLS, under its own license | Where the license allows, a replicated copy kept current, not a query per page view |
| IDX website | Saved searches and inquiries arriving as leads with history | Your MLS's IDX rules and your website provider | Match an existing contact before creating a new one |
| Portal leads | Zillow and Realtor.com inquiries in the same queue as every other lead | Each portal's lead program terms | Keep the source on the record so source reports stay honest |
| Email and calendar | Two-way sync with Google or Microsoft 365; showings on the calendar | Your workspace administrator | Log the touch on the contact, never copy whole inboxes |
| Texting and calls | Texts and call outcomes logged to the contact | Your texting provider, and each person texted | Every send checks the consent ledger first (section 05) |
| E-signature | Offers and listing agreements signed inside the deal | Your e-signature account | File the signed copy against the right transaction |
| Accounting | Commission disbursements without retyping | Your accountant and the accounting system | Send each split once; never let two systems calculate it |
Discovery maps each of these before a fixed price, and anything added later needs a written change request stating its cost and its effect on the date. More on how we connect systems is on our API and integration page.
We are engineers, not your lawyers; your counsel decides which rules apply to which messages. A CRM's job is to make that answer hard to break by accident, and two federal rules shape real estate CRMs more than any feature request.
The FCC's rule at 47 CFR 64.1200 requires prior express written consent for telemarketing calls and texts sent with an autodialer or a prerecorded voice, and lets a person withdraw consent in any reasonable way. A reply such as stop or unsubscribe, or any of the other opt-out words the rule lists, counts outright, and a withdrawal must be honored within ten business days at most.
So a CRM that texts needs a consent ledger: which number agreed, to what, when and where. Every automated send checks it first, and a reply that reads like a refusal stops every sequence for that number. The rule allows one plain confirmation text afterwards, with no marketing in it.
The Fair Housing Act at 42 USC 3604(c) makes it unlawful to publish any notice, statement or advertisement about selling or renting a dwelling that indicates any preference, limitation, or discrimination based on race, color, religion, sex
, and the same subsection goes on to name handicap, familial status and national origin.
A CRM that segments buyers can drift there by accident. The safer design segments on property and behavior, such as price band, area and saved searches, keeps no protected trait as a filter, and puts a review step in front of campaign and listing copy.
Agents leave, and their contacts should not leave with them. Access follows role and office, exports are limited to the roles that need them, and the audit log records who opened or changed each record.
Start with the market. GoodFirms surveyed more than 100 software firms for its 2026 cost report: most custom projects fall between $30,000 and $100,000, firms in Western markets quote about $50,000 to $250,000 for a medium build, and upkeep after launch averages 10 to 20 percent of the build each year.
Our own range for custom software: a focused first version typically costs $40,000 to $150,000, and complex enterprise platforms $250,000 to $500,000 or more, depending on scope, integrations, security and data migration. Your fixed price comes after discovery, against a written scope.
| Cost driver | Why it adds work | How to keep it down |
|---|---|---|
| Number of MLSs | Each has its own license, field quirks and display rules | Launch on your main MLS, add the next in a later cycle |
| Roles and offices | Every role multiplies the access rules and the testing | Agree three or four roles before design starts |
| Commission rules | Caps, overrides and referral fees each need their own tests | Bring last year's real splits as the test cases |
| Contacts to migrate | Duplicates, missing owners and old custom fields | Decide what to drop before mapping what to keep |
| A mobile app for agents | A second interface to design, test and ship to the stores | Start with a phone-friendly web app; build native apps in React Native once agents ask |
On time: discovery takes two weeks. After it, a first version of custom software usually takes 8 to 12 weeks to build and a production platform 16 to 28. The MLS license approval runs alongside, outside that schedule.
For a planning range, use our custom software cost calculator; a scoping call replaces the range with a written quote.
A fixed-bid build with us starts the same way every time, as on any custom software development project. What changes for a brokerage is where the real estate work lands.
Repositories and cloud accounts sit in your name and on your billing from the start, and our engineers are collaborators you can remove.
None of these three client builds is a real estate CRM, and we would rather say so. Each is shown with the client's permission, none has a published results figure, and each holds a part a brokerage CRM is made of.
The whole platform and its website: shift rosters, leave requests through three levels of approval with a speciality conflict check, certification expiry reminders, duty screens and an audit history of every change.
The CRM part: six roles each limited to its own scope, layered approvals, and reminders before something lapses, as an agent's license does.
A browser design editor, CSV variable-data print jobs, an order status history, PayFast checkout with its payment webhooks, transactional email and an admin panel with three roles, on Next.js 15, React, TypeScript and Supabase.
The CRM part: a status history on every order, as every deal needs, and outside events landing on the right record by webhook.
The athlete and trainer mobile apps, in React Native with Expo on Supabase. Athletes find trainers, book sessions and answer offers; trainers run their schedule, send offers and follow their earnings.
The CRM part: bookings, offers, shared chat and notifications on a phone, the shape of an agent working a buyer between showings.
One more you can test today: the Live Chat on this site, which we built and run. Cloudflare Workers serve its API and PostgreSQL on Supabase stores every conversation, and our CTO leads that work as he leads code review on our CRM builds.
For the wider picture of listing platforms, tenant portals and schedulers, see our real estate software development page.
Two of the people behind our CRM builds. Each line under a name is quoted from that person's published profile, which the name links to.
Divyansh “leads the architecture and code review of Digital Heroes API and integration, CRM and AI chatbot builds”.
“Navya brings five years of project management to Digital Heroes healthcare, wellness, logistics, real estate, manufacturing, retail and education builds, running sprint planning, scope and client communication from kickoff to launch.”
Founded 2017. Headquarters in New York and Delhi; engineering in Delhi and Lucknow, on hours that overlap New York. D-U-N-S 650878346 for procurement teams.
On Clutch, Digital Heroes is rated 5.0 from 66 verified reviews, checked on 13 October 2026. Who signs, which entity you contract with and how to check each claim are set out on our custom software development company page.
A polished demo says little about whether a CRM will survive your MLS, your agents and year two. Ask every firm on your shortlist these six questions, us included.
The first four questions are worded the way people search for them. The last two are questions that pages ranking beside this one answer, with our own answers.
With us, a focused first version of custom software typically costs $40,000 to $150,000; GoodFirms' 2026 survey finds Western firms quoting about $50,000 to $250,000 for a medium build. For a real estate CRM, the number of MLSs, roles, commission rules and contacts to migrate move the price most, and upkeep adds 10 to 20 percent a year. The cost section has the detail.
For a brokerage, the one that matches how your offices actually run. Follow Up Boss is built around lead follow-up for teams and prints a tier for 30 users at $1,000 a month. Offices that want a general CRM shaped to their process look at configuring Zoho CRM. A custom build fits when your deal steps, splits or models are what the products cannot hold; the seat fee table shows when it pays.
Yes, by three routes. Configure a platform you rent, which Zoho's own real estate customers have done. Assemble one on a no-code tool, which suits a small team with simple rules. Or commission a build you own. The hard parts are the same on every route: an MLS license, a consent record for texting and a clean contact model. Our no-code vs custom calculator compares the second and third over two to five years.
For a single agent, almost always a product, not a build. Wise Agent's CRM plan was $49 a month on 13 October 2026, covering up to five people on a shared login, and Follow Up Boss charged $69 per user a month. Try two on their free trials with your real leads for two weeks and keep the one you still open each morning.
With us, two weeks of discovery, then usually 8 to 12 weeks for a first version of custom software and 16 to 28 for a production platform. For a real estate CRM, watch the MLS license approval: each MLS sets its own pace, so apply during discovery.
Whatever your team can maintain after we leave. For a real estate CRM our usual pick is Next.js and React for the web app, Node.js for the API and background jobs, PostgreSQL on Supabase with row-level security for the records, and React Native when agents need a phone app. Listing data arrives through the RESO Web API, which is built on OData.
Last reviewed .
In 30 minutes we go through your lead sources, your MLSs and the steps your deals take. If the work suits us, a written scope and quote follow within 48 hours, and if a product you can buy fits better, discovery is designed to say so.
Published .
Pinch, scroll or double-tap to zoom · drag to pan
Where should we send the proposal?
Please enter your name and a valid email.
Any faster way to reach you? Optional.
Please fill in the one you picked.