Choosing a CRM for a brokerage: what generic CRMs get wrong about mandates
Unbroken · · 6 min read
Generic CRMs get one thing wrong about a brokerage: they model a sale as a single deal with a single contact, a value and a close date. A mandate is a deal with a seller on one side, a list of buyers on the other, each at their own stage, and a fee that depends on a price nobody knows yet. A CRM for a brokerage has to model the mandate, or the workflow ends up in spreadsheets beside it.
What does a generic CRM assume?
The pipeline in a general-purpose CRM was designed for selling software or services: a lead comes in, is qualified, receives a proposal, negotiates, and closes won or lost. The deal has one primary contact, one value, one owner and one probability. Activities hang off the deal or the contact. Reporting counts deals per stage and multiplies value by probability.
Every one of those assumptions breaks on a sell-side mandate. The 'customer' is the seller, but the people the broker spends most of their time on are buyers, and the buyers are not the customer. The deal's value is a fee that is a percentage of a price that will not be known until offers arrive. The stages of the seller's mandate (engaged, preparing, marketing, offers, due diligence, settled) are not the stages of each buyer's journey (teaser sent, NDA signed, IM sent, data room, offer, withdrawn). A generic CRM can hold one of these pipelines, and the other goes into a spreadsheet.
What does a brokerage's CRM need to model?
- Contacts and organisations as first-class records, since the same accountant refers three sellers, the same private equity firm looks at ten mandates, and the same owner is a seller this year and a buyer in two.
- Deals as mandates, with the seller and the business on the record, the mandate's own stages, and the engagement terms (fee structure, term, tail) attached.
- Buyers on a mandate as a list of related records, each with its own stage, its NDA status, its data room access, and its offer. A buyer's stage on one mandate is independent of its stage on another.
- Separate pipelines for different kinds of work. Lead generation (owners who might sell in two years), advisory engagements (appraisals, exit readiness), transactions (mandates), buy-side mandates, and strategic partners each have different stages and probabilities. One pipeline for all of them produces a report that means nothing.
- Activities, whether a call, an email, a task or a project step, on the contact and the deal, with due dates, so an adviser's day is a list rather than a search.
- Fields the brokerage can configure, with visibility rules, because a brokerage's data is confidential in a way a software company's pipeline is not: an adviser should see their own mandates and not another adviser's seller.
- The financials, the valuation and the documents connected to the deal, or at least linked to it, so the record is where the work is.
What goes wrong when the CRM is generic?
The most common outcome is a hybrid: contacts in the CRM, mandates in a spreadsheet, buyers in another spreadsheet, and the valuation in a third. Each adviser keeps their own version. When an adviser leaves, the practice discovers that the CRM has the contacts but not the reasons, the history or the state of the buyers. Reporting is done by hand at month end and is a week stale by the time the principal reads it.
The other cost is confidentiality. Client financials, an IM and a buyer list sitting in a general-purpose CRM's attachments, shared through its email integration, are subject to the Australian Privacy Principles like any other personal information, and a tool that was not designed for confidential deal work makes reasonable security harder to demonstrate. The OAIC's guide to securing personal information sets out what reasonable steps look like.
What should a brokerage look for in a CRM?
- Mandate as the deal record, with a related buyer list per mandate, each buyer with a stage. Ask to see it, not to hear about it.
- Separate pipelines with their own stages, and reporting that respects them: buyer funnel per mandate, pipeline velocity per pipeline, adviser accountability across all of them.
- Email, calls and SMS on one thread per contact, so nobody has to ask what was said. A CRM that only logs email leaves the phone calls, which is where the deal happens, out of the record.
- A migration path from what you have now: contacts, organisations and deals imported from a CSV export or directly from the current CRM, with a preview before anything is written.
- Configurable fields, labels, saved views and visibility groups, administered by the practice rather than by a consultant.
- The valuation, IM, data room and billing either in the same system or connected to the deal record without re-keying. See our post on the whole stack for why.
- Australian hosting, an audit log, and export of your own data in an open format. If you cannot get it out, you do not own it.
Unbroken's CRM is built on these lines: contacts, organisations and deals with configurable fields and visibility rules, separate pipelines for lead generation, advisory, transactions, business sales and strategic partners, activities grouped by day, and reports on buyer funnel, portal engagement and pipeline velocity. It exists because the practices behind it tried the generic route first. The why switch page compares the alternatives without pretending they never work.
How do you migrate a brokerage to a new CRM?
Export contacts, organisations and deals from the current CRM. Map the fields once, in a preview that shows exactly what would land and changes nothing. Fix the mapping until the preview is right, then import. Run the next new mandate entirely in the new system before moving live ones, and move those one at a time. Turn the old system to read-only rather than off, and keep it for the period the engagement letters' tails run. A migration that tries to move twenty live mandates on a Friday afternoon is the reason practices stay on the tool they dislike.
Frequently asked questions
Can Pipedrive or HubSpot be used for a business brokerage?
Yes, and many brokerages do, usually with custom fields for the mandate and a spreadsheet for the buyer list. It works until the buyer list, the valuation and the documents need to be in the same place as the record. Then the practice either builds a customisation or moves to a mandate-centred system.
What is the difference between a contact pipeline and a mandate pipeline?
A contact pipeline tracks a person or firm through a relationship (lead, qualified, client). A mandate pipeline tracks an engagement through its stages (engaged, preparing, marketing, offers, due diligence, settled). A brokerage needs both, and a buyer list per mandate as a third dimension.
How should a brokerage handle visibility between advisers?
By visibility groups on the deal record: an adviser sees their own mandates and those shared with them, an administrator sees everything, and reports are filtered the same way. A CRM that cannot restrict who sees a seller's financials is a confidentiality risk, not just an inconvenience.
Does a brokerage CRM need telephony?
It needs the calls in the record. Whether that is a built-in softphone or an integration matters less than whether every call, its outcome and its notes end up on the contact and the deal. Deals are done on the phone; a CRM that only sees email is missing most of the story.
How long does a CRM migration take for a small brokerage?
With a clean export and a preview-then-import tool, the data move takes days. The practice change, new mandates on the new system and old ones moved one at a time, takes a month or two. Budget for the second, not the first.
Sources & further reading
Written by the Unbroken team, following a Registered Business Valuer's framework. The valuer stays responsible for the opinion.