When one client goes to several lenders, a CRM built on "one client, one deal" stops telling the truth. The deal sits in one stage, while each lender actually has the case at a stage of its own.
I built the application intake and CRM for a business that helps clients buy property and arrange the financing. One applicant is often sent to several lenders at once. Before the rebuild, every case was created by hand: data was retyped, lender progress was hard to follow and follow-up emails went out late. The stack: a Webflow site, the CRM in GoHighLevel, emails in Kit.
1. A deal per lender, not per client. The client is one contact in GoHighLevel. But for every lender they chose, they get a separate opportunity with its own status and pipeline stage. Each lender moves at its own pace, and the team sees where every application stands without notes in the margins. Duplicate deals are blocked. If a deal's notes start to read "lender A waiting for documents, lender B approved", one deal is describing several processes.
2. Validation at the form, not in the CRM. The multi-step Webflow form checks the fields before anything is sent, and the questions change with the type of financing. The client gives digital consent in the same form, and it is stored on the contact. Data that is checked before it is sent does not need cleaning later. A mistake the form lets through multiplies: into the contact, into every deal and into every email.
3. Tags as the single language between systems. The CRM decides the state of a case, and Kit only reacts to it: it receives tags from the CRM and sends onboarding and follow-up emails by lender and by case status. Emails follow events, not just timers, and the team can override a sequence by hand. When the state of a case lives in one place, nobody has to ask which system to believe.
No half-created cases. Internal notifications and checks make sure a case cannot get stuck half-created.
An application now goes from the website to the CRM, the lender pipelines and the right emails without exports, copying or manual triggers. The team works the cases instead of creating them.
What to check in your own CRM
- Can one client have several processes running in parallel? Then the deal belongs to the process, not to the client.
- Are duplicate deals blocked?
- Is the data validated before the form is sent?
- Which system decides the state of a case, and which one only reacts to it?
- Can the team override an automated sequence by hand?