Discovery
Map lender entities, staff roles, source systems, borrower touchpoints, repayment workflows, approval handoffs, and reporting needs.
Implementation
Start with one workflow, then scale the platform.
Covenant Desk can begin as a portal-first rollout and expand into repayment, borrower app, intake channels, AI review, and multi-company operations as the lender is ready.
What it involves
Implementation is mostly a records question, not a software one.
Installing the software is the short part. Buying a plan and reaching your own workspace takes about fifteen minutes. What actually determines how long a rollout runs is the state of the records you already hold: how many lending companies they sit under, how consistently borrowers are identified across them, whether loan numbers follow one format, and how much of the history lives in a spreadsheet somebody maintains by hand.
So the work is sequenced to answer that first. Discovery establishes what exists and who may see it. Data setup maps your source fields to the borrower record. A pilot runs one workflow end to end with real records and real staff, because that is the only honest test of whether the mapping was right. Only then does scope widen. Nothing has to cut over in a single step — your existing system and Covenant Desk can run side by side while you move across at your own pace.
Rollout path
From demo discovery to connected operation.
Data setup
Configure company units, user scope, Softmedia source mapping, import files, FPS receiving IDs, activation flow, and demo-safe validation data.
Pilot
Enable the first workflow, validate dashboard/search/profile/notice behavior, train staff, and confirm audit and permission rules.
Scale
Add entities, borrower self-service, AI review, marketplace intake, WhatsApp/email channels, management exports, and advanced controls.
Before the demo
Prepare the operating facts that determine scope.
Companies
List each lending company, branch/unit structure, brand display needs, and which staff should see each company.
Source data
Identify Softmedia instances, Excel files, notice feeds, customer identifiers, loan number formats, and fields that must be trusted.
Workflows
Choose the first workflow: Customer 360, repayment notices, borrower app, AI review, marketplace intake, or management reporting.
Controls
Confirm user roles, approval authority, borrower consent points, phone/HKID visibility, audit expectations, and export needs.
Before you commit
What lenders ask about rollout.
If yours is not here, ask it on the demo. We would rather scope it honestly than discover it in week three.
Book a demoAccount setup is about fifteen minutes. Configuring products, roles and company scope is usually same-day. Migrating an existing portfolio is the variable part, and it depends on your records rather than on us: a single company with clean loan numbers moves far faster than four companies whose borrower identities were never reconciled. The demo scopes this before you commit to anything.
One person who knows how the book is actually run, and one who can authorise decisions about roles and permissions. They are often the same person. Beyond that we need the operating facts listed below: your company structure, your source systems, the first workflow you want live, and who is allowed to see what.
It is normal, and it is better found during mapping than after go-live. Duplicate borrower identities, inconsistent loan number formats and fields that were never trusted all surface during discovery, and the mapping records which fields are authoritative. What we do not do is silently clean your data — you decide what is correct, because you are the one who has to stand behind it.
Yes, and most lenders do at first. Records import into the Covenant Desk database and scheduled sync keeps them current, so both can operate during rollout. Cut-over happens on your schedule, not ours. Covenant Desk Lending holds its own database and does not run on top of another system, so the parallel period is a migration path rather than a permanent dependency.
The pilot is the training. One workflow goes live with the people who will actually run it, using real records, and the questions that come out of that week are the ones worth answering. Staff who already work a loan book tend to need orientation on where things live rather than instruction on what the work is.
The one that currently costs the most staff time, not the one that demos best. For most lenders that is either borrower search across companies or the repayment follow-up queue, because both replace work that is being done by hand today. Intake and AI review usually follow once the borrower record is trusted.