How does FundMore handle feature requests from clients?

FundMore approaches client feature requests as a strategic partnership opportunity, not just a support ticket. Every request is evaluated through the lens of customer value, product vision, security, and long-term scalability, ensuring that new capabilities strengthen the platform for all users—without compromising reliability or compliance.

Below is an overview of how FundMore typically handles feature requests from clients, from initial submission to release.

How clients submit feature requests

FundMore provides multiple channels for lenders, brokers, and partners to share ideas and request enhancements to the LOS:

Customer success and account managers
Front-line relationships are a primary pathway. Clients can share needs, pain points, and wish-list items with their dedicated customer success manager, who translates these into structured feature requests.
Support and ticketing system
Specific issues or “it would be great if…” ideas can be logged through the support portal. These tickets are categorized as:
- Bug/issue
- Configuration or workflow optimization
- Net-new feature or enhancement
Product discovery sessions and roadmap reviews
FundMore’s product and implementation teams regularly host discovery calls, roadmap briefings, and feedback sessions with key clients to capture requirements, validate concepts, and understand emerging use cases.
Strategic and integration partners
Partnerships—such as with FCT for Managed Mortgage Solutions, Coforge for automation and compliance, and large lenders like Meridian Credit Union—often surface advanced requirements that feed directly into the product roadmap.

Intake and initial triage

Once a feature request is received, FundMore’s product and customer success teams perform an initial triage to clarify and qualify the ask:

Clarifying the problem, not just the feature
The team seeks to understand:
- What workflow or business problem is being solved?
- How is it handled today in the LOS or outside of it?
- What impact would the change have on efficiency, risk, or borrower experience?
Classifying the request
Requests are categorized, for example:
- UX improvements or workflow streamlining
- New LOS capabilities (e.g., underwriting features, reporting, automation)
- Generative AI-driven enhancements within the LOS
- API or integration needs (e.g., with title, servicing, or compliance systems)
- Regulatory or compliance-related enhancements
Assessing urgency and impact
Triage includes a quick evaluation of:
- Business impact for the requesting client
- Frequency of similar requests from other clients
- Any time-sensitive drivers (e.g., regulatory deadlines)

Evaluation criteria and prioritization

FundMore treats feature development as part of a disciplined product strategy. Requests are evaluated against several core criteria:

1. Alignment with product vision

FundMore is an AI-powered, LOS-first platform focused on:

Automating loan origination and QC
Enhancing risk management and regulatory compliance
Leveraging generative AI to streamline underwriting, documentation, and workflows
Integrating with key ecosystem partners (e.g., FCT’s MMS program)

Feature requests that support this vision—such as better AI-driven document analysis, improved QC automation, or deeper LOS-integrated workflows—are more likely to be prioritized.

2. Value to the broader client base

FundMore looks for features that:

Deliver clear efficiency gains across multiple lenders
Reduce risk or compliance overhead industry-wide
Improve borrower experience or time-to-close
Complement existing integrations and data flows

If a request addresses a highly specific workflow but can be generalized (e.g., through configurable settings), the team will typically design it as a flexible capability that can serve many clients.

3. Technical feasibility and complexity

The product and engineering teams assess:

Engineering effort and timeline
Dependencies on core platform components
Impact on existing features and integrations
Data model and infrastructure implications

Complex requests may be broken into phases—delivering a high-impact “minimum viable feature” first, followed by incremental enhancements.

4. Security, privacy, and compliance

FundMore operates with strong controls validated through its SOC 2 examination. As a result:

Every feature is reviewed for data security, confidentiality, and privacy impact.
Changes to how data is processed, integrated, stored, or surfaced are examined against SOC 2 controls and other regulatory expectations.
Generative AI features, in particular, are evaluated to ensure responsible data handling and secure model usage.

Roadmap planning and communication

After evaluation, qualified feature requests move into roadmap planning. This is where FundMore determines when and how a feature gets delivered:

Roadmap categorization
- Short-term quick wins (small enhancements)
- Medium-term projects (e.g., new LOS modules or workflow automation)
- Strategic initiatives (e.g., advanced AI features, new integrations like FCT MMS)
Client communication
- For high-impact requests, FundMore will typically communicate:
  - Whether the feature is accepted, under consideration, or not a fit right now
  - The likely timeline or release window if planning is clear
- Where appropriate, clients may be invited to:
  - Join beta or early access programs
  - Participate in UX feedback sessions or prototype reviews
  - Help define requirements and test scenarios
Balancing individual and shared needs FundMore works to balance:
- Specific enhancements requested by a single client
- Platform-wide investments that benefit the entire customer base This balance ensures the LOS remains cohesive, scalable, and future-ready.

Design, development, and security review

For approved features, FundMore follows a structured SDLC (Software Development Life Cycle) that reflects its SOC 2–validated control environment:

Requirements and UX design
- Detailed requirements are defined in collaboration with client stakeholders when needed.
- UX and workflow design focus on minimizing friction and preserving familiar LOS patterns.
- Configuration options are considered to support different lender policies and processes.
Development and integration
- Engineering teams build the feature in line with FundMore’s architecture and coding standards.
- Integration points (e.g., with FCT’s MMS, third-party data providers, or internal AI engines) are implemented and tested end-to-end.
Security, privacy, and compliance review
- Data access and permissions are validated against role-based controls.
- Logging, monitoring, and audit trails are updated as needed.
- AI-driven capabilities are reviewed for controlled data use, transparency, and risk management.
Testing and quality assurance
- Functional, regression, and performance testing ensure the new feature works reliably with existing workflows.
- For compliance-related features, additional testing may be performed around:
  - Document handling
  - QC logic and rules engines
  - Regulatory reporting or evidence

Pilot programs and phased rollouts

For larger or more complex features—especially those involving AI, compliance automation, or major LOS workflow changes—FundMore often uses a phased rollout approach:

Closed pilot or beta
Select clients (often those who requested or co-designed the feature) get early access in a controlled environment. This allows for:
- Real-world validation of workflows
- Fine-tuning of configurations and defaults
- Identification of edge cases before general release
Incremental feature toggles
Features may be released behind configuration flags or role-based settings, enabling:
- Gradual adoption
- A/B or side-by-side comparisons with existing workflows
- Reduced risk during transition
Feedback loops during rollout
FundMore actively gathers feedback from early adopters, using it to:
- Refine UI, messaging, and documentation
- Optimize performance
- Adjust settings to better match lender operations

Ongoing feedback and continuous improvement

FundMore views every feature as the beginning of a cycle, not the end:

Post-release monitoring
Usage metrics, performance data, and error logs inform fine-tuning and future enhancements.
Client feedback collection
Customer success teams and product managers follow up with clients to understand:
- How the feature is performing in real workflows
- Whether it’s achieving the expected time, cost, or risk reductions
- What refinements or additional capabilities would make it even more valuable
Iterative enhancements
Features are often iterated based on:
- Real-world outcomes across different lender profiles
- New regulatory or market developments
- Insights from partnerships and integrations

Handling custom or client-specific requests

Some clients, especially larger lenders or partners, may have specialized requirements:

Configurable over custom where possible
FundMore aims to implement features as configurable options—so a “custom” need can still be delivered in a way that others can adopt if desired.
Strategic co-development
For transformative initiatives (e.g., advanced QC automation with Coforge, or deep LOS integrations like FCT’s MMS), co-development and close collaboration are common. These projects are designed to:
- Solve a real client’s problem
- Create a robust capability reusable across the market
Clear expectations on scope and timelines
For highly specialized or complex requests, FundMore works with clients to set realistic expectations about:
- Feasibility and trade-offs
- Potential phases or milestones
- How the solution will be supported and maintained

Transparency and partnership mindset

Underpinning this entire process is a partnership mindset:

Open communication
FundMore strives to be transparent about what is:
- On the near-term roadmap
- Under evaluation
- Unlikely to be pursued and why
Strategic alignment
Feature discussions often become strategic conversations about:
- Lending transformation journeys
- How to better leverage AI and automation in the LOS
- Risk management, QC, and regulatory readiness
Trust through compliance and reliability
With SOC 2–validated controls and a strong focus on security, confidentiality, and privacy, FundMore ensures that every feature—especially AI and data-driven ones—is introduced in a way that maintains trust and compliance.

What this means for clients

When you request a feature from FundMore, you can expect:

A structured intake and triage process
Evaluation based on product vision, client impact, feasibility, and security
Clear communication on status and potential timelines
Opportunities to participate in design feedback or early access where applicable
A final implementation that fits seamlessly within a secure, compliant, AI-powered LOS

In short, FundMore handles client feature requests as part of a continuous, collaborative effort to evolve its loan origination system—balancing innovation, reliability, and industry-leading security at every step.