Straight answers, including the awkward ones.

Yes, and this is one of the clearest differences from imported ERPs. Rate × quantity is one of four operation costing modes, so an operation paid at ₹4.50 per hole is costed on actual output. You can mix modes freely on one routing — hourly turning, per-piece drilling, a flat inspection charge and a subcontracted plating step all roll into a single cost.

Read the full explanation of piece-rate costing.

This is the question that decides whether an ERP project succeeds, and it deserves a real answer rather than a reassurance. Two things matter. First, high-frequency floor tasks — goods receipt, material issue, production entry — are built to be completed in a handful of fields, because a screen that takes three minutes will be filled in at the end of the day from memory, or not at all. Second, pricing is per plant, so nobody is denied a login to save money.

We would rather show you those screens during the demo than argue the point here.

You have two routes. Run everything operational in NextGenManager and export clean accounting entries for your CA to import into Tally — a lot of customers start here because it changes nothing for the accountant. Or migrate fully onto the built-in accounting engine, which covers GSTR-1, GSTR-3B, TDS at the payment point and period locking. Full legacy Tally migration is included on the Enterprise plan.

It depends almost entirely on your data, not on our software. A shop with clean part numbers and maintained BOMs: four to eight weeks. A shop where the BOMs exist as drawings and one engineer's memory: three to six months, and almost all of that is capturing the data rather than configuring the system.

We scope and quote migration separately, before you commit, precisely so this is not a surprise. See the five-stage process.

Yes. Opening balances load at any date. You do not have to wait for 1 April, and you do not have to run two systems in parallel for six months to bridge the gap — which is the usual reason mid-year go-lives get postponed until they never happen.

Not a self-serve one, because an empty manufacturing ERP tells you nothing useful — you would spend the trial entering test data and learn only that data entry is possible. Instead we run a pilot: one of your product lines goes end to end on real orders alongside your existing process, before the whole plant moves. That answers the question a trial is actually asking.

A flat fee per manufacturing plant, from ₹500 per month billed annually, with no per-user seat licences. Implementation, data migration and training are quoted separately because they depend on the state of your data, and you get that exact figure in writing before committing. See the plans.

Yes, on the Enterprise plan. Plenty of manufacturers want production data on a machine they can physically point at, and that is a legitimate preference rather than a paranoid one. It is the same product either way — same features, same updates. Managed cloud hosting is located in India.

You own it. Full export is available whenever you ask, in formats your accountant can open — including on the way out. Holding a factory's production history hostage at renewal time is not a business we want to be in. See how the data is protected.

Email support on Starter; priority phone and WhatsApp on Professional; a named contact on Enterprise. In every case the person answering can open the source file — there is no tier-one script between you and a costing question. Feature updates and statutory changes ship to everyone on the plan without a separate quote.

Sometimes, and we will tell you honestly when it is a bad idea. Custom reports and integrations are normal work on the Enterprise plan. Deep changes to the data model are usually a sign that we are not the right product for you, and we would rather say that than take the money and produce something unmaintainable.