Peyvand

It was a very good program, and nobody has been able to replace it. My father stopped working as a developer long ago, so he never upgraded it either. He has known for years that the funds were still using it, and he never had the chance to go back and start the upgrade.

At each fund, someone records members' payments, loans and instalments on the old DOS screen and prints a receipt. Every fund runs the program with its own rules, and the new version has to do exactly the same for every one of them before anyone is asked to switch. The first piece is already built: PeyvandCloud sends members text-message reminders for their loan instalments, using each fund's own records.

Nobody had the manual. Thirty years of each fund's own adjustments lived in the system's files and in the habits of the people using it, and rebuilding from the screens would have thrown all of that away. So before building anything, I wrote tools that read the original system's files directly and turned them into a complete map of how it works. Then I checked that map against real data from the funds.

The move is planned in careful stages, with the new system running quietly alongside the old one until every fund's numbers match. Seventy-two funds' data has already been recovered into PeyvandCloud. It is the only project where the client is my father. I want to keep his legacy going.