Why we built Daaga
A note on what we tried before, what didn't work, and the gap that turned into an ERP.
We've run a real business in India for over a decade. In that time we've used spreadsheets, off-the-shelf accounting tools, half-built operational apps and a stack of one-off integrations. None of them fit the way an Indian business actually runs day to day.
The pattern was always the same. The sales system didn't talk to inventory. Inventory didn't talk to accounting. Accounting didn't talk to GST. We'd reconcile by hand, every month-end. We'd lose money because nobody had a single view of who owed what, against which order, for which stock.
We tried wiring the tools together. It worked for a quarter, then broke. Each tool's idea of an “invoice” was different. Each tool's idea of “posted” was different. The integrations were brittle by design.
So we started writing the system we wanted. Accounting, GST, sales, purchasing, inventory and production — one model, one ledger, one product. We used it ourselves first. Six months in, other businesses asked if they could use it too. That became Daaga.
It started in our own operations, but the core is a general ERP — and today businesses across distribution, manufacturing, retail, services, warehousing and transport run on the same product we use ourselves. Every feature on the roadmap comes from a real business with a real problem. That's the only filter we trust.