tech-changes
/tech-changes
Use technology changes as signals — adopting a tool that pairs with yours, dropping a tool you replace, a stack migration, or a contract coming up — and monitor the stack of ICP accounts. Use for technographic targeting and switch moments. Do not use to bash a competitor's tool.
- Author
- kokasexton ↗
- Repository
- koka-sexton-gtm-skills ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Use technology changes as signals — adopting a tool that pairs with yours, dropping a tool you replace, a stack migration, or a contract coming up — and monitor the stack of ICP accounts. Use for technographic targeting and switch moments. Do not use to bash a competitor's tool.
Original author description
Use technology changes as signals — adopting a tool that pairs with yours, dropping a tool you replace, a stack migration, or a contract coming up — and monitor the stack of ICP accounts. Use for technographic targeting and switch moments. Do not use to bash a competitor's tool.
How it works
- Read the change
- Where to see it
- Message
- Routing
SKILL.md preview
---
name: tech-changes
description: Use technology changes as signals — adopting a tool that pairs with yours, dropping a tool you replace, a stack migration, or a contract coming up — and monitor the stack of ICP accounts. Use for technographic targeting and switch moments. Do not use to bash a competitor's tool.
when_to_use: "Use when an ICP account adopts, drops, or migrates a tool in or next to your category."
not_for: "Trash-talking the tool they just chose."
---
<!-- koka-first -->
Defaults come from `KOKA-FIRST.md`.
# Tech Changes
A stack change is a moment when the company is already open to change, has budget allocated, and is rethinking workflows.
## Read the change
| Change | Signal | Play |
|---|---|---|
| **Adopted a complementary tool** (one you integrate with) | Your value just went up | "Now that you're on X, here's what teams add next…" |
| **Dropped a tool you replace** | Gap or active evaluation | Help them avoid the mistake that made them drop it |
| **Migrating platforms** (e.g. a CRM switch) | Every connected tool is up for review | Offer to be the easy part of the migration |
| **Adopted your competitor** | They bought the category; they're not lost | Nurture; watch for renewal or competitor signals |
| **Hiring for a tool skill** | A JD names a tool (see `skills/hiring-signals`) | Confirms the stack |
## Where to see it
Technographic lookup tools, job descriptions, integration marketplaces and partner directories, public case studies, and employee posts ("we just moved to X").
## Message
> Saw the team is moving to a new CRM this quarter. The migration is the moment to fix lead routing, before old habits get rebuilt. Here's the checklist we use.
## Routing
- Competitor customers → `skills/competitor-signals`
- Score → `skills/multi-signal`
Versions
The database has no other skills named tech-changes.
Database snapshot: 13.11.2026 · package version fdcd2dee8a8a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100technographic-qualifier
Turns messy evidence of a company's technology stack — tech-detection output, script tags, a careers page, job descriptions, a marketplace or G2 listing, or free text — into a qualification decision for a seller whose product integrates with, complements, or displaces specific… - 90tool-selection-stack
Build the right GTM tool stack for any stage — solo founder ($100/mo), small team ($500/mo), growth team ($2K/mo), and enterprise ($10K+/mo). With cost breakdowns, tool comparisons, and stack architecture. Use when choosing GTM tools, building a tech stack, comparing platforms,… - 100tech-stack-signal-outreach
Use this skill when a company's technology choices are a buying signal for you: \"target companies using X\", \"they just added a tool we integrate with\", \"technographic outreach\", \"companies switching away from a competitor\". Reads technology signals (tools added, removed… - 100tech-stack-signal-reader
Detect which tools a company runs from its own website and turn the stack into a qualification and an angle. Use when someone wants to know what CRM or sequencer or analytics a company uses, wants to find companies on a competitor, or wants tech stack based targeting. - 100intent-signal-aggregator
Monitor buyer intent signals across the web including job postings, tech changes, funding rounds, and leadership changes. Alerts when prospects show buying signals and prioritizes "hot" accounts. Use for timing-based prospecting. - 100revops-tech-stack
Design, audit, and consolidate the RevOps technology stack — CRM, enrichment, sequencing, analytics, integration architecture, and cost optimization. Use when auditing GTM tools, designing revenue technology, or consolidating vendor spend. Triggers on: "RevOps stack", "sales…