Skip to main content

Any Loan, Any Time: How Modern Lenders Launch New Products Without Waiting on Development

In most legacy loan management systems, launching a new loan product requires a development project. A product manager writes a specification. Engineering estimates the work. The project enters a queue. Three to six months later — if the project doesn’t get delayed by higher-priority work — the new product is in production.

By the numbers: Total nonrevolving consumer credit outstanding in the U.S. reached $3.78 trillion in 2025, per the Federal Reserve G.19 Consumer Credit Report. Meanwhile, FDIC data shows 70.5% of banked U.S. households now primarily use off-site digital channels — making modern loan management software essential infrastructure for any competitive lender.

By the time the product launches, the market opportunity it was designed to address may have evolved. Worse, a competitor with a more configurable platform has already launched and is acquiring the customers you identified.

This is not a hypothetical scenario. The FDIC’s Small Business Lending Survey and Federal Reserve community banking research both document the speed at which lending market conditions change — interest rate shifts, regulatory changes, borrower demand patterns — and the competitive penalty paid by lenders who cannot respond quickly.

Modern loan management platforms, built with configuration-first architecture, have largely eliminated the development dependency for new product launches. Here is what that looks like in practice.

The Loan Configuration Manager: What It Controls

Vergent’s Loan Configuration Manager allows lenders to define any loan product as a “loan model” — a complete template that captures all rules, rates, fees, and behaviors governing that product. Creating a new loan model requires three configuration steps, all through a no-code interface:

Step 1 — Loan Model Setup. Product class (line of credit, installment, MCA, single-pay, consumer), minimum and maximum loan amounts, payment frequency options, due date rules, rescind period settings, repayment waterfall (the order in which payments are applied across fees, interest, and principal), and security type.

Step 2 — Fee Configuration. All fees associated with the product: origination fees (fixed amount or percentage), draw fees (for line of credit), late fees, NSF fees, prepaid finance charges — each with its calculation method, application timing, and refundability.

Step 3 — Rate Configuration. Fixed interest rate or variable rate (base index plus margin), APR calculation basis, rate floors and caps.

When all three steps are complete, the loan model is active and available for origination. No code. No deployment. No engineering involvement.

Multiple loan models — for different product types, different states, different rate structures — can coexist on the same platform simultaneously. A lender can offer an installment loan product in 12 states, a line of credit product in 8 states, and a merchant cash advance product nationally — each with its own fee structure, rate, and compliance rules — from a single platform instance.

The Rules Engine: Business Logic Without Code

Beyond loan model configuration, Vergent’s Rules Engine is the business logic layer that governs platform behavior across all products and operations. Rules control behavior at a granular level — from whether a draw is permitted on a delinquent LOC account, to how many days before a due date an ACH should submit, to whether a borrower with an existing open loan is eligible to apply online for a new one.

Rules are organized hierarchically: a rule set at the company level applies globally; a rule at the state level overrides the company-level rule for that state; a rule at the loan model level overrides both for that product. This structure allows a lender to define a default behavior globally, then create state-specific or product-specific exceptions without building separate configurations for each scenario.

The CFPB’s multi-state compliance framework requires lenders operating in multiple states to apply state-specific rules accurately — different rate caps, different disclosure requirements, different rescind periods. Vergent’s hierarchical rules architecture is designed for exactly this compliance requirement.

Product Line Breadth: Supported Loan Types

Vergent’s loan model architecture supports the following product classes out of the box:

  • Line of Credit (LOC): Revolving credit facilities with draw-on-demand functionality, average daily balance statement generation, and portal-initiated draw capability
  • Merchant Cash Advance (MCA): Revenue-based financing with configurable factor rates and remittance structures
  • Installment Loans: Fixed-term products with regular scheduled payments — configurable terms from short-duration to multi-year
  • Single-Pay / Short-Term: Balloon products including financed receivables and bridge facilities
  • Consumer Loans: Personal loan products governed by consumer lending regulations
  • Ancillary / Add-On Products: Optional products such as insurance products offered alongside primary loans where permitted by state regulation

Each of these can be configured as multiple distinct products — for example, a 6-month installment product and a 12-month installment product as separate loan models with different fee structures.

FAQ

How long does it take to launch a new loan product in Vergent?
A new loan model can be configured and activated in hours to days depending on complexity, with no engineering or development work required. The configuration process covers three steps: model setup, fee configuration, and rate configuration. Once complete, the product is available for origination immediately.

Does loan product configuration require technical expertise?
No. Vergent’s Loan Configuration Manager and Rules Engine use no-code interfaces designed for lending operations professionals. Configuration is performed by the lender’s operations or compliance team, not by developers. Vergent’s implementation team provides guidance during setup and is available for complex configuration questions.

Can the same platform support multiple loan products simultaneously?
Yes. Multiple loan models coexist on the same Vergent platform, each with independent fee structures, rate models, repayment rules, and compliance configurations. A lender can offer installment loans, lines of credit, and merchant cash advance products from a single platform instance, with each product managed under its own configuration.

What is a repayment waterfall in loan management?
A repayment waterfall defines the order in which incoming payments are applied across the different components of a loan balance — fees, interest, principal, and any other balance components. Vergent’s waterfall is configurable per loan model, allowing lenders to define the payment application sequence that matches their product design and regulatory requirements.

Learn more about Vergent’s loan product configuration at vergentlms.com

Sources: FDIC Small Business Lending Survey | Federal Reserve Z.1 Financial Accounts | CFPB Multi-State Compliance Guidance

Frequently Asked Questions

How long does it take to launch a new loan product?

With a modern LMS, lenders can configure and launch new loan products in days or weeks rather than months. A flexible product engine lets you define custom rate structures, eligibility rules, and compliance settings without code changes.

What makes a loan management platform flexible for product launches?

A flexible LMS allows lenders to configure new product parameters—loan amounts, terms, interest rates, fees, and eligibility rules—through a user interface rather than custom development, reducing IT dependency and accelerating time to market.

Can a single platform support multiple loan product types?

Yes. Modern LMS platforms handle consumer installment loans, lines of credit, title loans, BNPL, and commercial products within the same system, eliminating the need for separate siloed systems for each product type.

What compliance considerations apply when launching new loan products?

Every new product requires compliance review against TILA, ECOA, and applicable state usury laws. A modern LMS should automatically enforce disclosure requirements and rate caps based on the borrower’s state and product type.

Related Reading