Verified against ChatGPT · 2026-08-13
Design channel strategy rules that prevent partner and direct sales from fighting over the same deal
Drafts concrete channel conflict rules — deal registration, territory boundaries, and margin-sharing logic — targeted at the specific overlap causing friction, instead of a generic partner policy template.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Design channel conflict rules to stop direct sales and channel partners from fighting over the same deals — targeted at the specific overlap causing friction in our business, not a generic partner policy template copied from somewhere else. WHERE THE CONFLICT IS ACTUALLY HAPPENING Direct reps are cold-calling into accounts a partner already has an active relationship with, and neither side finds out until late in the deal. CURRENT DEAL REGISTRATION PROCESS, IF ANY Partners can register a deal in the portal, but direct reps don't check it before prospecting, so overlaps aren't caught until a partner complains. TERRITORY OR SEGMENT DEFINITIONS TODAY Direct sales owns accounts over 500 employees; partners own everything else, but the threshold isn't enforced anywhere systematically. WHAT'S POLITICALLY HARD TO CHANGE Direct sales leadership won't accept losing any named enterprise accounts to partners, full stop. WHAT NOT TO DO Do not propose a full territory re-carve if the political constraints say that's off the table — work within the stated constraints rather than recommending the ideal-world answer and ignoring what you were told isn't feasible right now. Do not propose deal registration rules so loose that both sides can plausibly claim the same deal was registered first — a rule that doesn't actually resolve the ambiguity it's meant to resolve isn't a real rule, just a paperwork step. Do not recommend a margin-sharing formula without stating the specific scenario it's meant to handle — a formula floating with no worked example is unverifiable and partners will each interpret it differently. BUILD THE RULES For the specific conflict pattern described, propose a deal registration rule with a clear, checkable tiebreaker for the exact ambiguity that's currently causing disputes — not a generic 'first to register wins' rule if that's not actually what's causing the friction. Propose territory or segment boundary clarifications only where the current definition is genuinely ambiguous, not a full redesign. Provide one worked numerical example of how the margin-sharing or credit-splitting rule would apply to a real deal size, so it's testable rather than abstract. OUTPUT FORMAT 1. The specific rule addressing the described conflict pattern, stated as a checkable procedure. 2. Any territory/segment clarification, scoped only to the actual ambiguity. 3. One worked numerical example of the credit or margin-sharing outcome. 4. One likely edge case this rule set still won't cleanly resolve, named honestly rather than glossed over.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Constraining the model to work within stated political limits rather than proposing an ideal-world redesign addresses a common gap between what a model generates and what an organization can actually implement: asked open-endedly to 'fix channel conflict,' a model will often produce the theoretically cleanest answer (a full territory re-carve), but that answer is worthless if leadership has already ruled it out, and presenting it anyway wastes the reader's evaluation time on something dead on arrival — explicitly anchoring to the stated constraint forces a genuinely usable answer instead of a textbook one. The instruction against a registration rule loose enough for both sides to plausibly claim priority targets a specific, real weakness in how these rules get drafted: a rule like 'first to register wins' sounds decisive but is only as good as the tiebreaker for what counts as 'first' and what happens when both sides say they were first — a model asked to write a rule will often produce the surface-level version without the tiebreaker mechanics that make it actually enforceable, so the prompt forces the harder, more specific version. Requiring a worked numerical example for any margin-sharing formula matters because an abstract formula ('partners receive X% based on deal influence') is exactly the kind of language that different parties will each interpret in their own favor during an actual dispute — a concrete example applied to a real deal size exposes ambiguity in the formula before it becomes a live conflict, which is the whole point of designing the rule in the first place. Requiring one honestly-named edge case the rules still won't resolve prevents the output from reading as a complete solution when channel conflict is rarely fully solvable with policy alone — overstating completeness here just relocates the next dispute to a place nobody prepared for it.
What you get back
Rule: a partner-registered deal is protected only if registered before any direct rep has logged a first outbound touch to that account in the CRM, verified by timestamp, not by either side's recollection. Worked example: on a $120K deal where the partner sourced and ran the full sales cycle, the partner retains 100% margin credit; if direct sales assisted post-registration (e.g., an executive intro), a 15% credit split applies, worked out to $18K attributed to direct on that deal size. Edge case not cleanly resolved: a prospect who independently contacts direct sales after already being in a partner's registered pipeline, with no timestamp trail proving prior partner contact — this will still require manual adjudication.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
