Tech Stack Change

Signal: A company adds or removes a technology from their stack — detected via technographic data providers (BuiltWith, Clearbit Reveal, Datanyze, HG Insights).

Window: 1–3 months after adoption. Too early and they’re still in implementation. Too late and they’ve formed new habits.

---

Why this works

Changing tools is expensive and disruptive. Companies only do it when something is broken badly enough to justify the pain. When they add Salesforce, they have a pipeline management problem. When they drop Marketo for HubSpot, their marketing automation was failing. When they add Outreach, their reps aren’t managing their own outreach effectively.

Every tech stack change reveals a specific problem. That problem is your opening.

---

How we find them

• Technographic providers: BuiltWith, HG Insights, Datanyze — we check against your ICP company list
• LinkedIn signals: job descriptions referencing new tools (“must know [tool] — recently implemented”)
• G2 / Capterra reviews: recent reviews mentioning switching (“we moved from X to Y because…”)
• Product Hunt launches: new integrations and partnerships signal stack expansion

---

The angle matrix

Tool added	Problem it reveals	Your angle
Salesforce / HubSpot	Pipeline visibility is broken	”Teams switching to [CRM] find outbound quality becomes the next gap”
Outreach / Salesloft	Reps aren’t doing enough outbound	”Adding a sequencer without fixing the list quality is like tuning an engine with bad fuel”
Apollo	They’re trying to DIY list building	”Apollo is great for finding contacts — the part that breaks is the copy and the follow-up”
Gong / Chorus	Call quality issues, want to understand why	”Most teams add conversation intelligence before fixing lead quality — they end up with perfect recordings of bad meetings”
Slack (sales channels)	Growing team, coordination breaking down	Operational signal — good firmographic signal, pair with another trigger

---

The sequence

Touch	Timing	Angle
1	Month 1–2 post-adoption	Name the gap the new tool reveals
2	Day 5	The next thing that usually breaks after [tool] goes in
3	Day 11	Peer reference — similar company, same stack
4	Day 17	Value add — a specific insight about their new setup
5	Day 23	Breakup

---

Sample opening

“Noticed [Company] added Outreach recently — solid choice for sequencing.
Most teams find by month 2 that the bottleneck shifts from sending to list quality.
We handle the upstream layer — finding the right contacts with the right signal — so the sequences actually convert. Worth 15 minutes?”

---

What to avoid

• Don’t name your data source — “We saw via BuiltWith that you added X” reads as surveillance
• Don’t position against the tool they just bought — they made that decision, they’re committed to it. Position as complementary
• Don’t lead with features — lead with the problem the stack change implies