GoHighLevel Pipelines for DSCR and Fix-and-Flip Lenders: Simplifying a Cluttered Account

The 12+ people most responsible for one lender's revenue over the next two years were the least touched people in any system the business used. That was the first thing we saw when we sat down to simplify a cluttered GoHighLevel account.

This story is about the owner of a mortgage business who runs DSCR and fix-and-flip lending funnels with a small core team. The account had grown sub-account by sub-account until it no longer matched how the business made money. If you run a lending team, our page for mortgage loan officers covers the wider approach.

The situation

The call combined a KPI review with a rebuild of the account. The business ran several GoHighLevel sub-accounts, and they had piled up pipelines and views that did not line up with where the revenue actually came from. Two lending products carried the business: DSCR loans and fix-and-flip loans. The account did not say so.

A system that does not reflect the business teaches people to stop trusting it. That showed up in two specific places.

What was broken

First, the relationships that mattered most were not working inside any pipeline. The owner named 12+ high-impact people who would drive the next two years of revenue. They were the least touched contacts in any system, so nobody was reminded to reach out and nothing showed when someone last had.

Second, statuses were missing. One loan officer had been assigned seven investor equity leads and had contacted all seven by text. None of those statuses had been updated in GoHighLevel. From the dashboard's point of view, the leads were untouched. From the loan officer's point of view, the work was done. That gap is what makes a KPI review useless.

Underneath both problems sat the clutter of a multi-sub-account setup that had never been organized around the two funnels that mattered.

What we built

We realigned the whole account around the two funnels that carry the business.

• DSCR and fix-and-flip became the priority funnels, and the account structure now follows them.
• We built two pipelines on the deal side: a deal-intake pipeline and a deal-to-sale pipeline.
• We defined the loan officer's role as the scenario-review gate. The loan officer reviews the scenario at that point and is not the person who moves the pipeline.
• We began cleaning and consolidating the sub-accounts so everything was built and ready before the team's working session.
• A separate pipeline holds the highest-impact relationships. The owner was assigned to populate it and start proactive outreach.
• To validate the workflow, each person in the core group of five sends one live message from their assigned stage by the end of that working week.

What changed

The call ended before any result could be measured, so this section describes the change in structure and not in numbers.

The account now has two priority funnels in place of a pile of equal-weight sub-accounts. Deal intake and deal-to-sale each have a pipeline of their own. The loan officer's role is a defined gate with a clear edge. The relationships that matter most for the next two years have a home and an owner for outreach. And the live-message test gives the team a way to check that a stage update follows each real message, which is the habit the seven texted leads showed was missing.

Check your own account in ten minutes

Pick the five to ten people who will drive your next two years of revenue and search for them in your CRM. If you cannot see when each was last contacted, you have the same gap.

Then take your last handful of text conversations with leads and look for a matching stage update on each. Every text without one is activity your reports cannot see.

Finally, write one sentence per team member that starts with 'Your job in this pipeline is'. If you cannot finish the sentence, the role is not defined yet.

Frequently asked questions

Why organize a GoHighLevel account around DSCR and fix-and-flip funnels?

Because the pipelines should mirror where the revenue comes from. For this owner, those two funnels carried the business, so the account was realigned around them. Equal-weight sub-accounts make it hard to see what is working and who owns the next step.

What does it mean for a loan officer to be a scenario-review gate?

It means the loan officer's job in the pipeline is to review the loan scenario at a defined point, not to move every card between stages. Defining the role in the system keeps the loan officer's time on the review that only a loan officer can do.

How do you test a new pipeline before the whole team relies on it?

Have every person in the core group send one live message from their assigned stage. In this build, that was the validation step at the end of the working week. It shows whether the stage, the message and the hand-off work under real conditions.

What should happen in the CRM after a loan officer texts a lead?

The stage or status should be updated right away. Here, seven investor equity leads had been texted but their statuses had not been updated in GoHighLevel. Until the status changes, reports and KPI reviews show no activity even though the work was done.

If your pipeline looks busy but your best relationships and your texted leads do not show up in it, book a 30-minute AI follow-up and reporting audit. We map your funnels to your pipelines and show you what to remove.