Architecture pressure-test
"How would you de-risk this migration?"
Before the call, you loaded the proposal, target architecture notes, and 3 postmortems from similar migrations. When the CTO asks, Minuta suggests: "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." The call shifts from abstract confidence to architecture judgment.
Scope boundaries
"What is included, and what is explicitly out of scope?"
You uploaded your scope template, past SOWs, and the client's intake notes. Minuta drafts the boundary in English: "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." You protect margin without sounding defensive.
Budget justification
"Your rate is high - why should we pay it?"
You loaded your rate sheet, testimonials, and outcome notes from prior projects. Minuta surfaces the 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." The conversation moves from price to value.
Seniority proof
"What tradeoff would you challenge us on?"
You attached discovery notes and your architecture tradeoff checklist. Minuta suggests a pointed but diplomatic answer: "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." You sound like someone who has seen the failure mode before.