Whitespace in Pipeline
Find the products and divisions your open accounts could buy but aren't in any deal — cross-sell whitespace hiding inside live pipeline.
RevOps - Whitespace
The cross-sell hiding inside accounts you already have a deal in
23
Whitespace products
Inside live pipeline
Accounts buying Observability whose
stack implies Security + Log Mgmt too.
Accounts buying Observability whose
stack implies Security + Log Mgmt too.
| Account | In deal | Whitespace |
|---|---|---|
| Acme | Observability | Security Analytics |
| Beta | APM | Log Management |
| Gamma | Observability | 2 subsidiaries |
Why it lands
The rep is closing an Observability deal at Acme. Acme's stack — and their current intent — say they need Security Analytics too. That cross-sell is sitting inside a deal the rep is already in.
Overview
For a pasted set of accounts with open deals, map the cross-sell and division whitespace using HG technographic and firmographic data — surfacing adjacent products the account's stack implies they need and subsidiaries not yet in any deal.
Use cases
Expand the deal you're already winning
The easiest cross-sell is into an account that's already buying. This finds the adjacent products their stack implies — before the first deal closes and the momentum fades.
Surface the subsidiaries nobody's working
A deal at the parent company often ignores three buying divisions. Firmographic family mapping puts those subsidiaries on the rep's radar as whitespace.
View workflow prompt
# Whitespace in Pipeline
## Parameters
- `{{accounts}}` *(required)* — Pasted accounts with current deal product (account, domain, product in deal). Example: `Acme - acme.com - buying: Observability`
- `{{product_catalog}}` *(required)* — Your products available to cross-sell. Example: `Observability, Log Management, Security Analytics, APM`
## Purpose
For accounts in {{accounts}} that already have an open deal, find the cross-sell whitespace from {{product_catalog}} that the account's installed stack and firmographics imply — plus subsidiaries not yet in any deal — so the rep expands the deal instead of leaving the rest on the table.
## Process
1. **Parse** — read {{accounts}} with the product currently in each deal.
2. **Stack gap analysis** — `company_technographic` per domain to see the installed stack; map which {{product_catalog}} items the stack implies a need for but the account hasn't bought from you.
3. **Intent corroboration** — `company_intent` to confirm the account is researching the adjacent category (validates the cross-sell timing).
4. **Subsidiary whitespace** — `company_firmographic` for the corporate family; flag subsidiaries/divisions not present in the pasted deal list.
5. **Prioritize** — rank whitespace by stack-fit × intent so the rep knows which cross-sell to lead with.
## Output Format
Markdown with:
- `# Whitespace in Pipeline`
- `## Cross-Sell Whitespace` (table: account | in-deal product | whitespace product | stack rationale | intent)
- `## Subsidiary Whitespace` (divisions not yet in any deal)
- `## Lead-With` (the single best cross-sell per account)
- `## Citations`
## Quality Checklist
- Every cross-sell rationale cites the installed stack via `company_technographic`
- Cross-sell timing cites `company_intent`
- Subsidiary mapping cites `company_firmographic` and handles the corporate family correctly
- Whitespace is genuinely absent from the account's current deal, not a re-pitch