Real Estate CRM for Agents: Build vs Buy, and What to Build First

Most agents and small teams should buy a real estate CRM: a subscription costs less than any build and is ready today. Build when the CRM is your product, or when your lead routing, brokerage structure or document process is the part no product handles. If you build, start with lead capture and routing, then agent dashboards, then documents, and leave MLS and marketing automation for later.

This guide is for brokerage owners, team leads and PropTech founders deciding whether custom software is worth it. RAITHub builds custom software, so the "buy" advice is given against our own interest where it applies. The build order comes from BlockEstate, a multi-tenant listing and inquiry platform RAITHub built, whose core is lead routing, agent dashboards and a document workflow. BlockEstate has no MLS integration, and nothing here claims one.

Should a real estate agent build a CRM or buy one?

Buy, unless one of three things is true: the software is what you sell, your structure is something CRMs model badly, or your process is your competitive edge.

Your situation	Usually the better fit	Why
Solo agent or a team under about 15	Buy	Lead capture, follow-up and calendars are solved problems
A brokerage with several offices that must not see each other's leads	Custom, or a product built for multi-office isolation	Isolation is architecture, not a permission setting
Routing rules that depend on your own data: area, language, property type, workload	Custom routing, possibly beside a bought CRM	Routing is where leads are won or lost
A PropTech startup selling a CRM or a lead platform	Custom	You need to own the product, data model and roadmap
Documents moving between agent, client and back office with approvals	Custom workflow, or a document tool integrated with your CRM	Each document needs an owner and a state
You mainly want drip emails and a mobile app	Buy	Those are the most mature parts of existing CRMs

There is a middle path worth considering first: keep a bought CRM for contacts and follow-up, and build only the piece that is yours, such as a routing service or a document workflow that talks to it through its API.

What does a bought real estate CRM cost over three years?

Less than most founders expect, which is why buying usually wins. As one published example, Follow Up Boss lists its Grow plan at $69 per user a month, Pro at $499 a month with 10 users included, and Platform at $1,000 a month with 30 users, with lower prices when billed yearly (Follow Up Boss pricing, checked on 29 September 2026). That is one vendor's list price, not a recommendation, and other products price differently.

Team (illustrative)	Plan at list price, billed monthly	Per year	Over 3 years
3 agents	Grow: 3 × $69	$2,484	$7,452
10 agents	Pro: $499 with 10 users	$5,988	$17,964
30 agents	Platform: $1,000 with 30 users	$12,000	$36,000

A custom first release costs more than the three-year subscription for small teams, and it also needs hosting, maintenance and someone to own it. So the question is never "is custom cheaper?" It is "what does the gap in the bought tool cost us?" Count leads that went to the wrong agent, deals slowed by document chasing, and staff hours spent copying data between tools. If that figure is larger than the build, custom is worth pricing.

If you build a real estate CRM, what should you build first?

The path a lead takes, in order: capture it, route it, show it to the agent, then move the documents. That is the order BlockEstate was built in, and its MVP shipped in 6 weeks on Next.js, TypeScript, Postgres and Prisma.

1. Lead capture. Every inquiry, from listing pages, forms and portals, lands in one table with its source, the listing it came from and a timestamp. Duplicates are merged on contact details, not left for agents to notice.
2. Lead routing. Rules decide who gets the lead: the listing agent, an area specialist, or the next available agent in round-robin. Routing runs on the server, where it can be tested, and every assignment is recorded.
3. Agent dashboards. Each agent sees their own leads, what is overdue, and the next action. A team lead sees the team; a brokerage owner sees offices. Nobody sees another brokerage's data.
4. Document workflow. Offers, IDs, agreements: each document has an owner, a state and a history. BlockEstate's document workflow treats a document as a record that moves between people, not a file in a shared folder.

Pipeline stages, reminders and reports come next, once the team is using the first four every day. The listing side of the same platform is covered in how to build a real estate marketplace, and the BlockEstate architecture is on the BlockEstate case study.

How does lead routing work in a custom real estate CRM?

As a small, tested function in the database layer: find the right pool of agents, pick one fairly, and record the assignment in the same transaction so two leads arriving together cannot both go to one agent by accident. A minimal round-robin in PostgreSQL:

-- Assign a new lead to the next available agent in its brokerage.
-- FOR UPDATE SKIP LOCKED stops two concurrent leads picking the same agent.
WITH next_agent AS (
  SELECT id
  FROM agents
  WHERE brokerage_id = $1
    AND accepting_leads
  ORDER BY last_assigned_at NULLS FIRST
  LIMIT 1
  FOR UPDATE SKIP LOCKED
), touched AS (
  UPDATE agents
  SET last_assigned_at = now()
  WHERE id = (SELECT id FROM next_agent)
  RETURNING id
)
INSERT INTO lead_assignments (lead_id, agent_id, assigned_at, rule)
SELECT $2, id, now(), 'round_robin' FROM touched
RETURNING agent_id;

Real rules layer on top: the listing agent first, then area or language matches, then round-robin as the fallback, with a timeout that reassigns a lead nobody has touched. Each rule is a branch with a test, and the rule column records why each lead went where it did, which is the first question a team lead asks when a lead is lost.

How do you keep each brokerage's leads separate?

Put the tenant boundary in the database, not in each screen. On a multi-tenant CRM, every lead, contact and document carries a brokerage ID, and every query is filtered by it automatically. PostgreSQL row-level security enforces that even when a developer forgets a WHERE clause; the patterns are in the PostgreSQL row-level security guide. If you already have a CRM where agents can see the wrong data, start with users can see other tenants' data.

What can wait until after the first release?

• MLS and IDX feeds. Access is granted by each MLS under its own rules, usually through a participating broker, so it comes after approval, not before. RAITHub has no live MLS integration to show; the process is explained in the MLS and IDX integration guide.
• Marketing automation. Drip campaigns are where bought CRMs are strongest. Integrate one rather than rebuilding it.
• A native mobile app. A responsive web app works on agents' phones from day one. RAITHub builds web applications and does not offer native mobile app development.
• AI lead scoring. It needs months of your own outcome data first. Record every lead's source, response time and result from day one so the data exists when you want it.

How does a CRM connect to property management?

Through the handover from "deal closed" to "tenancy starts". For agencies that also manage rentals, the CRM's closed deal becomes a lease, a tenant and a rent schedule. Keep them as separate modules sharing one contact record, rather than stretching the CRM to cover rent. What small landlords need on that side is set out in property management software for small landlords, and the wider picture is in the PropTech software development guide.

Why RAITHub for a real estate CRM

• The core has been built. BlockEstate's lead routing, agent dashboards and document workflow run on a multi-tenant architecture where each brokerage is isolated. Its MVP shipped in 6 weeks.
• The property side too. PropDesk, a property management platform RAITHub built, has Stripe rent collection, 4 user roles and 1,024 automated tests.
• Straight answers on MLS. RAITHub will tell you on the first call that it has no shipped MLS integration, and that your MLS's access decision comes first.
• Fixed scope. A free 15-minute technical audit, then a written fixed quote. You own the code; an NDA is standard.

When to buy a CRM instead

• Your team is small and your process is standard. Buy. A subscription will cost less than a build for years.
• You mainly need follow-up emails, texting and a phone app. Those are mature features in existing products.
• A live MLS feed is the core of the product and you need proof of shipped integrations. Choose an approved IDX vendor or a firm with live integrations on your MLS.
• You want developers placed in your team under your management. RAITHub offers fixed-scope builds and dedicated teams, not staff augmentation.

For a first release, the MVP development service explains how a fixed-scope build works, and the real estate industry page covers what RAITHub builds for PropTech. When you are ready, book the free 15-minute technical audit with your team structure, where leads come from, and the part your current tool gets wrong.

Last reviewed: 29 September 2026. Vendor pricing checked on 29 September 2026.

Frequently asked questions

Should I build my own real estate CRM?

Usually not. Build only if the CRM is your product, if you run several offices whose leads must stay separate, or if your routing or document process is something no product handles. Otherwise a subscription is cheaper and ready today.

How much does a real estate CRM cost?

Published list prices vary by vendor. As one example, Follow Up Boss lists $69 per user a month on Grow, $499 a month for 10 users on Pro and $1,000 a month for 30 users on Platform, billed monthly, as checked on 29 September 2026.

What features should a custom real estate CRM have first?

Lead capture, lead routing, agent dashboards and a document workflow, in that order. Pipeline reports, marketing automation, MLS feeds and AI scoring can follow once agents use the core every day.

How long does it take to build a real estate CRM?

A focused first release can take about 6 weeks: BlockEstate's MVP, with lead routing, agent dashboards and document workflow, shipped in 6 weeks. A broader product takes longer and keeps growing after launch.

Can RAITHub integrate MLS data into my CRM?

RAITHub has no shipped MLS integration. MLS access is granted by each MLS under its own rules, so confirming access comes first. Bring your MLS name to the audit call and RAITHub will tell you what it involves.

Can I keep my current CRM and build only part of it?

Often that is the smartest option. A custom routing service or document workflow can sit beside a bought CRM and exchange data through its API, so you pay to build only what makes you different.