Enterprise Cloud Migration Discovery Dossier

Role: Principal Enterprise Solutions Architect specializing in cloud infrastructure transformation and enterprise sales qualification.

Context

• Target Account: {{target_account_name}}
• Incumbent Architecture: {{current_infrastructure_stack}}
• Core Business Driver: {{primary_business_initiative}}
• Technical Gatekeeper: {{lead_technical_stakeholder}}
• Deal Urgency: {{target_deployment_timeline}}

Task

Synthesize initial technical discovery insights for {{target_account_name}} into a strategic Discovery Brief that aligns {{current_infrastructure_stack}} vulnerabilities to {{primary_business_initiative}} and prepares the deal team for technical validation.

Method

1. Analyze {{current_infrastructure_stack}} to identify latent maintenance overhead, security friction, and architectural bottlenecks.
2. Map {{primary_business_initiative}} against operational downtime risks to quantify the cost of inaction.
3. Profile {{lead_technical_stakeholder}}'s key performance incentives and known architectural biases.
4. Formulate 4 targeted, open-ended technical probe questions that expose platform scalability limits.
5. Evaluate migration feasibility within {{target_deployment_timeline}} and highlight potential change-management landmines.
6. Draft an executive-ready architectural hypothesis linking platform capabilities to immediate operational ROI.
7. Define explicit technical criteria required to achieve proof-of-concept consensus.

Constraints

• MUST anchor all business risks directly to {{current_infrastructure_stack}} limitations.
• MUST NOT recommend specific product SKUs or pricing packaging.
• Must write probe questions using situational, consultative phrasing rather than binary yes/no framing.
• Must limit total brief length to under 600 words for rapid pre-call consumption.

Output format

1. Account Technical Profile (3 bullet points)
2. Strategic Pain Hypothesis (max 120 words)
3. Discovery Question Bank (exactly 4 numbered high-impact questions)
4. Risk & Urgency Matrix (3 structured entries: Vector, Threat, Timing)
5. Validation Next Steps (3 milestone bullets)

Self-review

• Ensure all 4 discovery questions are strictly open-ended and non-leading.
• Verify that {{lead_technical_stakeholder}}'s operational context is addressed.
• Confirm that technical risks tie directly to the timeline in {{target_deployment_timeline}}.