Order in water intake operations
Intake records, pump monitoring, the network map and field crew work in a single system, available from a browser. The manager sees the state of every well, and the application keeps track of statutory deadlines.
We call back within 24 hours on business days.
Drinking water risk assessment: 31 December 2026
Directive 2020/2184 requires an assessment across three layers: the intake catchment area, the supply system and the installations in priority premises. The input data takes months to gather, not the week before the deadline.
The WSP module handles this: a water safety plan inside the operations logbook. In it you prepare the input data, send a pack to the assessor, load the finished assessment back in and maintain the registers of hazards, control measures, incidents and corrective actions.
Let's check your deadlinesFive modules, five concrete outcomes
Each one works on its own. Expand the one that describes your problem today. The newest of them, WSP, handles water safety plans and risk assessments.
The complete set of documents, tests and history for one well in a single file, ready to hand to an inspector.
A completed form with its workflow history and a PDF export, instead of a spreadsheet stitched together from three sources.
Export of the entire database throughout the contract, without asking our permission and with no exit fee.
HydroNexis versus Excel, paper and a network drive
Spreadsheets and binders work. Up to a certain scale they are even the cheapest option. Below is an honest comparison of where they stop being enough, and where they still have the advantage.
If you have a handful of wells, one member of staff keeping the records and a stable electricity bill, a spreadsheet is still a sensible choice. A conversation makes sense when one of the rows above describes a real problem from the past year.
Keeping things as they are costs money too
We have filled the fields with values typical of a mid-sized water utility in 2026, so the result means something straight away. Your figures will differ, so it is worth replacing them.
Control breaks this amount down by asset and reports kWh and PLN per cubic metre. How much of it can be recovered is known after the first month of measurements, not from a calculator on a website.
The result comes solely from the values entered alongside. We add no coefficients of our own and no industry averages.
Several people sign off the decision, and each of them fears something different
Below is the argument for each of them, written for their area of responsibility. You can forward it on without having to explain what it is about.
We have sent the file to the address given. You can forward it on without involving us.
Four sets of questions and answers in one file, one page per role. No newsletter sign-up and no phone call unless you leave a number.
A team that knows intake operations from the working end
Where public money is involved, what matters is who is accountable for the implementation and on what terms it can be tested. We show both: the team by name and the scale of live deployments, which you can verify at no risk.
Responsible for product direction and contact with operators. Knows intake operations from the working end.
Operations, contracts and conversations with procurement departments. Previously built a manufacturing business selling into export markets.
Platform architecture and integrations with customer systems. Ten years working on enterprise-class systems.
Telemetry, control systems and models that detect anomalies in pump operation.
We run an early access programme with operators in the water sector. We do not name customers at their request, but we can show the scale.
This is the largest deployment to date. It holds around 2,100 documentation files in the system.
Space for concrete deployment figures: the number of assets, the module scope and the project stage. We will fill them in once partners release this information from confidentiality.
What our price is made of
Pricing is individual, because two utilities with the same number of wells can have an entirely different scope. Below is everything that affects it, ordered by how strongly it does so.
The smallest deployment: one module, cloud, no integration, up to 20 assets. Greater scale raises the amount in line with the table alongside.
What the subscription does not include
The three things we hear most often
The doubts arrive in the same order: first about whether the change makes sense, then about how it would be implemented, and finally about the price and the supplier. We answer all three here, without waiting for a conversation with a salesperson.
"We have managed without it for years"
And that is true, because so far nothing has gone wrong. The problem is that this way of working does not cost a little each month; it costs all at once, at the least convenient moment: during a failure, or when the person who remembered the deadlines leaves.
Work through the calculator above on your own figures. If the result is low, you will see it for yourself and we will leave you alone.
"The rollout will paralyse our work"
That is usually how it ends when the entire burden sits with the customer. With us the account is live in 1-3 business days, and archive import, report configuration and training run alongside normal work, typically over 2-6 weeks.
AI reading loads the documents and prepares drafts with a marked confidence level. Your member of staff approves instead of re-typing. That is the difference between a week and a quarter.
"We have found a cheaper system"
Very possibly. In that case ask it three questions: does it handle Polish regulatory reporting without surcharges, can it be installed on your server, and who picks up the phone on a Sunday when a pump stops.
If it answers all three, it is the better choice and we will tell you so. We have no interest in talking you into a worse decision.
What happens after you click
No sales presentation at the first meeting and no calling twice a day. For each step we say how long it takes.
Two fields in the form, and within 24 hours on business days one of our team gets in touch. This contact serves solely to agree a time and who on your side should be in the conversation.
We ask about your infrastructure, your deadlines and your biggest bottleneck. We show no quote and no price list. If it turns out we are not a good fit, we say so in that conversation.
Everyone who will sign sits down together: the board, engineering, finance and IT. Each is accountable for something different, so we put the concept and the offer together with them rather than bringing a finished one. The scope, the schedule and the cost range come out of that meeting in writing.
We settle whether we go ahead. If you decide this is not the moment, we accept that without persuasion and without calling every fortnight. We would rather hear an honest no than carry on a conversation with nowhere to go. We come back when you tell us to.
Thank you, we will call back
We will call within 24 hours on business days. The call takes a quarter of an hour and serves to establish whether we are a good fit at all.
Leave your details and we will call back
Not sure which module would suit you best? We will work it out in a short call. Two fields, and we settle the rest by phone.
We call back within 24 hours on business days. Consent can be withdrawn at any time by writing to biuro@hydronexis.pl. We do not sign anyone up to a newsletter.
Upcoming webinars
Live and in Polish, with questions in the chat. No sales pitch and no call afterwards.
Sign-up takes you to the HydroNexis Academy (akademia.hydronexis.pl), which sends the meeting link and reminders.
Materials and contact at hand
The code opens the page directly on your phone. You will find the same set at our trade fair stand.
The ten questions we are asked most often
Every answer opens with the verdict, so it can be read without the context of the whole page.
How much does a HydroNexis implementation cost?
How long does implementation take?
Do all the modules have to be deployed at once?
Can the data stay on our own network?
Do you integrate with our SCADA and telemetry?
Does HydroNexis replace a SCADA system?
Which regulatory reports does the platform handle?
Will implementation halt the team's day-to-day work?
What happens to the data if we end the relationship?
Do you have references we can speak to?
We have collected more questions, technical and formal ones included, in the knowledge base.