One product.
Reshaped, not rewritten.
ERPSetu started from a boring observation: every small Indian business needs the same back office, and every one of them calls it something different. So we built the back office once and let the trade change its shape.
Forty products is forty half-finished products
An agency that ships a separate ERP per industry ends up maintaining forty codebases with one team. The fix in one never reaches the other thirty-nine, and every one of them is a year behind. We refused to start down that road.
But a generic ERP is nobody's ERP
The other answer — one product with everything switched on — asks a salon owner to learn what a bill of materials is, and a factory manager to scroll past appointment settings. Both of them give up in week two.
So the trade is a decision the product makes
Pick your trade at signup and the menu, the record names, the extra fields, the document series and the dashboard all change with it. One codebase underneath, one set of fixes, forty-odd shapes on top.
And the depth is stated, not implied
Some trades have screens built for them. Some have the core reshaped and their pack queued. Every page on this site says which, by name, because the alternative is a buyer discovering it after the money has moved.
We would rather lose a sale on this page than lose your trust in week two.
Which is why the demo credentials are published rather than gated, why every trade carries a marker saying what it actually has, and why the section below is titled what is not ready instead of being left off the site.
What is ready, and what is not
Updated as the product moves. If something below is wrong by the time you read it, it is because it shipped — check a demo and tell us.
- · All 13 core modules, on every plan
- · 19 demo tenants with real data, open to anyone
- · GST 2.0 slabs, document series, audit trail
- · Roles, permissions and cost visibility per role
- · Multi-business on one login
- · The full back office works today
- · Their own record names, fields and document series
- · No bespoke screens yet, and we say so per trade
- · Check your trade before you decide
Said plainly, because finding out later is worse than reading it now.
- · E-invoice and e-way bill are recorded, not auto-filed with the portal
- · Migration from Tally or spreadsheets is a service engagement, not a button
- · Mobile apps are not out; the product is responsive on a phone browser
- · The remaining industry packs land one at a time, not in a batch
How we decide what to build next
No public vote, no roadmap theatre. Three things move a pack up the queue.
A trade with a real business on the reshaped core tells us exactly which screens they are working around. That beats any survey.
A pack ships when its whole flow works end to end — document, ledger, dashboard, print. Half a pack is worse than none, because it looks finished.
If a trade needs something the core should have had anyway, that goes into the core first and every other trade gets it too.
Check the claims yourself.
Every demo on this site is a real tenant with real data. Sign in, break something, and tell us where the page overstated it.