Engineers who stay, and support that's written down.

Per engineer per month, full time on your roadmap. What moves the rate is seniority, specialism — DevOps, data engineering and AI cost more than a mid-level product developer — and how long you commit for. The seat includes their delivery lead, code review, QA support and the infrastructure they work on, so you're comparing a working seat rather than a body. Send us the roles and the stack and you get a written rate card within one business day, with no obligation to use it.

Continuity and cover. A freelancer who's ill, on holiday or takes a better offer stops your work; a squad has a lead who knows the codebase and can cover. You also get code review by default, which a single freelancer can't give themselves, and someone accountable above the individual if the fit is wrong.

Three to four weeks for a dedicated squad — that's the time to select the right people rather than the first available ones, and to onboard into your codebase properly. A single engineer joining an existing engagement can usually start in about two weeks. If we can't staff you properly in that window, we say so.

Monitoring and alert response, severity-tiered incident handling with defined response times, security patching and dependency upgrades, backup verification, and an agreed monthly allowance of enhancement work. Each month you get a report of incidents, patches applied and changes shipped. Anything beyond the allowance is quoted before it starts.

They're contractual, not aspirational: one hour for a Severity 1 production outage during covered hours, four hours for Severity 2, one business day for Severity 3 and two business days for Severity 4, with resolution at the next planned release. Extended and 24/7 cover is available and priced separately rather than implied.

Yes — your Jira or Linear, your repository, your standups, your review rules and your definition of done. Embedded working is the default. The alternative is a separate workstream with a defined interface between us, which causes fewer arguments when the two teams use different stacks.

Tell us and we replace them, with a handover from the outgoing engineer rather than a cold swap. No argument, no charge for the transition period. A dedicated team only works if you can say this easily, so we make saying it easy.

Yes, after a two-week audit — architecture, dependency health, test coverage, security exposure, deployment risk. We won't sign response-time commitments on a system we haven't assessed, because we'd be promising something we can't evidence. The audit output is yours either way.