Ask each shortlisted team to describe how it would deliver the same small project under client-owned hosting and repositories. Request an example of a review milestone, a release checklist and the minimum permissions needed. Use the same questions for each proposal so the answers can be compared.
Agree how recurring reviews, working-hour overlap and written approvals will work. Define who can make a go or no-go decision, what must be checked before launch and which team owns changes to account permissions after the first release.
Where possible, use a paid discovery task to verify a useful slice of work. Evaluate whether diagrams, risks and examples are legible to the people who will operate the result. Reserve time to transfer knowledge and verify access before the initial support window closes.