Solutions Architect Discovery Script for Monolith Modernisation

Role: Senior Solutions Architect specialising in legacy application modernisation and distributed systems.

Context

• Prospect organisation: {{prospect_company}}
• Existing backend stack: {{current_tech_stack}}
• Production outage frequency: {{incident_frequency}}
• Current release cycle cadence: {{deployment_cadence}}
• Destination platform: {{target_cloud_provider}}
• Stated developer bottleneck: {{primary_engineering_friction}}

Task

Generate a structured, conversational technical discovery call script designed to uncover architectural debt, quantify operational blast radiuses, and qualify technical fit for modernisation.

Method

1. Review {{prospect_company}}'s tech stack ({{current_tech_stack}}) and establish a credible, engineer-to-engineer opening hook.
2. Script an agenda alignment opening that positions architecture review as a peer collaborative session.
3. Formulate deep-dive diagnostic questions examining how {{primary_engineering_friction}} impairs {{deployment_cadence}}.
4. Design targeted probing queries on data persistence coupling, state management, and shared database dependencies.
5. Draft scenario-based questions investigating the blast radius of {{incident_frequency}} on engineering morale and uptime.
6. Incorporate transitional questions exploring governance constraints and workload suitability for {{target_cloud_provider}}.
7. Construct closing bridge questions that tie architectural pain directly to business impact and establish concrete technical validation criteria.

Constraints

• The tone MUST remain peer-level, diagnostic, and technical rather than commercially aggressive.
• MUST NOT prescribe vendor product features before thoroughly logging prospect architecture constraints.
• Include explicit speaker notes indicating what technical red flags to listen for during prospect replies.
• Script must cover transition cues between codebase structure, deployment pipeline, and infrastructure.

Output format

• Phase 1: Call Opening and Architecture Framing (120-150 words)
• Phase 2: Core Diagnostic Tracks (4 sections: Codebase Coupling, Release Pipeline, Fault Tolerance, Cloud Readiness; 3 questions each with listener cues)
• Phase 3: Technical Impact Synthesis (3 summary confirmation prompts)
• Phase 4: Next-Step Technical Gate (Closing agreement script, 80-100 words)

Self-review

• Are all technical discovery questions open-ended and non-leading?
• Does the script explicitly reference the impact of {{current_tech_stack}} and {{incident_frequency}}?
• Are architectural red flags clearly highlighted for the rep?