Services
Maintenance, operations and takeover
Software maintenance with hosting in the EEA and fixed response times, including for software someone else built.
We keep your software secure and running: hosting in the EEA, monitoring, security updates, tested backups and agreed response times. We also take over existing software when the original developer or agency is no longer available, after a review at a fixed price. For software maintenance, plan on 15 to 20 per cent of the project cost per year.
Typical triggers
Typical triggers
Clients get in touch when one of these situations arises.
- 01The developer or agency that built your software can no longer be reached or is stopping.
- 02Nobody installs security updates, and you do not know when the last backup was tested.
- 03A new project is going live, and operations should be settled from day one.
- 04When something breaks, it is unclear whom to call and how quickly anyone will respond.
Maintenance, operations and takeover
What you get
Hosting in the EEA
Your application runs in a data centre in the EEA. Hosting is included in the maintenance contract and not charged separately.
Security updates and upkeep
Operating system, runtime, database and libraries are updated continuously, critical vulnerabilities outside the normal cycle too.
Monitoring
Availability, errors, storage and interfaces are checked continuously. We learn about problems before your staff pick up the phone.
Backups with restore tests
Data is backed up automatically, kept in a second location and restored on a trial basis at regular intervals.
Support with fixed response times
A single point of contact, deadlines per priority set out in the contract and a pool of hours for small adjustments.
Takeover of existing software
Code review, assessment and documentation brought up to date. Then we keep the software running or plan its replacement with you.
What the maintenance contract includes
| Service | In the contract | Note |
|---|---|---|
| Hosting in the EEA | included | servers, database and storage for backups |
| Security updates | included | continuously, critical vulnerabilities immediately |
| Monitoring and alerting | included | availability, errors, interfaces |
| Backups and restore tests | included | copy in a second location, regular trial restore |
| Support with response times | included | deadlines per priority, set out in the contract |
| Small adjustments | pool of hours | for example a changed field or a new report |
| Move to a new major version | plan and budget | effort depends on how far behind the software is |
| Further development | not included | separate stage with a cost ceiling |
In practice: Verling CRM after go-live
Verling CRM has been in production since October 2026. Since then we have kept developing it: in the two weeks after launch, five extensions were added, including an interface for automatic address import and document storage per customer.
Every change goes into operation only after automated testing. That keeps the system stable, even though it grows every few days.
- five extensions in two weeks, without rebuilding the foundation
- automated tests before every change
- data on its own server instead of with a CRM vendor
Taking over software when the developer is no longer available
When the original developer or agency drops out, the software keeps running at first. The risk grows quietly: nobody installs updates, and when something breaks there is no one to call. This is how we approach a takeover:
- Secure access: servers, domain, repository, database and external services are secured in your company's name.
- Code review: we read the code, check versions, dependencies and security, and find the places where business rules are hidden.
- Assessment: servers, data, interfaces and backups are recorded. We deal with urgent security vulnerabilities first.
- Bring documentation up to date: structure, processes, access and operations are written down, so the software no longer depends on one person.
- Recommendation: keep running, modernise step by step or replace. The review takes a few days and is charged at a fixed price.
Maintenance, operations and takeover
Approach
01
Intro call
20 minutes, free of charge. We establish which software is affected, who looks after it today and which access credentials exist.
02
Fixed-price review
Code review and assessment of servers, data and interfaces. After a few days you know where your software stands.
03
Takeover and documentation
Secure access, set up repository and backups, document structure and operations. Urgent security vulnerabilities first.
04
Ongoing operations
Hosting in the EEA, monitoring, updates, backups with restore tests and agreed response times.
05
Further development
We plan new features as a separate stage with a cost ceiling, kept apart from maintenance.
Effort
Price range
- Price range
- CHF 4'500 to 24'000
- Duration
- Ongoing, per year
Non-binding estimate, excl. VAT.
What drives the effort
Plan on 15 to 20 per cent of the project cost per year, with hosting in the EEA included. For an interface costing CHF 30,000 that is CHF 4,500 to 6,000, for a replacement project costing CHF 120,000 CHF 18,000 to 24,000 per year. The deciding factors are integrations, user groups and service hours. The review before a takeover takes a few days and is charged at a fixed price.
Technologies
- Docker
- Linux
- PostgreSQL
- GitHub Actions
- C# / .NET
- Next.js
- PHP
Maintenance, operations and takeover
Frequently asked questions
What does software maintenance cost per year?
Plan on 15 to 20% of the project cost per year. For a project of CHF 60,000 that is CHF 9,000 to 12,000 per year, or CHF 750 to 1,000 per month, excluding VAT. With us, hosting in the EEA is included. New features count as further development and are planned separately with a cost ceiling.
Our developer can no longer be reached. What should we do?
First secure all access: servers, domain, repository, database and external services. We then review the code, operations and security at a fixed price and deal with urgent vulnerabilities first. After a few days you know whether continued operation, modernisation or replacement makes sense.
Do you also take over software without documentation?
Yes, in takeovers that is the rule rather than the exception. We read the code, record the structure, processes, access and operations, and hand this documentation over to you. If the source code itself is missing, the previous provider has to hand it over first. Whether they are obliged to depends on the contract.
Who runs the software after go-live?
We do, if you wish. A maintenance contract covers hosting in the EEA, monitoring, security updates, backups and agreed response times. The usual figure is 15 to 20% of the project cost per year. You can also run the software on your own infrastructure or hand it to your IT partner.
Can you take over existing software and develop it further?
Yes, after a short review. We look at the code, the data model and how it is operated, and tell you candidly whether further development makes sense or a gradual replacement would cost less. The review takes a few days and is charged at a fixed price.
What is the difference between software maintenance and further development?
Maintenance keeps the software secure and running, further development adds new features. Maintenance covers security updates, monitoring, backups, support and small changes within the agreed hours. A new module, an additional interface or another user group counts as further development and is planned as a separate phase with a cost ceiling.
Is a software maintenance contract mandatory?
No, the law does not require a maintenance contract. If you process personal data, however, you must protect it appropriately: in Switzerland under Art. 8 of the Data Protection Act, in Liechtenstein under Art. 32 GDPR. Without regular security updates and tested backups, that is hard to justify for a web application. Whether you handle maintenance yourself, through your IT partner or with the developer is your decision.
Can we cancel the maintenance contract and switch providers?
Yes, if the contract allows it and you hold the source code, documentation and access credentials. So when you sign, look for a reasonable term, a clear notice period and an obligation to hand over in an orderly way. With us, the repository, architecture description and operations manual are yours from day one.
How dependent do we become on Natter Solutions?
As little as possible, and we make sure of that from day one. Every project is documented and handed over so that it can be operated and developed without us: the repository, architecture description, operations manual and access credentials are in your hands.
Who holds the rights to the code and the data?
The data is yours. The source code is kept in a repository you have access to, and the usage rights to it pass to you once the work is paid in full. We rely on widely used technologies such as Next.js, C# and PostgreSQL, so that another team can take the software forward if needed.
Let us talk about your case.
20 minutes are enough to find out whether a custom solution is worth it for you.