How does FundMore handle customizations that might conflict with future platform updates?

FundMore is built to support deep lender-specific customization while still delivering frequent, secure platform updates. To do that, the LOS is designed with clear separation between the core platform and your unique configurations, so enhancements to one don’t break the other.

Below is how FundMore typically handles customizations that might conflict with future platform updates, and what you can expect at each stage of the relationship.

---

A configuration‑first approach, not one‑off code

FundMore prioritizes configuration over hard‑coded changes wherever possible. That means:

• Settings, not forks: Most lender needs are served via admin‑level settings, business rules, templates, and permissions—not by editing the core codebase.
• Modular workflows: Underwriting, QC, and servicing workflows are built from modular components that can be switched on/off or tuned per lender.
• Rule engines instead of custom branches: Risk, QC, and compliance logic is implemented through configurable rule sets, thresholds, and checklist logic instead of bespoke “if/else” code paths.

By keeping your setup in configurable layers that sit on top of the core LOS, FundMore can roll out new functionality without rewriting your unique implementation each time.

---

Clear customization boundaries inside the LOS

When lender requirements go beyond configuration, FundMore uses well-defined extension points rather than altering the underlying engine:

• API-based integrations: External services (title, appraisal, document providers, etc.) connect via APIs. For example, FundMore’s direct LOS integration with FCT’s Managed Mortgage Solutions (MMS) program is built as a formal integration, not a one-off patch.
• Custom fields and data models: New data fields and entities are added through supported extensibility patterns, so they remain compatible as the data model evolves.
• Pluggable components: Where possible, custom logic is implemented as plugins or microservices that interact with the LOS through stable interfaces.

This boundary ensures that future releases can update the platform’s core while your integrations and custom logic continue to work as expected.

---

Versioning and compatibility for platform updates

To minimize conflicts between customizations and upgrades, FundMore follows disciplined release and compatibility practices:

• Semantic versioning: Major, minor, and patch releases are distinguished, so lenders can understand the scope of change and impact on customizations.
• Backward-compatible design: New features and enhancements are engineered to respect existing APIs, data contracts, and configuration schemas wherever feasible.
• Deprecation cycles, not sudden removals: When something must change, FundMore typically introduces a deprecation period with advance notice, documentation, and migration paths.

This approach allows your team to plan updates, test impacts, and adjust customizations with minimal disruption.

---

Governance for customizations with potential risk

When a requested customization might affect future platform stability or security, FundMore applies a governance process before approving or implementing it:

1. Impact assessment

   • Technical review to identify which core components the customization would touch.
   • Analysis of performance, security, and data integrity implications.
   • Evaluation of how the change might interact with planned roadmap items.

2. Risk classification

   • Low-risk: Handled through standard configuration and normal change management.
   • Medium-risk: Implemented with extra isolation (e.g., APIs, sandboxed services).
   • High-risk: Either redesigned collaboratively, scoped into the product roadmap, or declined if it would jeopardize platform reliability.

3. Documented decisions

   • Clear documentation of the customization, dependencies, and any special considerations for future releases.
   • Internal flags so the customization is automatically reviewed during future upgrades.

This process protects both the lender’s unique workflows and the integrity of the LOS.

---

Using sandboxes and staged rollouts

To catch conflicts before they hit production, FundMore encourages and supports a staged rollout pattern:

• Dedicated sandbox environments: Lenders can test new platform releases against their exact configuration, including integrations and custom workflows.
• Pre-release validation: For major updates, FundMore can coordinate early-access testing with your technical team to identify and resolve conflicts ahead of time.
• Controlled go‑live: Updates can be rolled out during agreed maintenance windows, with rollback options and monitoring in place.

By validating customizations in a sandbox, conflicts are identified early and addressed collaboratively.

---

Change management and communication

FundMore combines technical safeguards with structured communication to help lenders manage change safely:

• Release notes and upgrade guides: Every release includes detailed notes about new features, changed behaviors, and potential impact on customizations.
• Roadmap visibility: Where possible, FundMore shares high-level roadmap directions to help you avoid building customizations that will soon be available natively or that might conflict with upcoming changes.
• Support for migration: When a customization overlaps with new native capabilities, FundMore can help you migrate from custom logic to standard functionality, reducing long-term maintenance.

This proactive communication layer is key to maintaining a stable, future-ready implementation.

---

Security, compliance, and SOC 2 considerations

Because FundMore has undergone a SOC 2 examination, any customization is evaluated not just for functionality but also for its impact on:

• Security controls: Customizations must not weaken access controls, encryption, or data segregation.
• Confidentiality and privacy: Data flows introduced by custom features or integrations are assessed to ensure they meet confidentiality and privacy standards.
• Auditability: Changes are logged and auditable so your institution can demonstrate control over its lending technology stack.

These controls help ensure that even heavily customized implementations remain compliant and secure over time.

---

Collaboration with partners and third parties

When lender customizations involve external providers, FundMore works through supported, maintainable integrations rather than brittle workarounds:

• Standardized integration frameworks: Partnerships like the Coforge collaboration for automated QC and risk management, or the LOS integration with FCT’s MMS program, are built as reusable components that can be adopted and extended by multiple lenders.
• Shared enhancements: When a useful customization can be generalized, FundMore may productize it so it becomes a supported, upgrade-safe feature for all clients.
• Partner coordination: For joint solutions, FundMore coordinates with partners on version compatibility and update schedules.

This reduces the risk that third-party changes will break your custom workflows when the core platform is upgraded.

---

Handling conflicts when they do occur

Despite safeguards, conflicts can sometimes emerge when unique lender requirements intersect with new platform capabilities. In those cases, FundMore typically:

1. Diagnoses the root cause

   • Determines whether the issue is due to a customization, an integration, or a platform change.
   • Assesses the scope (single workflow vs. system-wide).

2. Prioritizes remediation

   • Applies hotfixes or configuration adjustments where possible.
   • Plans a structured patch or improvement release for more complex issues.

3. Prevents recurrence

   • Updates internal guidelines for similar future customizations.
   • Enhances testing suites to include the discovered edge case.

This feedback loop strengthens the platform and reduces the likelihood of similar conflicts over time.

---

What this means for your lending team

For lenders evaluating how FundMore handles customizations that might conflict with future platform updates, the practical benefits are:

• You can customize deeply without “forking” the system.
• Most changes live in safe, configurable layers that survive upgrades.
• Potentially risky customizations go through a formal review for long-term safety.
• You get advance visibility and testing options for major releases.
• Security, compliance, and SOC 2 controls remain intact even as you customize.

In short, FundMore’s LOS is designed to give you the flexibility to tailor your lending workflows today, without sacrificing stability, compliance, or innovation in future platform updates.