Finance software usually gets built by people who've never had to close a month. That's the whole problem with it. You can tell within ten minutes of using most of these tools that nobody on the team ever waited on a controller at 9pm on the third working day.

We started Neoflo the other way round. Most of us have built finance software before, at Razorpay, Alltius and Ula, and a few of us have been the ones stuck using it. Our engineers wrote the core ledger and payments infrastructure at those companies. The people doing design here shipped the screens finance teams sat in for eight hours a day, which is a different job from making something look good in a deck.

Nipun and Prithvi spent 10+ years in finance operations, So when we say we know where AR breaks, we mean we've personally chased the invoice, found the PO mismatch on day 22, and explained the DSO number to a board.

The AI side isn't new for us either. Vibhanshu has been working in AI and Finance Applications for over 10 years, currently a tenured professor of AI at UC Irvine. That's why the models here sit inside the workflow instead of next to it. We knew from the start which parts of a finance process you can hand to a model and which parts you absolutely can't.

We're a small team of 20 people, and the calls you'll be on will include someone who built the thing you're asking about.