The Problem Every Finance Team
Lives With
Every time goods leave an industrial facility in India, finance has to produce three legal documents. An e-invoice, an e-way bill, and a delivery challan. Each one asks for largely the same information. Each one lives on a different platform.
Most finance teams were opening Tally, then the GST portal, then a third tool, re-entering the same data each time, every shipment, every day.
The Tradais founder lived this problem firsthand across his own manufacturing and construction businesses. He brought me in to collapse the whole process into a single workflow.
Who This Was Built For
Finance Manager at industrial companies
They weren't confused about what the documents required. They knew the process cold. The problem was pure repetition. Same information, multiple systems, every outgoing shipment.
How I Was Working
The compliance fields couldn't be simplified. Every legal requirement had to be there. The only room to move was in how users got information into the system. Early feedback came from finance staff at two companies the founder knew, through informal conversations, not structured testing.
Mapping the Problem Before
Designing Anything
I designed a single structured form, organized the way finance staff already think about a shipment. Party details first, then items, then transport and value.
Fields that didn't apply to a given shipment type stayed hidden. No clutter, no confusion about what's relevant.
Once the form was complete, one button generated all three documents simultaneously. Correctly formatted, ready to submit or download.
When finance staff from the two companies saw the single-submission output, that was the moment it clicked. They were used to treating these as three completely separate jobs.
The Connection to Vulcan
Pegasus was built as a standalone product. When I later worked on the Vulcan ERP and reached the finance module, the same document generation problem appeared at the end of the production chain.
Vulcan already held all the information those documents needed, captured earlier from sales, the BOM, and dispatch. The Tradais founder suggested connecting the two. Once I understood what was already in the system, integrating Pegasus into Vulcan's finance module was the obvious move. One click at dispatch, three documents out, using data the system had already captured.
Two products built separately, joined because the underlying problem was identical.
What I'd Do Differently
In Pegasus, I solved this as a form design problem. If I were starting today I'd solve it as an auto-fill problem first, using APIs to pull data that already exists, and only then think about the form. The less a finance user has to type on a compliance document, the less room there is for error.