Technology Stack Change Sales Trigger Outreach Playbook

Build an ethical B2B sales outreach playbook based on public technology stack changes, migrations, deprecations, or new tool adoption signals.

Prompt Template

You are a B2B sales strategist building account-based outreach from public technographic signals. Create a technology stack change trigger playbook for:

Product/service sold: [your solution]
Target account profile: [industry, company size, region, maturity]
Buyer personas: [CIO, RevOps, Head of Support, Engineering Manager, Security, Finance]
Trigger signal: [new CRM, analytics migration, ERP rollout, tool sunset, vendor consolidation, cloud migration, job post mentioning tool]
Signal source: [job posts, company blog, release notes, public case study, builtwith data, procurement notice, conference talk]
Likely business pain: [migration risk, adoption, training, data quality, integration gaps, compliance, cost]
Proof points: [case studies, benchmarks, customer logos, migration checklist, ROI]
Competitors/incumbents: [known tools or likely alternatives]
Outreach channels: [email, LinkedIn, phone, partner intro, event follow-up]
Sales motion: [SDR outbound, AE account plan, partner co-sell, executive outreach]
Compliance boundaries: [public-source only, no creepy personalization, no false urgency]

Create:
1. Trigger qualification rules and false-positive checks
2. Persona-specific pain hypotheses and discovery questions
3. Account research checklist using only appropriate public sources
4. Three-touch outreach sequence for each primary persona
5. Call opener and voicemail script tied to the trigger
6. Proof-point map that matches each pain hypothesis
7. CRM fields and tags to track the trigger campaign
8. Objection handling for timing, incumbent loyalty, and "how did you know?"
9. Ethical personalization checklist

Keep outreach helpful, specific, and transparent about the public signal.

Example Output

# Trigger Playbook: CRM Migration Signal

Qualification

Trigger is valid when at least two public signals match: job post mentions Salesforce migration, RevOps leader shares implementation post, and careers page lists Salesforce admin hiring.

Persona Hypothesis

RevOps: migration may create data quality, routing, and reporting gaps.

Sales leadership: pipeline reporting may be unstable during cutover.

IT: integrations and permissions may need governance.

Email Touch 1

Subject: Salesforce migration reporting risk

Hi {{first_name}}, I saw {{company}} is hiring around Salesforce migration work. Teams often discover pipeline reporting gaps only after cutover, especially when routing and lifecycle stages change at the same time.

We put together a migration QA checklist that helps RevOps teams catch the common misses before go-live. Worth sending over?

Tips for Best Results

  • 💡Use public signals only and state the signal plainly; vague surveillance-style personalization hurts trust.
  • 💡Qualify triggers with at least two sources before launching a campaign.
  • 💡Map the same trigger to different pains by persona instead of sending one generic migration email.