Maintenance & Support
Software rots quietly: dependencies age, certificates lapse, a payment gateway changes an API. We watch for it, patch it, and keep a small budget of hours each month for the improvements you keep meaning to ask for.
What you get
Typical stack
Engagement
Monthly retainer in three sizes, cancellable with thirty days notice. We also take on software we did not build, after a code review.
Planning your maintenance & support project
Support scope depends on the existing codebase, hosting, dependencies and business-critical workflows. Separate incident response from planned improvements and agree which systems are covered. Access to repositories, deployment documentation and recent incident history helps establish a practical starting point.
Explore our delivery process →Questions about maintenance & support
Can you maintain a product built by another team?
An initial code review helps identify technical risks, missing documentation and the effort needed to take over. The support agreement should follow what that review establishes.
What should a support agreement specify?
Define covered systems, response windows, escalation contacts, maintenance tasks and how improvement hours are used. A response-time commitment is different from a guaranteed resolution time.