Signal recipe
Tech changeTech stack change detected
A target account adds, drops, or swaps a technology that sits next to yours. A stack change signals an active evaluation cycle and a team open to new tools.
Where the evidence comes from
- Public tech-detection sources (page tags, job posts)
- Engineering blogs and changelogs
- Careers-page skill requirements
Public sources only. Every claim on a page cites back to one.
How Intakra weights it
Medium weight, and directional. Adopting an adjacent tool signals an in-flight modernization your product complements; dropping the incumbent you replace is a stronger displacement cue, so Intakra weights the two differently.
Who tends to own the decision
The technical or ops owner running the stack decision.
Recommended play
Anchor to the specific change and the gap it opens next to it. If they just adopted an adjacent tool, position as the complement, not a competitor to it.
Noticed {company} moved to {trigger}. Teams that make that switch usually hit the same next gap; here is how we slot in alongside it.
This is a template, not a real message. Placeholders like {company} and {trigger} fill in from the cited why-now once Intakra names the real account. Never send it unedited.
Related concept
Data used to infer that an account is researching or ready to buy, spanning first-party behavior, third-party topic consumption, and public events.
Intent data in the glossary →More signal recipes