We build the portal that registers every generator, assigns GPS-verified trips to transporters, and confirms weight at the receiving facility. One load, one record, four stakeholders.
All prices exclusive of 18% GST. GST invoice issued against every payment.
Right now you cannot prove which. The challan says one thing, the transporter says another, and the receiving site keeps a register nobody has opened since March. Without a verified trail, a penalty notice does not survive the first objection.
A working portal on your domain, the field app your drivers and site operators actually use, and the dashboard your officers open on Monday morning.
The build is ours to control. The rollout is not. Every window below assumes your transporters and site staff are available for the field trial when it starts.
We sit with the officer who signs off and the clerk who fills the register today. Every field on your existing challan is mapped before anything gets built.
Generator, transporter and facility flows, the trip engine, and the officer dashboard. You get a working staging link at the end of week three, not a status update.
The driver app goes to a handful of real vehicles on real routes. GPS behaviour, network dead zones and driver habits all surface here. Slippage in this block is almost always about vehicle access.
Full transporter onboarding, one training session per user role, then production deployment. Source code, database schema and deployment notes are handed over the same week.
One fixed price for the standard build: one material stream, four user roles, one authority. Anything past that is quoted before work starts, never after.
All prices exclusive of 18% GST. GST invoice issued against every payment.
Three things: how many material streams you track, how many outside systems we have to talk to, and where it is hosted. One stream, four roles and standard cloud hosting sit inside the fixed price. A second stream, a state portal integration, or deployment inside a government data centre is quoted before work starts.
Six to eight weeks from the first scoping session to go-live. One week mapping your existing challan and register, three weeks building, two weeks of field trial on real vehicles, then rollout and handover. The field trial is the part that slips, and it slips when vehicles and drivers are not made available on time.
Either your infrastructure or ours. For a government body we default to your servers or your department cloud account, because that is usually what procurement and the audit team want. The data is yours from the first record, exportable in full at any time. No lock-in clause, and no fee for getting your own data out.
You get the source code, the database schema and the deployment notes in your own repository. In-scope bugs are fixed at no charge for thirty days after handover. After that, departments with an internal IT team run it themselves. Everyone else moves to a monthly retainer for new wards, new reports and changes.
Yes. We are GST registered and every payment gets a proper tax invoice against our GSTIN, issued the same day the payment lands. Every price on this page is exclusive of 18% GST. Build work is billed in stages against the milestones in the SOW, by bank transfer or UPI. We do not ask for money before an invoice exists.
One officer who can sign off decisions and one clerk who fills the register today. Blank copies of your current challan, gate pass and monthly report format. A named list of transporters and receiving facilities. For the field trial, three or four real vehicles running real routes for two weeks. That is the whole ask.
Send a message with your department or company name, the material you need traced, and roughly how many vehicles move it. We will tell you within a day whether this scope fits.
