Replace a squad member without losing velocity: the Revin protocol

Replacing a dev in an external squad usually stalls projects for 30-60 days. Revin operates with a 5-14 day SLA and documented handoff. See the 4-phase protocol — and why this is the most underrated differentiator of a managed squad.

Por Victhor Araújo

Victhor Araújo

A dev asks to leave the project. In a generic squad or bodyshop, the client finds out Thursday and substitution starts from zero: open req, interview, hire, onboard. In 30-60 days, the replacement is productive. In the meantime, the project stalls.

Revin operates with a 5-14 day substitution SLA and documented handoff. Not a favor — encapsulated process. The 4-phase protocol below runs on every contract. This is the most underrated managed-squad differentiator: continuity independent of individual turnover.

For CTOs and founders who already lived 'the dev asked to leave and now the project stalls for 6 weeks' — or who want to avoid that pain before hiring an external squad.

A healthy substitution starts 5 days before the leaver's last day — not after

🔄 Why fast substitution is hard in squads without process

The leaving dev takes everything in their head: decision context, mentally-mapped tech debt, informal stakeholder conversations, implicit project patterns. Without documentation, the replacement starts from zero — and the client pays the learning curve.

Squads without substitution protocol operate on 'it will be fine' — until the first turnover, when it isn't. That's when the client discovers they bought a person, not capacity.

📋 The 4-phase protocol (Revin)

Phase 1 — Day 1 to Day 3: pre-handoff

• Tech lead identifies the replacement from internal senior pool (usually within 24h, given the seniority protocol we apply).
• Leaving dev prepares handoff doc on a standard template: product context, decisions of the last 90 days, known tech debt, open integrations.
• Tech lead reviews the doc — if there are gaps, forces detail before closing.

Phase 2 — Day 3 to Day 7: intensive pairing

• Replacement joins the project in parallel with the leaving dev (3-5 days of overlap).
• Pair programming on 2-3 real backlog tickets — not an exercise, production code.
• Introduction to the client stakeholder led by the leaving dev (cordial transition, not rupture).

Phase 3 — Day 7 to Day 10: monitored solo operation

• Replacement takes tickets alone. Tech lead reviews every PR in this phase.
• Daily with tech lead, 30 min/day, to unblock questions that would become bugs.
• Velocity metric compared to pre-substitution baseline — < 20% deviation is the target.

Phase 4 — Day 10 to Day 14: validation and close-out

• Retro with client: what worked, what needs adjustment.
• Handoff doc updated with what the replacement discovered during the process (becomes a living artifact).
• Tech lead reduces mandatory PR review to normal senior-squad standard.

Documented handoff separates "swap a person" from "unblock the project"

🛠️ What makes this protocol viable

• Internal senior pool available. Without a pool, substitution depends on recruiting again — weeks.
• Documentation as continuous practice. ADRs and handoff docs aren't written on exit day; they're written as part of normal work.
• Embedded tech lead. Without a tech lead, nobody coordinates the substitution — the client becomes coordinator.
• 3-5 days of overlap contractually covered. Without that, the client's internal team carries the handoff.

💰 The real cost of botched substitution

Substitution taking 60 days (generic squad) costs, in a 5-person squad, ~20% of velocity lost in the quarter. In USD: USD 50k-100k depending on contract. Substitution in 14 days (Revin) costs < 5% velocity loss — direct ROI differentiator.

📢 Suffered from botched substitution in the last squad and want to avoid it on the next? Book a Discovery Call — Revin includes the substitution SLA as standard contract clause.

🎯 Conclusion: continuity is differentiator, not luck

Managed squads deliver continuity because they have a senior pool + continuous documentation + tech lead + contractual clause. Squads without those 4 elements run on luck — and luck ends at the first turnover.

📢 See our cases to see where Revin squads operated with 0% impact on substitution.