INOVIX / Services

Software maintenance and product development

A product needs attention after launch. INOVIX helps with maintenance, bug fixes and ongoing development, with clear agreements on responsibility and scope.

Ticketio, a digital platform for tickets and events.
Design, engineering and automationService

A concrete delivery.

Final scope is agreed before work begins.

System and access overview

Agreed maintenance scope

Prioritisation of issues and changes

What does the maintenance agreement include?

The maintenance agreement covers updates, backups, speed and performance, technical help and monitoring within the agreed scope. Work beyond it, such as new features, is billed by the hour or as a fixed price when the task is clear.

The agreement can cover a website, an app or a system you already have. The written agreement states what is included, who is alerted when something fails and how quickly we respond. We do not promise round-the-clock cover unless the agreement says so.

Understand the system before taking over

For an existing system we start with code, environments, access and documentation. We map critical integrations and known issues. This reveals what can be maintained directly and what needs improving before further development.

Define what operations includes

Hosting, backups, monitoring and support are different responsibilities. The agreement needs to specify what is included, who receives alerts and how incidents are prioritised. We do not imply around-the-clock support or particular response times without an explicit agreement.

Prioritise meaningful changes

Bugs, user needs and technical risk should be considered together. Small releases with testing and a rollback plan can make changes easier to manage. Product ownership and engineering need a shared view of what matters most and why.

When someone else built it

If the previous supplier has stopped, no longer answers or has become too expensive, we start by collecting the access: the code, domain, hosting, database and accounts with the App Store, Google Play and payment providers. Anything registered in a former supplier's name is moved to your business.

Then we go through the code and the list of known bugs, and you get an overview of what can be run as it is and what should be fixed first. Our guide on taking over existing software explains what to have in place before a handover.

We run our own products too

We run apps and websites with real users every day ourselves, including Stamly, Tilbudsroboten, NordCRM, Venito and Peskot. Updates from Apple and Google, new framework versions and bugs that only appear for some users are things we handle in our own products, not only for clients.

A good place to start.

  • Who owns the code and access?
  • Which failures are critical?
  • How are backups handled?
  • What should the support agreement cover?

Questions & answers

What happens if the website goes down?

Monitoring alerts us, and we troubleshoot according to the priority in the agreement. With backups we can restore a working version while the fault is fixed.

Can we end the agreement?

The notice period is in the agreement. The code, domain and accounts are in your business name, so you take everything with you if you change supplier.

Can you take over software built by others?

It may be possible after a technical review and clarification of access and rights.

Are new features included in maintenance?

Only when agreed. Maintenance and new development should be specified separately in scope and pricing.

We use cookies

We use necessary cookies to make the site work, and analytics cookies (Google Analytics) only if you accept. Learn more

Software maintenance and product development | INOVIX