A CRM implementation for a mortgage brokerage is complete when your team can run a real loan file through the new system, from enquiry to settlement follow-up. Before you appoint a CRM consultant, write down the broker file workflow, the integration scope and the acceptance checks the delivered system must pass. The decision that shapes the rest of the CRM project is which system owns each record, so settle it before any configuration starts.
Define the Deployment You Are Buying
A CRM implementation delivers a working operating process. Staff know where each enquiry lands, who owns the file and what happens at each stage. Installed software with default fields does none of that until someone configures it around your files. Split the project into five deliverables so each one has its own scope, price and sign-off.
This guide assumes you have already chosen the platform. If you have not, compare the options in our mortgage broker CRM guide first.
Deliverables Matrix
| Deliverable | What it covers | What you receive | Complete when |
|---|---|---|---|
| Discovery | Workshops, a current-system audit and written requirements | A workflow map, system of record decisions and a prioritised gap list | You approve the workflow map and gap list in writing |
| Configuration | Fields, pipelines, page layouts, user roles and automations built with the platform’s own settings | A configuration register listing every field, stage and rule | A test file passes every configured stage |
| Custom development | Code or apps written for gaps the settings cannot close | Source code in a repository your brokerage controls, with build notes | The code sits in your repository and passes the agreed tests |
| Integration | Connections to telephony, email, document storage, accounting or the aggregator CRM | An integration schedule and a failure runbook | Each connection passes a success test and a forced-failure test |
| Maintenance | Fixes, platform updates and small changes after go-live | A support agreement with response times and a change log | The agreement is signed and the first support request is logged |
System of Record Decisions
Before anyone builds, name your existing aggregator CRM and the system that will own each record type. Many brokers already keep loan files in an aggregator CRM, such as Infynity or MyCRM, which carries the application through to lodgement. A general CRM, such as HubSpot or Dynamics 365, then sits beside it. When both systems hold the same contact or application, staff update one and the other goes stale.
| Record | Question to settle | Example decision |
|---|---|---|
| Contacts | Which system creates the client record, and which one copies it? | The general CRM creates the contact at enquiry and passes it to the aggregator CRM when the broker opens a file |
| Applications | Where is the loan application built and lodged? | The aggregator CRM holds the application, and the general CRM stores only its status |
| Documents | Where do payslips, statements and identification documents live? | One document store, linked from both systems |
| Client-review tasks | Which system raises the annual review or rate check? | The general CRM, from the settlement date the aggregator CRM supplies |
Agree to duplicate a record only when the decision names the master system and the direction of the copy.
Commission figures need the same decision. Trail and upfront arrive in the aggregator’s commission statements, so a CRM field that retypes them creates a second, unchecked version. Track My Trail reads those aggregator reports beside the CRM. Its Refinance Finder builds a client-review queue from each loan’s settlement date, so decide whether review tasks start there or in the CRM.
Run a Broker File Discovery Workshop
Run the CRM discovery workshop stage by stage around one loan file and assign a system and a staff role to every step. Bring a recently settled file and one that stalled, because the stalled file shows where the current process loses information. The broker, the credit assistant or loan processor, the office administrator and the consultant attend together.
Workshop Agenda
The allocations in this agenda are an example. Your workshop decides its own.
| Stage | What to map | System responsible | Staff role |
|---|---|---|---|
| Enquiry | Lead source, first contact, referral details and who receives the enquiry | General CRM | Office administrator |
| Joint applicants | How two or more applicants link to one file without duplicate contacts | General CRM and aggregator CRM | Credit assistant |
| Document collection | The request list, upload method, reminders and what counts as received | Document store or client portal | Credit assistant |
| Consent | Privacy and credit-check consents, how each is captured and where staff retrieve it | Aggregator CRM or general CRM, decided in the workshop | Broker |
| Broker review | Needs analysis, product comparison and the broker’s sign-off before lodgement | Aggregator CRM | Broker |
| Lodgement handoff | How a ready file passes to the aggregator CRM or lodgement platform, and who confirms it | Aggregator CRM | Loan processor |
| Settlement follow-up | Settlement confirmation, the post-settlement call and the first review date | General CRM | Broker or office administrator |
Turn the CRM Audit Into a Gap List
Run the CRM audit of your current system alongside the workshop, then turn what it finds into a prioritised gap list. A wish list names features. A gap names the failure in today’s process and the observable result that proves it is fixed.
| Wish-list item (incorrect) | Gap with completion criterion (correct) | Priority |
|---|---|---|
| Automated document reminders | Staff chase missing payslips by hand. Done when a missing item triggers a reminder within one business day and the reminder shows on the file. | High |
| A better dashboard | The owner cannot see files waiting on the client. Done when one view lists every file at document collection with the days it has waited. | Medium |
| Phone integration | Staff type call notes against the wrong client. Done when an inbound call from a known number opens the matching client and unmatched calls go to a review queue. | High |
Rank the gaps by the cost of the failure, such as a lost file or a missing consent, then by build effort. The ranked gap list becomes the scope the consultant prices.
Select a Consultant for the Work Required
Choose the provider type from the work on your gap list, then test each candidate on deployments like yours. The work on most gap lists calls for one of three kinds of provider, and a large project can use more than one.
Provider Types Compared
| Provider | Best fit | Ask for | Watch for |
|---|---|---|---|
| CRM consulting firm | Process design, configuration and staff training on one platform | A deployment for a broking, lending or other regulated advice business, with the configuration register it delivered | Custom code subcontracted without telling you who supports it |
| Integration specialist | CRM integration services between the CRM, telephony, email, accounting and the aggregator CRM | Integration schedules and failure runbooks from past projects | Middleware accounts or licences held in the specialist’s name |
| CRM development company | Custom apps or code where configuration cannot close the gap | Code samples, a test plan and a written statement that you own the code | Work kept in the developer’s repository or tied to its hosting |
Compare every candidate on the same five points: relevant deployment examples, competence on your platform, documentation, support responsibility and ownership of custom work. Ask who answers a support call at go-live and in the second year, and whether that is the same company. Put ownership in the contract. Your brokerage holds the administrator accounts, the code repository and any middleware subscriptions.
Check Platform Credentials
Each platform runs a directory that shows what its partners are certified to do. On Salesforce’s AppExchange, a consulting company’s Expertise tab lists its product and industry specialisations and its consultants’ current Salesforce certifications. For Dynamics 365 consulting, ask whether the partner runs Microsoft’s Success by Design reviews. These include a Solution Blueprint Review early in the project and a Go live Readiness Review before launch.
HubSpot CRM consultants appear in HubSpot’s Solutions Partner directory, which filters partners by service, industry and country. For monday CRM consulting partners, monday.com lists certified partners with their certifications and customer reviews in its go-to-partners marketplace. Zoho keeps a partner directory by country for Zoho CRM development and setup work.
A certificate shows that a consultant knows the platform. Understanding an Australian loan file is a separate skill, with joint applicants, credit consents and an aggregator that holds the application. Test it in the interview. Hand each candidate the stalled file from your workshop and ask how their build would have moved it to lodgement.
Platform configuration has its own guides. The Salesforce CRM implementation guide covers Salesforce, and the Zoho CRM setup guide covers Zoho. For monday.com, read the monday CRM implementation guide.
Specify Integrations and Custom Work
Write an integration schedule before development starts, and have the consultant price against it. For each connection, the schedule states the items below. The example column uses a phone system that syncs sales calls to the CRM as client notes.
Integration Schedule
| Item | What the schedule states | Example: calls to client notes |
|---|---|---|
| Objects | Which contact and loan records the integration reads or writes | Reads contacts and writes a call note to the contact and its open loan file |
| Field ownership | Which system is the master for each field | The general CRM masters phone numbers, and the phone system masters call duration and the recording link |
| Direction | One-way or two-way, and which system starts the sync | Phone system to CRM only |
| Permitted users | Which roles can see or change synced data | Brokers and credit assistants see call notes, and only the broker on the file sees restricted notes |
| Retries | How often a failed sync retries, and for how long | Three retries over 15 minutes, then the failure queue |
| Duplicate handling | What happens when one record matches several existing records | The call goes to the review queue instead of the first match |
| Failure repair | Who receives the alert and fixes the fault, and how quickly | The integration specialist, by the next business day, under the support agreement |
VoIP Call Note Example
A VoIP CRM integration shows why each line matters. The phone system matches an inbound number to a contact, then writes a call note against that client. Joint applicants can share a home number, so one number can match two contacts. Send that call, and any call from an unknown or withheld number, to a failed-match queue that a staff member clears each day. Zoho’s PhoneBridge FAQ warns against saving an anonymous caller ID as a contact, because every later anonymous call would attach to it.
If calls are recorded, the schedule states how callers are told and where the record of that notice or consent is kept with the call. Our guide on how to record a phone call explains recording notices. Some calls cover hardship, health or a relationship breakdown. Mark those notes restricted so only the broker on the file can read them. Health information is sensitive information under the Australian Privacy Principles, which set stricter rules for collecting and using it.
Vendor Connectors and Custom Code
Treat each vendor connector as a capability the consultant documents before building on it. Servetel, which now trades as Acefone, describes a Zoho CRM integration with click-to-call and call logs and recordings tracked in Zoho. Zoho’s own PhoneBridge telephony integration runs on the Professional, Enterprise and higher editions of Zoho CRM. It does not record calls by default, and only administrators can enable it. Ask the consultant which connector they would use and which records it reads and writes.
A Zoho CRM and NetSuite integration needs the same check. Zoho’s marketplace lists third-party apps that sync NetSuite customers, sales orders and invoices into Zoho CRM. Ask which app the consultant proposes, which records move in each direction and who holds its licence. For HubSpot connector details, read the HubSpot CRM integration guide.
Configuration uses the platform’s own settings, so another administrator can change it later. Custom development is code your brokerage must own, test after each platform update and pay to maintain. Ask for configuration first, and approve CRM customisation in code only for a gap the settings cannot close. Every custom item needs a named owner, a test and an entry in the configuration register.
Accept the Deployment Against a Loan File
Accept the deployment by running a test loan file through every stage and checking each result against the workflow map from discovery. Use test data, never a live client’s file. The illustrative file below follows two joint applicants buying their first home, with Broker A as the file owner.
Illustrative Acceptance File
- Submit a web enquiry for the first applicant. Expected result: one contact and one file, assigned to Broker A with a first-contact task.
- Add the second applicant. Expected result: two contacts linked to the same file, with no duplicate created when the second applicant’s email arrives.
- Send the document request. Expected result: the request list appears on the file, and a missing payslip raises a reminder and a follow-up task for the credit assistant.
- Record the privacy and credit-check consents. Expected result: each consent is stored on the file, and a user with broker access can open it with the name of the person who captured it.
- Complete the broker review. Expected result: the file moves to ready for lodgement only after Broker A signs off.
- Hand the file to the aggregator CRM. Expected result: the application is built and lodged in the aggregator CRM or lodgement platform, and the general CRM shows the lodged status with Broker A still as owner. The general CRM does not submit the application.
- Mark the loan as settled. Expected result: a settlement follow-up task and a first review date appear for Broker A.
Deployment Acceptance Checklist
| Check | Expected evidence | Signs off |
|---|---|---|
| Joint applicants link to one file | Two contacts and one file, with no duplicates after a second import or email | Credit assistant |
| Staff permissions match each role | A credit assistant login cannot open restricted notes or change the file owner | Brokerage owner |
| Consent can be retrieved | Each consent opens from the file and shows who captured it | Broker |
| A failed integration is caught | A forced sync failure raises the alert, lands in the failure queue and is repaired by the named party | Operations manager |
| The complete file exports | One export holds every contact, note, document link and consent for the test file in a readable format | Brokerage owner |
| File ownership survives the handoff | Broker A stays the file owner from enquiry to settlement follow-up | Broker |
Sign the acceptance only when every row passes on the test file. A failed row goes back to the provider that delivered it, under the deliverables matrix. Moving records from the old system needs its own trial imports and checks, which our CRM migration guide covers.
Agree Costs, Handover and Ongoing Support
Price each deliverable separately, because each one has its own cost driver. Platform subscription fees sit outside this list and come from the platform’s own pricing.
Implementation Cost Drivers
| Cost item | What drives it | How to keep it bounded |
|---|---|---|
| Discovery | The number of workflows, offices and staff roles to map | Run the first workshop on one file type |
| Configuration | Fields, stages, automations and user roles | Build only what the gap list asks for |
| Custom development | Gaps the platform settings cannot close | Approve each item against a written gap |
| Data cleaning | Record volume, duplicates and missing fields in the old system | Clean before migration and set a cut-off for archived records |
| Integration | The number of connections and whether each syncs one way or two | Start one-way where staff do not edit both sides |
| Staff training | The number of roles and staff to train | Train each role on the accepted workflow |
| Maintenance | Platform updates, change requests and integration monitoring | Agree a monthly allowance and a change process |
Staff training works best by role once configuration is accepted, and our guide to CRM training sets out that programme.
Model Three-Year Value
Model three-year value with your brokerage’s own figures, and keep measured pilot results apart from benefits you hope for. The hypothetical brokerage below settles 30 files a month and values staff time at $55 an hour. Its consultant quoted a one-off implementation fee of $25,000 and a support agreement of $6,000 a year. A two-month pilot measured a saving of 40 minutes of administration per file and duplicate-record fixes that would take 72 hours a year. The consultant expects automated reminders to save another 20 minutes, but that saving has not been measured.
| Line | Assumption | Year 1 | Year 2 | Year 3 | Total |
|---|---|---|---|---|---|
| Measured time saved | 240 hours a year (40 minutes on each of 360 files), half in year 1 | $6,600 | $13,200 | $13,200 | $33,000 |
| Rework avoided | 72 hours a year of duplicate-record fixes, half in year 1 | $1,980 | $3,960 | $3,960 | $9,900 |
| Implementation fee | Quoted one-off fee | -$25,000 | $0 | $0 | -$25,000 |
| Support agreement | Quoted yearly fee | -$6,000 | -$6,000 | -$6,000 | -$18,000 |
| Internal administration | 48 hours a year of in-house CRM upkeep | -$2,640 | -$2,640 | -$2,640 | -$7,920 |
| Net value | Measured results only | -$25,060 | $8,520 | $8,520 | -$8,020 |
On measured results alone, this project returns $8,020 less than it costs over three years. The unmeasured 20-minute saving would add 120 hours a year, worth $3,300 in year 1 and $6,600 in each later year. With it, the three-year total becomes a gain of $8,480. Approve the project on the measured line, and confirm the reminder saving in a second pilot before you count it.
Handover and Ongoing Support
Before the final payment, settle access, change control and support in writing. Your brokerage holds the administrator accounts, the integration credentials and any middleware subscriptions. The consultant’s own logins are removed or reduced at handover. Every later change goes through a written request, a test in a sandbox and your approval before it reaches live files.
The CRM setup and maintenance agreement names who fixes an integration failure and how quickly. It also says where the configuration register, the integration schedule and the failure runbook are kept. Appoint the provider whose proposal prices each deliverable separately, accepts the acceptance checklist as its completion test and hands over these documents at the end.
