Managed systems
We don’t disappear after launch.
DevnTech operates, monitors and continuously improves the systems we build. Most of the value in an automation shows up in the months after go-live — and so does most of the risk.
- From $4,500
- About 4 weeks to launch
- 30 days operating support
Where a system nobody owns usually shows up
01
The last project stopped working in month five
Something changed upstream, nobody owned it, and by the time anyone noticed the team had gone back to doing it by hand.
02
Nobody is watching the numbers
Uptime is monitored. Accuracy and exception rate are not, so quality drifts invisibly.
03
Your team inherited something they did not build
It works, but changing it is nobody’s idea of a good afternoon, so it stays frozen while the business moves.
04
Improvements never get made
The obvious next optimization is understood by everyone and scheduled by no one.
05
The 2am question has no answer
When an automated workflow makes the wrong call overnight, it is not clear who finds out or who fixes it.
What we actually deliver
Incident management
Monitoring, alerts that come to us, and a named response path.
Maintenance
Vendor API changes, model changes, dependency updates and your own system upgrades — handled as routine work rather than as emergencies.
An improvement backlog
Ranked by value against the KPI, reviewed with you on a set cadence, and worked through rather than admired.
KPI reporting
The agreed operational metric, still measured against the baseline captured before anything was built.
Operating what we build is the only honest quality incentive.
A vendor who never has to run their own work does not feel the cost of building it badly. We do, which is a far more reliable guarantee than a promise about our standards.
- Alerts come to us first, not to your operations manager.
- Exception rate and accuracy are tracked as KPIs, not just uptime.
- Changes go through the same controlled pipeline after launch as before it.
- You can end the arrangement and keep the system running. That is the point of the documentation.
What fixing a system nobody owns looks like in practice
Watching for drift
Exception rate → threshold → investigation
A rising exception rate usually means something upstream changed. We treat it as an incident, not a curiosity.
Vendor changes
Deprecation notice → migration → verification
The endpoint that is going away in ninety days is handled in week one, not in week thirteen.
Model updates
New model → evaluated against baseline → promoted or rejected
A newer model is not automatically a better one for your task. It has to beat the current numbers first.
Quarterly KPI review
Baseline → current → next improvement
A conversation about the number, and what we are doing next to move it.
What this looks like in production
Case studies that used this capability
Internal software · Integration
Five to Nine
Workplace events platform
Event scheduling, user management and reporting were spread across the product and a set of external tools, and the platform could not be extended safely because so little of it was covered by tests.
Integration · Managed system
Mula
Mobile payments
Users needed to pay bills, buy airtime and send money across many separate banks and providers, each with its own interface and failure behaviour.
Internal software · Automation
Paved
Newsletter sponsorship marketplace
Matching advertisers to newsletter publishers, placing campaigns and reporting on them was relationship-by-relationship work that did not scale.
The rest of what we do
- AI implementation
- Workflow automation
- Integrations
- Internal applications
- Managed systemsYou are here
Questions about a system nobody owns
How is this priced?
A monthly fee based on how many workflows we operate and how critical they are, quoted in writing after the pilot. It covers monitoring, incident response, maintenance and an agreed amount of improvement work. Anything larger is scoped separately so you always know what is included.
Can we cancel?
Yes, and the system keeps running. It is on infrastructure you control, the code is yours, and it is documented. Nothing about the arrangement depends on you being unable to leave.
What is your response time when something breaks?
Agreed per workflow based on what it costs you when it stops. A workflow that would halt shipping gets a different commitment from one that produces a weekly report, and we would rather set that expectation honestly than promise the same number for everything.
Is our company the right size for this?
The offer is built around businesses doing roughly $5M to $30M in revenue, with recurring internal processes and someone who owns them. Outside that range we will still reply — we will just be honest about whether we are the right fit.
What does this cost?
The 30-day pilot starts at $4,500 and covers one workflow end to end, including 30 days of operating support. Ongoing managed systems are a monthly fee that depends on how many workflows we run for you and how critical they are. We quote both in writing before anything starts.
Already have something built that nobody is looking after?
Tell us what it does and what breaks. We will tell you what it would take to operate it properly, and whether it is worth keeping before we offer to run it.
- For businesses with $5M to $30M in revenue
- No long-term commitment
- Start with one workflow
- Keep ownership of everything we build