Maintenance and support
What happens after delivery. Thirty days of fixes included, then a small monthly plan or nothing at all, your choice.
The first thirty days
Every fixed-scope delivery includes thirty days of fixes. If something in the done-checklist does not behave as written, we fix it, at no charge, within two working days for anything blocking and within the week for the rest. This is not a trial period; it is us standing behind the work.
After that
Three options, and "none" is a real one:
- None. The system runs on your accounts, the docs are in the repo, you call us if you ever need us. Most small tools live happily like this.
- Monthly care. A small fixed fee covers dependency updates, security patches, monitoring, backups verified, and a few hours for small changes. Priced per system; ask.
- Ongoing development. A monthly budget and a rolling plan, reviewed together. This is the sales track.
Response times
| Severity | Example | We respond | We aim to fix |
|---|---|---|---|
| Blocking | Production down, data at risk | Within 4 working hours | Same day |
| Degraded | A feature broken, workaround exists | Within 1 working day | Within 3 working days |
| Minor | Cosmetic, nice-to-have | Within 3 working days | Next planned release |
Our working hours cover most of the business day across Europe and Asia.
What maintenance is not
It is not a way to drip-feed new features without a scope. New work is scoped like any other. It is also not an excuse to never upgrade: part of monthly care is keeping dependencies current so there is never a painful big-bang upgrade later.