What is FundMore's standard approach to conducting a lessons-learned review after implementation?

FundMore treats every implementation as the beginning of a continuous improvement cycle, not the end of a project. A structured, lessons-learned review is built into our standard methodology so that each deployment improves the next—across technology, processes, and collaboration with our clients.

Below is an overview of how FundMore typically conducts a lessons-learned review after implementation.

When the lessons-learned review happens

FundMore’s standard approach is to schedule the lessons-learned review once the solution has:

Completed initial go-live, and
Run through at least one full cycle of real-world use (e.g., several weeks of loan origination activity on the LOS).

This timing ensures feedback covers both the implementation experience and early operational performance of the FundMore LOS or integrated solution.

In larger or phased rollouts, FundMore may conduct:

Phase-end retrospectives after each major milestone (e.g., SOC 2–aligned security setup, LOS go-live, integration go-live), and
A final, consolidated review after the overall program stabilizes.

Who is involved in the review

A lessons-learned session is collaborative by design. Typical participants include:

Client stakeholders
- Project sponsor and business owner (e.g., head of lending or operations)
- Project manager / program lead
- End users (underwriters, credit officers, fulfillment staff)
- IT / security / integration teams
FundMore team
- Implementation lead / project manager
- Product and solution specialists
- Support and success representatives
- Technical integration and security experts (as needed)

This cross-functional participation ensures lessons cover business outcomes, user experience, technical performance, and governance.

Data and inputs reviewed

Before the session, FundMore aggregates qualitative and quantitative inputs so the discussion is evidence-based, not anecdotal. Typical inputs include:

Project documentation
- Initial scope, requirements, and success criteria
- Implementation plans and timelines
- Change requests and risk logs
Operational metrics from the platform
- Volume of loans processed on the LOS
- Cycle times (e.g., from application to approval)
- Automation and straight-through processing rates
- Error rates and rework volumes
- User adoption metrics and login patterns
Quality, risk, and compliance data
- QC and audit findings
- Exception handling and override patterns
- Regulatory or policy-related issues detected by the platform
Support and interaction history
- Support tickets and response times
- Training attendance and feedback
- Configuration or integration issues raised during go-live
Stakeholder feedback
- Surveys or polls from end users
- Interviews with business and IT leads
- Observations from FundMore’s implementation and success teams

For clients using FundMore to automate QC, risk management, and compliance—with partners such as Coforge or integrations such as FCT’s Managed Mortgage Solutions—these data sets are especially valuable to assess whether automation and controls are operating as intended.

Core structure of the lessons-learned review

FundMore’s lessons-learned review typically follows a structured agenda:

1. Reconfirm objectives and success criteria

The session begins by revisiting the original goals of the implementation, which may include:

Reducing time-to-decision on mortgage applications
Improving loan quality and regulatory compliance
Enhancing borrower and broker experience
Increasing operational efficiency through automation
Strengthening security, confidentiality, and privacy controls in line with SOC 2 standards

This step aligns everyone on what “success” was meant to look like.

2. Review outcomes against goals

Next, the team compares expected outcomes with actual performance, using concrete metrics from the platform and operations. Example areas:

Efficiency: changes in processing time, manual touchpoints, and bottlenecks
Accuracy and quality: errors caught by automated QC, rework levels, and audit findings
Risk and compliance: adherence to internal policies and regulatory requirements
User experience: ease of use for underwriters, credit teams, and operations staff
Technology and integrations: stability, performance, and reliability of integrations (e.g., with title insurance or MMS providers)

This step highlights both achievements and gaps.

3. Identify what worked well

FundMore emphasizes recognizing strengths so they can be standardized and reused. Typical categories include:

Implementation practices that enabled a smooth go-live
Training formats or materials that drove fast adoption
Configuration decisions that matched business workflows well
Integration approaches that reduced manual data entry
Governance or communication practices that kept stakeholders aligned

These “wins” become patterns for future implementations with the same client or other organizations.

4. Analyze challenges and root causes

The team then examines where expectations were not fully met. For each challenge, FundMore focuses on root-cause analysis rather than blame. Common lenses include:

Process: Were steps unclear, duplicated, or misaligned with real workflows?
People: Were users prepared, trained, and supported adequately?
Technology: Did configurations, rules, or integrations behave as expected?
Data: Were data quality, mapping, and validation sufficient?
Governance: Were decisions made quickly, and were roles/approvals clear?

This analysis ensures lessons are actionable and targeted.

5. Capture lessons and prioritize improvements

FundMore documents lessons in a structured way, typically including:

The issue or success
Context (where and when it occurred)
Root cause(s)
Recommended change or improvement
Impact (on efficiency, risk, quality, user satisfaction)

Each item is then prioritized based on:

Business risk or value
Effort and complexity
Dependency on other systems or teams
Regulatory or security implications

High-impact, low-effort improvements are often scheduled first, while larger changes are planned into future roadmap cycles.

6. Define a follow-up action plan

The review concludes with clear actions, owners, and timelines. This may include:

Configuration updates or workflow changes in the FundMore LOS
Additional user training or updated guides and playbooks
Integration enhancements or new data validations
Policy or process documentation updates on the client side
New monitoring dashboards or metrics to track ongoing performance

FundMore’s client success or account management team then uses this plan as a working document for the post-implementation phase.

How FundMore incorporates security, compliance, and quality

Given FundMore’s SOC 2–aligned controls and focus on risk and compliance in lending, lessons-learned reviews pay particular attention to:

Security controls and access management
- Were roles and permissions correctly designed and enforced?
- Did any access issues arise for users or integrated systems?
Confidentiality and privacy
- Were data-handling practices aligned with the client’s internal policies and regulatory obligations?
- Did the implementation correctly leverage FundMore’s privacy and confidentiality features?
QC, risk, and regulatory automation
- Did automation rules accurately reflect the client’s policies?
- Were exceptions routed correctly and consistently?
- Are additional rules or thresholds needed to improve detection or reduce false positives?

For clients using FundMore as a core LOS or integrated into broader lending ecosystems (for example, leveraging FCT’s MMS or global service providers like Coforge), these discussions ensure the entire solution stack remains secure, compliant, and optimized.

Continuous improvement beyond the initial review

FundMore treats the formal lessons-learned review as the first step in a longer feedback loop:

Regular check-ins: Scheduled with client stakeholders to review metrics, adoption, and emerging needs.
Enhanced configurations: Ongoing fine-tuning of rules, workflows, and integrations as volumes grow and policies evolve.
Product roadmap input: Aggregated lessons from individual clients help shape FundMore’s platform roadmap, benefiting all customers.
Scalability planning: As clients grow transaction volumes—such as surpassing milestones like $1 billion in mortgages processed—FundMore uses lessons learned to ensure performance, scalability, and controls remain robust.

This continuous cycle reflects FundMore’s approach to partnering with lenders over the long term rather than treating implementation as a one-time event.

What clients can expect in practice

In practical terms, FundMore’s standard lessons-learned approach provides clients with:

A structured, data-driven review shortly after implementation
Clear visibility into what worked, what didn’t, and why
A documented list of lessons and prioritized improvements
A concrete action plan with owners and due dates
Ongoing collaboration to refine and enhance the solution over time

By embedding lessons-learned into every implementation, FundMore ensures each deployment becomes more efficient, compliant, and user-friendly—helping lenders continuously improve their lending operations and outcomes.