Developer Observability Account Expansion Readiness Checklist

Role: Principal Technical Account Manager specializing in enterprise APM and distributed tracing software.

Context

• Target Customer: {{target_account}}
• Current Observability Toolchain: {{current_toolchain}}
• Engineering Team Scale: {{engineering_headcount}}
• Production Incident Frequency: {{incident_frequency}}
• Target Expansion Business Unit: {{target_business_unit}}
• Governance & Security Posture: {{security_posture}}

Task

Develop an actionable account plan expansion checklist to transition engineering teams within {{target_account}} from fragmented debugging workflows to a centralized observability and telemetry platform.

Method

1. Inventory current APM, logging, and distributed tracing tools listed in {{current_toolchain}} across {{target_business_unit}}.
2. Quantify mean time to resolution (MTTR) impacts associated with {{incident_frequency}} to build value justification.
3. Map engineering org structure based on {{engineering_headcount}} to identify platform engineering champions and site reliability engineers (SREs).
4. Evaluate data residency and compliance prerequisites dictated by {{security_posture}} for telemetry ingestion.
5. Formulate technical proof-of-value (PoV) success criteria centered on debugging complex distributed service dependencies.
6. Identify potential commercial friction points and license rationalization opportunities across {{target_account}}.
7. Sequence rollout milestones into pre-sales discovery, architectural validation, executive alignment, and contract closing checklists.

Constraints

• Focus exclusively on technical telemetry, SRE workflows, and engineering account expansion dynamics.
• MUST organize checklist items into prioritized chronological deployment phases with binary verification states.
• MUST NOT introduce generic software sales boilerplate that neglects distributed system debugging realities.
• Limit checklist items to clear operational directives under 20 words each.

Output format

• Phase 1: Pre-Engagement Architectural Scoping (4-6 checklist items with checkbox format)
• Phase 2: Technical PoV & SRE Validation (4-6 checklist items with checkbox format)
• Phase 3: Commercial & Procurement Realization (4-6 checklist items with checkbox format)
• Risk & Dependency Matrix (markdown table containing Risk, Severity, and Mitigation)

Self-review

• Verified all 6 variables are referenced directly in Context and Method.
• Confirmed checklist items focus on debugging and distributed systems observability.
• Checked that output format contains exact named phase headers with checkbox formatting.