Tier 3 — Implementation
Software Maintenance
Ongoing support and improvement for systems already in production — whether we built them, or you inherited them from someone else.
Technical Approach
How we build it
Design
Architecture and requirements confirmed before a line of code is written.
Build
Development in visible, iterative cycles — not a black box until launch.
Test
Functional, performance, and security testing before anything reaches production.
Deploy
Staged rollout with monitoring in place from day one, not added afterward.
Technology Notes
- Available as a monthly retainer or ad-hoc, depending on what the system needs.
- Security patching and dependency updates handled proactively, not only when something breaks.
- Starts with a short architecture review if we didn't build the original system.
Not sure yet?
Every build benefits from an architecture review first, so what gets built can actually scale. If you haven't scoped this yet, start with technology architecture review.
Technology Architecture Review →Retainer Support
Response times by support tier
Maintenance is quoted per engagement, not sold as a fixed package. Retainer clients get a defined response-time commitment based on severity:
4 hours
Critical — production down, data at risk, or a client-facing system unusable.
8 hours
Priority — a significant feature or workflow broken, no acceptable workaround.
12 hours
Standard — a non-blocking bug, a minor issue, or a scoped change request.
24 hours
General — new maintenance enquiries and requests outside an active retainer.
Exact tier definitions and response-time commitments are confirmed in your retainer agreement.
Frequently Asked Questions
Can you maintain a system another company built?
Yes — we typically start with a short architecture review to understand what we're inheriting before taking on ongoing maintenance.
Do you offer retainer-based support?
Yes — ongoing maintenance is available as a monthly retainer or as ad-hoc support, depending on what your system needs.