Skip to content
RateStack
← All case studies
Case studyAnonymized

Wholesale broker network

40 LOs across 12 markets · 5 wholesale lenders

Migrated 40 loan officers from logging into five wholesale-lender portals to one workspace. Saved scenarios + per-quote drill-down. Webhook DLQ replay closed an entire class of operational tickets.

5 → 1

portals per LO

+2 hr

per LO per day

100%

webhook recoverability

−40%

ops-ticket volume

The problem

Forty loan officers were spending the first 30–45 minutes of every day logging into five wholesale-lender portals to pull current ratesheets. Pricing was reactive — when a borrower asked for alternatives, the LO had to re-enter the scenario in each portal. Operational tickets piled up around stale ratesheets, lost webhook deliveries, and broker-to-LO commission disputes that hinged on which scenario was active when.

The migration

Six weeks. The IMAP-in pipeline replaced four of the portal logins on day one; portal automation handled the fifth (a vendor with no email distribution). LOs ran their first day on RateStack with all five lenders pre-loaded and a saved-scenario library for their top 20 recurring borrower profiles.

The results

Two hours per LO per day reclaimed across the 40-person team. Webhook deliveries that used to drop during subscriber outages are now retried and replayed on demand from the DLQ — 100% recoverability replaced 80% with manual intervention. Ops-ticket volume dropped 40%, mostly via the elimination of stale-ratesheet incidents and broker-LO scenario disputes (the saved-scenario history makes "what was quoted when" a deterministic answer).

The webhook DLQ replay alone justified the migration. We used to lose deliveries when subscribers blipped; now we replay them in one click and the trace shows exactly what we did.
Director of EngineeringWholesale broker network

Want a similar outcome?

Let's see what the math looks like for you.

Case study — Wholesale broker network | RateStack