Prospecting
AuraScore 81/100

Enterprise Outbound Cold Call Script for Infrastructure Modernization

Generate a high-conversion cold calling script with tactical objection handlers for technical enterprise prospects.

Use this template when preparing outbound calling sprints targeting engineering or infrastructure leadership. It produces an opening hook, pattern interrupt, qualification questions, and objection handling pivots tailored to your target account.

Template

Role: Principal Outbound Sales Development Representative specializing in enterprise software architecture.

Context

  • Prospect persona and seniority: {{prospect_title}}
  • Target enterprise organization: {{target_company}}
  • Incumbent or legacy architecture: {{legacy_tech_stack}}
  • Primary operational challenge: {{core_pain_point}}
  • Unique technical differentiator: {{product_value_proposition}}
  • Measurable peer benchmark or case proof: {{social_proof_metric}}

Task

Draft a high-conversion cold calling dialogue script designed to bypass defensive gatekeeping, establish peer-level credibility, uncover latent architectural debt, and secure a 20-minute technical discovery meeting.

Method

  1. Analyze {{prospect_title}} responsibilities against systemic challenges found in {{legacy_tech_stack}} environments.
  2. Write a 10-second pattern-interrupt greeting that acknowledges cold outreach without using standard sales cliches.
  3. Formulate an insight statement linking {{core_pain_point}} directly to {{social_proof_metric}} achieved by similar engineering teams.
  4. Draft two diagnostic open-ended questions targeting infrastructure scalability and team velocity.
  5. Map out immediate talk tracks for the top three defensive objections: no time, currently evaluating internal builds, and satisfied with {{legacy_tech_stack}}.
  6. Formulate a low-friction close focusing on architectural exploration rather than a hard product demo.
  7. Add bracketed conversational delivery notes indicating tone, pacing, and strategic pauses.

Constraints

  • MUST write all spoken dialogue in natural, spoken-syntax English free of marketing jargon.
  • MUST include explicit delivery cues in brackets (e.g., [pause 2s], [downward inflection]).
  • MUST NOT exceed 250 spoken words across the primary conversation flow (excluding objection branches).
  • Spoken lines must emphasize peer-to-peer engineering trade-offs rather than feature checklists.

Output format

1. Opener & Pattern Interrupt (Spoken script with delivery cues)

2. Value Wedge & Diagnostic Questions (Hook, validation, 2 diagnostic questions)

3. Objection Playbook (Three branches: 'Not a Priority', 'Using Incumbent', 'Send Info')

4. Low-Friction Close (Direct ask with proposed agenda)

Self-review

  • Verify that {{target_company}} and {{product_value_proposition}} are integrated seamlessly into the dialogue.
  • Ensure objection handlers validate the prospect's concern before pivoting.
  • Check that word count for the primary track remains under 250 words.
AuraScore breakdown
81/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 engineering12/12 · Strong

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 efficiency5/10 · Thin

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-prospecting
technology-software
cold calling
outbound sales
enterprise sdr