Keep production software stable and improving

Yes, that's the usual case. We begin with technical onboarding: reading the code, mapping infrastructure, verifying backups and documenting what we find. You get that assessment regardless of whether you continue with us.

We read the codebase, map the infrastructure and dependencies, audit access, and verify that backups exist and restore correctly. It produces a written picture of the real state, including risks the previous team may not have flagged.

Either. A retainer suits ongoing maintenance and a steady improvement cadence; fixed scope suits a defined piece of stabilisation work. We'll recommend the one that fits your situation rather than the one that bills more.

By impact, against response times agreed in advance. A production outage and a cosmetic bug are not the same ticket, and the arrangement says so explicitly so there's no negotiation mid-incident.

Yes. Most live products need a steady stream of small improvements, and a support arrangement is a sensible way to get them without carrying permanent engineering headcount. Larger features are scoped separately.

Primarily TypeScript, React, Next.js, Node and Python stacks on PostgreSQL and the major clouds. If your stack is outside that, we'll say so during onboarding rather than take on something we can't support well.