Frequently asked questions
The questions that come up in every evaluation, including the uncomfortable ones. Nothing here is softened for marketing.
Understanding the product
GoDravix is a configurable loan management system built by DigiWagon Technologies. It runs the full post-sanction life of a loan, approval, disbursement, interest accrual, repayment allocation, waivers, certificates, closure. Schemes, interest rates, borrowers, roles and data scoping are configuration; form fields and certificate formats are fixed in code today.
It began as a system built for a state government finance board that lends to municipalities, and is being productised into a platform for any organisation that sanctions money and recovers it over time.
Yes. GoDravix is the product name for what was previously described internally as LMS by DigiWagon. The product, the deployment and the team are the same.
A loan origination system handles everything up to the lending decision: application, documents, credit checks, underwriting, approval. A loan management system takes over at sanction and runs the loan to closure. GoDravix is the second. It does not score applicants, pull bureau data or make credit decisions.
No, and the boundary is deliberate. GoDravix does one job: it runs the loan after sanction, with the ledger depth, interest engine and audit trail that lending needs. Deposits, savings, share capital and payments infrastructure stay with your core system, and the two run side by side. Connecting them is a scoped integration today rather than something that ships in the box.
What is built, and what is not
The full loan lifecycle with maker–checker approval; single and multi-tranche disbursement; simple and monthly-compound interest with a separate penal rate; on-demand accrual with recompute; automatic penal–interest–principal repayment allocation; monthly, half-yearly and yearly frequency; grant-deduction and cheque recovery; waivers with approval authority; six certificate types; a complete running ledger; amortisation schedules generated at sanction; six default roles with a role builder, a granular permission editor and query-level data scoping; a read-only borrower portal; portfolio and borrower dashboards; five reports; an append-only audit trail with no edit path for any role; multi-factor authentication; and masters for schemes, borrowers and users.
All seven AI capabilities. Multi-tenancy and white-labelling. custom fields and certificate templates. Working capital and overdraft products, joint-liability group lending, gold and LTV lending, pre-EMI and floating-rate housing, payroll recovery, co-lending splits. The collections module: DPD buckets, ageing, promise-to-pay. Borrower-side transactions on top of the read-only borrower portal: online payment, request submission and document upload. Every external integration, including NACH, UPI, bank statement import, accounting connectors, e-sign, KYC, messaging and any REST API. SOC 2 attestation.
Yes, and we would rather do it here. The interest engine is currently order-sensitive: entering repayments in bulk before recomputing can produce wrong or negative interest, so the correct procedure is interleaved. Outstanding balance recomputes on page load and has shown instability under that pattern. Both are on the fix list, and both are the kind of thing that destroys trust when a customer finds them first.
The capability ledger on the platform page is the authoritative list, and it is kept current. Everything in the shipping column runs in the live deployment, and you can ask us to demonstrate any line of it on a call. Anything in the Built with you column is scoped and quoted as part of an engagement.
Migration and rollout
Yes, through a documented method that rebuilds each loan’s timeline and reconciles the result against your existing figures before cut-over. It has been done on a real multi-year loan with multiple disbursements and more than a dozen repayments, and on a full portfolio of roughly 195 loans in the live deployment.
Often, but not always, and we test rather than promise. Where a legacy book used an interest convention that neither simple nor monthly-compound reproduces, we quantify the variance loan by loan and agree in writing whether to replicate the historical method or adopt the new one and treat the residual as a documented adjustment.
The software configuration is rarely the long pole; migration and reconciliation are. A corporate loan book with clean records moves quickly. A government portfolio reconstructed from paper registers with an undocumented interest convention takes considerably longer. We scope after a records assessment rather than quoting a duration up front.
Six role-based user manuals with screenshots, one per role, produced for the live deployment and handed over as part of the work. Support is included in the cloud subscription and defined by agreement in an enterprise engagement.
Commercials and evaluation
Pricing is by portfolio size rather than per seat. We do not publish price points and will not quote before understanding your book, because the variables (portfolio size, record quality, development needed to close a gap you depend on, deployment shape) move the number too much for a published figure to be meaningful.
No. A self-serve trial cannot answer the question that actually decides a loan management purchase, which is whether your specific lending rules can be configured. We offer a walkthrough of the live production deployment on real data instead.
In several situations you should not. If you need feature breadth, a wide integration catalogue, SOC 2 attestation or a large support organisation, the incumbents have those and we do not.
The case for GoDravix is narrower and more specific: institutional and scheme-based lending workflows that retail-shaped platforms handle badly, a live government reference, a deterministic engine with a genuinely append-only ledger, the services capability to actually implement rather than hand over a login, and a vendor that publishes its defects.
DigiWagon Technologies Pvt. Ltd., a software company founded in 2016 and based in Ahmedabad, India, with a team of around thirty-three. GoDravix is being productised out of a live client build rather than developed speculatively.
Question not here?
Send the one that will actually decide this. We answer awkward questions in writing before a call, not after.
45 minutes | On the live deployment | A straight answer on fit