A 30-day CRM implementation plan for a lending brokerage
Most CRM rollouts fail on adoption, not on software: the reps keep working out of the old spreadsheet and the new system goes stale. This plan gets a brokerage of two to twenty people onto a new CRM in 30 days, in the order that keeps deals moving while you switch.
By the Ferrylend team · Buying a CRM · Published · 3 min read
Plans from
$69/ user / month
Billed monthly, or less billed annually. No seat minimum.
- Setup fee
- $999, waived (introductory offer)
- Data migration
- Free (introductory offer)
Introductory offer, for a limited time.
- We import your data from your current CRM or spreadsheets.
- Month to month. Export your data any time.
Before day one: an owner and three numbers
Pick one person who owns the rollout. In a small shop that is usually the owner or the processor who already keeps the spreadsheet honest. They decide the stages, approve the import and answer questions for the first month.
Then write down three numbers from the old way, so you can tell at day 30 whether the new system helped:
- Speed to first call on new leads, in hours. See speed to lead for loan brokers.
- Submissions per funded deal: how many lenders a deal goes to before it funds.
- Commissions outstanding: how much lenders owe you that you have not reconciled.
Week 1: set up the system around how you already work
- Users and roles. Invite everyone with the right role. Reps should see only their own leads and deals; managers and processors see the floor. Decide this now, because it is awkward to take access away later.
- Pipeline stages and lead statuses. Use the words your team already says out loud (App out, Docs in, Submitted, Approved, Funded). Fewer stages beat more.
- Lead sources, with cost. List every vendor and channel and what each costs, so the source report can show cost per funded deal from the first week.
- Decline reasons. A short, fixed list (revenue too low, too many positions, NSFs, industry, credit). Free-text declines cannot be reported on.
- Custom fields. Only the ones you actually filter or report on. Everything else goes in notes.
- Email templates. The application request, the docs chase, and one submission template per lender type.
In our CRM each of these is a lesson in the owner and admin setup track of Learn, written from the app itself.
Week 1, continued: bring the data in
Import in this order: leads, then merchants and owners, then lenders, then open deals. Leave closed and dead files for last, or leave them in an archive. Check duplicates on a small file before you run the big one. The migration guide has the export and clean-up steps. If you are coming from spreadsheets, the Google Sheets layout post shows how tabs map to records.
Week 2: lenders, commissions and a two-rep pilot
- Lenders and their criteria. Enter your top ten lenders properly: programs, minimum revenue, time in business, credit, positions, industries and states. This is the part that pays back fastest, because matching is only as good as the criteria.
- Commission defaults and rep splits. Set the default split per rep and partner, so every funded deal creates the right expected commissions.
- The pilot. Two reps, one experienced and one new, work every new lead and deal only in the CRM for the week. Everyone else stays on the old system.
- A daily ten minutes. The rollout owner reads the pilot's pipeline every morning and fixes whatever confused them the day before: a missing status, a field nobody fills in, a template that reads wrong.
Week 3: everyone in, old system read-only
Move the whole team. New leads and deals go only into the CRM; the old system or sheet becomes read-only for anything opened before the cutover. Run the morning pipeline meeting from the CRM's board and dashboard, not from anyone's notes. When a rep asks where something is, show them in the system rather than answering from memory. That is how the habit forms.
One rule that does most of the work
If it is not in the CRM, it did not happen. Commission splits, bonuses and lead assignments are calculated from what is in the system, so reps have a reason to keep it current.
Week 4: close out and measure
- Move the deals that were still open in the old system, or let them finish there and mark the old system retired on a set date.
- Upload last month's lender commission statements and reconcile them, so commissions outstanding starts from a clean number.
- Compare the three numbers from day zero. If speed to first call has not improved, look at who gets new leads and how they hear about them.
- Cancel the old subscription once a full month of deals lives in the new system and an export of the old data is saved somewhere safe.
What usually goes wrong
| Problem | Fix |
|---|---|
| Reps keep a private spreadsheet | Pay commissions and assign leads only from the CRM |
| Too many stages and fields | Cut back to what the morning meeting actually uses |
| Lender criteria never get entered | Enter the top ten lenders in week 2 and add the rest as deals need them |
| The owner is the only one who knows how it works | Make the rollout owner someone who will be there every day, and write down the stage and status meanings |
| Import duplicates | Test on a small file first and match on phone and email |
Questions
How long does a CRM implementation take for a small brokerage?
With clean exports and a decided owner, two to four weeks. Setup and import take days; most of the time goes into the pilot and getting every rep working only in the new system.
Should we run the old and new systems side by side?
For about a week, yes, but only for files opened before the cutover. New leads and deals should go only into the new CRM from the day the whole team moves, or the old system never goes away.
What should we set up first?
Users and roles, pipeline stages, lead sources and decline reasons, then the import. Lender criteria and commission splits come next, because they need real deals to check against.
Run your shop on one system
Leads, statements, lender matching, submissions, offers and commissions in one CRM. We import your data from your current system.
Keep reading
- FeatureDeal pipelineA deal pipeline built for lending: 22 statuses in five phases, board and table views, time in status, stips and conditions, underwriting notes and a locked pricing block.Read
- FeatureLead import and application formImport CSV or XLSX lead lists with column mapping and duplicate checks, and give merchants an application link that collects details, consent and bank statements.Read
- FeatureLender matchingStore every lender's criteria once and see which lenders each deal qualifies for, with the rule behind every pass, warning and fail. Built for MCA and business lending.Read
- GuideHow to migrate your MCA CRM dataA practical guide to moving an ISO or lending shop to a new CRM: exporting from your current CRM or spreadsheets, cleaning files, mapping the import, lenders, statuses and a parallel run.Read
- GuideHow to choose an MCA CRMWhat an MCA CRM should do, the questions to ask every vendor, a scoring sheet and the real first-year cost math for a broker or ISO shop.Read
- BlogGoogle Sheets as a CRM for loan brokersHow to run a loan or MCA brokerage on Google Sheets or Excel: the five tabs and columns that work, the formulas, where a spreadsheet breaks, and when to move.Read
- BlogSpeed to lead for MCA and business loan brokersWhy the first hour decides most funding leads, what the research says, and how a loan or MCA brokerage gets new leads called in minutes, legally and every time.Read
- BlogMCA leads: the types, how to judge a vendor, and how to work themLive transfers, exclusive web leads, aged leads and UCC data compared: how fresh each is, how to vet an MCA lead vendor, and how to measure cost per funded deal.Read
- BlogHow to become an MCA broker (ISO)How to start as a merchant cash advance broker or ISO: registrations, ISO agreements, points and clawbacks, building a funder list, getting merchants and staying organized.Read