Write a Trigger-Event-Based Cold Call Script

You are a senior outbound strategist for agencies. You know that trigger-event calls convert 5–10x cold lists when the rep makes the trigger the WHOLE reason for the call — not an afterthought.
Agency: [AGENCY_NAME] | Services: [SERVICES] | Rep: [REP_NAME] | Prospect: [PROSPECT_NAME], [PROSPECT_TITLE] at [PROSPECT_COMPANY] | TRIGGER EVENT: [TRIGGER_EVENT] | Date of trigger: [TRIGGER_DATE] | Why this trigger matters for [SERVICES]: [TRIGGER_RELEVANCE] | Hypothesis about their priority right now: [HYPOTHESIS]
Write a cold call script (≤90 seconds of rep talk total) built entirely around [TRIGGER_EVENT]. Structure: (1) Opener that names the trigger in the first sentence, (2) Hypothesis statement, (3) Question that invites them to confirm or correct the hypothesis, (4) ONE branch if they engage, (5) ONE branch if they push back. End with a meeting ask tied to the trigger's timeline urgency.

- Trigger must be in the FIRST sentence — not buried after "how are you"
- Hypothesis must be specific and falsifiable, not generic
- No "congratulations on the round" — that's what every other SDR says
- Meeting ask must reference WHY now (urgency tied to trigger)
- ≤90 sec rep talk total across the script
- No fake stats

## OPENER (≤20 sec)
[REP]: ...

## HYPOTHESIS + INVITE TO CORRECT (≤20 sec)
[REP]: ...

## BRANCH A — PROSPECT ENGAGES
[REP]: ...
[Meeting ask]: ...

## BRANCH B — PROSPECT PUSHES BACK
[REP]: ...
[Fallback ask]: ...

• [AGENCY_NAME] — Your agency
• [SERVICES] — What you sell
• [REP_NAME] — Rep first name
• [PROSPECT_NAME] — Prospect first name
• [PROSPECT_TITLE] — Their title
• [PROSPECT_COMPANY] — Prospect company
• [TRIGGER_EVENT] — Specific event — funding, hire, ad change, etc.
• [TRIGGER_DATE] — When the trigger happened
• [TRIGGER_RELEVANCE] — Why this trigger creates demand for your services
• [HYPOTHESIS] — Your specific hypothesis about their priority

Agency: Northbeam Growth | SEO + paid search | Rep: Jordan | Prospect: David Liu, VP Marketing at LumenCRM | Trigger: closed $40M Series B, announced May 12 | Relevance: Series B SaaS typically 2x's paid pipeline target within 6 months and SEO falls behind | Hypothesis: David is being asked to deliver pipeline fast and is leaning on paid because SEO takes too long

## OPENER (~18 sec)
[REP]: "Hey David — Jordan from Northbeam. Cold call. Reason I'm calling is your Series B announcement two weeks ago. Mind if I take 30 seconds and you can tell me to buzz off?"

## HYPOTHESIS + INVITE (~18 sec)
[REP]: "My guess is the board just doubled your pipeline target for next half, and you're leaning hard on paid because SEO takes too long to move the needle. Fair, or am I way off?"

## BRANCH A — ENGAGES
[REP]: "Thought so. Every Series B SaaS marketing leader I've talked to this quarter is in the same spot. Reason I called: there's a way to compress SEO timeline by 6–8 weeks if you do technical fixes in the first 30 days instead of saving them for later. Worth a 20-min look at LumenCRM's top 10 pages so I can show you which ones we'd prioritize?"
[Meeting ask]: "Thursday 2pm or Friday 10am your time?"

## BRANCH B — PUSHES BACK
[REP]: "Totally get it. Different ask: can I send you a 90-second Loom of the 3 fastest-payback technical fixes for LumenCRM? If it's not useful, no reply needed."
[Fallback ask]: "Cool — best email for the Loom?"

• Use a trigger feed (Crunchbase, LinkedIn Sales Nav, BuiltWith) — don't rely on memory
• Call within 5 business days of the trigger — urgency decays fast
• If your hypothesis is wrong, you still win — the prospect corrects you and now you're in a conversation