Practice5 min read
The handover is the product
ARQON EngineeringARQON Singapore
If your team can't ship on its own three months after we leave, we've failed, whatever else we delivered.
At the centre of agency and consulting work sits an awkward incentive: the longer you're needed, the more you earn. Most firms deal with it by not thinking about it too hard. We would rather decide how we'll leave in the first week.
Signs a handover is going wrong
- Your engineers have never opened a pull request in the outside team's repository.
- Design decisions live only in the outside team's heads and their Slack history.
- Someone from the outside team has to be awake for every deploy.
- The documentation gets written in the last two weeks.
How we do it
From the first commit, we work inside your repository, your CI and your cloud. From week four, every feature is built in pairs with your engineers, as authors, not observers. We write architecture decision records (ADRs) at the moment we decide, while the alternatives are fresh enough to describe honestly.
In the final phase we deliberately step back. Your team leads the work and we move to review. On the invoice it looks like the stretch where we do the least. We think it is worth more than any other.
We measure success by how quickly clients stop needing us. It's an awkward way to run a business. It's also a very good filter for finding the clients we work best with.
Filed under Practice · 2026.04.30
Back to the journal