Partner Tech-Overlap Finder
Find where your product and a partner's are installed together — the joint install base that's already proof the integration matters.
Partner - Tech overlap
The accounts running both products — proof the integration matters
214
Joint installs
Proof + expansion
214 run both. 1,100 run one - the
integration-expansion target list.
214 run both. 1,100 run one - the
integration-expansion target list.
| Group | Accounts |
|---|---|
| Both products | 214 |
| Ours only | 620 |
| Partner only | 480 |
Why it lands
The 214 accounts already running both products are living proof the integration matters — your co-marketing references. The 1,100 running just one are the expansion list: pitch them the integration their peers already use.
Overview
Find the accounts where both your product and a partner's product are installed (the joint install base) using HG technographic data — quantifying the overlap and surfacing the accounts that prove the integration's value, for co-marketing references and expansion targeting.
Use cases
Co-marketing references that are real
An integration case study lands when you can point to 214 accounts already running both. The joint install base is your evidence and your reference pool.
Integration-expansion in both directions
Accounts on your product but not the partner's (and vice versa) are the warmest integration upsell — they already run half the story.
View workflow prompt
# Partner Tech-Overlap Finder
## Parameters
- `{{our_product}}` *(required)* — Our product to find in the install base. Example: `our observability platform`
- `{{partner_product}}` *(required)* — The partner product to overlap with. Example: `PagerDuty`
- `{{segment}}` *(optional)* — Optional segment to scope the overlap. Example: `US software, 200-5000 employees`
## Purpose
Find the joint install base where {{our_product}} and {{partner_product}} co-occur (optionally scoped to {{segment}}) — quantifying the overlap, surfacing reference-worthy accounts, and flagging single-product accounts as integration-expansion targets.
## Process
1. **Find each base** — `company_technographic` + `search_companies` for accounts running {{our_product}} and for accounts running {{partner_product}}.
2. **Intersect** — the joint install base is the overlap; quantify it (count, and as a share of each product's base).
3. **Scope** — `company_firmographic` to apply {{segment}} if provided.
4. **Reference candidates** — flag joint-install accounts as the proof points for co-marketing.
5. **Expansion targets** — accounts running one product but not the other are integration-expansion targets; surface both directions.
## Output Format
Markdown with:
- `# Partner Tech-Overlap — {{our_product}} x {{partner_product}}`
- `## Joint Install Base` (count + share of each base)
- `## Reference Candidates` (joint-install accounts)
- `## Expansion Targets` (run one, not the other — both directions)
- `## Citations`
## Quality Checklist
- Joint install base cites `company_technographic`
- Overlap quantified as count and share of each base
- Expansion targets surfaced in both directions
- No invented integration-adoption numbers