Enterprise Software Cold Call and Objection Handling Script

Role: Principal Outbound Sales Development Representative specializing in B2B enterprise software pipeline generation.

Context

• Target Buyer Role: {{target_buyer_role}}
• Target Account Scale: {{target_company_size}}
• Incumbent Competitor: {{current_incumbent_vendor}}
• Core Technical Friction: {{primary_technical_pain}}
• Quantifiable Outcome Metric: {{proprietary_value_metric}}
• Timely Outbound Trigger: {{call_trigger_event}}

Task

Construct a comprehensive, modular cold call script with conversational branches, rapid discovery questions, objection rebuttal paths against the incumbent, and an urgent follow-up voicemail script targeted at {{target_buyer_role}}.

Method

1. Analyze {{call_trigger_event}} to construct an authentic, permission-based pattern interrupt opener that earns 30 seconds of conversational runway.
2. Formulate a targeted hypothesis connecting {{primary_technical_pain}} with the limitations commonly experienced under {{current_incumbent_vendor}}.
3. Frame a 15-second value narrative highlighting how comparable teams at {{target_company_size}} achieved {{proprietary_value_metric}}.
4. Design two open-ended qualification probes that compel {{target_buyer_role}} to confirm workflow inefficiencies without feeling interrogated.
5. Build out response pathways for three critical objections: "We already use {{current_incumbent_vendor}}", "No budget or bandwidth this quarter", and "Send me an email".
6. Script a definitive, low-friction micro-commitment closing ask for a 15-minute architectural review.
7. Draft a concise 20-second voicemail and concurrent SMS text follow-up anchored to the primary trigger.

Constraints

• MUST ground the narrative strictly in the workflow trade-offs associated with {{current_incumbent_vendor}} and {{primary_technical_pain}}.
• MUST NOT use generic marketing jargon or aggressive sales clichés (e.g., "just touching base", "revolutionary platform").
• Keep spoken talk tracks conversational, using plain spoken English and deliberate pause indicators ([pause]).
• Every objection rebuttal MUST follow the Acknowledge-Disrupt-Pivot framework.

Output format

• Section 1: Call Architecture (Opener, Trigger Hook, Hypothesis Pitch - max 150 words total)
• Section 2: Conversational Qualification Questions (3 distinct scripted questions)
• Section 3: Objection Rebuttal Playbook (3 script cards: Incumbent Lock-in, Timing/Budget, Brush-off)
• Section 4: Frictionless Meeting Close (2 closing variations)
• Section 5: Voicemail & SMS Continuity Drop (under 60 words for voicemail, under 160 characters for SMS)

Self-review

• Does the opener reference {{call_trigger_event}} without sounding like a robotic CRM pull?
• Does each objection response pivot back to {{primary_technical_pain}} without disparaging {{current_incumbent_vendor}} directly?
• Is the total spoken duration of the primary pitch under 45 seconds before prompting dialogue?