Competitor-Add Outbound
A new competitor install is the buying signal — sequence it inside the 6-month window before it becomes background context.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.
Overview
Surface accounts that newly installed a named competitor or adjacent product in the last 6 months — a leading buying-signal proxy. Builds the cohort with `search_companies` filtered to the installed technology + firmographic ICP, then per-account verifies the install date with `company_technographic`. Returns a ranked list with one-line opening hooks citing the installation date.
Use cases
The install date that converts inside 6 months
Your SDR runs this with a competitor name and gets a list of accounts that installed it inside the last 6 months, ranked by ICP fit, with the leading function named. The opening line cites the install date directly — recipients can tell at a glance the message isn't a list blast.
ICP as a gate, not a soft filter
Accounts outside the industry / employee band don't survive the workflow. The output is ICP-true by construction, so the SDR doesn't waste sequence slots on accounts that won't qualify even if they reply.
View workflow prompt
# Competitor-Add Outbound
## Parameters
- `{{competitor_or_adjacency}}` *(required)* — Competitor or adjacent product to detect as a recent add (matched via `search_companies` technologies + per-account `company_technographic`). Example: `Snowflake`
- `{{your_product}}` *(required)* — Your product or category — anchors the displacement or extension angle. Example: `Databricks`
- `{{added_within_months}}` *(required)* — Lookback window for `firstVerifiedDate` (use 6 unless your category has unusually long evaluation cycles). Example: `6`
- `{{territory_filter}}` *(optional)* — Optional firmographic filter for the cohort (industry, country, employee band). Example: `industry: SaaS, country: US, employees 1001-5000`
## Purpose
You are an SDR working a competitor-add motion against {{competitor_or_adjacency}}. A recent install (≤{{added_within_months}} months by `firstVerifiedDate`) is a leading buying-signal proxy. Build the cohort with `search_companies`, verify the install date per account, gate by firmographic fit, and return ranked rows with one-line opening hooks per [`opening-line-discipline`](https://phoenix.hginsights.com/gtm/skills/opening-line-discipline) that name the install date and connect it to {{your_product}}.
## Process
1. **Resolve product** — `get_vendor_information` once with `vendorName: {{competitor_or_adjacency}}` to capture the `vendorId` (and `productId`s if multiple products are returned).
2. **Cohort build** — `search_companies` with `technologies: [{{competitor_or_adjacency}}]` and any firmographic filters from {{territory_filter}}. Returns a domain list of accounts running the product.
3. **Per-account verification** — for each domain, `company_technographic` with `vendorIds: [<vendorId>]` (or `productIds`) to capture the `firstVerifiedDate`. Keep accounts where the date falls inside the last {{added_within_months}} months.
4. **Firmographic gate** — `company_firmographic` per survivor for industry and employee-band columns; drop ICP misses not already caught in the `search_companies` filters.
5. **Function context** — `company_fai` per survivor with the resolved `productIds` (or `products: [{{competitor_or_adjacency}}]` as a name-fuzzy-match fallback) to identify which department's `departmentUsageShare` leads the install (drives contact-title selection).
6. **Contact pass** — `contact_search` per survivor for the function's senior titles; `contact_enrich` budget-capped at the top 5 accounts.
7. **Rank** — by recency of `firstVerifiedDate` (most-recent first), then by firmographic-fit strength.
## Output Format
- `# 🆕 Competitor-Add Outbound — recent {{competitor_or_adjacency}} installs`
- `## Ranked accounts` — table: rank | domain | industry | employee band | install date (`firstVerifiedDate`) | leading function | suggested contact | one-line hook
- Per-row citation: `[search_companies]` for cohort source, `[company_technographic]` for install date, `[company_firmographic]` for industry/employees, `[company_fai]` for function
## Quality Checklist
- Every row's `firstVerifiedDate` is inside the {{added_within_months}}-month window — outside that, the row is cut, not retained as context
- Firmographic columns are gating, not decorative — accounts outside ICP do not survive the ranking
- Each opening hook names the install date explicitly + connects it to {{your_product}} — no generic "noticed your team is growing"
- `contact_enrich` capped at 5 accounts per run per credit budget