Source Reddit post: https://www.reddit.com/r/loanoriginators/comments/1udodp4/i_hate_trying_to_get_my_borrowers_to_send/
One-line thesis: Build a lightweight chase queue for independent mortgage loan originators and small broker teams that turns lender/underwriter condition lists into borrower-friendly missing-doc checklists, reminders, status tracking, and handoff notes without replacing the LOS/POS.
Classification: opportunity / idea_filter.
This is a cautious BUILD if positioned as a narrow workflow layer, not another mortgage portal. The Reddit seed is unusually direct pain language: an originator says they hate trying to get borrowers to send documents, and the visible search snippet mentions post-close work. Treat that as pain discovery, not market proof. The stronger validation is that the mortgage stack already contains first-party borrower portals, condition linking, document upload, reminders, and post-closing QC requirements — meaning the job is real, compliance-sensitive, and operationally expensive.
The wedge is the space between broad LOS/POS systems and the daily loan-officer grind: borrower does not understand a condition, sends the wrong thing, forgets a missing doc, uploads a blurry/partial file, or leaves the processor/LO with no clean status trail. A small tool can win if it makes conditions human-readable, keeps borrowers serious about getting the loan done, and gives the LO/processor a clean chase queue and handoff log.
Best initial customer:
Avoid at first:
1. The Reddit seed contains explicit buyer language. The title is “I hate trying to get my borrowers to send documents,” and the parent search result showed it as fresh. The visible snippet also mentions “post close,” which fits the hypothesis that the pain is not just initial application intake; it extends through underwriting conditions and cleanup.
2. Borrowers are formally expected to answer document requests during closing. CFPB’s borrower guidance says borrowers may be asked to provide additional financial information and submit documents to verify what they previously reported, and it tells borrowers to ask their loan officer what additional documents may be needed. That validates the plain-English borrower side of the chase: these are recurring borrower tasks, not an edge case.
3. Post-closing and approval-condition documentation are real lender obligations. Fannie Mae Selling Guide D1-3-02 says lenders selected for QC must verify the accuracy and integrity of information used to support underwriting, review underwriting decisions, DU findings, approval conditions, origination and closing documents, and data integrity. It also says lenders must ensure data submitted to DU is true, correct, and complete and that the loan file contains documentation supporting submitted data. This supports the seriousness of “conditions” and “post close” cleanup.
4. Major platforms already advertise document upload, status, and reminders. ICE Encompass Consumer Connect says borrowers can complete online applications, instantly engage with their loan officer, securely upload and eSign documents, get real-time status updates, and be invited/reminded to complete abandoned applications. That validates demand for digital borrower engagement — but also signals a crowded incumbent environment.
5. Broker-native systems already collect documents based on rules. ARIVE markets a complete LOS/POS/PPE for mortgage brokers with a branded, mobile-friendly secure client portal to collect loan applications and supporting documents based on rules, plus lender marketplace status updates. That suggests the startup should not compete as “the broker portal,” but as a condition-chase layer around messy lender/underwriter outputs.
6. Condition-to-document linking is an explicit workflow. LendingPad’s help article explains uploading a document, selecting one or multiple underwriting conditions from a conditions dropdown, and letting underwriters view documents linked with each condition from the UW/Conditions panel. This is very close to the core workflow: the problem is not that condition tracking is unknown; it is that the borrower-facing chase and LO handoff remain painful.
7. Specialized mortgage intake/checklist tools already use the same promise. PerfectLO says it creates a detailed document checklist based on borrower answers, imports into the current LOS, provides text/email notifications, allows reminder text, and offers a secure Document Center for borrower uploads. Floify similarly appears in search results for needs-list email/text notifications and mortgage document collection. These competitors validate the category and budget while forcing a more precise wedge.
Weekend-buildable first version: Condition Chase Queue for Mortgage Brokers.
Inputs:
Core workflow:
1. Condition parser: Convert lender/underwriter wording into structured items: condition, borrower-friendly explanation, accepted proof examples, owner, due date, status, and risk level.
2. Borrower checklist: Mobile-friendly link showing only what the borrower needs to do, using plain language around missing docs, explanations, and conditions.
3. Reminder cadence: Email/SMS reminders for “borrowers to send documents,” with configurable tone: friendly, urgent, deadline, post-close cleanup. Escalate stale items back to the LO/processor.
4. Upload and evidence capture: Allow borrower uploads or mark “sent by email / in lender portal / handled by processor.” Store timestamps, filenames, notes, and rejection reason.
5. Handoff notes: Generate a clean status summary for processor/lender: received, still missing, borrower says N/A, needs LO explanation, post close.
6. No LOS replacement: Export PDF/CSV/email summary and copy-ready notes. Integrations can come later through Zapier/webhooks, ARIVE/LendingPad/Encompass APIs, or browser-assist flows.
7. Compliance guardrails: No underwriting decisioning, no credit advice, no “condition cleared” unless marked by a human. Encrypt docs, limit retention, maintain audit logs, and use consented borrower communication.
| Dimension | Score | Rationale |
|---|---|---|
| Pain | 8 | The seed pain is direct, and platform/vendor behavior confirms document/condition chase is a real operational loop. |
| Willingness to pay | 6 | Brokers pay for LOS/POS/processors, but may expect this to be included in existing tools. Budget exists if it saves live deals or processor time. |
| Reachability | 8 | Independent LOs and brokers are reachable through Reddit, Facebook, AIME-style communities, processor groups, and LOS-specific communities. |
| MVP simplicity | 7 | A paste-to-checklist/reminder/status tool is feasible without deep integration; secure docs and SMS compliance add work. |
| Competition | 4 | Many incumbents already cover portals, document upload, notifications, and condition linking. The wedge must be very specific. |
| Overall | 7 | Worth piloting as a narrow post-submission condition-chase queue for small broker teams, not as a full POS/LOS replacement. |
The biggest weakness is competition. The evidence shows borrower portals, document checklists, reminders, and condition linking are already common in serious mortgage platforms. A generic “borrower document collection app” is probably a bad idea. The opportunity only survives if the product attacks a neglected micro-workflow: converting lender/underwriter conditions into borrower-friendly tasks and persistent chase notes across a small broker team’s messy reality.
The Reddit source is a useful spark but not sufficient proof. I could not fetch the live Reddit thread content due Reddit blocking, so only the permalink, title, freshness evidence from the parent run, and visible search snippet should be treated as Reddit evidence. Customer discovery should ask 10+ independent LOs/processors how often files stall because of missing docs, how they currently chase, and whether their LOS/POS already solves it.
The report may overestimate willingness to pay because many LOs view admin tools as overhead, and small brokers often tolerate manual work. The stronger buyer may be a broker-owner or processor managing multiple originators, not an individual LO.
The MVP should avoid storing sensitive documents until trust is proven. A first pilot could be checklist/reminder/status-only, with links back to the existing secure portal, then add secure uploads after compliance posture is credible.
Real recurring mortgage admin pain with revenue linkage, but the wedge must prove it beats existing LOS/POS portals without becoming an integration-heavy compliance product.