Skip to content
Nine-Phase AI Operating System

The most capable real estate CRM. $0 in license fees. AI built in from day one.

We take Twenty CRM — MIT-licensed, self-hosted — and build 10 custom real estate objects, an MCP server, WhatsApp integration, and full AI query on top of it. The result: a real estate CRM your competitors pay $9,600 to $36,000 per year to run. You pay hosting only.

Annual CRM Cost - 20-User Brokerage

HubSpot Sales Hub Professional $24,000/yr
Salesforce Sales Cloud Enterprise $39,600/yr
Zoho CRM Enterprise $9,600/yr
Bitrix24 Enterprise $4,700/yr
$0/yr
The Real Problem

Three reasons your current CRM is costing more than it delivers

Each one is fixable. Together they explain why your portal spend isn’t converting the way it should.
01

$24,000 a year for a contact database with a pipeline view

HubSpot Sales Hub Professional costs $100 per user per month. For a 20-agent brokerage, that is $24,000 per year — $96,000 over four years. The platform stores contacts, manages deals, and sends emails. It does not know what a Site Visit is. It does not have a Channel Partner object. It does not understand the relationship between a Builder Project, a Property Listing, and a Buyer’s Requirements. You have built workarounds for all of this. You call them “custom fields” and “workarounds.” You pay $24,000 a year for workarounds.

The consequence

The subscription is only the visible cost. The invisible costs: developer time to build real estate workarounds, manual data entry agents do because the CRM doesn’t auto-update from WhatsApp conversations, reporting that requires custom dashboards because property pipeline doesn’t map to a standard deal stage, and the AI layer you cannot build because the CRM API is too restrictive for real-time writes. The CRM was built for SaaS companies selling software. Not brokerages selling apartments.
$96,000 over 4 years — for a generic CRM with RE workarounds
02

Your CRM was not built for AI to live inside it

Your lead qualification AI runs on a separate platform. Your reactivation engine syncs data across via API every 15 minutes. Your call intelligence layer writes transcripts to a Google Sheet because the CRM API rate-limits bulk writes. Every time an agent qualifies a lead on WhatsApp, a human has to open the CRM and update the record. You have three systems where one should exist. Every sync is a point of failure. Every point of failure is data that disappears.

The consequence

AI that cannot write directly to the CRM does not work well. The reactivation engine that reads stale lead data recommends buyers who have already closed elsewhere. The call intelligence layer that cannot access the buyer’s full conversation history scores calls without context. The qualification AI that cannot check the CRM for existing records creates duplicates. Data integrity is not a technical detail. It is what determines whether the AI makes good decisions or bad ones.
Three systems syncing = three points of failure per transaction
03

Agents avoid updating the CRM because the interface requires effort

A field agent finishes a site visit at a Whitefield property at 5:30 PM. To update the CRM, they need to open the browser app, find the lead record, navigate to the visit log, fill in outcome, notes, and next step, and save. Instead, they make a mental note. The data is in their head by the time they get home. By next morning, it is partial. By the following week, two of the three visit outcomes are gone. The CRM shows the visit happened. It does not know what the buyer said or what happens next.

The consequence

A CRM that agents don’t update is a contact list with a pipeline view. Every coaching conversation is based on the data agents remembered to enter. Every reactivation message is sent with incomplete context. Every pipeline report understates active deals and overstates cold ones. The fix is not training agents to update the CRM. The fix is making the CRM update itself — from WhatsApp replies, from voice commands, from the AI agent the team already uses. The interface should not be a browser form.
Incomplete CRM data makes every AI decision less accurate

Why generic CRMs fail in real estate

"Generic CRMs were built for SaaS and e-commerce. Real estate has relationships generic CRMs cannot model."

A buyer has Requirements. Those Requirements match Property Listings. A Site Visit connects a Buyer, a Property, and an Agent in a single event. A Deal links a Property, a Channel Partner, and that Site Visit. A Partner Allocation ties back to the Developer’s Project. None of this fits into a standard “Contact → Deal → Company” pipeline. Building it as workarounds on a generic CRM costs $24,000 a year and delivers a data model that breaks every AI phase that follows.
Custom data model

10 objects. 200+ fields. Built for how real estate actually works.

Every relationship in a real estate brokerage — buyer to property, property to deal, deal to channel partner, partner to developer — modeled as a native object. Not a workaround. Not a custom field on a Contact record.
Custom Object

Property Listings

74 fields · Links to 8 objects
Custom Object

Requirements

40 fields · Buyer's original brief
Custom Object

Site Visits

44 fields · Connects buyer + property + agent
Custom Object

Deals

31 fields · CP firm management
Custom Object

Channel Partners

74 fields · Links to 8 objects
Custom Object

Partner Allocations

Links deals + projects + CPs
Custom Object

Builder Projects

Developer project tracking
Standard Objects

People, Companies, Notes, Tasks, Workflows

Standard Twenty CRM objects — enhanced with RE links

How the objects connect

Buyer has Requirements

Every People record links to their structured requirement brief. AI matches against it on every new listing.

Requirements match Property Listings

Phase 9 reactivation runs this match in 1.2 seconds on every new property. Scored by budget, location, type.

Site Visit = Buyer + Property + Agent

One Site Visit record holds all three links plus GPS check-in, outcome, objections, and follow-up task.

Deals link Property + Partner + Visits

A Deal holds the full transaction context: which property, which channel partner, which site visits led to it.

Builder Project → Companies

Developer projects are linked to the builder company. Partner allocations, phase pricing, and listings all roll up to the project.

Tasks + Workflows run across everything

480 tasks, 2 active workflows. Any object can have tasks attached. Automations trigger across the full data model.

Complete Relationships

See everything connected end-to-end. Buyer to property to visit to deal to partner to developer — one record trail.

AI That Actually Works

AI operates on structured business context, not flat contact records. Every phase answers from real data.

Manager Visibility

Real-time pipeline by project, partner, and agent. No custom reports. Query in plain language and get the answer.
MCP Server · Model Context Protocol

Your CRM becomes an AI agent's brain.

MCP (Model Context Protocol) is an open standard that lets AI assistants — Claude, ChatGPT, and any compatible agent — connect directly to external tools and data sources. When we configure Twenty CRM as an MCP server, your entire CRM becomes readable and writable through natural language, from any AI interface.
 
No dashboards. No report builders. No manual data entry. Your team lead types a question in Claude, the MCP server reads from the CRM, and the answer comes back in seconds. Your agent replies to a WhatsApp message, the AI processes it, and the CRM updates automatically.

Buyer has Requirements

Every People record links to their structured requirement brief. AI matches against it on every new listing.

Buyer has Requirements

Every People record links to their structured requirement brief. AI matches against it on every new listing.

Buyer has Requirements

Every People record links to their structured requirement brief. AI matches against it on every new listing.

Buyer has Requirements

Every People record links to their structured requirement brief. AI matches against it on every new listing.
MCP Query Demo · Live CRM Access via Claude
"Pull all active leads in Dubai who have budget above AED 1.5M, haven't had a site visit in 60 days, and were originally enquiring about off-plan inventory"
  • Omar Al-Rashidi · AED 2.1M budget · Off-plan JVC · Last contact: 68 days ago · GV eligible
  • Fatima Al-Hassan · AED 1.8M budget · Off-plan Business Bay · Last contact: 71 days ago
  • Arjun Mehta · AED 1.6M budget · Off-plan Palm · Last contact: 84 days ago · GV eligible

...and 5 more. Create follow-up tasks for all 8?

✦

All 8 follow-up tasks created in CRM · Assigned to senior agents · Flagged for GV conversation

Screenless CRM

The CRM without a screen. Update it from WhatsApp. Query it from Claude. Let it run itself.

When the CRM becomes an MCP server, every AI interface becomes a CRM interface. Your field agents update records by replying to WhatsApp messages. Your team lead queries the pipeline through Claude. Your AI agents write back to the CRM on every interaction — automatically.
WhatsApp Field agents · Auto CRM update
Agent
System Site visit with Priya Mehta at Sterling Park completed. How did it go? Agent · Ravi Very interested. Wants 3-BHK. Concerned about parking. Coming back Saturday with husband. Got it. Updated Priya's record: outcome = Interested, objection = parking, follow-up = Saturday viewing. Confirmation sent to Priya.
CRM updated automatically. Agent never opened a browser.
✦
Claude Team lead · Pipeline queries
Lead
Team Lead · Sumit Which deals have been at "Offer Sent" for more than 2 weeks without a response? Claude + CRM 4 deals. Rajesh Kumar (17 days, Kondapur 3-BHK), Omar Hassan (19 days, JVC off-plan), Meera Patel (21 days, Gachibowli 2-BHK), Vinod Sharma (15 days, Hitech City). Want me to create follow-up tasks for all 4? Yes. Mark all as urgent and assign to senior agents. Done. 4 urgent follow-up tasks created and assigned. Agents notified by WhatsApp.
CRM read and written. No dashboard opened.
>_
ChatGPT Ops · Workflow automation
Ops
Operations Book a site visit for Meera Patel at Sterling Park Phase 3 on Friday at 11 AM and send her a WhatsApp confirmation. ChatGPT + CRM Site visit created in CRM: Meera Patel, Sterling Park Phase 3, Friday 10 June, 11 AM. Agent Ravi assigned based on availability. WhatsApp confirmation sent to Meera. Calendar invite created. Also add a note that she's allergic to dust - new construction may be a concern. Note added to Meera's People record and this visit. Agent briefed via WhatsApp before the visit.
3 CRM actions executed from one conversation.

No limit on customization

Because the code is open-source and self-hosted, you can add any field, create any object, build any MCP endpoint, and automate any workflow — without waiting for a vendor to add it to their roadmap. The CRM grows with your operation, not with the vendor's priorities.

Automatically updated by every AI phase

Phase 5 qualification writes to leads. Phase 8 call intelligence writes transcripts and scores to contacts. Phase 9 reactivation writes outreach events and responses to lead history. By the time a human looks at any record, it is already current — without any agent having touched it.

Connect from any AI that supports MCP

Claude, ChatGPT Enterprise, Cursor, any MCP-compatible AI client. As the MCP ecosystem grows, every new AI tool that supports the standard inherits access to your CRM. You are not locked into one AI vendor's capabilities.

Your data. Your server. Always.

Self-hosted on your infrastructure. No query to an AI assistant passes through a third-party CRM server. No conversation between your team and Claude is stored by a CRM vendor. The data stays where you put it — on a server you control.
Head-to-head comparison

The most capable real estate CRM. At a fraction of the cost.

Each table compares Twenty CRM + SuperteamAI against one competitor directly. Pricing based on a 20-user brokerage at published rates.
Twenty CRM + SuperteamAI vs HubSpot Sales Hub Professional
Factor HubSpot Sales Hub Pro Twenty CRM + SuperteamAI
Annual license cost (20 users) ✗$24,000/yr
$100/user/month · No RE objects
✓$0/yr
Hosting only · ~$1,200-3,600/yr infra
Real estate objects ✗Generic: Contact, Deal, Company only. Property listings require custom fields stacked on Deals. Site visits don't exist as a native concept. ✓10 native RE objects: Property Listings (74 fields), Requirements, Site Visits, Deals, Channel Partners, Partner Allocations, Builder Projects - all pre-built.
AI native integration ✗HubSpot Breeze AI add-on. Separate cost. Answers from CRM data but requires HubSpot's own AI - not MCP compatible. ✓MCP server included. Claude, ChatGPT, and any MCP-compatible AI can read and write to the CRM directly in plain language.
WhatsApp integration ✗Available via third-party integration (extra setup, extra cost). Not a native object - conversations don't write to CRM records. ✓WABA registered under client entity. Every WhatsApp conversation writes to the correct CRM record automatically.
Data ownership ✗HubSpot servers. Export formats limited. Data hostage to subscription continuity. ✓Self-hosted on your server. MIT open-source license. You own the code, the data, and the infrastructure.
Screenless / MCP access ✗No MCP server. HubSpot API requires developer setup per use case. Not queryable by external AI agents. ✓Full MCP server. Query or update the CRM from Claude, ChatGPT, or WhatsApp in plain language - no developer required.
User limit ✗Per-seat. Every new agent is $100/month. 5 agents = $500/month more per year. ✓Unlimited users. Add any number of agents, admins, and leadership without changing the hosting cost.
Twenty CRM + SuperteamAI vs Bitrix24 Enterprise
Factor Bitrix24 Enterprise Twenty CRM + SuperteamAI
Annual license cost ✗$4,788/yr
$399/month · 250 users · Vendor cloud
✓$0/yr
Hosting only · Self-hosted · Open source
Real estate customization ✗Extensive but complex. RE objects must be manually built using custom entity builder. No pre-built property or site visit model - requires significant developer setup time. ✓10 RE objects pre-built and pre-configured. Data model matches how real estate actually works - no custom build required. Operational from day one of Phase 3.
AI and MCP ✗Bitrix24 AI is a separate partner product. No MCP server. External AI agents cannot read or write to Bitrix24 natively. ✓MCP server included as standard. Any MCP-compatible AI assistant queries and updates the CRM in real time.
WhatsApp ✗Available via Bitrix24 Open Channels. Conversations visible in CRM but limited automatic write-back to deal and contact records. ✓WABA native. Every conversation writes back to the correct contact, lead, and visit record automatically. No manual sync.
Data ownership ✗Cloud-hosted by default. On-premise available - but on-premise Bitrix24 license costs $24,990 one-time. Not open-source. ✓Open-source (MIT). Self-hosted on any cloud provider of your choice. No one-time fee. No vendor dependency.
Setup complexity ✗Significant setup time to configure RE workflows. Many brokerages find the interface overwhelming and adoption suffers. ✓RE objects pre-configured. Team onboarded in one session. Interface is clean and purpose-built for property pipeline management.
Twenty CRM + SuperteamAI vs Salesforce Sales Cloud Enterprise
Factor Salesforce Enterprise Twenty CRM + SuperteamAI
Annual license cost (20 users) ✗$39,600/yr
$165/user/month · Vendor hosted
✓$0/yr
Hosting only · MIT open source
Real estate objects ✗Available via Salesforce Financial Services Cloud or AppExchange RE apps - both require additional licensing ($50-150/user/month extra) and 3-6 months implementation. ✓Pre-built in Phase 3. Property Listings, Site Visits, Requirements, Deals - live within the 6-10 week build timeline.
AI (Einstein vs MCP) ✗Salesforce Einstein AI: $75/user/month additional = $18,000/year more. Closed to external AI agents. No MCP compatibility. ✓MCP server at no additional cost. Use Claude, ChatGPT, or any MCP-compatible AI for free. Not locked to one AI vendor.
Implementation time ✗6-18 months for full Salesforce RE implementation with developer team. AppExchange RE apps require further customization. ✓Phase 3 complete in 6-10 weeks. RE objects pre-configured. Team trained before go-live.
Total cost, year 1 (20 users + AI) ✗$57,600+/yr
$39,600 license + $18,000 Einstein AI
✓Build fee only
One-time phase cost + hosting. No annual license.
Screenless / voice access ✗Salesforce Voice available but requires Salesforce Service Cloud license (additional). No MCP support. External AI integration requires custom Apex development. ✓WhatsApp, Claude, ChatGPT - all query and update the CRM natively via MCP. No custom development required.
Our AI agents can also connect with

Already on another CRM? Our AI works with yours.

If your existing CRM passes our API capability audit, every AI phase we build — qualification, reactivation, call intelligence — connects directly to it. You keep your interface. Our AI keeps working underneath it. Below are the CRMs our agents can operate with, their API capability level, and the caveats to know before the audit.

Salesforce Headless / CRM 360

No limit on customization
Salesforce's REST and SOQL API provides field-level read/write, real-time webhooks, and full custom object access. The strongest API of any closed CRM. Our AI agents can run all 9 phases on top of Salesforce if configured correctly.
Caveat: API rate limits at standard tier require careful phase design. Einstein AI licensing costs not eliminated — you still pay Salesforce.

Zoho CRM

Good API Access
Zoho's REST API supports field-level writes, webhook triggers on record changes, and custom module creation. Suitable for lead qualification, call intelligence, and reactivation phases. Zoho Analytics can run alongside for reporting.
Caveat: Rate limits on bulk operations may affect Phase 9 reactivation scans at high lead volumes (>5,000 records).

HubSpot CRM (Free / Pro)

Partial API Access
HubSpot's API supports lead ingestion and most read operations well. Write access to custom objects is Enterprise-only. If you are on Professional tier or below, Phase 5 and Phase 9 write-back may require workarounds.
Caveat: Custom objects require Enterprise plan ($24,000/yr). We recommend migrating to Twenty CRM for full AI capability at this price point.

Pipedrive / LeadSquared

Limited API Access
Pipedrive and LeadSquared have REST APIs adequate for lead ingestion and pipeline updates. Custom objects are limited. Real-time webhook delivery has known latency issues at scale. Adequate for Phases 5-7, challenging for 8-9.
Caveat: Both typically fail our API audit for full Phase 8-9 support. We usually recommend migration to Twenty CRM for these markets.
What you get

Everything included in Phase 3. Nothing extra to buy.

Audit

CRM audit before any migration is suggested.

6-criteria API capability test. Field write access, webhooks, custom objects, rate limits, bulk operations. Full report delivered in the free audit call. Migration only recommended if the audit proves it necessary.
Zero license cost

$0 annual licensing on Twenty CRM.

MIT-licensed. Self-hosted on your infrastructure. No per-user fees, no per-deal fees, no annual subscription. Trusted in production by PwC, Zillow, and Ryan Serhant’s team.
Data model

10 RE objects, 200+ fields, pre-configured.

Property Listings, Requirements, Site Visits, Deals, Channel Partners, Partner Allocations, Builder Projects — all built with the relationships that real estate brokerage pipelines actually require.
MCP server

Query and update in plain language from any AI.

MCP server configured as part of Phase 3. Claude, ChatGPT, and any MCP-compatible AI can read the full CRM and write to any record in real time. No additional developer work required after setup.
Screenless CRM

WhatsApp updates CRM. No agent needs to open a browser.

Field agents reply to post-visit WhatsApp prompts. Responses parsed and written directly to the CRM. Every site visit, follow-up, and objection captured — without a single browser session.
No limits

Unlimited users, objects, fields, automations.

Because the code is yours, there are no tier limits on users, custom fields, workflow automations, or API endpoints. As your operation scales, the CRM scales with it at no additional licensing cost.

What changes when the CRM is built for real estate, not around it

$0

Annual CRM licensing fees on self-hosted Twenty CRM
vs. $9,600 to $57,600/yr for Zoho to Salesforce + Einstein

10

Custom real estate objects pre-built and configured
Property Listings · Requirements · Site Visits · Deals · Partners · Projects

200+

Fields across the RE data model — all queryable via AI
74 fields on Property Listings alone. 40 on Requirements.

∞

Users, fields, objects, automations — no tier limits
Open-source MIT license. Self-hosted. You own everything.

Frequently Asked Questions

Twenty CRM is an open-source customer relationship management platform released under the MIT license. It is the open-source equivalent of Salesforce in terms of data modeling flexibility — you can create any object, any field, any relationship. It is used in production by companies including PwC, Zillow, and Ryan Serhant’s real estate team. “Open-source” means the source code is public, auditable, and free to use. You pay for the server it runs on, not for the software itself. We take Twenty CRM and configure it specifically for real estate brokerage operations, adding 10 custom objects, the MCP server, and the WhatsApp integration as part of Phase 3.

MCP (Model Context Protocol) is an open standard developed by Anthropic that defines how AI assistants connect to external tools and data sources. When we configure Twenty CRM as an MCP server, Claude, ChatGPT Enterprise, and any other MCP-compatible AI can read from and write to your CRM in real time — using natural language, without any custom development. The practical result: a team lead can query the full pipeline in Claude (“which deals have been at offer sent for more than 2 weeks?”) and get a live answer. An agent can say “create a follow-up for Rajesh for Friday” and it writes to the CRM. The MCP server eliminates the need for a human to open the CRM interface for most day-to-day operations.

A screenless CRM is one that does not require a user to open a browser interface to read or update records. Instead: field agents update records by replying to WhatsApp post-visit prompts. The AI qualification system (Phase 5) writes lead qualification results directly to the CRM after every conversation. The call intelligence system (Phase 8) writes transcripts and scores to the correct contact record after every call. A team lead queries pipeline status through Claude or ChatGPT without opening a dashboard. The CRM stays current without any manual interface interaction. The browser dashboard is still there for anyone who wants to use it — but it is no longer required.

Not necessarily. We run a free 6-criteria API audit on your existing CRM during the audit call. We test field-level write access, real-time webhook delivery, custom object creation, bulk operation rate limits, and historical data export fidelity. If your CRM passes all 6 criteria, we build all AI phases on top of it — your team keeps their interface, and nothing changes for them operationally. We only recommend migration if the audit finds that your CRM cannot support the AI phases you need. If migration is required, we handle the full data migration and your team is trained on the new interface before go-live.

The hosting cost depends on your infrastructure choice and the data volume you are running. For a typical brokerage with 5,000 to 20,000 records and all 9 phases active, the monthly hosting cost runs $100 to $300 per month on DigitalOcean or AWS — a separate environment per client with all data isolated. This compares to $800 to $3,300 per month in CRM licensing alone for a 20-user team on Zoho to Salesforce. The hosting cost is included in the Phase 3 scoping and the monthly maintenance retainer covers infrastructure monitoring after go-live.

Yes. Because the CRM is open-source and self-hosted, you can add any field, create any new object, modify any relationship, and build new MCP endpoints without our involvement — or ask us to do it as part of the monthly maintenance engagement. There is no vendor approval required, no roadmap dependency, and no additional licensing cost for adding capabilities. This is the fundamental difference between an open-source CRM and a closed one: the CRM grows at the pace your operation needs, not the pace a product team decides.

Stop paying $24,000 a year for a CRM that doesn't know what a site visit is.

Book a free 45-minute audit. We test your current CRM against our 6-criteria API checklist, show you the data model your brokerage actually needs, and give you a specific recommendation.
What happens in the free audit:
We walk through your current CRM, run the 6-criteria API test live on the call, and show you exactly what the data model would look like for your specific operation. You receive the full audit report — whether you work with us or not.