A missed payment exposed the visibility problem
One tenant's rent stopped coming in. Identifying the source of the missing payments took about four months. The team won the engagement, and Nirvaan led development and owned client delivery, connecting preparation, review, invoicing and reconciliation while keeping approval with people.
Own the whole delivery
Nirvaan owned architecture, development, QA, deployment, production operations and vendor selection/integration. The platform brought status and drafts into WhatsApp, with maker-checker approvals, reconciliation, follow-ups and dashboards. Human-approved drafts went through Webtel GSP for GST e-invoicing and tenant delivery.
Resume the workflow from persisted state
FosterX is CloudRedux's organisational AI platform, built by a team; Nirvaan is one of its primary engineers. The billing platform used FosterX's Temporal recovery to resume each failed workflow from its last persisted step. That gave recovery a place in the production workflow rather than leaving progress inside a single agent conversation. Reconciliation and follow-ups connected execution to the client's ongoing billing operations.
Separate preparation from authorization
Maker-checker review keeps draft preparation and approval separate. A human approves the draft before Webtel GSP submission. Nirvaan worked directly with the client's CXOs, translated their requirements into software and remained their point of contact after launch. His delivery responsibility continued into production support.
Before a step, workflow code controls RBAC and permitted tools. Retrieved company data and live system state ground the model input. Code checks the output before execution, then maker-checker approval authorizes the draft before invoice submission. Automated review supports these checks; approval stays with the person.
From days to a reviewed billing run
The platform processed ₹22.5 crore in invoices in its first six months. Monthly billing that had taken days became about 20 minutes of human review plus about 10 minutes of automated processing per monthly cycle. Review remained an intentional step, while the system took on preparation, submission and follow-through.
Proposed next iteration
The next iteration would bring approval, submission and reconciliation into a clearer end-to-end trace, with explicit duplicate-action handling and recovery tests around the invoicing boundary. That would make it easier to follow a billing run from the client's decision through the external submission and its reconciliation.