Managed Service
Software does not stop needing attention after launch. Managed service is the arrangement for the years after, whether we built it or someone else did.
Ongoing operation of what we or someone else built: monitoring, deployment, security patching, incident response and a monthly change budget.
What we do
Managed Service
We take over operation of a running system: monitoring and alerting, deployments, security patching, backup verification and incident response. If we did not build it, the engagement starts with an audit and a written picture of what we are taking on.
Response commitments are agreed by severity, so an outage and a cosmetic bug are not treated as the same thing. What we are on the hook for, and what we are not, is written down before the first month starts.
A monthly change budget covers the small work that would otherwise wait for a project: a report, a field, a permission, an integration change. Anything larger is quoted separately rather than absorbed quietly.
Managed Service
What you get
Monitoring, alerting and an on-call path agreed by severity
Deployments, security patching and verified backups on a stated schedule
Incident response with a written cause and correction after the fact
A monthly change budget for small work, with what it covers made explicit
An entry audit when we inherit a system we did not build
Our Expertise
Typical stack
How we work
How a project starts, and how it is priced
Tell Us The Problem
Reach us by email or WhatsApp and describe what is broken or what you want built. We reply with our reading of the problem and the options.
Get Scope And Price
You receive a written scope, a timeline and a fixed price, including what is explicitly not included. No surprise line items later.
We Build And Hand Over
We deliver on the agreed timeline, with documentation and a working deployment. You can keep us on for support, or take it in-house.
How pricing works
The price follows the scope. Once we understand the problem, you receive a written quotation that states what is included, what is explicitly not included, the timeline and the price.
If something outside that scope turns up during the work, we write it down and tell you before anything changes. Extra work is quoted separately and only starts once you agree to it.
You can also stop after the quotation. Reading our scope does not commit you to building with us.
FAQ
Questions buyers ask us
How is managed service priced?
As a monthly arrangement, written down before the first month starts: what we are on the hook for, what we are not, the response commitments by severity, and the monthly change budget. Work larger than that budget is quoted separately rather than absorbed quietly.
How fast do you respond to an incident?
Response commitments are agreed by severity, so an outage and a cosmetic bug are not treated as the same thing. They are written into the agreement before the first month starts, and every incident ends with a written cause and correction.
Who owns the system while you operate it?
Ownership does not change because we operate it. The access we hold, and ownership of anything new we build under the change budget, are written into the agreement.
Do you take over systems you did not build?
Yes. The engagement starts with an audit and a written picture of what we are taking on, so you know what is covered before we are responsible for it.
What does the monthly change budget cover?
The small work that would otherwise wait for a project: a report, a field, a permission, an integration change. What it covers is made explicit in the agreement, and anything larger is quoted separately for you to approve.
Start with one conversation
Describe the problem and you get our reading of it, a scope and a price. If we are not the right fit, we will say so.