SYSTEM BUILD

Per-workspace activation required

●  Mortgage brokers — Mortgage Pipeline Recovery

Never lose another renewal
because nobody followed up.

A renewal-recovery system for mortgage brokers: the closed-client book is scanned on a schedule, upcoming renewals surface inside a 120-day window, consent and suppression checks decide who is contactable, and renewal reviews get booked. The brokerage owns its data — a human owns every client conversation.

Broker reviewing upcoming mortgage renewals surfaced by the recovery system
WHAT THIS COULD CHANGE ACROSS A 1,200-RECORD BOOK

Illustrative model — not a measured client result · 8.7% retention rate from booked reviews.

164

Renewals surfaced — clients inside the 120-day window.

23

Reviews booked — broker conversations from the eligible cohort.

2

Clients retained — illustrative, at 8.7% retention from booked reviews.

MANUAL RENEWAL TRACKING

  1. Client funds
  2. File goes quiet
  3. Renewal date sits unwatched
  4. Window passes unnoticed
  5. Client shops around
  6. Renewal lost — discovered months later

WITH THE SYSTEM

  1. Book scanned on schedule
  2. Renewal window surfaced
  3. Consent & suppression checked
  4. Review booked to broker’s calendar
  5. Broker has the conversation

HOW THE MODEL HANGS TOGETHER

1,200 past-client records scanned → 164 inside the 120-day window → 138 pass consent and suppression (84%) → 23 renewal reviews booked → 2 retained at an 8.7% retention rate from booked reviews → $600K modelled volume at a $300,000 average balance.

Modelled for planning a pilot — not measured. Dashboards show preview data.

IndustryMortgage brokers — renewal recovery
Stackn8n · Gmail · operator dashboards — installed around the brokerage’s existing accounts
Operating needEvery upcoming renewal surfaced early with consent checked — before the client starts shopping around
01 — THE OPERATING PROBLEM

Renewals don’t announce themselves.

A brokerage can fund hundreds of mortgages and still watch renewals walk out the door. The failure is rarely the rate or the service — it is that nobody was watching the renewal window, so nobody started the conversation in time. Closed files go quiet, dates live in spreadsheets nobody opens, and the broker only learns the client refinanced elsewhere when it is already done.

  • Renewal dates scattered across spreadsheets, CRMs, and memory
  • The 120-day window passes with no trigger and no owner
  • Brokers chase new deals while past clients quietly shop around
  • Nobody knows which past clients are actually contactable
  • Lost renewals are discovered months later — if ever
  • Follow-up, when it happens, is manual and inconsistent
02 — THE OLD PROCESS

How it typically runs today.

CLIENT FUNDS (day 0) ↓ file goes quiet RENEWAL DATE SITS IN A SPREADSHEET / CRM ↓ nobody watches the 120-day window RENEWAL APPROACHES UNNOTICED ↓ client starts shopping CLIENT REFINANCES ELSEWHERE ↓ discovered months later, if ever RENEWAL LOST — recorded nowhere as lost
03 — SYSTEM ARCHITECTURE

Scan the book. Surface the window. Book the review.

Mortgage Pipeline Recovery turns the closed-client book into a renewal pipeline. Scheduled scans find clients entering the 120-day window, consent and suppression checks decide who is contactable, and renewal reviews land on the broker’s calendar — early enough to matter.

CLOSED-CLIENT BOOK ↓ SCHEDULED SCAN — renewal dates evaluated nightly ↓ RENEWAL WINDOW (120 DAYS) — upcoming renewals identified ↓ CONSENT & SUPPRESSION CHECKS — contactable cohort only ↓ RENEWAL REVIEW BOOKING — broker calendar, client notified ↓ BROKER CONVERSATION — human-owned, always ↓ RETAINED / LOST — human decision with evidence ↓ BACKUP & EXPORT — the brokerage keeps everything
n8n — workflow engine: scans, triggers, backups, reconciliation Dashboards — operator interface: renewal views, morning brief, exports Email — broker notifications: summaries, backup confirmations

HUMAN CONVERSATIONS

The system surfaces opportunities and handles scheduling mechanics. The renewal conversation itself is always human — the system never messages borrowers on its own.

04 — INSIDE THE SYSTEM

Five workflows. One heartbeat.

Five n8n workflows run the operation; an hourly heartbeat proves the schedules are alive — because a silent schedule is the one failure this system cannot afford.

n8n new-lead webhook: incoming client records captured into the book

New-Lead Intake

New client records enter through a webhook and land in the book with source preserved. Nothing arrives by spreadsheet import alone — every record has an entry point.

n8n client-replies flow: Gmail trigger with document matching to the right record

Client Replies

A Gmail trigger catches client replies and matches documents to the right record. A reply never sits in an inbox — it routes to the renewal it belongs to.

n8n weekly backup workflow: scheduled full backup of the client book

Weekly Backup

A scheduled full backup of the client book, confirmed by email. The brokerage’s data is never held hostage by the system that manages it.

n8n intake and ledger reconciliation: intake matched against the ledger

Intake / Ledger Reconciliation

Intake is matched against the ledger so nothing enters twice and nothing drifts. The book the broker sees is the book the system acts on.

n8n hourly heartbeat monitor proving schedules are alive

Heartbeat Monitor

An hourly check that the schedules actually ran. If the scan stops, the broker knows within the hour — not at the next lost renewal.

IMPLEMENTATION EVIDENCE — BUILDER WORKSPACE, NOT CLIENT DATA
05 — CAPABILITIES

What the system does.

Scans the closed-client book on a schedule — renewals surface inside the 120-day window
Consent and suppression checks before anyone counts as contactable
Renewal reviews booked straight to the broker’s calendar — early enough to matter
Morning brief — today’s renewal actions in one view, every weekday
Weekly backup plus full data export — the brokerage owns everything, always
Heartbeat monitoring — a silent schedule pages the operator within the hour
06 — OPERATOR INTERFACE

What the broker sees every morning.

Three views run the operation: the book at a glance, the renewal pipeline, and the morning brief — today’s renewal actions in one screen.

MPM overview dashboard: the closed-client book at a glance

Above: the overview — the whole book, searchable, with renewal positions visible.

MPM renewal recovery dashboard: upcoming renewals inside the window

Above: renewal recovery — who is entering the window, who is contactable, who already has a review booked.

MPM morning brief dashboard: today's renewal actions

Above: the morning brief — today’s actions, nothing else.

PREVIEW MODE — DEMO DATA, NOT CLIENT RECORDS

What the broker receives.

Product email templates keep the broker informed without opening a dashboard: the monthly retention summary, the weekly backup confirmation, and the full data export.

Monthly retention engine summary email template

Above: the monthly retention summary — renewals surfaced, reviews booked, retained.

Weekly backup complete email template

Above: the weekly backup confirmation — proof the book is safe.

Full data export email template

Above: the full data export — everything, on demand.

PRODUCT TEMPLATES — PLACEHOLDERS, NOT SENT-CLIENT PROOF
07 — IMPLEMENTATION

Proven in stages, not big-bang.

StageFocusKey results
Stage 1DiagnoseBook review first: record quality, renewal-date coverage, consent posture — or a book that isn’t worth scanning, in which case there’s no sale.
Stage 2ConfigureWorkspace activated per brokerage: book imported, consent rules set, calendar bound, notifications routed. Existing tools preserved — never silently replaced.
Stage 3AcceptBuilder acceptance runs, then Review Mode before live activation. Consent logic and copy reviewed before anything client-adjacent goes live.
Stage 4MeasureHonest baselines captured, then Day-30/60/90 evidence snapshots: renewals surfaced, reviews booked, retained. Verified, unknown, or not available — missing data never becomes zero.
08 — SAFEGUARDS

What the software can do — and what still needs a person.

ActionSystem authorityHuman requirement
Record scanningAutomatic (scheduled)Brokerage provides the book; source data stays theirs
Consent & suppressionAutomatic checksBroker defines consent policy; ambiguity goes to review
Borrower outreachNoneThe system never messages borrowers on its own
Review bookingAssistedBroker confirms; the conversation is always human
Retained / LostNoneHuman outcome decision with evidence
Backup & exportAutomatic (scheduled)Brokerage owns every export; nothing held hostage

CONSENT-FIRST DESIGN

A record without clear consent is visible but uncontactable — counted in reporting, excluded from outreach. Suppression is a first-class state, not an afterthought, and it survives re-imports.

09 — BEFORE / WITH SYSTEM

Operating models, compared.

WITHOUT A DEFINED SYSTEM

  • Renewal dates scattered and unwatched
  • 120-day window passes unnoticed
  • Past clients shop around silently
  • Contactability unknown
  • Lost renewals discovered months later
  • Follow-up manual and inconsistent
  • Book value invisible

WITH THE SYSTEM

  • Every renewal date scanned on a schedule
  • Window entries surface with days remaining
  • Consent-checked cohort, visible at all times
  • Reviews booked before clients shop
  • Heartbeat proves the scan ran
  • Weekly backup plus full export
  • Retained / lost recorded with evidence
10 — WHAT ISN’T PROVEN

No bullshit.

  • Modelled impact is not a measured client outcome
  • A surfaced renewal is not proof the client would have left
  • A booked review is not proof of a retained mortgage
  • Dashboard figures are not client records — they are preview data
  • Email templates are not proof of sent client communications
  • n8n canvases prove implementation, not production outcomes
  • Per-workspace activation is still required before any of this runs on a live book
11 — STACK & OWNERSHIP

Built on tools the brokerage already trusts.

Installed around the brokerage’s existing accounts — not hidden inside a Laneo black box. The brokerage owns its book, its accounts, its sender, and its business data.

n8nn8n GmailGmail
  • n8n — the workflow engine: scheduled scans, reply triggers, backups, reconciliation, heartbeat
  • Gmail — reply intake: client replies trigger document matching to the right record
  • Dashboards — the operator interface: book overview, renewal recovery, morning brief, exports
12 — BUILD NOTES

What implementation uncovered.

  • Consent is a data state, not a checkbox. It has to survive re-imports, merge with suppression lists, and default to uncontactable when ambiguous — otherwise the first bad send poisons the whole book.
  • The heartbeat is the most important workflow. Five workflows doing the right thing mean nothing if the schedule silently stops; the hourly proof-of-life exists because renewal windows don’t wait.
  • Reconciliation beats re-import. Matching intake against the ledger keeps one canonical record per client — duplicate records would double-count renewals and corrupt every downstream figure.
  • Backup is a trust feature. Weekly confirmed backups plus one-click full export mean the brokerage never has to wonder who really owns its book.
13 — WHAT THIS MAKES POSSIBLE

Once the book is visible.

When every renewal date is watched and every past client carries a contactability state, the brokerage stops discovering lost renewals by accident. The broker can see the next quarter’s renewal pipeline before it arrives, staff the conversation workload honestly, and measure retention against a real baseline instead of a feeling. None of that is a revenue claim — it’s what a visible book allows.

See whether this system
fits your business.

Book a free 20-minute Process Review. We’ll map how your process works today, find the biggest gap, and tell you honestly whether there’s anything worth installing.

Book a Free Process Review →

The review is free. Any third-party software or usage costs remain separate.

Find your biggest leak →