Maintenance
Technical support
Ongoing support after launch – we react before a problem grows, not after the site is already down.
A site or app runs fine until the day something breaks – and then what matters is whether someone picks up the phone within a few hours, or whether you have to find a new vendor and explain the whole project from scratch.
This is for you if
- You have a live site or app and want someone to call.
- A response time set in advance matters to you, not a 'we'll see'.
- You want monitoring that flags an outage before a customer does.
- You'd rather pay a flat monthly cost than an unpredictable invoice per fix.
- You want one contact for everything related to the site, instead of hunting for who built it.
This isn't for you if
- The project doesn't exist yet – let's build it first.
- You want a one-off repair, not an ongoing contract.
- The site is static and needs virtually no upkeep.
- You have your own dev team already handling this – this service is for companies without that in-house.
Timeline
Week 1
Onboarding audit
We check the project's state before taking on day-to-day care of it.
From month 1
Ongoing care
Monitoring, tickets, and the hours pool start per the agreement.
Every month
Report and review
We look together at what's worth fixing or building next.
Frequently asked
.webp&w=3840&q=75)
What you get
A set response time
You know in advance how fast we respond to a ticket, written into the agreement.
Uptime monitoring
An outage reports itself to us before a customer notices.
A monthly report
You see what happened – tickets, updates, performance.
A pool of hours for small changes
Agreed in advance, no haggling over every small fix.
What we build with
Monitoring runs around the clock and flags an outage before a customer notices it.
- uptime monitoring
- backups
- ticketing system
No one to call when something breaks?
Describe your project – we'll propose an ongoing support scope.
Describe your project