Everything before the application and everything after funding happens outside the loan origination system — referral partners, the pre-approval funnel, milestone updates, the database you already paid to acquire. Twopir builds the Salesforce layer that owns those, and draws a clean boundary with the LOS instead of duplicating it. Partners, pipeline, borrowers and recapture on one architecture.
Trusted by 500+ organizations — including lenders, fintech platforms and financial services firms building their operations on Salesforce with Twopir Consulting. The rail below carries both clients and the certified ecosystem partnerships we deliver with.
Built for Lending Operations
Loan origination systems are very good at the loan file and were never designed for anything else. Almost every lost origination happens before the application or after the funding — which is precisely where the LOS has nothing to say.
The agent and builder relationships that drive purchase volume live in an LO's phone. When they leave, the production leaves. The company cannot see which partners actually send funded loans, or which ones stopped six weeks ago.
Nobody wrote down which system owns which field, so the borrower is keyed twice, the two drift, and every report has to be caveated. The fix is not a bigger integration — it is a boundary decision that was never made.
Borrowers and their agents mostly complain about silence, not speed. Status updates get sent when a processor has a spare moment, which means the loans under stress — the ones generating the calls — are the ones that get updated last.
Underwriting raises conditions, the processor emails the borrower, the borrower sends a photo of a bank statement to the wrong address. Nobody has one view of what is outstanding, so files sit in suspense and pull-through drops for reasons nobody can name afterwards.
Lead cost is measured, funded volume is measured, and the path between them is not. Which partner, campaign, product or LO turns applications into fundings — and where in the pipeline the rest die — is a question the LOS cannot answer and the CRM was never asked.
You paid to acquire every one of those borrowers. Without rate-change, equity and anniversary triggers running against them, the next transaction goes to whoever is marketing — and recapture, the cheapest origination a lender can make, is left on the table.
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. In lending, most failed CRM projects fail the same way: the CRM is built as a shadow copy of the loan origination system. Two systems then hold the same borrower, they disagree within a week, and originators go back to the one that actually funds loans.
We start by drawing the boundary and writing it down. The LOS owns the loan file, the disclosures and the regulatory record of the transaction. The CRM owns the relationship: the referral partner, the pre-application funnel, the communications, the marketing consent, and every borrower between one transaction and the next. Each field has exactly one owner, and the integration moves status in one direction rather than trying to keep two masters in step.
Lending sits alongside the three real estate segments we architect — residential, commercial and investment — under the Salesforce for real estate practice, and shares a great deal with our fintech and Salesforce consulting work. Lenders that take referrals from brokerages usually want the residential page read alongside this one.
One thing we are explicit about: Twopir Consulting builds systems, not compliance opinions. We design architecture that makes your compliance and legal teams' requirements enforceable and auditable — timing, disclosure, record retention, fair-lending-safe automation — and we implement what they specify. We do not provide legal or regulatory advice, and no page on this site should be read as any.
This is the decision every lending CRM project stands or falls on, and the one most of them skip. Below is how we normally set it. Every row is a design choice, not a rule — but every row has to be a choice somebody made, wrote down, and enforced in the integration.
| Record or process | Owner | Direction | Why it sits there |
|---|---|---|---|
| DemandReferral partner | CRM | CRM only | The LOS has no concept of a relationship that has not produced a loan yet, and partner development is mostly what happens before it does. |
| DemandLead & pre-qualification | CRM | CRM only | Most inquiries never become applications. Holding them in the LOS pollutes the pipeline and the reporting that depends on it. |
| HandoffApplication started | Point of sale → LOS | CRM writes once | The application is the handoff point. The CRM passes the borrower it already holds so nobody re-keys, then stops writing to the file. |
| Loan fileLoan data & disclosures | LOS | LOS → CRM | The loan file is the regulatory record of the transaction. Nothing outside the LOS should be able to change it. |
| Loan fileMilestone & status | LOS | LOS → CRM | The LOS knows the truth; the CRM turns each change into the borrower, agent and partner communication the LOS will not send. |
| Loan fileConditions | LOS | LOS → CRM | Underwriting owns the condition. The CRM owns chasing it — reminders, the borrower-facing list, and escalation as it ages. |
| RelationshipCommunication history | CRM | CRM only | Every call, text and email across every transaction belongs on one borrower record that outlives any individual loan. |
| RelationshipMarketing consent | CRM | CRM only | Consent and opt-out have to be enforced at the point of sending, which is the CRM, and honoured across every channel at once. |
| After fundingFunded loan & terms | LOS | LOS → CRM | A funded copy in the CRM — rate, term, product, close date — is what makes rate-change and equity triggers possible later. |
| After fundingRecapture & retention | CRM | CRM only | Servicing may be sold; the relationship is not. Recapture runs entirely in the CRM, off the funded copy above. |
Read the middle column again: the loan file moves one way only. Almost every painful lending integration we are asked to rescue is one that tried to make the CRM writeable into the loan file and then spent two years reconciling the two.
Six areas, all of them on the CRM side of the boundary. Salesforce provides the platform and, through Financial Services Cloud, a mortgage data model; what we build is the operating model on top of it.
Make agents, builders, advisors and past clients a company asset with measurable production — the single highest-value thing a purchase-focused lender can put in a CRM.
Everything from first inquiry to a pre-approval letter, held in the CRM so the pipeline is not polluted with applications that were never going to start.
A one-way, field-level contract between the CRM and the loan origination system, documented and enforced — not a two-way sync that quietly diverges.
Every status change becomes the right message to the right party automatically, and conditions get chased by the system rather than by whoever has capacity.
The cheapest origination a lender makes is the second one to the same borrower. This is the work that turns a funded database back into pipeline.
The production reporting a lender runs the business on — and, where a CRM is already in place and unused, the work to make it usable.
Five stages, one continuous engagement. In lending the second stage is the one that decides the project: the boundary gets agreed with production, operations and compliance in the room, and signed off before anything is built.
We trace a loan from inquiry to funding and a borrower from funding to their next transaction, and find every point where a human moves data between two systems.
Field-level ownership between CRM and LOS is agreed and documented, alongside the partner, borrower and loan model and the controls compliance requires.
The CRM layer, the LOS integration, the milestone journeys and the condition workflows are built together and tested against real loan scenarios, not sample records.
Rollout branch by branch with the past-borrower database migrated and cleaned, and with originators onboarded on what the CRM does that the LOS does not.
New channels, products and acquired branches extend the same model, with pull-through and recapture reviewed as production numbers rather than as project metrics.
A lending stack has more systems touching the same borrower than almost any other industry. Each entry below names what moves and in which direction.
Salesforce's industry layer. Its mortgage data model provides prebuilt objects for the residential loan application and the applicants behind it — address, employment, income, assets, liabilities and declarations — modelled on the U.S. Uniform Residential Loan Application, alongside a guided 1003-compliant application flow and document tracking. Read the Salesforce mortgage data model for the full entity list.
The system of record for the loan file. Milestones, status, conditions and the funded terms flow from the LOS into the CRM; the borrower and property pass the other way exactly once, at application. Nothing else in the CRM is allowed to write to the file.
The borrower-facing application. The CRM hands it the borrower it already holds so nothing is re-keyed, and receives back the fact that an application started — which is the event that moves the opportunity and starts the milestone journeys.
Product and pricing engines and credit services sit behind the pre-qualification step. The CRM stores the outcome and the product discussed — never the raw credit data — so pre-approval status is reportable without the CRM becoming a consumer-report repository.
Partner agreements, marketing consents and borrower-supplied condition documents are captured through the CRM and routed to the right file, with the envelope status on the record — so chasing a document is a workflow rather than an email thread.
Milestone texts to borrowers and agents send from the record and replies log back to it. Consent state and quiet hours are enforced centrally at the point of sending, so an individual originator cannot text someone who has opted out.
Where partner marketing and borrower nurture run in HubSpot while production runs in Salesforce, we set one owner for the contact and one for consent, sync engagement and campaign attribution into Salesforce, and push funded volume back so campaigns are measured on loans closed.
Salesforce's own AI layer. Useful for summarising a long borrower history before a call, drafting a milestone update for review, and ranking which past borrowers are worth contacting on a rate move. In a regulated lending context we scope it behind human review and inside the controls your compliance team sets, not as an autonomous decision-maker.
The engagements below come from adjacent parts of Twopir's practice — real estate and financial services — and are labelled with the segment they were delivered in. The architectural pattern is the one this page describes: unify the record, automate the paperwork and the follow-up, and make compliance a property of the system rather than a habit.
AML/KYC, inquiries, contracts and commission unified on one Salesforce platform, with API-driven synchronisation.
Guided next-best-action recommendations built on Salesforce for a regulated financial services book.
Lenders don't struggle because they lack a CRM. They struggle because nobody ever decided which system owns the borrower — and every problem downstream descends from that.
Field-level ownership between the CRM and the LOS is agreed, written down and enforced in the integration. It is an unglamorous deliverable and it is the difference between a CRM lenders use and a second system they resent.
Your compliance and legal teams set the requirements; we make them structural — audit trails, timing you can evidence, consent enforced at the point of sending, and automation that cannot quietly do something a person would not be allowed to do.
An LO between showings will not maintain a CRM that gives them nothing back. The system has to surface the next call, the partner who has gone quiet and the borrower whose rate is now in the money — otherwise it is data entry with extra steps.
Acquisition, origination and recapture are one lifecycle on one record. That is what makes recapture rate a number you can manage, and it is the cheapest origination volume a lender has available to it.
New channels, new products, acquired branches and a swing from refi to purchase and back should all be absorbed by the same architecture. Lending volume is cyclical; the system should not need rebuilding each time the cycle turns.
No, and a project that tries to is the most reliable way to fail. The LOS remains the system of record for the loan file, the disclosures and the regulatory record of the transaction. Salesforce owns everything around it: the referral partner, the pre-application funnel, the communications, marketing consent, and the borrower between one transaction and the next. Milestones and conditions flow from the LOS into Salesforce; the borrower passes the other way once, at application. That boundary is the deliverable.
It depends on how much of the borrower's financial picture you need to hold. Financial Services Cloud adds a mortgage data model with prebuilt objects for the residential loan application and the applicants behind it — addresses, employment, income, assets, liabilities and declarations — modelled on the U.S. Uniform Residential Loan Application, plus a guided 1003-compliant application flow and document tracking. If your CRM's job is partners, the pre-application funnel and recapture, and the loan detail stays in the LOS, a leaner build on the core platform is often the more sensible spend. We size both against what you actually need to report on.
By building what your compliance team specifies and making it auditable, rather than by deciding it ourselves. Referral arrangements in US mortgage are governed by RESPA and its implementing regulation, which the CFPB publishes guidance on — and the rules on what may be given or received for a referral are strict and fact-specific. What we do is make partner relationships, co-marketing activity and any agreements visible and logged so your compliance function can review and evidence them. Twopir Consulting builds systems; we do not give legal or regulatory advice.
The disclosures themselves belong in the LOS, which is where they are generated, delivered and evidenced. What the CRM contributes is visibility and escalation: a clock running against each file, alerts when something is approaching its window, and an audit trail of every communication sent. The underlying timing requirements sit in the TILA-RESPA and Equal Credit Opportunity rules, which the CFPB publishes and your compliance team owns. We implement to their specification and do not interpret the rules for you.
It starts with a copy of each funded loan's own terms — rate, product, term, balance and close date — written back from the LOS into the CRM. Everything else runs off that: a rate-move trigger that fires only for borrowers whose specific rate is now above market, an equity trigger as values move, anniversary and life-event journeys, and in-market signals where the lender licenses them. The alert routes to the originating loan officer rather than to a generic queue, because a call from the person who closed the loan converts at a completely different rate. Recapture is then reported as a production number, not a marketing one.
Not by mandate — originators who feel a CRM is surveillance will keep a private list, and you will have both problems instead of one. It works when the system gives the LO something they cannot get from their phone: the rate alert on their own past borrowers, the partner who has not sent a referral in six weeks, the pre-approval that is about to expire. Pair that with a permission model where the LO's activity is theirs and the aggregate is the company's, and adoption follows on its own. Getting that split right before go-live is most of the work.
HubSpot is a strong fit for a broker shop or a smaller lender whose pressing problem is partner marketing, borrower nurture and getting to a working system quickly. Salesforce is the stronger answer once the requirements include a real LOS integration, branch and channel permissioning, licence-aware routing, a mortgage data model, or reporting that has to satisfy an audit. Many lenders run both, and we build the boundary explicitly. Twopir Consulting is a Salesforce Partner and a HubSpot Partner, so the recommendation is not decided by what we can implement.
Twopir Consulting builds the Salesforce layer lenders originate on — referral partners, the pre-application funnel, milestone and condition communication, and recapture — with a clean, documented boundary against the loan origination system.
Speak with a team that understands origination, LOS boundaries & recapture
