Account plans
AuraScore 79/100

Cloud-Native Architecture Modernization Account Strategy Checklist

Structure pre-sales validation and architectural buy-in for large-scale enterprise microservices transformations.

Use this checklist when drafting an account strategy for selling modernization platforms into legacy monolithic codebases. It aligns technical debt discovery, cloud infrastructure boundaries, and buying committee validation.

Template

Role: Strategic Enterprise Account Executive specializing in distributed cloud-native architecture platforms.

Context

  • Enterprise Account: {{enterprise_name}}
  • Current System Architecture: {{architecture_type}}
  • Primary Cloud Provider: {{cloud_provider}}
  • Technical Debt Summary: {{technical_debt_backlog}}
  • Target Fiscal Budget Cycle: {{budget_cycle}}
  • Key Technical Champions: {{key_engineering_sponsors}}

Task

Generate a comprehensive strategic account sales checklist to guide the sales team in securing architecture modernization commitments from engineering leadership at {{enterprise_name}}.

Method

  1. Assess architectural bottlenecks in {{architecture_type}} against modernization objectives.
  2. Validate compatibility with existing infrastructure hosted on {{cloud_provider}}.
  3. Tie {{technical_debt_backlog}} metrics directly to business costs, release velocity, and operational risk.
  4. Map alignment strategies for {{key_engineering_sponsors}} across VP of Architecture, Principal Engineers, and DevOps directors.
  5. Synchronize deal milestones with {{enterprise_name}}'s capital allocation schedule for {{budget_cycle}}.
  6. Formulate proof-of-concept verification steps demonstrating microservice isolation and rapid debugging.
  7. Construct an execution checklist covering architectural scoping, business value alignment, and closing operations.

Constraints

  • Focus exclusively on enterprise software architecture, cloud platforms, and engineering stakeholder management.
  • MUST present checklist items in actionable imperative voice starting with a strong verb.
  • MUST NOT omit technical infrastructure considerations in favor of purely commercial terms.
  • Maximum 5 distinct phases in the output checklist.

Output format

  • Phase 1: Architectural Discovery & Debt Assessment (4-5 checklist items)
  • Phase 2: Technical Champion Mobilization (4-5 checklist items)
  • Phase 3: Cloud Architecture Proof-of-Concept (4-5 checklist items)
  • Phase 4: Commercial & Procurement Scheduling (3-4 checklist items)
  • Executive Summary Table (Key Objectives, Identified Champions, Budget Window)

Self-review

  • Confirmed all variables are embedded logically in the context and method steps.
  • Checked that technical debt and cloud provider elements are explicitly addressed.
  • Ensured formatting adheres to the 4 phases and final summary table structure.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-account-plans
software-engineering-debugging
cloud-native
microservices
system-architecture