All case studies
Financial services / operations ML

Propensity and throughput models for a lending operation that needed cleaner signal

Top US mortgage lender, client name withheld

Classical machine learning still wins when the problem is ranking, routing, and cycle-time reduction. This build improved lead quality and shortened operational crossing time.

Mortgage operations control room with propensity scores, lead routing, and throughput optimization

The lender did not need a chat interface. It needed better judgment embedded into daily routing: which leads to prioritize, which loans to move, and where throughput was being lost.

High-volume lead pools made small ranking errors expensive because sales capacity was fixed.

Operations teams needed recommendations that improved conversion without starving downstream teams or creating queue imbalances.

The model had to work inside a regulated environment where explainability, auditability, and operational control mattered.

Propensity ranking

We trained a selection model that scored likelihood of conversion using historical lead, borrower, channel, and interaction signals, then calibrated the output for operator review.

Throughput optimizer

A second optimization layer modeled the loan flow as a constrained operation, identifying which queues and handoffs had the largest effect on crossing time.

Human-in-the-loop controls

The system shipped with cutoffs, review bands, override reasons, and monitoring so managers could tune capacity without losing the model's signal.

  1. Benchmarked the model against the existing lead selection process before changing routing behavior.
  2. Introduced recommendations in a review workflow so managers could see the score, rationale, and operational effect.
  3. Extended the work from lead ranking into loan-throughput optimization after the first model proved lift.

Propensity lift improved by roughly fifty percent against the prior baseline.

Qualified lead volume nearly doubled because the team spent capacity on better-ranked opportunities.

The optimizer reduced crossing time from thirty-one to twenty-nine days by focusing on operational constraints, not generic automation.

Not every AI win is an agent. In high-volume operations, a well-calibrated ranking model and a sober queue optimizer can create more value than a flashy interface.

Start the conversation

A 25‑minute call to pick the first workflow.

BM
KJ
AM
BuildModal / Discovery
Pick the first workflow.

Bring one slow, manual, or expensive workflow. We will pressure test the use case and tell you the cleanest next step.

What we cover
  • Where the workflow is stuck today
  • What data, tools, and people it touches
  • Whether it fits a partner retainer, sprint, or pod
25 minutes
Google Meet
America/Toronto
Book directly

Tell us about the workflow.

Send a short note with the workflow you want to improve and the team size. We will reply with times for a 25-minute intro.

Email to book