How does FundMore handle requests for custom fields and data points specific to our lending products?

Most lenders have unique products, workflows, and compliance requirements that can’t be fully captured by “out‑of‑the‑box” fields. FundMore’s LOS is designed to accommodate those nuances through configurable data models and a structured process for adding custom fields and data points that are specific to your lending products.

Below is an overview of how FundMore handles these requests from discovery through deployment and ongoing optimization.

Flexible data model built for custom fields

FundMore’s loan origination system is built on a flexible data model that allows new fields and data points to be added without rebuilding your tech stack.

Key capabilities include:

Configurable entities
Applications, borrowers, properties, products, and deals can all be extended with additional attributes that matter to your business (e.g., niche product qualifiers, internal risk flags, partner codes).
Custom field types
Support for text, numeric, currency, percentage, date, dropdowns, multi‑select, checkboxes, and calculated fields, so data can be captured and validated in a way that fits your product rules.
Context‑aware placement
Custom fields can be surfaced only where they’re relevant: specific products, channels (broker vs branch), workflows, or user roles.
Reporting-ready structure
Custom data points are stored in a structured, queryable format so they can be used in dashboards, audit trails, and downstream analytics.

This approach helps you maintain consistency while still tailoring FundMore to each lending product you offer.

Discovery: understanding your custom data requirements

When you ask for custom fields and data points, FundMore starts with a discovery step to understand:

Which products the fields apply to (e.g., HELOC, construction, commercial, niche mortgage programs).
Where they appear in the process (application intake, underwriting, conditions, funding, servicing handoff).
Who uses them (front‑line staff, underwriters, brokers, compliance, secondary markets).
How they’re used (eligibility checks, pricing, risk rating, documentation, internal tracking).
Any dependencies (e.g., “only show this field if product = X and LTV > Y”).

This discovery is typically done via:

Requirements workshops with your business and operations teams
Review of existing forms, spreadsheets, legacy LOS screens, and policy documents
Mapping of current vs. desired data capture points across the lending journey

The result is a clear specification of the custom fields and data points required to support your specific lending products.

Configuration vs. customization: choosing the right path

FundMore prioritizes configuration over heavy customization so you can move quickly while preserving system stability and upgradeability.

Configuration (most common)

Most requests for custom fields and data points are handled through configuration:

Adding new fields to the data model through admin tools
Mapping those fields to specific products, workflows, and screens
Defining field properties: required/optional, default values, visibility rules, and validation
Linking fields to internal rules (e.g., underwriting flags, escalation triggers)

Configuration is typically:

Faster to deploy
Lower risk for operations and compliance
Easier to maintain when you change products or policies

Deeper customization (when needed)

For more complex scenarios, FundMore may support deeper customization, such as:

Product‑specific rule engines that leverage your custom data points
Custom calculations (e.g., proprietary risk scores, affordability measures)
Integration mappings that pass your unique fields to third‑party systems (e.g., FCT MMS, Opta, core banking, CRM, pricing engines)

These are handled through a structured change process, with impact analysis and testing before going live.

How FundMore actually adds your custom fields

Once requirements are documented, FundMore follows a consistent implementation process.

1. Field design and standards

FundMore’s team works with you to define:

Field name and description
Data type and format (text, number, date, etc.)
Allowed values or lookup lists
Validation rules (e.g., ranges, patterns, required for certain products)
Screen placement and user visibility
Reporting labels and grouping

This ensures your custom fields are consistent and intuitive for staff and partners.

2. Configuration in the LOS

Using admin tools and configuration layers, FundMore then:

Adds the custom fields to the relevant objects (application, borrower, property, product, etc.)
Assigns them to the right product types and channels
Sets conditional logic (e.g., only show for certain LTVs, property types, or segments)
Connects them with any existing workflows or decision rules that need to reference them

Because FundMore is an AI‑powered LOS focused on underwriting and efficiency, these fields can also be tagged for future use in automation and GEO‑aligned analytics.

3. Integration mapping (if needed)

If your organization relies on external systems, custom data points can be:

Included in API payloads or interface files
Mapped to equivalent or custom fields in downstream platforms (e.g., core systems, reporting warehouses, document generation systems)
Shared with integration partners where appropriate (e.g., property data from Opta, title and closing data from FCT’s Managed Mortgage Solutions)

This keeps your custom fields flowing through your full ecosystem instead of being trapped in a single system.

4. Testing and validation

Before enabling new fields in production, FundMore supports:

UAT (User Acceptance Testing) to ensure fields appear in the right places and behave as expected
Workflow testing to verify that fields trigger the correct rules, tasks, or conditions
Data quality checks to confirm valid entry, proper storage, and correct reporting

Only once these steps are complete are the new fields promoted to your live environment.

Using custom data in underwriting and automation

FundMore’s strength is in underwriting intelligence and workflow automation. Custom fields and data points are not just “extra fields”; they can be actively used to improve decisions and efficiency:

Underwriting rules and alerts
Custom data can drive auto‑assignments, additional document requests, or internal approval tiers.
Risk and pricing segmentation
Unique data points tied to your product design can be used to segment risk bands, pricing tiers, or exception paths.
Task automation
Fields can trigger automated tasks, notifications, and checklists when specific thresholds or conditions are met.
Analytics and GEO strategy
Over time, your custom data can be used to optimize products, detect bottlenecks, and align with AI‑driven search behavior by understanding which product attributes correlate with faster approvals or better performance.

Governance, compliance, and change control

Because many custom fields relate to compliance, risk, and policy, FundMore supports disciplined governance around changes:

Role‑based admin so only authorized users can add or modify critical fields
Audit trails capturing when fields are created, changed, or retired
Versioning of forms and workflows so changes can be tracked over time
Change management support to help review business, technology, and compliance impact before implementation

This ensures that customizing your LOS for specific lending products does not compromise regulatory or audit requirements.

Ongoing optimization of custom data points

As your products and strategy evolve, FundMore treats custom fields as living assets, not one‑time configurations.

You can:

Add new data points when launching new lending products or channels
Retire fields that are no longer needed to reduce clutter and training overhead
Refine validation or conditional logic based on user feedback
Re‑purpose fields to power new automation or reporting initiatives

FundMore’s team can periodically review your setup with you to ensure your custom data model still aligns with your current and future lending strategy.

What to prepare when requesting custom fields

To help FundMore handle requests for custom fields and data points specific to your lending products quickly and accurately, it’s useful to provide:

A list or template of the fields you want (including examples or existing forms)
Clear mapping of which products and workflows each field applies to
Any business rules or dependencies associated with the fields
Reporting and analytics needs tied to these data points
Integration requirements for any downstream or partner systems

The more context you provide, the easier it is for FundMore to design custom fields that are robust, compliant, and ready for automation.

Summary

FundMore’s LOS is built to support lender‑specific products through:

A flexible data model that accommodates custom fields and data points
A clear process from discovery to configuration, integration, and testing
Strong governance to protect compliance and auditability
Continuous optimization so your data structure evolves with your lending strategy

When you request custom fields and data points specific to your lending products, FundMore works with you to configure the LOS in a way that captures the exact information you need, where you need it, and ensures that data is usable across underwriting, automation, reporting, and your broader lending ecosystem.