Pressure-test de arquitetura
"How would you de-risk this migration?"
Antes da call, você carregou a proposta, notas da arquitetura alvo e 3 postmortems de migrações parecidas. Quando o CTO pergunta, o Minuta sugere: "I would de-risk it in two phases: shadow traffic for 48 hours, feature flags around the new path, and a rollback lever owned by one person. The main risk is data drift, so I would measure that before cutover." A call sai de confiança abstrata para julgamento de arquitetura.
Limites de escopo
"What is included, and what is explicitly out of scope?"
Você subiu seu template de escopo, SOWs anteriores e as notas de intake do cliente. O Minuta monta o limite em inglês: "Included: migration plan, cutover runbook, and two validation checkpoints. Out of scope: rewriting the reporting layer or owning team staffing decisions. If those become necessary, I would price them as a separate workstream." Você protege margem sem soar defensivo.
Justificativa de orçamento
"Your rate is high - why should we pay it?"
Você carregou o rate sheet, depoimentos e notas de outcome de projetos anteriores. O Minuta puxa os receipts: "The rate maps to risk reduction: in similar migrations I shortened the decision loop, avoided one failed cutover, and left the team with a repeatable runbook. If useful, I can walk through the economics against the cost of a delayed migration." A conversa muda de preço para valor.
Prova de senioridade
"What tradeoff would you challenge us on?"
Você anexou notas de discovery e seu checklist de tradeoffs de arquitetura. O Minuta sugere uma resposta direta e diplomática: "I would challenge doing platform cleanup and product delivery in the same milestone. It looks efficient, but it hides two different risks. I would separate the dependency cleanup from the customer-visible release and make the acceptance criteria explicit." Você soa como alguém que já viu aquele modo de falha.