Engineering
Custom software
Internal systems, portals, integrations and automation, built around how your business works.
Custom softwareMaintenance & Support
We provide application maintenance services for web, mobile and custom software: bug fixes, security and dependency updates, monitoring, performance work and small features. We also take over software another team built. The team behind it has delivered more than 85 projects in five countries over about a decade, and keeps the systems it looks after current and documented.
Details
One team looks after your application month after month, with the scope and response times written into your contract. You get a clear log of the work and one point of contact.
Discovery
We learn your goals, users and constraints and agree the scope.
Design
Flows, prototypes and the interface, tested before we build.
Build
Two-week sprints with a working version to review each time.
Launch
Testing, security checks and a release without surprises.
Support
Monitoring, updates and new features at an agreed pace.
Software does not stay finished. Browsers, operating systems, app stores and the libraries your code depends on change every few months, and each change can break something that worked yesterday. Most companies call us for one of these reasons:
If one of these sounds familiar, a maintenance agreement gives the work an owner and a rhythm, instead of a scramble every time something breaks. It also costs less over time: an update applied when it is released is a small task, while the same update left for two years often turns into a rewrite.
A large part of our support work starts with code we did not write. Before we accept responsibility for it, we need to understand it, so every takeover follows the same path:
If the audit shows the system is too old to maintain at a reasonable effort, we say so and explain the options, including our legacy application modernization service.
Maintenance runs on a simple monthly cycle. At the start of the agreement we set the scope together: which systems are covered, how many hours a month are reserved, how issues are reported and how quickly each priority level gets a response. Those response times are agreed per contract, because a small company website and a payment platform need very different levels of cover.
Each month we apply security and dependency updates, review the monitoring alerts, fix the reported bugs in order of priority and use the remaining time for the small improvements on your list. Every change goes through code review and testing before release, with the help of our QA and testing services when the system needs automated tests. You receive a short report of what was done, what is planned and anything that needs a decision from you.
Good maintenance leaves the system in better shape every month, not only patched. Under an agreement with us you receive:
Your code, repositories and accounts stay in your name throughout. If you ever move the work to another team or in-house, the documentation and access are already in order.
We support the same kinds of software we build, which means we know where they usually break:
If your stack is unusual, tell us what it is. We review the code before we agree to maintain it, so you know where we stand from the start.
Our engineers work from Albania on Central European time. For a company in New York or Toronto, our afternoon is your morning: an issue you report when you start your day can be investigated the same day, and fixes can be released while your users are still active. We work in English, in writing and on calls, and keep the same people on your system so you are not explaining it to someone new each month.
So far we have delivered 32 projects for clients in the USA and 18 in Canada. If you need more than maintenance hours, for example several engineers working on your product full time, look at our dedicated development team service. For anything else, send us a message through the contact page and tell us about the system you want looked after.
Maintenance and support
Application maintenance services keep software working after launch. They cover bug fixes, security patches, dependency and framework updates, monitoring, performance tuning and small improvements. The goal is that the application stays secure, fast and compatible with the browsers, devices and services around it, without waiting for something to break first.
Maintenance is the planned work on the code: updates, fixes, tuning and small changes. Support is the reactive side: answering questions, investigating reported problems and restoring service when something goes wrong. Most of our agreements include both, with the split between planned hours and reactive work set in the contract.
Yes, and it is a common starting point. We begin with a code audit, collect all access and accounts, document how the system is built and deployed, and fix the urgent issues. Only then do we move to regular maintenance. If the code is not worth maintaining, the audit tells you that before you commit.
Response times are agreed per contract and depend on how critical the system is. We define priority levels together, for example a system outage versus a cosmetic bug, and write the response time for each into the agreement. That way the cover matches the system, and you pay only for the level of support it actually needs.
It depends on the size and age of the system, how many applications are covered, the hours reserved each month and the response times you need. We start with a short call and, for software built elsewhere, a code audit. Then we send a written proposal with the scope, the monthly plan and the timeline.
Yes. Most of our clients are abroad: we have delivered 32 projects in the USA and 18 in Canada. We work in English, our working day overlaps with the North American morning, and the same engineers stay on your system so the knowledge of it stays with the people who maintain it.