billing evidence ready
Every complaint, technician and asset across all your projects and schemes on one live map. Your office opens a laptop. Your field team taps a basic Android. Nothing gets written down twice.
Free, and nothing to fill in. Pick a district, see it in five seconds.
A phone call somebody half remembers. A WhatsApp group nobody scrolls back through. A register riding around in a bag. For ten villages that holds together fine. At five hundred it is three separate places for things to disappear, and every disappearance eventually has a price attached to it.
The Sarpanch calls at 8pm. Somebody says "kal dekhte hain." Nobody writes it down. Two weeks later it is sitting in the JE's file as a grievance with your name on it. The clock that mattered started running on a night you never heard about.
Two men sent to one village. A pump sitting dead in another because the plumber drove out without the spare and has to go back tomorrow. You pay for the diesel, the day and the second trip. And you find out on the bill, not on the day.
The JE asks for six months of proof. Three of your people spend four days putting it back together from photo galleries and memory. Your RA bill sits there the whole time. You are funding his paperwork out of your own working capital.
Nobody sends you a bill for any of this. That is why it keeps happening.
Nobody does. There is no line item, no vendor, no due date, no follow-up call. The money simply leaves. So we worked out one year on a 500-scheme portfolio and put it on paper.
That is the figure this decision is actually against. Not the price of software.
Four steps, and your office types up none of it. The record comes out of the work itself. That is the only kind of record that stays current.
The Sarpanch calls, or your site engineer logs it. It is in the system before he puts the phone down, with a clock on it that nobody can quietly stop.
Scheme, asset, village and priority filled in automatically. Valve cluster B, Scheme RJ-114. No guesswork.
Nearest technician with the right skill, materials listed before he leaves the store. One trip, not three.
Photo, reading and spares attached on site. That one record does three jobs: bill evidence, audit proof, and your answer if anyone asks two years later.
No evening data entry to skip. No format to learn. No register to carry. Four buttons, in his own language, on the phone already in his pocket.
Every field system that ever died on a site died the same way: the men below quietly stopped filling it, and by the time anyone noticed, three months of records were missing. So we stopped asking them to fill anything. The service log is wired to the payment. Until the location-stamped photo and the closure are on the app, no monthly bill generates for that work. Nobody is chased, nobody is retrained. Their money arrives through it, so they learn it in two days.
Pick any of the 75 UP districts and the village log opens on the spot: schemes running, complaints with the clock on them, evidence already filed. Five seconds, and you will know whether the rest of this page is worth your time.
This is the screen your control room would open every morning. Give it five seconds and decide whether it is worth ten minutes of your time.
Village names and counts above are sample data for the demo. In the 10-minute walkthrough we load your own scheme list.
The rate was locked the day you signed and nothing moves it now. What is still moving is how much of that rate survives to the end of the term, and it gets decided by things costing fifty rupees to prevent and lakhs to explain afterwards.
Illustrative model using published benchmarks · not a guarantee · actuals vary by scheme mix and state.
Priced the way your own contract is priced: per scheme, for the term. Not per user, per ticket, per login or per report you export.
You send us the scheme list. We map every village, asset and technician and hand it back ready to use. This is not a data-entry project for your office.
Not per seat. Put the whole crew on it, add ten more next month, add the subcontractor's men. Works offline, in regional language, on a basic Android.
Every call becomes a ticket with a response window. Nearest skilled man, spares listed before he leaves. This is the one that stops grievance penalties.
Field kit checks and lab samples scheduled across every parameter. A bad reading raises its own re-test and repair job automatically.
Asset registers, repair logs, quality trails and response times building continuously. When the JE asks, you open it. You never build it.
Vendor contracts against the assets they cover, maintenance that triggers itself, and the final handover file building from day one.
We come and train your control room and your field crew ourselves. Not a PDF and a login link.
Deployed on MeitY-empanelled infrastructure matching whatever policy your department already follows. Role-based access, full logs, full API access, and a written exit and data-handover clause from day one.
Every repair, every test, every closed complaint lands as a dated, location-stamped record that belongs to you. The pack is not something you assemble the night before a review. It has been assembling itself since the day you switched on.
India's first JJM performance audits landed hard. The schemes they found failing were not old ones. They were villages already certified Har Ghar Jal, going down inside somebody's maintenance window. Somebody had signed for those.
Nothing here changes the decision. Open the parts your own team would ask about.
Tap into a single asset and see everything about it: full history, the contract that covers it, what maintenance is due, and whether it puts you at risk. Operators who run on this kind of data rather than guesswork cut 10 to 20 percent of maintenance cost. That saving lands straight in your margin.
Your schemes, your assets, your records. One system that stays yours and keeps working whether or not there is a signal in the field.
Big asset software was built for one factory behind a fence. You run a thousand villages: a Sarpanch's phone call, a field test kit, a technician two districts away, and a service standard you are measured against daily.
Every scheme, asset, repair and reading in one private system that you control, instead of scattered across registers, WhatsApp groups and people's memory. Works offline. The records stay yours for the life of the contract.
A call from a Sarpanch, a Paani Samiti or a villager becomes a tracked ticket with a clock on it. It cannot be forgotten, lost or quietly closed. That is exactly how complaints turn into penalties.
Assign work by skill and distance across hundreds of villages, with materials listed before anyone sets out. Fewer wasted trips, less idle labour and lower fuel on every job.
Schedule field test kit checks and lab samples across every required parameter. A bad reading automatically raises a re-test and a repair job, so a quality issue never grows into a penalty.
Track materials used, cost per scheme and user-charge collection in one place. See which schemes drain money and which pay their way, early enough to fix it.

Contracts stored against the exact assets and vendors they cover, with early alerts before anything lapses. You hold vendors to their response windows, not the other way around.
Work orders generate on calendar, running hours or a sensor reading, each carrying a step-by-step checklist. Nothing depends on someone remembering.
Manuals, as-builts, warranties and asset registers build up as the work happens, so the final settlement never waits on a missing file.
Twenty years on site, building and running water infrastructure across India. Sustain is the system we kept wishing somebody would hand us.
"We did not write software and then go looking for water operators. We are water operators, and we built the thing we needed."
Representative of the organisations and projects our team has worked across over the past two decades. Company names are the property of their respective owners and do not imply a current partnership or endorsement.
Ten minutes on a call with your own district already loaded on screen. No slides and no procurement conversation. If it is not clearly worth it by minute eight, say so and we will leave you alone.
We call once. No mailing list. Privacy Policy
The price was fixed for ten years the day you signed. What you keep was not.