helper.lt
Menu
LietuviškaiSend an enquiry

Maintenance and ongoing development

Work on a system doesn't end at launch: new needs appear, the libraries and outside services it relies on change, and bugs turn up. We look after the software we build and systems built by other developers, once we have reviewed them. The scope is agreed in advance – for example, how many hours a month go to maintenance.

Example

Example: a fictional company and made-up data.

A maintenance overview of a fictional company's system
Maintenance overviewWarehouse and ordering system

Availability over 30 days

1–30 September 2026

99.97%one outage, 12 min

Error alerts

  • 29 Sep 2026, 16:42An invoice email failed: the mail server did not respondFixed
  • 24 Sep 2026, 09:15The monthly report takes over 30 seconds to buildInvestigating
  • 17 Sep 2026, 03:08System unavailable: the disk ran out of spaceFixed

Updates

  • 28 Sep 2026Security updatesThe operating system and 14 libraries
  • 22 Sep 2026New report: sales by region
  • 17 Sep 2026Disk space monitoring and clean-up of old logs
  • 8 Sep 2026Fixed: VAT on discounted invoices

Support requests

  • Jurgita K., accounts29 Sep 2026Add the payment date to the invoice exportDone
  • Mantas R., warehouse28 Sep 2026New orders don't show on the tabletIn progress
  • Ieva S., sales25 Sep 2026A new discount rule for wholesale customersAwaiting approval

What it covers

  • Bug fixing and help for users
  • Security updates and updates to the libraries and frameworks in use
  • Availability and error monitoring
  • Changes and new features as new needs arise
  • Maintenance of systems built by others, after a technical review (System modernisation)
  • Keeping up with new browser, operating system and phone versions

Who it suits

  • Your system is used every day, but whoever built it no longer has time for it or no longer works with you.
  • You want new features without looking for a new contractor for every change.
  • You hear about errors and outages only from customer complaints.

How the work goes

How we work
  1. 1We find out what you need
  2. 2We analyse and propose
  3. 3We design the solution
  4. 4We build in parts
  5. 5We test and launch
  6. 6We maintain and improve

Examples of our work

Development and modernisation of a training organisation's platform

2024–2026

We took over a working platform, updated its technology and keep developing and maintaining it.

The platform we maintain has 30 pages, 19 API controllers and 25 data models.

Nuxt 4 / Vue 3, AdonisJS (Node.js), MySQL, Docker

Field technicians' app that works offline

2023–2026

Tasks, customer sites, equipment, van stock and payments – on the technician's phone, even where there is no signal.

Developed continuously since late 2023, it syncs 33 data types to the phone.

Flutter / Dart, SQLite, Node.js / TypeScript, Server-Sent Events

Integration with courier services

2026

Labels are printed straight from warehouse dispatches, pickups are booked, parcels tracked and returnable containers swapped, with parcel status updated every five minutes.

The new integration took over the parcels already in transit.

TypeScript, courier REST API, SQS, Jest

Questions and answers

How is maintenance paid for?

Usually we agree a number of hours per month, and larger changes are estimated separately. You can also pay by the hour, only for the work actually done.

Can we order a one-off fix?

Yes. We take on single bug fixes and small changes too, and ongoing maintenance can start at any time later.

All services

Got a task or an idea?

Describe it in a few sentences – we'll reply and talk through how we could help.

Send an enquirycontact@helper.lt