The LenderCX platform
Not a roadmap — a live platform at www.lendercx.net, verifiable in a demo. Here is what your team gets on day one.
Modern step-wizard — tap-to-advance choice cards, autosave & resume, conditional paths (purchase/refi, self-employed, co-borrower), self-building review screen. Quick app and full URLA included as templates.
Drag-and-drop forms with 20+ field types, multi-step journey designer, state-machine workflows with tasks & document requests, a visual + SQL report builder with pivots, subtotals, calculated columns, conditional formatting and Excel / PDF export, PDF template designer, custom fields and tokens.
Admin-authored API endpoints publish any report or form as a secure integration, or run a custom action stack with declared parameters — JSON in, or a MISMO 3.4 / iLAD loan file in XML. Actions call outside systems through one egress broker, parse JSON and XML, sign payloads, loop, branch on error, schedule a later run, create tasks and ring notifications. A scheduler runs any of it on a cron; an event registry wires platform events to actions.
Bidirectional field sync on a 504-binding admin-managed registry: pipeline, milestones, documents, rate locks, loan creation, one-click deep sync, diff-based write-back with dry-run safety. Underwriting conditions are mirrored from the LOS into borrower document requests, and an accepted upload can be attached back to its condition.
Each portal chooses its loan origination system; the connector, the field map and the LOS actions are neutral behind it. Encompass is live today, and the seam is designed so a second system — LendingPad is next — is a connector, not a rebuild.
An embedded companion runs inside the loan officer's Encompass window — two-way borrower texting, keyword-driven authorization workflows, live loan-party recipients. Support for ICE's next-generation Encompass Web is already built.
Soft-pull credit ordering through the bureau integration, and text-message authorizations: the borrower replies a keyword, the platform files the signed authorization letter to the eFolder and stamps the loan.
SMS/email payment requests, hosted pay page (card + ACH) with in-browser tokenization — card data never touches our servers (SAQ A posture) — receipts, and automatic Encompass fee write-back.
Two-way SMS with consent management and keyword-reply workflows, templated email, automated messages routed by party role, feedback surveys triggered at clear-to-close and funding — scored for the officer and for the process, with a leaderboard and a friction map — and coordinate-placed e-sign with multi-recipient counter-signing.
A portal offers Spanish and the borrower chooses it: sign-in, the application, documents, messages, payments and every platform sentence, with English one click away. The lender's own words are translated in a side table with AI drafts an administrator approves; legal text is only ever counsel's translation, and the consent record keeps the English it pairs with.
The loan officer builds two to four scenarios side by side — APR beside every rate, no "best" label — priced through the portal's pricing engine or by hand, and shares a link the borrower opens on their phone with an assistant inside the page. The borrower's choice is recorded, a compliance-export PDF documents the conversation, and a weekly scan raises an officer task when a funded loan's rate environment moves.
Leads on the same contact record as the loan, with an activity timeline, a today queue, one-tap text / email / invite, routing rules with service-level escalation and a claim queue, branches and lead sources, referral-partner scorecards, speed-to-lead metrics, and click-to-call through Twilio Voice. A paid add-on, off until a portal turns it on.
Describe each role's work in plain language; the platform proposes the steps for review, lays them out on a swimlane, matches each one against a code-owned catalog of what LenderCX automates, computes the savings deterministically, renders a Workflow Assessment Report in your branding, and turns the assessed map into a draft workflow with a setup checklist. A public version runs at www.lendercx.net/assess.
Uploaded paystubs, W-2s, 1040s, 1098s and 1099s are read in our own cloud — fields extracted, a deterministic qualifying-income calculation with Selling Guide citations, disagreements with what the borrower typed flagged for staff review, and an upload check that tells the borrower at once when a file is the wrong document or unreadable. Inside the application a document read only suggests values; the borrower confirms each one. Raw documents are never sent to an outside AI.
Ask about this file: a grounded assistant over the loan's own data that answers from stored reviews, proposes follow-ups as approval cards, and never writes on its own. Since October it reads the agency guides and your overlays through the Guideline Knowledge Engine and cites the section beside the loan's facts.
A staff member asks an underwriting question — in English or Spanish — and gets a short answer with the passages it rests on from the Fannie Mae Selling Guide, HUD 4000.1, the VA Lenders Handbook, USDA HB-1-3555 and the lender's own credit policy, each with its section, its edition date and a link to the page. Every passage is rendered from the stored guide text; a citation the store cannot verify is dropped and counted. A fifty-question evaluation gates each guide's publish. A reading aid — the underwriter decides.
The platform notices a stalled application, an overdue document, an open LOS condition or a finding in a reviewed document and chases it conversationally over text — consent-gated, with AI-drafted replies staff approve before anything sends. Inside the borrower's message thread the same assistant answers first and leaves the thread waiting for staff.
Self-serve pre-approval letters the borrower or their agent regenerates at any offer price within LO-set bounds, plus a referring-agent portal with live milestones and document status — firewalled to borrower name and contact info only.
Parent portal authors the golden experience; one-click distribution to child portals with drift detection. Each child re-skins the entire product — colors, type, logo — from a branding editor, and a portal admin exports and imports their own build as a module bundle.
LOS-synced pipeline with needs-list health, loan detail with live milestones, docs, rate locks, loan-team assignment, custom fields, and one-click Encompass sync & push; watch a borrower's application live and jump in where they stall; an automation scorecard that measures what the platform did against what people did — plus an installable staff workspace.
A progressive web app borrowers and staff install on any device, with passkey (biometric) sign-in, push notifications, and a mobile-first surface on every screen.
Import/export bundles, a template library, and tiered module entitlements — a new lender portal stands up from templates in days, not implementation quarters.
How it compares
| Capability | LenderCX | Typical incumbent POS |
|---|---|---|
| Out-of-the-box application | Yes | Yes |
| Lender-editable forms & fields | Full builder | Config only |
| Lender-editable application journeys | Visual designer | Vendor ticket |
| Lender-editable workflows & automation | State machine + actions | Partial / vendor |
| Lender-built reports & documents | Visual + SQL, PDF designer | Canned |
| White-label child portals with inheritance | Native | Basic branding at best |
| Admin-managed LOS field mapping | 504-binding registry | Vendor engagement |
| Cited answers from the agency guides & your overlays | Built in, section cited | Separate tool, if any |
| Process discovery & savings assessment | In the product | Consulting engagement |
| Borrower surfaces in Spanish | Portal offers, borrower chooses | Varies |
Directional comparison based on public product documentation. Configuration ≠ composition: incumbents allow parameter changes inside vendor-defined structures; LenderCX lets the lender author the structures themselves.
A demo takes an hour, and the reskin happens in front of you — that's the point.