Partner Account Mapping
Map the overlap between your target accounts and a partner's footprint — where they already have a relationship you can co-sell into.
Partner - Account mapping
The accounts where your partner already has a foothold to co-sell into
28
Overlap accounts
9
Warm co-sell candidates
| Account | Partner footprint | Co-sell |
|---|---|---|
| Acme | AWS heavy spend | Warm + in-market |
| Beta | AWS installed | Warm |
| Gamma | No AWS | Skip |
Why it lands
Co-selling cold is hard. Of 40 target accounts, 28 already run your partner's platform and 9 of those are in-market right now — those 9 are where the joint motion starts warm, with the partner's rep already in the door.
Overview
Map the account overlap between your target list and a named partner by comparing technographic footprints and firmographic profiles — surfacing accounts where the partner already has a technical relationship (their product installed) so co-sell starts from an existing foothold.
Use cases
Co-sell where the partner's already in
The best co-sell accounts are where the partner already has a relationship. Footprint mapping finds them, so the joint motion starts from a foothold instead of cold.
Prioritize the warm overlap
Overlap plus in-market intent points the joint pipeline at the accounts where both companies have a reason to engage now.
View workflow prompt
# Partner Account Mapping
## Parameters
- `{{partner}}` *(required)* — The partner whose footprint to map. Example: `AWS`
- `{{target_accounts}}` *(required)* — Pasted target accounts (account, domain). Example: `Acme - acme.com; Beta - beta.com`
- `{{co_sell_motion}}` *(optional)* — The co-sell motion the overlap should enable. Example: `joint cloud-migration offer`
## Purpose
Map which of {{target_accounts}} already run {{partner}}'s technology — the accounts where the partner has a foothold and a {{co_sell_motion}} can start warm instead of cold.
## Process
1. **Parse targets** — read {{target_accounts}}.
2. **Detect partner footprint** — `company_technographic` (+ `company_cloud_spend` if the partner is a cloud) per domain to confirm the partner's product/platform is installed.
3. **Confirm fit** — `company_firmographic` to validate the accounts fit the {{co_sell_motion}}.
4. **In-market overlay** — `company_intent` to flag overlap accounts that are also in-market on the relevant category (the warmest co-sell candidates).
5. **Map** — accounts where you + partner both have a reason to engage, ranked by foothold strength + in-market signal.
## Output Format
Markdown with:
- `# Partner Account Map — {{partner}}`
- `## Overlap Accounts` (table: account | partner footprint | in-market | co-sell readiness)
- `## Warmest Co-Sell Candidates` (partner foothold + in-market)
- `## Citations`
## Quality Checklist
- Partner footprint cites `company_technographic`/`company_cloud_spend`
- Overlap is a confirmed installation, not an assumption
- Warmest candidates require both foothold and in-market signal
- No fabricated partner-relationship claims