“Then I depend on you.”
We hear this objection in conversations about NUNAV Studio, and we understand it well.
A logistics company has built up its transport planning over years. Its dispatchers know their customers, its drivers know their tours, and the operation works.
Now a software vendor comes along and says: we can plan this better, automatically, with traffic forecasts and tour optimization. At first, that sounds good.
But what happens if the vendor raises its prices tomorrow? If the software fails? If the company wants to part ways at some point? And who actually owns the data that has been entered into the system over the years?
These are not awkward questions. They are the right ones.
Digitalisation must not be a one-way street
When all of transport dispatch runs through one piece of software, its availability becomes business-critical. And when data, interfaces and planning knowledge sit only with the vendor, real vendor lock-in can follow.
Anyone who digitalises their transport planning should gain more control by doing so, not less. The aim cannot be to get the experience out of dispatchers’ heads only to lock it into a system that a single vendor controls. That would not solve the dependency problem; it would only move it.
A vendor’s answer therefore cannot be “trust us”. It has to show how customers stay independent, technically and contractually. That includes data sovereignty, documented interfaces and exports, regulated backups and a regulated exit.
What does data sovereignty mean in practice?
Data sovereignty starts with a simple question: do I get my data back completely and in a usable format?
This does not mean an unreadable database copy, but a form a company can actually keep working with. It includes, for example:
- customer and location data,
- orders and time windows,
- vehicles and drivers,
- planned and driven tours,
- company-specific planning rules.
Documented interfaces and data exports help make this information available in other systems as well. That matters when a company changes its ERP system, wants to connect additional software, or parts ways with a vendor.
An interface alone is not yet a guarantee of independence, though. What decides is which data is actually accessible through it, and whether that includes the rules that have grown into the planning over the years.
What happens to the data?
Besides the question of how data gets out again, there is the question of what happens to it while it is in the system. This, too, should have concrete answers before a contract starts:
- How is data processing on the customer’s behalf regulated?
- Where is the data stored and processed?
- Who on the vendor’s side has access, and how is that controlled?
- When is data deleted, and how is that demonstrated?
- Is customer data used to improve the product, and if so, in what form?
The last question gains weight with AI-based optimization. A model that learns from planning data learns from someone’s data. Whether and how that happens should not be in the small print, but explicitly agreed.
And what happens if the software is unavailable?
A backup protects data. It does not keep transport planning running.
A business-critical process therefore needs more than backups. It needs clear agreements on availability, recovery and emergency procedures, that is, on how an operation can keep working when something goes wrong.
A regularly exported tour plan can, for example, be part of such an emergency concept. Dispatch must not come to a standstill just because a single system is temporarily unreachable.
What about escrow?
With business-critical software, the term software escrow comes up sooner or later. Source code and technical documents are deposited with an independent party. If a contractually defined event occurs, such as the vendor’s insolvency, they are released to the customer.
Escrow is an established instrument with a long legal track record. It was, however, designed for software installed on the customer’s own premises. There the idea is sound: the program already runs in-house, and with the source code someone else can maintain it.
For software delivered as a cloud service, the SaaS model, the idea holds only partly. The source code is just one part of the whole. For a service such as tour planning to actually run, you also need:
- the infrastructure it is operated on,
- the data it works with, for example map and traffic data,
- connected services from other providers, whose contracts do not transfer automatically,
- and people who know the operation, monitor it and step in when something goes wrong.
A company that receives the source code in an emergency therefore does not yet have a running service. Its first task would be to build up a complex operation itself, under time pressure. On top of that, cloud software changes continuously; a deposit is only worth as much as it is current. Legally, too, release in an insolvency is not always as simple as it looks in the contract; that should be checked by lawyers case by case.
So we do not rule out escrow. But we think it is more honest to clarify together first which risk it is actually meant to cover, and whether a deposit really reduces that risk for a SaaS service. Often the answer is that the concern is keeping one’s own dispatch running. For that, complete data exports, adequate transition periods and an emergency concept are usually more effective than deposited source code.
What NUNAV Studio offers for this today
For NUNAV Studio, we can say the following today: orders and master data can be taken over by file, for example as CSV or Excel files, or through a documented interface agreed for the specific project. Tour results, tour lists and data exports go back to the downstream systems the same way.
Which further data is returned in which format, how backup and recovery are regulated, and what happens on separation should be put in writing before the first project starts. That applies to every vendor, including us.
Trust is good. A regulated exit is better.
We believe a software vendor should be able to answer an uncomfortable question: how can customers keep working without us if one day they want to, or have to?
That does not mean we want to make our software superfluous. It means we should convince through benefit, not by making a switch as hard as possible.
With NUNAV Studio, we want to help companies improve their transport planning and make their operational knowledge systematically usable. Taking control over one’s own data and processes seriously is part of that.
A customer should stay with us because our software gives them an advantage every day. Not because they can no longer find a way out.



