From first call to go-live, and what your team brings to each step
You will know what each step asks of your team before you agree to it. There are nine, from a 30-minute call with a founder to support after go-live, and your current system keeps the book until a sample of your loans reconciles on both.
- First step
- A 30-minute discovery call with a founder.
- Timeline
- Six weeks to four months, indicatively, set by your products, integrations, migration depth and team time.
- The switch
- Made when a sample of loans agrees on both systems, after at least one full billing cycle.
- Available now
- Loan Management, AI Loan Servicing and RBI Model Risk Management. Loan Origination is on the roadmap.
The nine steps, in order
Three phases, and one gate between the second and the third. AI proposes, the core decides, the record proves it: you see that on your own cases from the demo onwards.
Evaluate Steps 1-4
You decide whether Lokta fits, on your own cases.
Prove Steps 5-6
Your loans run on both systems until the numbers agree. A fresh licence skips it.
Go live Steps 7-9
The book moves, the first cycle is rehearsed, and the reviews begin.
Evaluate Steps 1-4
01 Discovery call
Thirty minutes with a founder. You describe how the book is operated today and where it strains, and we say whether the work sits inside what Lokta covers. If it does not, we say so on that call.
You bring
The person who knows how the book is operated, and the question you most need answered.
02 Your questionnaire or RFI
Lenders often arrive with their own questionnaire, RFI or security review. Send it and we answer it in writing, line by line. If you have none, the RFP toolkit holds a question set you can put to every vendor on your shortlist, us among them.
You bring
Your questionnaire, and the name of the person who will score the answers.
03 NDA
Signed when you ask for it, before you share product terms, policy documents or any extract of the book.
You bring
The NDA, yours or ours, whichever your legal team prefers.
04 A demo on your own use cases
You name the situations that cost your team time today: a part-payment with a waived charge, a loan that rolled back a bucket, a co-lent account, a sourcing-partner payout. We work through those cases on the platform. For each one you see what an agent proposes, what the core decides, and what the record holds afterwards.
If your current LMS already handles a case, name it, and we take that one first.
You bring
The cases you want to see, written as real situations from your book.
Prove Steps 5-6
05 Migration assessment
If you are moving an existing book, the six-stage assessment comes next. It runs from establishing what you operate today to a written plan, and the written outcome can be a recommendation to stay. A fresh licence with no book has nothing to assess and skips ahead.
You bring
Someone with access to your current deployment, and someone from finance who can rule on a reconciliation mismatch.
06 A sample parallel run
A sample of your loans runs on both systems at once, for at least one full billing cycle. Choose the sample for difficulty: accounts with part-payments and waivers, a loan that moved between buckets, a co-lent split. The switch happens when both systems agree on the ledger balance, the classification bucket and the next instalment due for every loan in the sample.
Your current system keeps running the book until the numbers agree.
You bring
The loan tape for the sample, and a finance owner who signs off each mismatch.
Go live Steps 7-9
07 Migration and cutover
Your book migrates onto Lokta’s ledgers against one freeze date, held to a timestamp. Loan master and terms, the schedule as billed, the ledger, classification history, charges and waivers, and bureau history move as one unit. On cutover the old system stops taking entries, the final snapshot loads, and the day-end classification job runs on it before anyone touches a live account.
You bring
The book extract at the freeze date, your product definitions, and a contact for each integration: bureau, payment rails, KYC and accounting.
08 Go-live
Before the first repayment cycle, a rehearsal on four accounts with known answers: reconciled control totals, a pending mandate, a handover between operators. The morning after cutover, three numbers tie out before a new payment posts: total ledger balance, accounts by bucket, and charges outstanding. Then your team does the day’s work on Lokta, with your servicing and collections policy configured as the guardrails agents propose inside.
You bring
Your servicing and collections policy, signed off, and the staff who will work the first cycle.
09 Support and review
Our team works through go-live alongside yours. After it, support runs by email and phone, and a regular review with your owner covers what agents proposed, what your people approved, and which policy change to test next. The cadence of that review is agreed with you at go-live.
You bring
Your named owner, at every review.
What lenders said
How soon lenders said they could start, and what they saw.
Asked when he wanted servicing automated
“At this point, I can start within a month.”
On why Lokta starts after sanction
“The post-sanction area is the one which still today remains a grey area.”
After the portfolio dashboards
“This kind of concise and clear dashboard I never saw.”
On hearing the rate, ₹1,000 per crore of book a month
“It's a reasonable price.”
On the partner and payout view
“Traditional systems never had something like this.”
On seeing bucket roll-back and roll-forward at account level
“My team takes half a day today just to get this data out manually.”
At the end of the demo
“You have covered all the pain points of the smaller NBFC.”
How long it takes, and what moves it
Indicatively, six weeks to four months. A single-product lender on a fresh licence with clean data sits at the short end. A multi-product lender bringing years of history through a parallel run sits at the long end. Four things decide where your project lands, and you control most of them.
- Product countEach product needs its own day-count, appropriation order, charges and foreclosure logic set up and tested.
- Integration countEvery bureau, payment rail, KYC and accounting link carries its own test environment and its own onboarding queue.
- Migration depthA new book has no history to carry and no parallel run. A replacement carries classification, charges and bureau history intact.
- Your team’s bandwidthConfiguration and testing need your product, operations and compliance people, who are also running today’s book.
A number given before anyone has seen your product list, integration list and extract is a guess. We give a dated plan after seeing all three. The implementation timeline post works through each variable.
What your team brings
- A named ownerOne person on your side who can make a decision and chase an answer. Every step above runs faster with one.
- The loan tape or book extractA sample for the parallel run, then the full book at the freeze date. A fresh licence brings none.
- Product definitionsTerms, schedule logic, charges and foreclosure rules for each product, written down rather than held in two people’s heads.
- Servicing and collections policyThe rules agents work inside. The core enforces them and the approvals they require before the record changes.
- Integration contactsA person at each bureau, payment rail, KYC provider and accounting system, because their queues set their own pace.
Capacity and what it costs to start
Under Lokta Next 100 we take 2 implementation starts a month, so each go-live gets our team’s full attention. Bringing an existing book in carries a one-time migration fee of ₹1 lakh plus applicable taxes. A fresh licence with no book pays no migration fee. Past the Next 100 ceiling, implementation runsUSD 5,000 to 10,000, sized to migration depth and the number of integrations. The pricing page has the full terms.
What we will not do
- A screen-by-screen configuration walkthrough on the first call. The first call is about your book. Configuration is worked through on your products once there is a reason to.
- Loan Origination. It is on the roadmap. Loan Management, AI Loan Servicing and RBI Model Risk Management are available now. If you keep your own LOS, approved loans hand off to Lokta for servicing.
- Leasing. There is no leasing module.
If you keep your own origination system, the handoff post sets out what an approved loan has to carry when it arrives for servicing.
Read before the first call
- How long an LMS implementation actually takesThe four variables behind the range above.
- What has to move together when your LMS migratesFreeze date, cutover order and the day-one checks.
- Before your first repayment cycleThe four-account rehearsal before go-live.
- LOS-to-LMS handoffFor lenders that keep their own origination system.
- The LMS RFP toolkitQuestions to put to any servicing platform.
Short answers on everything else sit in the FAQ.
Questions about getting started
Timeline, what you provide, and what happens to your current system.
How long does it take to go live on Lokta?
Indicatively, six weeks to four months. The short end is a single-product lender on a fresh licence with clean data. The long end is a multi-product lender migrating years of history through a parallel run. Product count, integration count, migration depth and your team’s bandwidth decide where you land, and a dated plan follows once we have seen your product list, integration list and extract.
What does our team have to provide?
A named owner, the loan tape or book extract, written product definitions, your servicing and collections policy, and a contact at each system Lokta connects to. A lender on a fresh licence brings everything except the extract.
Will you answer our RFI and sign our NDA?
Yes to both. Send your questionnaire, RFI or security review and we reply to it in writing. The NDA is signed when you ask for it, ahead of any product terms or data changing hands.
Can we see the platform on our own cases before we commit?
Yes. A demo is offered to any prospect, and it runs on the situations you name from your own book rather than a tour of every screen.
Do we have to switch off our current system to start?
No. A sample of your loans runs on both systems for at least one full billing cycle, and the switch is made only after the ledger balances, buckets and next instalments agree on both.
Does Lokta cover loan origination or leasing?
Loan Origination is on the roadmap and is not available now. There is no leasing module. What is available now is Loan Management, AI Loan Servicing and RBI Model Risk Management, covering the book after approval.
How many lenders can start at once?
Under Lokta Next 100 we take 2 implementation starts a month, because every go-live is assisted. An approved lender who misses this month’s window takes the next open one.