Hypercare and support come as standard
Custom software maintenance starts with one week of hypercare on site, at every go-live.
That week we answer user questions on the spot and fix whatever falters: an operator who gets stuck, a step that turns out unclear in practice, a connector that hiccups. We pick it up straight away.
Most questions come up in the first days, when everything is new and anything unclear costs time on the floor immediately. After that, everything runs through the support channel: on working days between 07:30 and 18:00 Estonian time. Outside working hours only with a separate support contract.
We keep fixing bugs in what we built, after that week too, free of charge.
Keep developing, cancellable monthly
Want to keep developing? Then a maintenance agreement does the job. It doesn’t auto-renew and is cancellable monthly: if you need nothing more, you pay nothing more.
You choose from two forms:
Fixed monthly price. For ongoing development: a fixed budget per month for new features, adjustments and small integrations. The amount depends on scope and rhythm; after a short conversation you get an indicative price.
On an hourly basis. For when you occasionally want something done: a new report, a small adjustment, a change driven by a new statutory requirement. You pay for what you use.
When in doubt, we start on an hourly basis and switch to a fixed monthly price as soon as the rhythm is clear.
Working software every two weeks
Continued development runs in the same rhythm as the build phase: two-week sprints, short check-ins and working software at the end of each sprint. A one-week adjustment gets no long analysis phase.
This is what we take on:
- New features for your growth or changing work
- Adjustments to existing features based on real-world use
- Integrations that weren’t there yet at go-live
- Speed improvements as you grow
- Security updates
- Updated documentation for new features
Direct contact with the people who built it
A direct line. You email or call the people who built your software, with no ticketing system in between.
Remote, and on site when needed. We work remotely; for on-site visits we make arrangements.
Software from another builder? We’ll take a look
We also take over maintenance of software built by another party. Here is how:
Code review first. We look at the code, the architecture, the hosting and the documentation, and tell you honestly whether a takeover is feasible and what it means.
Honest advice. Sometimes software is cheaper to replace than to maintain. Then we say so, even if it means we don’t get the maintenance.
Frequently asked questions
What does maintenance cost per month? That depends on scope and rhythm. After a short conversation you get an indicative price, for a fixed monthly price or an hourly basis.
Do you ever stop maintenance? Only if you stop. We don’t leave a project unannounced, and on exit we hand over documentation, code and hosting access cleanly.
What if the software just keeps running without maintenance? That works, and it happens often: a well-built system keeps running for years. But components age and security updates fall behind. We recommend at least one security round a year, even if nothing else changes.
What if I want a larger expansion than fits within the monthly budget? Then you get a separate proposal with fixed scope and price, apart from your maintenance contract: a small project of its own.
Plan your maintenance conversation
Already a client? Then we schedule the maintenance conversation after your go-live.
Is your software running with another builder? Send us a short description of what is running and what you expect, and we’ll tell you whether a code review makes sense.