Expert guide
A practical guide to pricing models, implementation budgets, and five-year total cost of ownership
Dieser Artikel ist derzeit nur auf Englisch verfügbar.
18 min read
Loan management software can cost less than $100 a month for a small servicing tool, several thousand a month for a managed lending platform, or hundreds of thousands to build as custom software. Those figures are all real and almost useless without scope. A ten-loan servicing plan, an enterprise loan subledger, and a full origination-to-collections platform are not substitutes for one another.
The budget that matters is not the subscription displayed on a pricing page. It is the five-year cost of running the target lending operation: platform, implementation, migration, integrations, external data and payment services, security, support, internal labour, product changes, and eventual exit. This guide shows how to calculate that number and compare proposals that use different pricing models.
Public prices currently show the width of the category. Bryt publishes an entry-level loan servicing plan at $89 per month for up to ten active loans. Nortridge starts at $1,200 per month for up to three full users, with a $1,750 setup fee and separately priced users, modules, training, consulting, and origination integration. EasyFlow publishes €2,000 per month for a managed full-lifecycle Launch plan and €4,000 per month for Growth. Enterprise pricing is quoted for the deployment. For comparison, ScienceSoft estimates $400,000 to $1.5 million to develop custom loan management software of average complexity.
| Public example | Published price | Scope signal | Comparison caveat |
|---|---|---|---|
| Bryt Business / Professional | $89 / $160 per month | Servicing. Business covers up to 10 active loans. Professional is positioned for growing lenders with modular add-ons. | Not a complete benchmark for full origination, decisioning, and collections. |
| Nortridge SaaS | From $1,200 per month, plus a $1,750 setup | Loan management for up to 3 full users. Extra users, advanced modules, data access, services, and LOS integration are priced separately. | The starting subscription is only one line of the full commercial schedule. |
| EasyFlow Launch / Growth | €2,000 / €4,000 per month | Full lending lifecycle, portal, back office, decisioning, collections, managed hosting, support, updates, and standard configuration. Enterprise is quoted separately. | Additional development, third-party services, and out-of-scope integrations may be separate. |
| Custom development estimate | $400,000 to $1.5 million | A vendor estimate for average-complexity custom loan management software. | A development estimate is not a fixed market tariff. It excludes time, permanent ownership, and operating responsibility unless those are stated. |
The phrase loan management software covers at least four purchases. Price comparisons become credible only after every shortlisted product is placed in the same scope category.
| Scope | Typical capabilities | What often remains outside |
|---|---|---|
| Loan tracking | Borrower records, balances, schedules, reminders, and basic reports | Automated decisioning, payment orchestration, subledger accounting, complex collections, and enterprise controls |
| Servicing or LMS | Loan booking, schedules, accruals, payments, account changes, arrears, statements, payoff, and portfolio reporting | Application capture, underwriting, the marketing funnel, or specialist recovery tools |
| End-to-end lending platform | Origination, decisioning, contracting, servicing, collections, portals, workflow, and reporting | Some external data, payments, core banking, ERP, and jurisdiction-specific services |
| Custom lending system | Capabilities designed around the lender's own operating model and architecture | The owner still funds product management, engineering, security, hosting, support, testing, and regulatory change |
A useful commercial discussion separates three numbers, then adds the horizon a board actually decides on. The platform price is what the vendor charges for access or usage. The implementation cost is what it takes to reach an accepted production state. Total cost of ownership is what the lender spends to operate, change, control, and eventually leave the system over a defined period.
| Cost view | Includes | Decision it supports |
|---|---|---|
| Headline price | Base subscription or licence, and the published billing unit | Initial affordability and vendor screening |
| Implementation budget | Discovery, configuration, migration, integrations, testing, training, cutover, and contingency | Funding and delivery approval |
| Annual run rate | Platform, usage, support, infrastructure, third parties, internal operations, and expected change | Operating budget and unit economics |
| Five-year TCO | Implementation plus all annual costs, growth, change, risk allowances, and exit | Commercial comparison and the board-level decision |
Use the same time horizon and portfolio forecast for every proposal. If a vendor will not price a line, mark it unconfirmed and run a sensitivity range. Do not enter zero. Discounting future cash flows may be appropriate for a formal investment case, but it should not hide operational assumptions.
| Model | How the bill moves | When it can fit | Risk to model |
|---|---|---|---|
| Per user or seat | Rises with named or concurrent users and with role type | Small, stable teams with predictable access | Operations and collections headcount can grow faster than the loan book. Read-only, API, and service users may be treated differently. |
| Per active loan or account | Rises with the number of billable live accounts | Servicing businesses with a clear account definition | Active is vendor-specific. Closed, charged-off, deferred, zero-balance, or recently active accounts may still be billable. |
| Per funded loan or transaction | Rises with originations, postings, payments, or another event | Variable businesses that prefer cost to follow activity | Retries, reversals, split payments, failed applications, and minimum charges can change the effective rate. |
| AUM or outstanding balance | A percentage or basis-point fee follows the size of the book | Portfolios where value is a better proxy than account count | Larger average tickets increase cost even when operational workload is unchanged. Clarify write-offs and sold or serviced assets. |
| Flat platform tier | A fixed fee covers an agreed capacity band or scope | Teams seeking predictable budgeting | Step changes at thresholds can be material. Confirm included modules, environments, storage, API use, and support. |
| Modular or hybrid | Base platform plus modules, users, volume, or usage | Lenders that need a controlled capability set | A low base price can expand quickly as essential functions are added. Model the complete target stack. |
A servicing-only system should cost less than an end-to-end platform, but it may require a separate LOS, decision engine, portal, collections tool, document service, and reporting layer. Compare the whole target architecture. List every system and manual process that the proposal replaces, retains, or introduces.
Account count is only one dimension. A book with one monthly instalment and few exceptions is different from revolving credit with daily accruals, frequent transactions, restructures, and multi-channel payments. Model active accounts, new applications, funded loans, payment events, average ticket, transaction frequency, data retention, and peak load.
Each product variant adds configuration, testing, reporting, and change work. Interest methods, day-count conventions, fee rules, payment waterfalls, grace periods, holidays, balloon payments, prepayment, restructuring, collateral, participation, multi-currency, and jurisdiction-specific notices all affect effort. Count rule variants, not just product names.
Pricing and implementation can change with branches, legal entities, portfolios, brands, currencies, user roles, approval levels, and maker-checker controls. A user count without an access model is incomplete. Operations, collections, finance, audit, compliance, customer service, partners, and service accounts may need different permissions.
Migration cost is driven by source quality and evidential depth, not only by the number of accounts. A lender may need current balances, future schedules, complete payment history, documents, collection notes, product versions, accounting events, audit records, and closed-loan archives. Every imported balance must be reconciled to an agreed control total before cutover.
01
A migration number agreed before anyone has seen the data is a guess. The profile decides the work.
02
Define which history is migrated, archived, or left read-only in the legacy system.
03
Assign ownership for cleansing, mapping, exception resolution, and sign-off.
04
Reconcile principal, interest, fees, cash, arrears, suspense, write-offs, and account counts.
05
Budget at least one rehearsal and a rollback path for material portfolios.
An API endpoint is not a production integration. The budget must include event definitions, mapping, authentication, idempotency, error handling, retries, reconciliation, monitoring, support ownership, test environments, and change control. The external service may also charge per call or transaction.
| Integration area | Project cost | Recurring cost or exposure |
|---|---|---|
| Payments and banking rails | Mandates, payment initiation, statement mapping, return codes, settlement, and reconciliation | Transaction fees, failed-payment fees, account fees, refunds, and scheme changes |
| Identity, KYC, AML, and bureaus | Consent, data mapping, decision workflow, evidence storage, and fallback handling | Per check, bureau pull, monitoring event, or document verification |
| Accounting and core banking | Chart mapping, journal design, controls, posting, the close process, and reconciliation | Support, interface monitoring, additional environments, and change projects |
| Messaging and documents | Templates, triggers, consent, localisation, delivery status, and archive | SMS, email, signature, document generation, storage, and postage |
| Data and analytics | Warehouse model, extracts, lineage, dashboards, and regulatory reporting feeds | Storage, compute, BI seats, data egress, and report maintenance |
Managed multi-tenant SaaS, single-tenant cloud, private cloud, and on-premises delivery allocate cost differently. The buyer may need penetration tests, security evidence, disaster-recovery tests, audit rights, data-processing terms, subcontractor review, resilience commitments, and service reporting. These activities consume vendor and internal time even when the software is unchanged.
These are different cost categories. Configuration uses supported product controls and should normally survive upgrades. Custom development adds code, testing, maintenance, and future compatibility obligations. A workaround leaves work with staff or another system. A proposal should label each requirement accordingly.
EasyFlow's published plans illustrate why included scope matters more than a naked price. Launch, at €2,000 per month, includes the full lending lifecycle, customer portal, back office, decisioning, collections, dashboards, standard loan-product configuration, managed hosting, support, and updates. Growth, at €4,000 per month, adds more advanced workflows, product setup, integrations, decisioning, collections, reporting, and onboarding. Additional development, third-party services, and integrations beyond the agreed scope may be quoted separately. Buyers should demand this same boundary clarity from every vendor.
Support can mean a ticket portal during business hours or a named team with response and restoration targets. Price production incidents, weekend coverage, severity definitions, service credits, environments, release support, data corrections, and root-cause analysis. Then model routine change: new products, policy changes, regulatory reporting, partner integrations, pricing rules, templates, and collections strategies.
The following example is fictional and exists to demonstrate the method. It is not an EasyFlow quote or a market estimate. Assume a lender whose portfolio grows from 10,000 to 60,000 average active loans, adds products and integrations, and requires increasing operational support. Figures are thousands of euros. A hyphen means no cost in that year.
| Cost line (€000) | Year 0 | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|---|
| Implementation and configuration | 35 | - | - | - | - | - |
| Migration and reconciliation | 25 | - | - | - | - | - |
| Integration delivery | 40 | - | - | - | - | - |
| Due diligence, testing, training | 15 | - | - | - | - | - |
| Platform | - | 48 | 54 | 66 | 78 | 90 |
| Usage and third-party services | - | 42 | 48 | 60 | 72 | 86 |
| Support, security, environments | - | 12 | 12 | 18 | 18 | 18 |
| Product and regulatory change | - | 20 | 24 | 30 | 36 | 42 |
| Internal operating labour | - | 60 | 60 | 75 | 75 | 90 |
| Exit and data transition | - | - | - | - | - | 20 |
| Annual total | 115 | 182 | 198 | 249 | 279 | 346 |
A procurement decision based only on subscription would therefore compare about one quarter of the economic picture. The exact ratio will vary. The lesson is to expose every line before negotiating the headline fee.
Create one worksheet with identical business assumptions for every provider. Separate vendor charges from external and internal costs. Then require evidence for every inclusion. A blank cost line remains a question. It never becomes zero by assumption.
| Cost line | Question to resolve | Evidence to request |
|---|---|---|
| Billing metric | Exactly what makes a user, loan, account, transaction, or asset billable? | Contract definition, plus a sample invoice using your portfolio data |
| Growth and tiers | What will the same scope cost under base, upside, and stress volumes? | Five-year price schedule, thresholds, minimums, indexation, and overage rates |
| Modules and environments | Which functions, brands, legal entities, sandboxes, storage, and APIs are included? | A scope matrix tied to the order form |
| Implementation | Which deliverables, workshops, configurations, tests, and acceptance cycles are included? | A statement of work with owners, assumptions, dates, and acceptance criteria |
| Migration | Which records and history move, who cleans them, and how are balances reconciled? | Mapping, rehearsal plan, control totals, tolerance, exception process, and rollback plan |
| Integrations | Is the price for a connector, a configured interface, or an accepted end-to-end process? | Interface specification, environments, monitoring, reconciliation, and the support model |
| Third parties | Which data, payment, messaging, signature, hosting, and storage charges are pass-through? | Rate card, expected volumes, minimums, mark-ups, and annual uplift terms |
| Support and SLA | What hours, response, restoration, service reporting, and release support apply? | SLA, severity matrix, escalation path, service credits, and exclusions |
| Change | What can trained administrators configure, and what requires paid professional services? | Configuration rights, day rates, change allowance, lead time, and regression responsibility |
| Security and compliance | Which assessments, tests, evidence, audit rights, and resilience activities are included? | Current evidence pack, testing calendar, contract terms, and a responsible-party matrix |
| Exit | How will complete data, documents, event history, and configuration be returned? | Export format, frequency, cost, assistance rate, deletion evidence, and the transition window |
01
What exact functional scope does the quote cover: origination, decisioning, servicing, collections, portal, subledger, reporting, and integrations?
02
How is every billing unit defined, and which statuses, retries, service accounts, closed loans, write-offs, or sold assets remain billable?
03
What does the five-year bill look like under the base, upside, and downside portfolio forecasts?
04
Which implementation deliverables and acceptance criteria are fixed price, and which assumptions can trigger a change order?
05
What migration history is included, who owns data cleansing, and which financial control totals must reconcile?
06
Which integrations are already supported, and what production work remains beyond API access?
07
Which third-party services are required, who contracts for them, and how are usage, minimums, mark-ups, and price changes handled?
08
What can administrators change safely without vendor engineering, and how are configuration changes tested and audited?
09
What service levels apply to production incidents, data corrections, security events, and critical reporting periods?
10
What is the full exit process, including export content, format, timing, assistance, cost, continued access, and deletion?
| Option | Cost profile | Best fit | Main risk |
|---|---|---|---|
| Managed SaaS | Recurring platform fee plus onboarding, integrations, usage, and agreed out-of-scope work | Lenders that value speed, predictable operations, upgrades, and vendor accountability | Roadmap and configuration limits. Commercial dependence must be managed through contracts and exit design. |
| Platform plus extensions | Subscription plus targeted development and ongoing compatibility testing | Distinctive workflows where a proven core still covers most lending operations | Extensions can become a private codebase if boundaries and ownership are weak. |
| Custom build | A large initial programme plus permanent product, engineering, security, hosting, support, and change teams | Unusual economics or capabilities that create durable advantage and justify ownership | The first release is only the start. Technical and regulatory maintenance continues indefinitely. |
| Open source | No proprietary licence, but implementation, hosting, security, operations, upgrades, localisation, and support remain | Institutions with strong engineering capacity and a strategic reason to own the stack | Licence savings can be outweighed by production hardening and long-term operating responsibility. |
ScienceSoft's published $400,000 to $1.5 million range is a useful reminder that custom development belongs in a different budget class from SaaS subscriptions. It should not be treated as a universal market average. A build decision also requires the cost of product ownership after launch: incident response, security, infrastructure, testing, documentation, key-person risk, and every future policy or product change.
| Lender stage | Cost concentration | Budget discipline |
|---|---|---|
| New product or first portfolio | Core platform, product configuration, essential payments, identity, accounting, and launch support | Protect runway with a complete minimum production scope. Avoid custom work that does not change risk, conversion, or control. |
| Scaling digital lender | Volume curve, automation, exception handling, analytics, collections, new products, and partner integrations | Model thresholds early. Measure cost per funded loan and per active-loan-month by product. |
| Complex or regulated institution | Migration, security, resilience, procurement, legal entities, controls, reporting, SLA, and change governance | Fund due diligence and exit as real workstreams. Lower implementation risk can be worth more than a lower licence. |
| Portfolio acquirer or servicer | Boarding, data quality, bulk migration, multiple owners, reporting, reconciliation, and varying product rules | Price repeatable boarding and exception resolution, not only steady-state accounts. |
Loan management software cost is not a number you discover. It is a model you build. Public prices are useful anchors, but they become comparable only after scope, billing units, implementation, growth, external services, internal labour, change, and exit are expressed on the same basis.
The disciplined buying process is straightforward: define the target operating model, forecast the book for five years, normalize every quote, keep unpriced lines visible, and test the cost of routine change. The winning proposal is not automatically the lowest subscription. It is the system that runs the required lending operation at the lowest credible total cost while preserving accuracy, control, adaptability, and a practical way out.
Public prices range from under $100 per month for small servicing tools to several thousand per month for managed full-lifecycle platforms. Enterprise deployments are often quote-based. Custom development may require hundreds of thousands or more. Scope and five-year TCO matter more than a category average.
The bill may depend on active loans, users, assets, transactions, modules, integrations, deployment, support, and implementation. Quote-based pricing can reflect genuine complexity, but buyers should still request a transparent formula and a five-year schedule.
It may include platform access, hosting, maintenance, updates, and standard support. Configuration, migration, integrations, premium support, non-production environments, storage, external services, and custom development vary by provider. The order form must state the boundary.
There is no reliable percentage that fits every lender. Implementation follows scope: products, organisations, migration, integrations, testing, controls, training, and cutover. Require a work breakdown and acceptance criteria instead of assuming implementation is a multiple of the licence.
Sometimes only a standard import is included. Historical events, documents, cleansing, transformations, reconciliation, rehearsals, and rollback may be separate. Define the source population and financial controls before accepting a migration price.
The best model follows a predictable business driver without punishing normal growth or creating billing ambiguity. Compare per-user, per-loan, transaction, AUM, flat-tier, and hybrid models against the same portfolio scenarios before choosing.
API access may be included while implementation is not. Budget mapping, authentication, testing, monitoring, reconciliation, support, and external provider fees. A supported connector can lower effort, but it still needs acceptance against your process.
The licence may be free. Production deployment, hosting, security, localisation, integrations, upgrades, monitoring, support, compliance, and internal engineering are not. Compare operating responsibility, not licence price alone.
A custom build can make sense when the operating model is truly distinctive, creates strategic advantage, and the organisation can own the product permanently. If most requirements are standard lending operations, a configurable platform usually reduces delivery and lifecycle risk.
Put both proposals into the same five-year worksheet using identical scope, volumes, users, products, integrations, service levels, third-party rates, change assumptions, internal labour, and exit requirements. Unpriced lines remain questions or sensitivity ranges, never zero.
A servicing-focused LMS may begin after approval or disbursement, so a separate LOS is required. An end-to-end platform can include both origination and servicing. Compare event ownership and the complete operating scope rather than the product label.
Include target products and rules, lifecycle scope, forecast volumes, the user and entity model, migration population, an integration catalogue, accounting controls, security and resilience requirements, service levels, implementation acceptance, configuration rights, a commercial schedule, and an exit specification.
Sprechen wir über Kreditvergabe
Sehen Sie, wie EasyFlow Ihre Kreditprodukte unterstützen, Ihre Abläufe automatisieren und Ihren Betrieb vereinfachen kann. Buchen Sie eine persönliche Demo und entdecken Sie, was die Plattform für Ihr Geschäft tun kann.
Ein Live-Rundgang, zugeschnitten auf die Anforderungen Ihres Geschäfts.