The six layers, and what sits in each
Every product on the market fits into one or more of these layers. Naming the layer a product occupies is more useful than its category name, because the category names overlap and the layers do not. The products named are placed as of September 2026.
- Front office: lead sources, the agent and brokerage websites, the CRM and marketing automation. Follow Up Boss, BoldTrail (kvCORE), Lofty and Brivity live here.
- Transaction layer: transaction management, forms, e-signature and broker compliance review. SkySlope, dotloop and Lone Wolf live here; DocuSign is often attached for signing.
- Back office: commission plans and disbursements, accounting, agent onboarding and recruiting, license and E&O tracking. Lone Wolf's back office, QuickBooks and Xero live here.
- MLS data: the listing feed the MLS licenses to members, delivered through a data vendor, displayed under IDX or VOW rules, and used for comps, CMAs and market statistics.
- AI: assistants that answer leads, draft follow-ups, classify documents, triage review and brief the agent or broker. Lofty builds AI into the front office; Raven's EVE reads across every layer.
- Integration: the connectors, Zapier zaps, API keys and webhooks that carry a contact or a transaction from one layer to the next.
Where the same transaction gets copied
Follow a single sale through a typical stack. The lead is a contact in the CRM. When it goes under contract, an agent creates a transaction in the transaction tool and re-types the client, the property and the price. The purchase contract is filled in the forms provider, sent for signature from the e-signature product, downloaded, and uploaded to the transaction tool for broker review. At close, the commission is entered again in the back office, and the closed file is exported to an archive.
That is five copies of one transaction, and none of them updates the others. The broker's compliance view is only as current as the last upload; the CRM does not know the file closed; the back office does not know the review was complete. Every reconciliation meeting a brokerage holds is a consequence of this diagram.
How to decide what to consolidate and what to connect
The test is not whether a product can integrate. Everything integrates. The test is whether two products would hold copies of the same fact.
- Does it hold the transaction record, or point at one? Ask where the file of record lives. A tool that stores the documents, the review decisions and the dates is the record; a tool that links to a folder in another product is a view of it, and two views of one file drift.
- Consolidate any two layers that would each hold the transaction: CRM and transaction, transaction and e-signature, transaction and compliance. A copy in each is where status drifts.
- Connect the layers that hold something the transaction does not: accounting, an association forms library, a lead source, team chat. A notification about a transaction is safe to send; a second copy of it is not.
- Is compliance enforced or advisory? Enforced means a stage cannot advance and a file cannot close while a required document is missing or unreviewed. Advisory means a checklist that turns red. Ask which the product does by default, and whether it can do the other for a solo agent or a team under an outside broker.
- Is e-signature native? Native means the signed copy lands on the transaction and updates its requirements without an export. Count how many times a document is uploaded between filling, signing and broker review.
- Does the AI cite its sources? An assistant that drafts a client update should be able to show the document, message or date it drew from, and it should hold anything about price, contract terms, financing or a complaint for a person to approve.
- What does it cost to switch? Count the imports (contacts, open transactions, closed files), the retraining, the forms provider you keep, and the retention obligation on closed files (Arizona requires five years), which usually means the old archive stays readable rather than being migrated.
Where Raven fits
Raven is an AI-native real estate platform for agents, teams and brokerages: CRM, transaction management, compliance, e-signature, communications, marketing, MLS data and commissions in one platform, with EVE, its built-in AI, working across every client and transaction.
In the stack, Raven is the system of record for the front office and the transaction layer together: the contact, the Connect thread, the transaction, its documents, Raven Ink, the brokerage's own forms and the broker's review are one record, and Raven Vault seals the closed file. For the back office it holds commission plans, recruiting and credential tracking, and connects to QuickBooks and Xero for accounting. MLS data reaches each agent under that agent's own active membership. EVE is the AI layer, reading the same record rather than a copy of it, and the integration layer is Gmail and Outlook, Slack and Teams, lead sources, anything with a Zapier connector, an org API key and signed webhooks.
- Replaces: CRM, transaction management, compliance and broker review, e-signature, brokerage forms, communications, marketing, commission plans, recruiting
- Connects: Gmail and Outlook, Slack and Teams, QuickBooks and Xero, lead sources, Zapier, a public API with signed webhooks
- Stays where it is: your state association forms with their authorized provider, and your MLS membership with your MLS
Go deeper
The pages that cover each point above in full, and the comparisons that name each product.
- Real estate integrations
- Transaction management
- Raven for brokerages
- The platform, in detail
- Raven vs SkySlope
- Raven vs Lone Wolf
- Raven vs Follow Up Boss
- Best real estate software for brokerages
Descriptions of other companies' products on this page are as of September 2026 and describe what each product does, not how it compares.
Frequently asked questions
What is a real estate brokerage technology stack?
The set of software a brokerage runs, organized by layer: front office (leads, websites, CRM, marketing), transaction (file, forms, e-signature, compliance), back office (commissions, accounting, recruiting), MLS data, AI, and the integrations that connect them. Most brokerages run one or two products per layer.
How many tools does a typical brokerage run?
Commonly four to six with a customer-facing role, plus accounting and the MLS itself. A CRM, a transaction and compliance tool, an e-signature product, a forms provider and a marketing suite is the usual shape, and the same transaction is copied into most of them.
What is the difference between consolidating and integrating?
Consolidating puts two jobs on one record, so there is one copy of the fact. Integrating keeps two products and sends data between them, which creates a second copy that has to be kept in sync. Consolidate where two tools would hold the same transaction; integrate where a tool holds something the transaction does not.
Where does MLS data sit in the stack?
Underneath everything that shows a listing: the website, the CRM's property alerts, CMAs and market statistics. It is licensed by the MLS to its members, delivered through a data vendor, and displayed under IDX or VOW rules. Each agent's access depends on an active membership, and an AI that reads listing fields needs authorization from that source.
Does Raven replace the whole stack?
It replaces the front office and the transaction layer, and the parts of the back office that concern agents: commission plans, recruiting and credential tracking. It connects to accounting, email, team chat and lead sources rather than replacing them, and state association forms stay with their authorized provider.