Built inside a real deployment, not a product roadmap
GoDravix is a product from DigiWagon Technologies. It exists because a state government finance board needed a loan management system and there was nothing on the market shaped like their business.
The origin
DigiWagon Technologies is a software company founded in 2016 in Ahmedabad, India, with a team of around thirty-three people. We build custom software: platforms, AI systems, mobile applications and the unglamorous integrations that hold them together.
GoDravix started as client work. A state government finance board that lends to municipalities needed a system to run its loan book, scheme-based sanctions, recovery by grant deduction, waivers authorised by board order, statutory certificates, and oversight tiers from the state down to the individual municipal body.
The available options were retail lending platforms with institutional workflows bolted on, or enterprise core banking priced for banks. We built what the requirement actually described, and ended up with a loan management system shaped for a class of lender the market underserves.
Productising honestly
Turning a client build into a product is where most of these stories go wrong. The temptation is to describe the vision as though it were the release, because the vision is more impressive and nobody checks until implementation.
We took a different approach. Every capability on this site carries an availability label. The known defects are written on the pages where they matter. The comparison page lists six situations in which you should buy from a competitor. This costs us meetings, and it means the meetings we do get are with organisations we can actually serve.
Verified 29 July 2026
We will arrange a call with the board’s accounts team through the programme’s lead contractor. Publicly, they are a state government finance board.
Why we published the defects
The first version of this site did not have a defects section. I took it out twice before it stayed in.
The argument against was obvious. You do not open with the thing that is wrong. But we had just spent a fortnight rebuilding one municipal loan by hand, multiple disbursements and more than a dozen repayments across several years, and neither interest method reproduced the board’s own closing figure. We had to go back and say so. That conversation was uncomfortable and it took about twenty minutes. Finding it in month three of a rollout would have cost the relationship.
So the order-sensitivity in the interest engine is on the interest engine page, where a buyer will actually meet it. If you are evaluating lending software and a vendor has no page like that, it is worth asking why.
Kartik Gajjar
Founder and Director, DigiWagon Technologies
What this page does not have. A customer logo wall, an analyst quadrant, or a founder photograph in a warehouse. One deployment, named on a call through the programme’s lead contractor. Everything else here is checkable in a demo, and we would rather you checked.
Four commitments
Labels are literal
Nothing is described in the present tense unless it runs in production today. Roadmap items are never counted as delivered in a contract.
Defects are published
Where the product has a known weakness that would affect you, it is written on the page where it matters rather than raised in implementation.
We say no
Six situations on the comparison page describe when to buy from a competitor. If you are in one of them, we will tell you on the first call.
We can build the gap
DigiWagon is a services company as well as a product company. Where a requirement is development rather than configuration, we can quote and build it.
Talk to the people who built it
Not a sales development representative reading from a script. The conversation is with someone who can answer a question about the interest engine.
45 minutes | On the live deployment | A straight answer on fit