The Merged-Team Data System
Client identity withheld.
Results
41,000 → 26,800
CRM contacts after approved merges
14,200
Duplicate merges approved by a person
~120
New duplicates caught each week by the ongoing sweep
640
Agent policy questions answered with a cited source in 90 days
22%
Questions escalated to the broker for judgment
Weekly
Owner summary across CRM, deals, back office and accounting
Company Profile
Company
Residential brokerage formed by merging a 52-agent brokerage with an 18-agent team. 70 agents, 1 managing broker, 1 broker-owner, 3 TCs. ~600 closings a year.
Stack
Follow Up Boss-class CRM combined from two databases, transaction management platform, back-office software, accounting software, a policy manual in shared drives.
Operating Need
Make the combined database trustworthy, give the owner one view of the merged business, and stop the broker answering the same questions all day.
The Challenge
The merger doubled the brokerage's reach but tripled its data problems. Both teams had imported their contacts into one CRM, and the same past clients now appeared two or three times under different spellings and emails. Agents worried about contacting someone another agent was already working with, so they stopped trusting the database. The newly arrived agents also had dozens of questions about the brokerage's forms and policies, and they all went to one managing broker.
The Audit
We sampled the combined CRM, reviewed the owner's reporting, and logged two weeks of agent questions to the broker.
Patterns Found
- About a third of contacts had at least one likely duplicate
- Duplicates used different spellings, emails or phone numbers for the same person
- Cleaning the database by hand was estimated at over 1,000 hours
- The owner's numbers lived in four tools, with no combined view
- The broker fielded about 30 agent questions a day, mostly about forms and policies
- Most answers already existed in the policy manual or in earlier answers
The merger was sound. The brokerage needed one trusted database, one view of the business, and a way for agents to find answers that already existed.
The Architecture
Three systems working as six parts, built to finish the merger operationally.
CRM Clean-Up
Scans the whole contact list and finds likely duplicates across spellings, emails and phone numbers.
Merge Review
Suggests each merge and shows why, like "same phone, same address, 'Jon' vs 'John'," for a person to approve.
Weekly Sweep
After the one-time clean-up, runs a small check every week to catch new duplicates.
Broker Owner Dashboard
Pulls every night from the CRM, transaction platform, back office and accounting into one view of the combined business, with a Monday summary.
Broker Answer Desk
Answers agent questions by text or chat from the policy manual, forms list, state rules and past answers, showing the source.
Escalation and Learning
Sends judgment questions or anything not in the documents to the broker, and saves the broker's answer for next time.
How the System Operates
The system finds, suggests and answers. People approve every merge, and the broker answers every judgment call.
- Every merge is approved by a person, since a wrong merge can lose history
- Every answer shows where it came from, like "Policy manual, page 14"
- Questions needing judgment always go to the broker
How It Flows
- 1Duplicates are found, or an agent asks a question
- 2The AI suggests a merge or drafts an answer with its source
- 3A person approves the merge, or the broker handles the escalation
- 4The database stays clean, and new answers are saved
Merges that would combine contacts owned by different agents always go to the broker.
Implementation
| Stage | Focus | Key Results |
|---|---|---|
| Stage 1 | Data audit | CRM sampled; duplicate patterns and reporting gaps mapped |
| Stage 2 | Clean-up | Duplicate merges suggested and approved in batches |
| Stage 3 | Owner view | Owner Dashboard and Monday summaries live |
| Stage 4 | Answer desk | Policy manual and forms loaded; Answer Desk live for all agents; weekly sweep running |
Ownership
The clean database, dashboard and answer library belong to the brokerage.
A cleaned, merged CRM with a record of every merge
A weekly duplicate sweep
An owner dashboard pulling from all four tools
A growing library of approved policy answers
Operational Impact
Agents trust the database again, so they reach out to past clients without worrying about stepping on each other. The owner sees the combined business in one place every Monday, and new agents get answers to policy questions in seconds. The managing broker spends time on the decisions that need a broker, and the merger finally feels like one company.