Enterprise-ready, compliance-first.
Past-client intelligence for the institutional buyer. Built for branches that need supervisor visibility, for lenders that require vendor legal review, and for compliance teams that say "show me the documentation" before they say yes.
Six modules that unlock procurement approval.
Each module addresses a specific blocker that compliance teams raise during vendor review. Status indicates current deployment state.
Employer Authorization Module
AvailableYour compliance team signs off on LO Radar as an approved data processor. One DPA-style signature, audit-trail-backed, satisfies the GLBA data-ownership question lenders ask first.
Branch Compliance Dashboard
AvailableRead-only view for the branch's compliance officer of every draft LO Radar generates. Filter by LO, by date, by trigger type. Removes the #1 reason compliance departments block LO-installed tools.
RESPA Legal Opinion Letter
In legal reviewWritten opinion from recognized RESPA counsel addressing the per-deal fee under §8 (software consideration vs referral fee), attribution mechanism, and LO indemnification posture. Distributed under NDA to enterprise procurement.
Consent Status + Re-consent Workflow
AvailableEvery past-client record stores its consent basis, the entity the consent was given to, and the date. When an LO changes employers, LO Radar prompts for re-consent before any outreach — with a TCPA-safe first-touch template that explicitly acknowledges the change.
State Disclosure Engine
10 states live · 50-state roadmapAutomatically populates state-required mortgage advertising disclosures on every outreach draft, based on the LO's licensed-state set. Currently live for CA, TX, FL, NY, IL, PA, OH, GA, NC, AZ; expanding to all 50.
Credit Signal Methodology Whitepaper
PublishedTechnical document explaining what feeds the credit-improvement flag, why our soft-pull aggregation is FCRA-clean, and why LO Radar is not a consumer reporting agency. Pre-empts institutional risk-management scrutiny.
Three institutional buyer profiles.
Mortgage branch (5-50 LOs)
Branch manager wants every LO compounding their book. Branch compliance officer wants supervisor visibility. Procurement wants a DPA signed. LO Radar Enterprise covers all three with one deployment.
Mid-sized lender (50-500 LOs)
Retention team operates centrally; LOs run their own books. SSO/SAML integration, branch-level Pipeline NPV aggregation, prioritized LOS API connectors, and a dedicated CSM. Custom compliance overlay supported.
Bank / credit-union mortgage division
Heavy regulatory scrutiny, formal vendor-management review, SOC 2-style control expectations. LO Radar's per-record access log, GLBA-aligned encryption posture, and explicit FCRA non-CRA architecture are designed for this review.
What enterprise procurement asks.
01 What does the Employer Authorization Module actually do?
What does the Employer Authorization Module actually do?
It gives your compliance team a signed, audit-trail-backed acknowledgment that LO Radar is an approved data processor handling past-client information on behalf of the employing lender. The employer signs a DPA-style authorization once; LO Radar then surfaces an active 'authorized by [Employer Name]' status on every page of every LO's interface. Authorization can be revoked at any time. This satisfies the GLBA data-ownership question that almost every enterprise vendor-management review opens with.
02 How does the Branch Compliance Dashboard work for NMLS supervision?
How does the Branch Compliance Dashboard work for NMLS supervision?
A branch's designated compliance officer is granted a read-only role inside LO Radar. They see every outreach draft generated by every LO at the branch, filterable by LO / date / trigger type, with the underlying borrower context. Drafts are timestamped and immutable. This gives the supervising entity the audit visibility NMLS expects without giving the compliance officer write access (or the ability to read past-client PII outside the draft context).
03 When does the RESPA legal opinion letter become available?
When does the RESPA legal opinion letter become available?
We are engaging recognized RESPA counsel (shortlist: Hudson Cook, Bradley Arant, McGlinchey Stafford). Expected timeline: opinion letter signed and distributable under NDA within 4-8 weeks of engagement. In the interim, the /security/respa-opinion page documents our pre-opinion compliance posture and we will share the engagement scope letter with enterprise prospects on request.
04 What's the re-consent workflow for LOs who change employers?
What's the re-consent workflow for LOs who change employers?
Every past-client record stores three consent fields: consent_basis (originator-prior-relationship, borrower-volunteered, etc.), consent_entity (the employer the consent was given to), and consent_date. When an LO changes employers and their current employer differs from the stored consent_entity, LO Radar automatically gates outreach to that contact behind a re-consent prompt. The first-touch template for re-consent is TCPA-safe — it acknowledges the LO's new employer explicitly and asks the borrower to confirm continued contact preferences before any commercial outreach.
05 Which states does the State Disclosure Engine currently cover?
Which states does the State Disclosure Engine currently cover?
Live today: CA, TX, FL, NY, IL, PA, OH, GA, NC, AZ (the 10 highest-mortgage-volume states, covering ~70% of US originations). Each state's required mortgage-advertising disclosures are automatically appended to outreach drafts when the borrower's property is in that state and the LO is licensed there. 50-state coverage is on the Q3 2026 roadmap, ordered by mortgage volume and rule complexity (next states: NJ, VA, MI, WA, MA, CO, MD, MN, IN, MO).
06 Is the Credit Signal Methodology whitepaper enough for FCRA review?
Is the Credit Signal Methodology whitepaper enough for FCRA review?
Yes for vendor-management pre-screening at most institutions. The whitepaper documents our soft-pull aggregation approach, our explicit non-consumer-reporting-agency posture, and the role of the LO's own permissible-purpose framework for any actual credit decision. For institutions that require a separate signed opinion (rather than a vendor methodology document), we will support that engagement with the same outside counsel handling the RESPA opinion.
Talk to us about your branch.
We'll bring the compliance documentation, the DPA template, and (on request) the engagement scope letter for the RESPA opinion. You bring the questions. 30 minutes.