Finova Broker CRM: what mortgage firms should know

Finova Broker CRM is a broker CRM platform from Finova, with roots in the eKeeper and Mortgage Keeper products that many UK firms have used for years. It is positioned as a specialist system for financial services rather than a general sales database, and its public material emphasises tailored workflows, audit trails, customer communication, application tracking, onboarding, customer portals, lead acquisition connections and implementation support.

The thread running through all of that is configurability. That is the thing to evaluate, because it is both the reason to buy and the reason some firms should not.

When a fixed workflow is the problem

Plenty of firms do not want to be told how to work. They have an introducer arrangement with its own reporting, a packaging process shaped by the lenders they use most, administrator roles that evolved for good reasons, and a file-check routine their compliance function trusts.

A platform with a strong opinion about the right process asks those firms to change several things at once. Sometimes that is exactly what a firm needs. Sometimes it means abandoning arrangements that are working and taking on a change project the business has no capacity for.

A configurable system offers the other trade: keep your process, and shape the software around it. For firms with genuinely distinctive operations, that can be the difference between adoption and a shelf-ware purchase.

The cost of flexibility, stated plainly

Configurability is not free, and the price is rarely on the invoice.

Somebody has to specify the workflow. That means writing down what you actually do, which most firms discover is harder than expected because different advisers do it differently. The specification stage is where implementations slip.

Somebody has to own it afterwards. Fields get added, statuses multiply, an automation is created for a situation that stopped happening two years ago, and nobody dares remove anything. Configurable systems accumulate. Name the person responsible for pruning yours before you go live.

And somebody has to decide when to stop configuring. The most common failure is a firm that reproduces every quirk of its old process, including the ones that were causing the problem it bought the software to fix.

What to have demonstrated

• A workflow being built or amended, in front of you, so you can judge how much is self-service and how much is a support ticket.
• Permission levels and roles across advisers, administrators, managers and compliance.
• Lead capture and source attribution from wherever your enquiries come from.
• The client portal and document collection, experienced as a client on a phone.
• Identity, document and signature steps as they would run on a real case.
• The audit trail as a reviewer sees it, months later, on a case that changed direction.
• Introducer reporting, if introducers matter to you.
• Pipeline, commission and management information, and how each figure is populated.

Migration, which deserves its own conversation

Finova is frequently considered by firms with an existing system and years of history, which makes migration the hard part rather than an afterthought. Ask how records from your current CRM are mapped, field by field, and who does that mapping. Ask what happens to documents, to notes, to cases that are live on cutover day, and to data that has no equivalent field in the new structure.

Ask how long your historic files remain accessible and in what form, because retention obligations do not pause because you changed supplier. Get the answers in writing and treat any vagueness as a cost.

Who it tends to suit

Firms with an established, distinctive process they have good reasons to keep. Larger broker businesses where roles are specialised and oversight matters. Firms with introducer networks or packaging relationships that need tracking the average CRM does not contemplate. Businesses that want management information shaped to their own definitions rather than a supplier's.

It suits less well a sole adviser or a two-person firm who wants something usable next week with no configuration decisions to make. For them the flexibility is overhead, not value.

Before you commit

Confirm with Finova directly what the package includes, what implementation covers, how long a firm your size typically takes to go live and what ongoing support looks like. Ask what a configuration change costs once you are a customer, because that number shapes how the system will evolve.

If you are an appointed representative, check what your principal firm requires and whether it will accept the records this system produces. Whether you are AR or directly authorised, ask where data is hosted, what the retention controls are and what an export contains if you leave.

Bottom line

Finova Broker CRM is worth shortlisting when your process is genuinely your own and you need the software to fit it rather than the reverse. Its value depends on your firm having both a clear description of how it works and someone willing to own the system after implementation. With those two things it can be an excellent fit. Without them, flexibility becomes a slow-motion problem.