Most lending technology is built around product silos: a consumer loan system here, a mortgage system there, a separate module for anything in between. Each silo runs its own database, its own rule set, and its own maintenance team, and the cost shows up every time a lender tries to launch something new.
Why silos slow lenders down
Running separate systems per product creates three recurring problems:
- Technical debt compounds. Every update to one silo risks breaking dependencies in another.
- Customer experience fragments. A customer with both a mortgage and a personal loan gets treated as two separate records, which complicates servicing and reporting.
- Time-to-market stretches to 9-18 months. By the time a new product idea clears IT, market conditions have often moved on and a competitor has already launched something similar.
The fix isn’t connecting these systems together. It’s replacing them with one configurable core.
Configuration instead of custom code
The distinction that matters here is between customisation and configuration.
Customisation means writing or modifying source code. It carries high upfront development cost, ongoing engineering overhead, and the risk that a core system update breaks whatever was custom-built on top of it.
Configuration means adjusting parameters, rules, and templates inside a graphical interface, without touching code. Updates apply without breaking anything because the configuration sits independently of the core.
A configurable LMS gives business users, not just IT teams, the tools to define a new product directly:
- Rules engines for pricing, risk assessment, and collections logic.
- Product templates for common structures (for example, an amortised instalment loan or a revolving credit line) that can be adjusted rather than rebuilt.
- Workflow builders to map the customer journey from application through servicing to repayment.
Handling products at both ends of the complexity range
A single core needs to support very different product types without separate systems for each.
High-volume, short-term products (payday loans, consumer instalment loans) need sub-second decisioning, daily interest accrual, and fee structures that change with loan tenure or amount. With pre-set interest calculation methods and repayment frequencies, this kind of product can go from configuration to deployment within a day.
Long-term secured products (auto loans, mortgages) need collateral management, escrow and tax tracking, and support for long-duration amortisation schedules. A lender selects a secured-loan template, configures fields for loan-to-value, asset tracking, and required documentation, and the product is ready without any code changes.
Specialised or hybrid products (P2P lending, lines of credit, business loans) need to handle revolving balances, usage-based repayment, or revenue-sharing models. A workflow editor can map a P2P loan’s investor fund allocation and payout process, or set rules that reset a credit line’s available balance based on repayment history.
What faster configuration changes for the business
Faster response to market moves. If a competitor launches a new product, a lender with a configurable core can adapt an existing template and launch a competing product within a month, rather than waiting out a multi-month build cycle.
Lower operational overhead. One system means one set of compliance rules, one training process, and one reporting pipeline, instead of a separate maintenance burden per product silo.
Simpler expansion into new markets. Rather than installing new software per country, a lender creates a new product variant or region profile within the same system, adjusting currency, interest caps, document requirements, and language at the configuration level while the core logic stays the same.
Configuration that carries through the full loan lifecycle
Configuring a product at the loan management level needs to flow through origination and into collections, not stop at servicing.
| Stage | What changes when a product is configured |
|---|---|
| Origination | The application portal’s document checklist and underwriting routing rules update automatically to match the new product’s requirements. |
| Servicing | Payment schedules, fee changes, rescheduling, and early settlement calculations follow the specific configuration of that loan product. |
| Collections | Workflows adjust by product risk profile - for example, a short-term high-risk loan can trigger an automated collections sequence after 7 days, while a mortgage might allow a 30-day grace period before manual outreach. |
Keeping these three stages on one configurable core removes the data handoff problems that come with running origination, servicing, and collections as separate systems.