Procure to pay and loan origination workflows for large Indian enterprises, from the requisition to the sanction letter.
Expenzing builds spend management and lending workflow software for Indian enterprises. My ground was the unglamorous middle of fintech: purchase requisitions, approval matrices, invoice matching, and the journey a loan application takes from a branch officer's desk to a sanction letter. The clients were large and demanding, Bajaj, HDB Hiranandani and Akasa Air among them, and the requirement specifications I wrote there lifted transaction speeds by 40 percent.
What the work taught me is that most of fintech is modeling somebody's policy document correctly the first time. A delegation of authority matrix looks simple in a PDF and becomes forty edge cases in production. The product wins or loses on those questions, not on the dashboard.
Not a facelift. A new formula for how budgets are computed and consumed, and a new way for finance teams to actually work with it day to day: how money is allocated, committed and burned down against real spend. The old module described budgets. The new one runs them.
A complete, ready to build UI mockup for an employee uniform management product: every screen, every state, every flow. It ties together four systems that normally never talk: HR for who joined and what they need, procurement for buying it, inventory for stock and reissue, and the uniform lifecycle itself.
Built real time credit approvals and disbursements into the procurement flow for HDB Hiranandani. It started as an idea, shipped as a complex cross-team application, and ended up a module clients pay for.
Owned the mobile app lifecycle end to end, from UI mockups to release, plus an OCR module that read invoices so accounts payable did not have to retype them.
Found a critical reconciliation defect in production, then formulated and tested the credit note and open invoice logic that fixed it. Product managers who can read a ledger are surprisingly rare.
Requirements from a Bajaj scale client arrive as a policy binder, not a user story. Turning that into configurable product, without forking the codebase per client, was the real discipline the job taught.
Users tolerate an ugly screen. They do not tolerate a purchase order stuck with no explanation. State, ownership and escalation were where all the real design happened.
Every enterprise believes its process is unique. Ninety percent of it is the same eight patterns wearing different names. Building the patterns once, configurable, was the difference between a product and a services shop.
Years of watching big companies buy workflow software made the gap obvious: the small business that needs it most can afford none of it. PitStop is that lesson, applied.
Approval matrices, invoice matching, loan journeys. I have scars and opinions.
venkatesh@venkateshgardas.com