Reverse mortgage LOS buyer guide and demo scorecard
Compare reverse mortgage LOS options with a fictional file, a 45-minute demo agenda, exception tests and a weighted evidence scorecard.
In this article
For a lender evaluating a replacement LOS, the useful demo output is a record of what your team saw, what remains unproven and what the proposed agreement includes. Use the same fictional file across vendors. Agree on mandatory outcomes before assigning weights.
Set the decision rules before the demo
This illustrative scorecard totals 100 points. Change weights before meetings, not after a preferred vendor presents. Score each category 0 for unproven, 1 for partly observed and 2 for the full scenario observed; multiply the weight by score/2. A described or promised capability remains unproven. An essential failed scenario prevents progression regardless of the total.
| Test | Weight | Synthetic result | Points | Evidence still needed |
|---|---|---|---|---|
| HECM file moves from originator to receiving processor | 25 | 2: demonstrated in vendor environment | 25 | Repeat in intended configuration |
| Replacement document retains review context | 20 | 1: current copy shown; prior review missing | 10 | Version history and receiving-role view |
| Data correction identifies affected work | 15 | 0: described | 0 | Demonstration and impact record |
| Absent owner is covered with appropriate permissions | 15 | 2: observed | 15 | Confirm permissions in intended roles |
| Migration reconciles records and attachments | 15 | 0: roadmap promise | 0 | Sample mapping and reject report |
| Commercial scope, support and exit terms are documented | 10 | 1: draft scope only | 5 | Written agreement and export scope |
The fictional result is 55/100. If migration reconciliation is mandatory, this candidate does not progress yet. This is an evaluator-designed rubric, not a score for ReversePilot or a market ranking.
Run a one-file demo
Allocate a proposed 45 minutes: five to confirm role/configuration assumptions, ten to enter synthetic facts, ten for the receiving processor, fifteen for exceptions and five to assign evidence gaps. Use file DEMO-01, a fictional borrower label and blank sample documents, never copied production records. Ask the presenter to identify the source of each input and every skipped step.
Follow entry, preparation and handoff in the same file. Change to the receiving role: can that person identify the current owner, open evidence gap and next action? Ask a representative user to explain what they would do, rather than accepting a tour of menus.
Run three exceptions: replace an incomplete statement; correct an input that could affect later work; make the assigned owner unavailable. For each, inspect the final usable record, not just the alert. Mark integration, configuration, subscription or custom-development dependencies separately. None of these scenarios asserts an existing product capability.
Keep promises separate from acceptance
Record scenario ID, product/build, role, timestamp, evidence location, observed/described/unresolved status, follow-up owner and decision impact. Keep quoted cost and contractual scope in a separate register; a demo does not establish either. Carry unresolved tests into controlled UAT and migration acceptance before rollout.