What a demo is optimised for
A vendor demo is a rehearsed performance on data built to make the product look good. That is not dishonest — you would do the same — but it means the default demo tells you almost nothing about how the product behaves in your brokerage, because your brokerage does not have clean data and does not follow the happy path.
The fix is not to be adversarial. It is to change what is being demonstrated.
Bring a real scenario, in advance
Send the vendor a specific scenario a week before, and ask them to run the demo on it. Something like:
A borrower comes in through a referral partner. Two applicants, one self-employed. They apply, we submit, the lender comes back with three conditions, one document is wrong and has to be re-collected, the deal funds, and the referring partner gets a share of the commission. Show me that, end to end.
That single request does more work than an hour of feature questions. You will see how conditions are tracked, what document re-collection looks like, whether the referral partner exists as a real entity or as a note, and whether the commission share is calculated or typed in. You will also learn something from whether they agree to do it.
Questions that separate platforms
"What does this do badly?" The most useful question in the meeting. Every product has a weak area, and a vendor who names theirs is telling you they know their product and expect a long relationship. A vendor with no answer either has not thought about it or is willing to find out after you have signed.
"Which of my current subscriptions do I cancel on go-live day?" Forces "all-in-one" into a specific list. See what a mortgage CRM actually costs for why this is the number that matters.
"What happens to a client after the deal funds?" In Canada the value of a book is concentrated in renewals and refinances over the following decades. Ask to see the renewal mechanism, and specifically ask what triggers it, who owns it, and what happens if the agent who wrote the deal leaves.
"Show me the migration." Not a slide about migration. The actual import screen, the actual field mapping, the actual duplicate-handling behaviour. This is where implementations go wrong and it is almost never in the demo.
"Show me an audit export." Ask them to produce the record a regulator would request for one client — identity verification, disclosures, who did what and when. If that takes them a while to find, it will take you a while too, at a worse moment.
Things to insist on seeing
- Permissions. What an agent can see versus a team lead versus head office. Ask specifically whether one agent can see another's pipeline, and whether that is configurable.
- The mobile view. Not the marketing screenshot — the actual page an agent uses in a parking lot between appointments.
- A messy record. Ask them to show a contact with a duplicate, or a deal that fell apart and came back. Clean data hides most design problems.
- The commission arithmetic. If splits matter to you, ask to see a statement that shows how a figure was reached, not just the figure. See how a mortgage commission is actually calculated.
Answers that should worry you
"That's on the roadmap." Fine as an answer, as long as it is marked as one. What matters is whether the rest of the conversation distinguishes clearly between what ships today and what is planned. A vendor who blurs that line in a demo will blur it in an implementation plan.
"You can build that with the API." Sometimes true and reasonable. But it means the cost includes somebody to build and maintain it, and that somebody is you.
"Everyone uses it differently." Usually means the product has no opinion, which sounds like flexibility and behaves like homework. A platform with no opinion is one you have to configure into being useful.
After the demo
Write down, the same day, what you actually saw versus what you were told. The gap between those two lists is the most reliable signal you will get, and it fades fast.
Then ask for a second session on your own data with your own team, not the buyer, in the room. The people who will live in the software daily notice different things than the person signing for it — and they are usually right.
If you are still shortlisting, our comparisons state each competitor's genuine strengths before the contrast, and the guide to choosing a mortgage CRM covers the four questions that narrow a list faster than any feature matrix.