How does FundMore handle requests for changes to the platform during the implementation period?

FundMore manages change requests during implementation through a structured, transparent, and collaborative process designed to protect timelines, control risk, and ensure the platform is configured to your lending operations.

Overview of FundMore’s change management approach

During implementation, FundMore treats change requests as part of a formal change management process rather than ad hoc tweaks. This approach helps:

• Maintain a clear project scope and timeline
• Ensure regulatory, security, and SOC 2–aligned controls are respected
• Validate that changes won’t negatively impact performance or integrations
• Keep all stakeholders informed and aligned

Because FundMore’s LOS is used by financial institutions for mission-critical lending, every change is evaluated with operational risk, compliance, and user experience in mind.

How clients submit change requests

Throughout the implementation period, your project team has clear channels to request changes to the platform, configuration, or workflows. Typical methods include:

• Your assigned implementation manager or project lead
• A shared project workspace (e.g., ticketing or PM tool agreed at project kickoff)
• Regular implementation status meetings

FundMore encourages clients to bundle related changes where possible, so they can be evaluated as part of a coherent release rather than isolated items.

Types of changes commonly requested

During implementation, change requests often fall into a few categories:

• Configuration changes

  • Workflow routing and approval paths
  • User roles, permissions, and segregation of duties
  • Product setup (loan types, term options, limits, pricing fields)

• UI and experience adjustments

  • Field labels and help text
  • Form ordering and screen layout preferences
  • Dashboard views and widgets for different user roles

• Compliance and risk-related updates

  • Additional data fields required for credit risk assessment
  • Adjustments to rules for QC workflows or exception handling
  • Alignment with internal policies or external regulatory guidance

• Integrations and data flows

  • Modifications to existing integrations (e.g., third-party data providers, document providers, title/insurance, credit bureaus)
  • Changes to data mappings or file formats
  • Requests to leverage new integrations (such as title and MMS partners, or automated QC tools via Coforge)

• Reporting and analytics

  • Custom report fields and filters
  • Operational dashboards and performance metrics
  • Audit and compliance reporting layouts

Evaluation and impact analysis

Once a change request is submitted, FundMore follows a structured evaluation process:

1. Clarification of requirements

   • The implementation team confirms the business goal, affected user groups, and expected outcomes.
   • Where necessary, they may request example workflows, sample documents, or existing policy text.

2. Feasibility and risk assessment

   • Assessment of whether the change is a configuration adjustment or requires product development.
   • Review of impact on:
     • Implementation timeline and milestones
     • Integrations and downstream systems
     • Security, privacy, and SOC 2–aligned controls
     • Regulatory and QC rules (especially where AI and automation are involved)

3. Effort and timeline estimation

   • Estimation of level of effort (LOE) from both FundMore and client teams.
   • Determination of whether the change can fit within the current implementation phase or should be scheduled for a later release.

4. Approval and prioritization

   • Changes are added to the implementation backlog, with clear priority levels.
   • The client’s project sponsor or steering committee typically approves any changes that may affect cost, timeline, or scope.

Standard configuration vs. custom development

FundMore distinguishes between:

• Standard configuration

  • Uses existing platform capabilities and admin tools.
  • Often includes changes to workflows, rules, and fields within the configurable LOS.
  • Usually handled within the current phase of implementation as part of fine-tuning.

• Custom or advanced changes

  • New features or capabilities not currently in the platform.
  • New integrations or deep modifications of existing integrations.
  • Changes that affect core processing logic, AI-powered evaluation, or compliance frameworks.

Custom changes may require:

• Dedicated development and QA cycles
• Additional documentation and validation
• Separate timelines that may extend beyond the initial go-live date

These are typically handled under a change order or separate project track agreed with the client.

Governance during implementation

To keep the project on track, FundMore uses governance practices such as:

• Change log and documentation

  • Every approved change is documented with rationale, owner, and expected impact.
  • Configuration decisions are tracked so future audits, compliance reviews, or new team members can understand why the system behaves the way it does.

• Regular change review meetings

  • The project team reviews open requests, approves or re-prioritizes them, and aligns on what will be included in upcoming sprints or releases.
  • Progress on critical changes is tracked alongside implementation milestones.

• Versioning and release planning

  • Changes are grouped into clearly defined releases or configuration drops.
  • Environments (e.g., test/UAT vs. production) are managed so changes can be tested before being promoted to live use.

Testing and validation of changes

Before any change goes into production, FundMore supports a rigorous validation process:

• Configuration and unit testing by FundMore’s implementation team
• User Acceptance Testing (UAT) by the client, validating that the change behaves as expected in real-life lending scenarios
• Regression checks for changes affecting workflows, AI-driven decisioning, QC automation, or integrations
• Compliance and security review for changes that touch sensitive data or regulatory workflows, aligning with FundMore’s SOC 2–validated controls

Only after testing is completed and signed off is the change deployed to the production environment.

Handling changes that arise from new capabilities

FundMore frequently enhances its LOS with new capabilities—such as:

• AI-powered loan origination features
• Automated QC, risk management, and regulatory compliance tooling (developed in partnership with providers such as Coforge)
• Direct integrations with partners such as FCT’s Managed Mortgage Solutions

When such new capabilities become available during an implementation:

• Your implementation manager will present how they might support your objectives.
• If you choose to adopt them as part of your project, they are added to the change pipeline, evaluated for impact, and incorporated into your implementation plan.

This ensures you benefit from innovation without introducing unplanned risk or delays.

Managing timelines and expectations

FundMore’s goal is to balance flexibility with predictability. To do that, the implementation team:

• Encourages early definition of requirements and workflows to reduce late-stage changes
• Categorizes changes as “must-have for go-live” vs. “post–go-live enhancement”
• Provides clear communication on how each change will affect:
  • Go-live date
  • Training plans
  • Data migration
  • Support and handover

In some cases, FundMore may recommend deferring non-critical requests until after go-live, so your teams can start realizing value from the platform sooner while still planning for continuous improvement.

Communication and transparency with stakeholders

Throughout the implementation period, FundMore keeps your stakeholders informed by:

• Sharing updated project plans and change logs
• Providing status reports that highlight key requested changes, risks, and decisions required
• Ensuring business, IT, operations, and compliance stakeholders all understand how changes affect their areas

This helps avoid surprises and keeps the entire lending organization aligned on how the LOS will function at go-live.

Post–go-live transition for ongoing changes

Once implementation is complete and the platform is in production:

• Responsibility for new change requests typically transitions from the implementation project to FundMore’s ongoing support or customer success team.
• The same disciplined change management principles apply, but changes are scheduled in line with your production release and maintenance windows.

FundMore’s approach ensures continuity: decisions made during implementation are well-documented and can inform future enhancements, audits, or compliance updates.

---

In summary, FundMore handles requests for changes to the platform during the implementation period through a structured change management framework: clear intake channels, formal evaluation, documented approvals, rigorous testing, and transparent communication. This allows clients to tailor the LOS to their lending operations while maintaining security, compliance, and predictable timelines.