Jaideep Raiyani · Director, Endurance Consultants Private Limited · 2023–present
A Direct Selling Agent network for loan products across India. The Odoo 17 platform now carries 400+ DSAs.
← All case studies
Endurance
From a payout spreadsheet to a 400+ DSA network on Odoo.
Endurance Consultants runs a Direct Selling Agent network for loan products across India. In 2023 they came to us with Excel-driven operations and a payout problem. We built the Odoo 17 system that now carries 400+ DSAs and ₹1,400+ Cr in loans disbursed across a 20+ branch multi-state network. We’re still building it, including the mobile app built on Flutter that every DSA now works in.
400+
DSAs on the platform
₹1,400+ Cr
Loans disbursed
20+
Branches · multi-state network
300+
Payouts processed monthly
The first ask was a payout system. The problem was a distribution network.
Endurance is not a single back office. It is a growing network of agents who originate loans, submit files, chase their own payouts, and need to see the associates they referred and the business they wrote. Behind them, finance has to match bank dumps, vendor bills, TDS and MIS.
Before Odoo, payouts and partner activity lived in disconnected tools. Lead tracking, partner onboarding and commission logic sat nowhere the management team could trust as one number. Every DSA added made the spreadsheet worse, not better.
That is the shape of the problem we were actually handed.
Three layers, built in sequence, still extending.
Layer 01
The payout and partner core
Odoo Community 17 as the system of record. CRM and sales carry partner and lead flow; accounting carries disbursements and vendor bills; a custom partner layer we built carries MIS lines, documents, payout rates, loan-account workflows and Indian localisation. Bank-calendar logic sits on the same stack finance uses to set disbursement dates.
Layer 02
The portal the network actually runs in
Where associates work daily. Signup and verification, Udyam certificate flows, a dashboard built to facilitate DSAs so they can see their business-related information, profile changes that route through approval, invoices grouped by fiscal year, rankings for the month’s highest business, FAQ templates with presentation PDFs, payout requests that land in helpdesk, certification PDFs. Not a brochure login. The product the network touches.
Layer 03
The layer that arrived after go-live
Contests and rankings so the network sees progress the way Endurance runs competition. A CRM integration so leads sync into Odoo instead of a third spreadsheet. WhatsApp for operational alerts. And a mobile app built on Flutter, in-house on versioned APIs off the same Odoo portal: signup, referred associates, contests, invoices, fiscal-year labelling. The app is the field surface of the same ERP.
A DSA network fails quietly when portal numbers and finance numbers drift.
The hard part was never listing modules. It is keeping payout truth when money, bank calendars and partner claims meet in the same week.
The failures are small and specific. A payout requested in the portal that finance cannot match to a bank dump. A vendor bill that posts without the fiscal-year logic the MIS expects. A contest ranking that disagrees with what the DSA dashboard shows the same agent. We stay on those seams because that is where a distribution ERP earns trust or loses it.
The second hard part is growth shape. 50 DSAs behave like a team. 400+ DSAs across a 20+ branch multi-state network behave like a platform. Signup, verification, Udyam and contest mechanics all had to become product, so Endurance could add associates without adding spreadsheet operators. That is why the engagement never ended at payout go-live.
The network that ran on a payout sheet now runs on Odoo 17.
400+
DSAs on the platform
₹1,400+ Cr
Loans disbursed
20+
Branches · multi-state network
300+
Payouts processed monthly
Partners work in the portal for their business, invoices, contests and verification. The mobile app built on Flutter carries the same stack into the field, and every DSA in the network uses it.
None of those figures are a go-live spike. They are what staying on the system while the network grew looks like from the outside.
Endurance started with us in 2023. We’re still shipping.
The payout implementation was the first slice, not the last. Since then the same team has extended the portal, built contests and rankings, added Udyam and compliance surfaces, integrated the CRM, wired WhatsApp, and shipped the DSA mobile app.
Recent delivery is still portal depth, contest ranking, the DSA business dashboard, bank calendar, vendor bills, CRM sync and app work. That is the continuity claim in concrete form: the people who wrote the payout logic are the people shipping the next surface the network needs.
Surfaces
One stack, three places the network meets it.
Same ERP underneath, three product surfaces on top.
Engagement facts
- Sector
- Financial distribution · DSA network
- Client since
- 2023 · engagement active
- Model
- Odoo implementation + Managed Continuity
- Platform
- Odoo Community 17
- Portal
- Custom partner portal (associate-facing)
- Mobile
- Mobile app built on Flutter · versioned APIs off Odoo
- Integrations
- CRM sync · WhatsApp alerts · bank calendar
- Localisation
- Indian localisation · Udyam · TDS · MIS
This proves
We stay past go-live.
Endurance is the canonical case for continuity. A single payout module in 2023; a portal, contests, CRM sync, WhatsApp and a mobile app built on Flutter in 2025. Same team, same foundation, no rewrite.
→ Next
Building a distribution network on a spreadsheet that’s already too small?
Tell us what the system has to carry. We’ll come back with a real assessment - not a demo.