Documentation & handover
What you receive when a project ends — and how we make leaving us easy.
The handover package #
- Architecture documentation: system diagrams, data flows, and the reasoning behind major decisions.
- Runbooks: deploy, rollback, backup/restore, and incident procedures written for an engineer who has never seen the system.
- Access inventory: every account, credential location, and third-party service, with ownership transferred to you.
- Onboarding guide: what a new hire needs to read, in order, to become productive.
Pair-onboarding your team #
Documentation alone never transfers a system. Handover includes working sessions where your engineers deploy, break, and fix the system with ours sitting next to them. For most projects this is one to two weeks; we are done when your team has run a full deploy-and-rollback cycle without us touching a keyboard.
Warranty & afterwards #
Every project carries a 30-day post-launch warranty: defects in what we built are fixed free. After that, you choose — your team runs it, we run it under managed services, or anything between. About 70% of project clients keep some ongoing relationship; the rest leave cleanly, which is exactly how it should work.
The handover timeline #
| Phase | Duration | Exit criteria |
|---|---|---|
| Documentation freeze & review | 1 week | Your team has read it and filed gaps; we fixed them |
| Pair-onboarding sessions | 1–2 weeks | Your engineers deploy, roll back, and restore a backup unassisted |
| Shadow period | 1–2 weeks | Your team operates; we watch and answer — not the reverse |
| Warranty | 30 days | Defects in delivered work fixed free, response within 1 business day |
NoteThe exit criterion for pair-onboarding is deliberately practical: a full deploy-and-rollback cycle by your team with our hands off the keyboard. Knowledge that has not been exercised is documentation, not capability.
Maintained by the delivery team · updated quarterly