How we work
From first call to running on real orders.
The software is the easy part. The project is your item master, your BOMs, and getting the floor to enter data the same way twice. Here is exactly how we run it, and what we need from you at each stage.
The five implementation stages
Fit check
A call where you describe what you make, how your operators are paid, and how much of your process goes out to job workers. We tell you whether we fit — before anyone talks about price.
You bring: a rough part-number count and an honest description of your process.
We bring: a straight answer, including "not us" if that is the answer.
Demo on your data
Not a slide deck. We take one of your real assemblies, build its BOM, route it, cost it across all four modes, raise a job-work challan against it and produce the tax invoice — while you watch.
You bring: one real assembly with its components and operations. Send it beforehand and it will already be built.
We bring: the engineers who wrote the costing engine, not a sales rep.
Data migration
Item master, BOMs, customers, vendors and opening balances. This is the stage that decides your timeline, which is why we scope and quote it separately before you commit to anything.
You bring: whatever you have — Tally exports, spreadsheets, or the engineer who knows the BOMs.
We bring: import templates, a cleaning pass, and a written list of every ambiguity we found.
Pilot on live orders
One product line runs end to end in the system while everything else carries on as before. Mistakes surface on a small surface area, where they are cheap to fix.
You bring: one product line and the people who actually run it.
We bring: daily availability during the pilot, and configuration changes turned around same-day.
Go live and support
The rest of the plant moves across. Training is by role, not by module — your storekeeper learns three screens, not the whole system. Opening balances load at whatever date you go live, so you are not waiting for 1 April.
You bring: a decision that the old spreadsheet is now closed.
We bring: role-based floor training and a support channel answered by people who can read the code.
After go-live
What ongoing support actually means
You reach an engineer
Support is answered by people who can open the source file. There is no tier-one script standing between you and a costing question.
Updates included
New features and statutory changes ship to every customer on the plan. You are not quoted separately when GST changes a form.
You can leave
Full data export in formats your CA can read, whenever you ask. We would rather earn the renewal than trap it.
Start with the fit check.
Thirty minutes, no deck, and a straight answer about whether this is worth either of our time.