DevOps Account Executive Discovery Call Script for CI/CD Optimisation
Guide a high-impact discovery conversation with VPs of Engineering on CI/CD pipeline stalls and code quality debt.
Use this template to author a strategic discovery conversation script for enterprise sales discussions with engineering executives. It surfaces developer productivity waste, pipeline bottlenecks, and security scan friction.
Role: Enterprise DevOps Strategic Account Executive specialising in continuous integration and developer productivity.
Context
- Enterprise account: {{target_enterprise}}
- CI/CD tooling in use: {{cicd_platform}}
- Build and test failure rate: {{build_failure_rate}}
- Security/compliance gate blockers: {{security_scan_blockers}}
- Total engineering headcount: {{engineering_headcount}}
- Strategic business delivery goal: {{quarterly_release_goals}}
Task
Develop a strategic executive discovery script to lead a consultative conversation with engineering leadership, linking pipeline inefficiencies and testing delays to missed product delivery milestones.
Method
- Structure an executive opening framing developer velocity as the catalyst for {{quarterly_release_goals}}.
- Script conversational questions that quantify developer idle time caused by slow pipelines in {{cicd_platform}}.
- Formulate deep discovery questions on the financial and velocity costs of {{build_failure_rate}} across {{engineering_headcount}} engineers.
- Design specific inquiries into how {{security_scan_blockers}} interrupt continuous delivery flows and create friction between AppSec and Dev teams.
- Develop transition scripts to shift the conversation from technical symptoms to lost roadmap opportunity cost.
- Script objection responses for common engineering executive pushbacks (e.g., 'We prefer building in-house scripts').
- Outline a joint discovery summary script that confirms mutual alignment before proposing a technical pipeline audit.
Constraints
- Tone MUST balance high-level business impact with authentic DevOps pipeline literacy.
- MUST NOT dwell entirely on low-level syntax errors; anchor findings to engineering throughput and delivery risk.
- Provide explicit talk-tracks for handling at least two executive objections.
- Maintain crisp stage directions for pacing, silence, and active reflection.
Output format
- Stage 1: Executive Hook & Meeting Alignment (100 words)
- Stage 2: Pipeline Velocity Discovery (3 core questions with financial impact calculation prompts)
- Stage 3: Quality & Security Friction Diagnostic (3 questions with executive follow-ups)
- Stage 4: Strategic Impact & Roadmap Risk Validation (2 high-level framing questions)
- Stage 5: In-House Tooling Objection Handling (Scripted response and pivot, 100 words)
- Stage 6: Next-Step Agreement Script (75 words)
Self-review
- Does the dialogue connect pipeline failures directly to {{quarterly_release_goals}}?
- Is the calculation framework realistic for an engineering team of {{engineering_headcount}}?
- Are the objections tailored to engineering leaders defending existing {{cicd_platform}} setups?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.