Partner Competitive Overlap
Check whether a prospective partner also sells your competitor — the channel-conflict risk that sinks alliances, surfaced before you sign.
Partner - Conflict check
Does the prospective partner also sell your competitor? Find out before you sign
1
Conflict assessment
Eyes open before signing
Partner shows Datadog in their
served base. Soft conflict - add guardrails.
Partner shows Datadog in their
served base. Soft conflict - add guardrails.
| Check | Finding |
|---|---|
| Competitor signals | Datadog present |
| Severity | Soft conflict |
| Verdict | Proceed w/ guardrails |
Why it lands
Discovering your new partner is also a Datadog reseller after launch is how alliances die. Checking their competitive overlap first lets you either walk away or sign with deal-registration guardrails that manage the conflict.
Overview
Assess a prospective partner's competitive overlap by examining whether their served-account footprint includes your competitors' products (a sign they also sell the competition) — so the channel team enters a partnership knowing the conflict risk, not discovering it after launch.
Use cases
Avoid the conflict that sinks alliances
A partner who also sells your competitor will route deals to whoever pays more. Knowing this before signing lets you structure the partnership — or pass.
Sign with guardrails, not blind faith
Soft conflicts are manageable with the right clauses. Surfacing the overlap early means the partnership agreement addresses it from day one.
View workflow prompt
# Partner Competitive Overlap
## Parameters
- `{{partner}}` *(required)* — The prospective partner to assess. Example: `SI Firm A`
- `{{competitors}}` *(required)* — Your competitors whose presence signals conflict. Example: `Datadog, New Relic`
- `{{category}}` *(required)* — Your category. Example: `observability`
## Purpose
Assess whether prospective partner {{partner}} also works with {{competitors}} in the {{category}} — the channel-conflict risk that derails alliances — so the channel team signs (or structures) the partnership with eyes open.
## Process
1. **Profile the partner** — `company_research` (+ `company_technographic`) to understand {{partner}}'s practice areas and the products they implement/resell.
2. **Competitor signals** — look for evidence the partner works with {{competitors}}: competitor tech in their served-account patterns, public partnership/certification signals (fall back to web search if HG signals are thin).
3. **Assess conflict severity** — none (clean), soft (works with competitors but not deeply), or hard (a primary competitor partner).
4. **Structure recommendation** — if overlap exists, recommend how to structure the partnership (exclusivity clauses, deal-registration rules) to manage it.
5. **Honest verdict** — proceed / proceed-with-guardrails / reconsider.
## Output Format
Markdown with:
- `# Partner Competitive Overlap — {{partner}}`
- `## Partner Profile` (practice areas, cited)
- `## Competitor Signals` (evidence of competitor relationships)
- `## Conflict Severity` (none / soft / hard)
- `## Structure Recommendation` (guardrails if needed)
- `## Verdict`
- `## Citations`
## Quality Checklist
- Competitor-relationship signals are cited (HG or web), not assumed
- Conflict severity is graded honestly
- Structure recommendation is specific (clauses, rules)
- Where evidence is thin, that uncertainty is stated, not glossed