Why Your Brokerage Has 11 Logins (And What It Costs)

Start By Counting

Open your password manager and count the work entries. Then ask your transaction coordinator to do the same, and your marketing person, and one producing agent who has been with you five years.

The number is almost never the one on your budget line. There is the CRM you bought. There is the second CRM two teams still use because they liked it better and quietly never stopped. There is the e-signature account tied to a card that belongs to someone who left in 2023. There is the social scheduler somebody expensed once. There is the analytics tool that renews every January and auto-charges three weeks before anyone remembers to review it.

Nobody planned this. Every one of those purchases was reasonable on the day it was made. Software sprawl is not a decision, it is an accumulation, and accumulation does not show up in a single line item you can point at.

What Is Actually in the Stack

Before you can price sprawl, you have to inventory it. Most brokerages, regardless of size, are running some version of this list.

Eleven categories. If two of them have a duplicate in active use, and most brokerages have at least two, you are at thirteen accounts before anyone opens the MLS.

Read the table again and notice something: the same contact record exists in at least six of those rows, and no two rows agree on what a "client" is.

The Four Costs That Never Appear on One Invoice

Per seat multiplication

Per seat pricing is the reason a stack that felt cheap at twelve agents feels punishing at forty. Adding an agent does not add one subscription, it adds one subscription for every per seat tool you run. Your cost curve is headcount multiplied by tool count, and only one of those two variables is under your control.

This is also why growth feels expensive in a way leadership struggles to explain. Recruiting ten agents adds ten seats across six tools before those agents close anything. The stack scales with the org chart instead of with revenue.

The integration tax

Nothing in the table above talks to anything else by default. So somebody built glue: a Zapier chain, a nightly CSV export, a webhook a former contractor wrote, a shared sheet that two systems both read from.

Glue is real infrastructure with none of the ownership of real infrastructure. It breaks when a vendor ships a field rename, deprecates an API version, or changes an auth flow, and it breaks silently. You usually find out because a lead sat unrouted for four days, not because anything alerted you.

The cost is not the build. The cost is the permanent maintenance obligation on code nobody on payroll wrote.

Reconciliation labour

This is the largest cost and the least visible, because it wears the uniform of ordinary work.

Somebody re-keys a new agent into six systems during onboarding. Somebody exports from the CRM and pastes into the reporting tool because the numbers disagree. Somebody chases down which of the two contact records for the same seller is current. Somebody rebuilds the same monthly report by hand because no single system holds all the inputs.

None of that appears as a software cost. It appears as headcount, and it is why operations teams grow faster than the brokerage does.

Vendor and security surface

Every vendor in that table is a data processor holding your agents' and your clients' personal information. Each one is a separate breach path, a separate access review, a separate contract renewal, and a separate answer you owe when a client, a carrier, or a regulator asks who has their data.

Eleven vendors means eleven offboarding checklists when someone leaves, and the honest question is whether all eleven actually get run. This is why we publish our own security posture and a full sub-processor list: a stack you cannot enumerate is a stack you cannot govern.

Build the Number Yourself

Here is a worked example. Every input below is illustrative. We picked round figures to make the arithmetic legible, not because they represent market rates, industry averages, or any vendor's pricing. Replace all of them with numbers from your own invoices.

Illustrative brokerage: 40 agents, 11 tools, 6 of them priced per seat.

Now run the growth case with the same illustrative inputs. Recruit ten agents and the per seat line moves by 10 x 6 x $25 x 12, which is $18,000 a year, for zero additional capability. That is the shape of the problem: the multiplier, not the sticker price.

Fill in your own version. The blanks matter more than our example.

That last row is the one that surprises people. Pull the actual login records before you pull the invoices.

What You Should Not Consolidate

Consolidation is not a religion, and any vendor telling you to move everything is selling, not advising. Three categories should usually stay where they are.

Genuinely best in class specialists. If a tool is materially better at a narrow job than any suite module will be, keep it and integrate it properly. A merged version that is eighty percent as good costs you real production for a line item saving. This is a judgment call and it should be made tool by tool, with the people who use it daily in the room.

Anything carrying a regulatory or accounting audit trail. Your commission accounting, your executed document retention, and your trust or escrow handling sit inside a chain of evidence your auditor and your state regulator already accept. Moving them mid-year means re-establishing that chain and re-proving retention. Do it on a fiscal boundary with your accountant leading, or do not do it at all. There are worse outcomes than paying for one extra subscription.

Tools your agents personally love. Agents are not employees you can mandate into a workflow, and a tool they chose themselves is one they actually use. Forcing a migration you cannot justify to them buys you a licence saving and costs you adoption on everything else you are trying to change. Recruiting is competitive enough without adding a grievance.

The tradeoff, stated plainly: keeping specialists means keeping integration work and keeping vendor surface. You are choosing which cost to carry, not eliminating cost. Make the choice deliberately and write down why, so the next operations lead does not undo it.

Where consolidation does pay is the overlapping middle: the systems that all hold the same contact, the same agent record, and the same listing. That is CRM, website and IDX, marketing, training, events, and broker management sharing one record instead of six copies of it.

Migration Is Not Free Either

Any honest consolidation case has to price the transition, not just the destination.

• Data migration. Your CRM contains a decade of inconsistent entry. Migration surfaces every duplicate, every dead record, and every field somebody repurposed. That cleanup is real work and it happens before go-live, not after.
• Retraining. Every person who touches the old system needs hours on the new one, and those hours come out of production weeks.
• The overlap period. You will run both systems at once for a stretch. Budget for paying twice during that window, because you will.
• Change management. The loudest cost is the quietest to plan for. Someone has to own adoption, answer the same question fifteen times, and hold the line when a team asks for an exception.

A vendor who skips this conversation has not done many migrations. We walk through it explicitly in our FAQ and in case studies.

A 90 Day Consolidation Plan

1. Days 1 to 10: inventory. Pull every recurring charge from the card and bank statements, not from memory. Match each to an owner and a renewal date. Expect to find at least one thing nobody claims.
2. Days 11 to 20: measure actual use. Ask each vendor for seat-level login data over the last 90 days. Billed seats and active seats are different numbers.
3. Days 21 to 30: build the cost model. Fill in the blank table above with your figures, including the reconciliation hours. Bring finance in so the labour line is credible.
4. Days 31 to 40: classify. Sort every tool into consolidate, keep, or cancel outright. Apply the three exemptions above honestly rather than conveniently.
5. Days 41 to 55: cancel the dead weight first. Unused and duplicate subscriptions need no migration and no change management. Bank that before you touch anything harder.
6. Days 56 to 70: pilot with one office or one team. Never migrate the whole firm at once. Pick a group with a strong operations lead and a manageable data set.
7. Days 71 to 85: migrate and reconcile in parallel. Run old and new together, compare records daily, and fix mapping errors while the old system is still authoritative.
8. Days 86 to 90: decide and document. Cut over or roll back on evidence from the pilot, then write down what broke so the next office goes faster.

Do not schedule a cutover across a fiscal close, a licence renewal cycle, or your busiest listing month. The plan survives contact with reality or it is not a plan.

Where to Start

Start with the count. Not the demo, not the proposal, the count. Most brokerages discover the problem is not the price of any single tool, it is the multiplication table sitting behind eleven of them.

When you have your number, bring it to us. We will map what to consolidate, what to leave alone, and what it costs to run fewer systems: see what we build for brokerages, review how we handle pricing against your existing invoices, or get in touch with your inventory in hand.

Frequently Asked Questions

What CRM do most realtors use?

There is no single CRM that most agents use, and that fragmentation is the actual finding. Agents typically end up on whatever their brokerage provides, whatever a team lead bought, or whatever they carried over from a previous firm, which is why one office often runs two or three at once. The practical question for a brokerage is not which CRM is most popular but which one your agents will actually put data into, because a CRM nobody updates is a cost with no return.

What is brokerage management software?

Brokerage management software is the operational layer that runs the firm rather than the deal: agent and office records, license and insurance tracking, continuing education status, document retention, production reporting, and commission-relevant data. It sits behind the CRM and the transaction system and answers questions about the business itself, such as who is compliant, who is producing, and what the office owes. You can see how we scope it on the [broker management](/solutions/bms) page.

How much does real estate CRM cost?

Almost every real estate CRM is priced per seat per month, which means the honest cost is the seat price multiplied by headcount, plus onboarding, data migration, and any integration or API fees the quote does not mention. Ask every vendor for a total first-year figure rather than a monthly rate, and ask what happens to the price when you add ten agents. We publish our approach and build a tailored breakdown against your current invoices on the [pricing](/pricing) page rather than posting a list price that would not survive contact with your stack.

What software do real estate agents use?

A working agent usually touches a CRM, the MLS and an IDX-powered site, a transaction management system, an e-signature tool, a CMA generator, email and SMS marketing, a social scheduler, and whatever the brokerage requires for training and compliance. Most of those tools were chosen by different people at different times for different reasons. The count matters more than any individual tool, because every additional login is another place a contact record can be created and then never updated.

Should a brokerage build or buy its platform?

Most brokerages should buy, because building means owning MLS data compliance, security patching, accessibility, and a permanent engineering payroll line for software that is not what you sell. Building makes sense only when a genuinely differentiated workflow is central to how the firm competes and no vendor supports it. The middle path that usually wins is buying a configurable platform and building only the few workflows that are actually yours.