What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when no dedicated RevOps hire yet ?
What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when no dedicated RevOps hire yet (batch 1 #236) is a gap most SaaS vendors gloss over — here is the operator-level answer.
Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.
Why this is under-answered online
Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.
What good looks like
- Definition of done tied to revenue or data quality, not activity counts.
- Documented rollback and a named DRI.
- No shadow spreadsheets for metrics leadership reviews.
Related on PULSE
- [What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when no dedicated RevOps hire yet ?](/knowledge/q10394)
- [What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when parent-company rollup reporting ?](/knowledge/q10314)
- [What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when sales on Outreach ?](/knowledge/q10234)
- [What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when parent-company rollup reporting ?](/knowledge/q10074)
- [What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when sales on Outreach ?](/knowledge/q9994)
- [How do you audit colo and hyperscaler partner-sourced pipeline opportunity hygiene in Salesforce during BDR-to-AE split to prevent commission disputes on split credit when SDRs on Outreach?](/knowledge/q10771)
The Zero-RevOps Audit: Mapping Your Current Commission Flow in Under 48 Hours
When you don't have a dedicated RevOps hire, the first step isn't building a perfect system—it's understanding exactly where your commission disputes are born. Here's a practical, self-service audit you can run using only Salesforce and a shared spreadsheet.
Step 1: Pull the last 90 days of closed-won opportunities where BDR touched the deal. Create a Salesforce report with fields: Opportunity Name, Close Date, Amount, BDR Owner, AE Owner, Created Date, Stage History (specifically when it moved to "Qualified" or "Discovery"), and any custom commission split fields you already have. Export to CSV.
Step 2: Flag every deal where the BDR-to-AE handoff date is unclear or disputed. In a new column, manually calculate the time between the BDR's first meaningful activity (call, email, or meeting logged) and the AE's first activity. A reasonable handoff window is 24-72 hours. Anything outside that range is a dispute risk.
Step 3: Identify your top 3 dispute patterns. Common patterns in organizations without RevOps include:
- Double-dipping disputes: Both BDR and AE claim credit for the same sourced lead because the lead was re-assigned or re-entered through a different channel.
- Time-based disputes: The BDR worked a lead for weeks, then the AE re-assigned it to another BDR or claimed the lead was "cold" after a period of inactivity.
- Split percentage confusion: The BDR believes they should get 30% of commission, but the AE or comp plan says 20%, and there's no documented agreement.
Step 4: Document your current state in a single Google Sheet. Create columns for: Deal Name, Amount, BDR, AE, Handoff Date, Dispute Type, Current Resolution (if any), and Estimated Financial Impact. This becomes your baseline data for the design phase.
The goal of this audit is not perfection—it's visibility. Most disputes arise from ambiguity in handoff timing or credit assignment. By mapping your actual flow, you'll see the 2-3 root causes responsible for 80% of your disputes. This audit should take one person no more than 4-6 hours of focused work across two days.
Building the Commission Dispute Prevention Framework in Salesforce (No Code Required)
Once you've completed your audit, you need a lightweight, repeatable system that prevents disputes before they happen. Without a RevOps hire, you'll rely on Salesforce automation features that don't require coding—Process Builder, Flow, and validation rules.
Field Architecture (5 fields max)
Create these custom fields on the Opportunity object:
- BDR Handoff Date (Date field) – The date the BDR officially passed the lead to the AE. This should be populated by the BDR when they move the opportunity to a specific "BDR Qualified" stage.
- AE Acceptance Date (Date field) – The date the AE accepted the handoff. Populated by the AE when they first log an activity on the opportunity after handoff.
- Handoff Status (Picklist: Pending, Accepted, Disputed, Resolved) – Tracks the current state of the handoff agreement.
- Commission Split % (Formula field, number) – Calculates the BDR's percentage based on time-to-acceptance. Example: If AE accepts within 24 hours, BDR gets 30%. If 24-72 hours, 25%. If over 72 hours, 20%.
- Dispute Reason (Long Text Area) – Captured only when Handoff Status = "Disputed."
Automation Rules (Build in Salesforce Flow)
Create two flows:
*Flow 1: Handoff Timer*
- Trigger: When Opportunity Stage changes to "BDR Qualified"
- Action: Set BDR Handoff Date = Today()
- Action: Send email notification to AE with link to opportunity and message: "BDR handoff initiated. Please accept within 72 hours to maintain standard split."
*Flow 2: Acceptance Window Monitor*
- Trigger: When AE Acceptance Date is populated
- Action: Calculate hours between BDR Handoff Date and AE Acceptance Date
- Action: Update Commission Split % based on the time window
- Action: If >72 hours, set Handoff Status = "Disputed" and send alert to both BDR and AE manager
Validation Rules (Prevent Bad Data)
Add a validation rule on Opportunity that prevents closing the deal if Handoff Status is "Pending" or "Disputed." The error message should read: "Cannot close opportunity until BDR handoff is resolved. Contact your manager to update Handoff Status."
Reporting for Dispute Resolution
Create a dashboard with three components:
- Dispute Aging Report – List of all opportunities where Handoff Status = "Disputed," sorted by days since dispute opened. This gives you a clear queue.
- Commission Split Distribution – Bar chart showing how many deals fell into each split percentage bucket (30%, 25%, 20%). If you see a spike in the 20% bucket, your AEs may be intentionally delaying acceptance.
- BDR/AE Handoff Compliance – Table showing each BDR's average time to handoff acceptance and each AE's average acceptance time. This identifies who's consistently causing delays.
This entire framework can be built in a single afternoon by someone comfortable with Salesforce setup. No developer needed. The key is enforcing the handoff process through automation rather than manual tracking—because without RevOps, you can't afford to chase people for data.
The 30-Day Pilot: Testing Your Commission Resolution Process Without Breaking Live Deals
You can't roll out a new commission dispute process across your entire organization overnight—especially without a RevOps team to manage the change. Instead, run a controlled 30-day pilot with one BDR and one AE who have a history of disputes. This gives you real data without risking your entire comp cycle.
Selecting Your Pilot Participants
Choose a BDR-AE pair that meets these criteria:
- They've had at least 2 documented disputes in the last 90 days
- They're willing to participate (get verbal buy-in from their managers)
- They represent a typical deal size for your organization (not your biggest or smallest accounts)
Pilot Process (Days 1-30)
*Week 1: Setup and Training*
- Install the field architecture and flows described above in a Salesforce sandbox or a dedicated pilot record type
- Hold a 30-minute session with the BDR and AE explaining: the new handoff fields, the acceptance timer, and the dispute resolution flow
- Define the escalation path: If a dispute arises, they first try to resolve it themselves using the Dispute Reason field. If unresolved in 48 hours, it escalates to their respective managers. If still unresolved after 7 days, it goes to the CFO or CEO (since you have no RevOps).
*Weeks 2-3: Live Monitoring*
- Every Monday, run the dispute report and review with the BDR and AE in a 15-minute standup
- Track: Number of handoffs, average acceptance time, any disputes triggered, and time to resolution
- Document any confusion or friction points (e.g., "The BDR doesn't know when to set Handoff Date" or "The AE keeps forgetting to log their first activity")
*Week 4: Retrospective and Adjustment*
- Compare dispute frequency during the pilot vs. the previous 30 days for this pair
- Interview both participants: What worked? What was confusing? What would make them use the system voluntarily?
- Adjust the process based on feedback. Common adjustments include: simplifying field names, adding in-app guidance, or changing the dispute escalation timeline
Measuring Pilot Success
Define success as:
- 50% reduction in disputes for the pilot pair (from baseline)
- 100% of handoffs have Handoff Status updated within 72 hours
- Both participants rate the process 4/5 or higher on ease of use
Rollout Decision Point
After 30 days, you have three options:
- Full rollout (if pilot shows clear improvement and high satisfaction) – Expand to all BDR-AE pairs, schedule training sessions, and make the validation rule active.
- Refined pilot (if there are minor issues) – Fix the top 2-3 friction points and run another 2-week pilot with the same pair.
- Pivot (if the process fundamentally doesn't work) – Go back to your audit data and identify a different root cause. Perhaps the issue isn't handoff timing but credit assignment for multi-touch leads.
Without a dedicated RevOps hire, your biggest risk is overcomplicating the process. Keep it simple: one handoff date, one acceptance date, one split formula, one escalation path. The pilot proves the concept works before you invest time in building dashboards or training materials for the whole team. If the pilot fails, you've learned cheaply what doesn't work—and you can pivot before the next commission cycle starts.
Sources
- Salesforce Help & Training — official documentation on Salesforce objects, permissions, and automation for managing commission splits and user roles.
- Harvard Business Review — articles on sales compensation design, territory alignment, and revenue operations best practices.
- Gartner — research reports on revenue operations frameworks, commission dispute resolution, and sales process governance.
- The RevOps Collective (community) — practitioner guides and templates for building RevOps processes without a dedicated hire.
- LinkedIn Learning — courses on Salesforce administration, sales compensation management, and RevOps fundamentals.
- SaaStr — case studies and playbooks on scaling revenue operations and handling BDR-to-AE transitions in SaaS companies.
FAQ
What is the first step when a commission dispute arises between a BDR and AE? The first step is to audit the Salesforce opportunity history and the associated lead/contact source. Check the "Campaign Source" or "Lead Source" field on the opportunity, and verify the BDR’s activity (tasks, calls, emails) logged before the AE’s first touch. This audit reveals whether the dispute is about attribution timing or a missing field value, not about who worked harder.
Who should own the commission dispute resolution process when there is no RevOps hire? The Sales Operations manager or the most senior sales leader (e.g., VP of Sales) should temporarily own the process. They need to define a simple, written escalation path: BDR and AE first try to resolve directly, then escalate to the ops lead with a shared report showing the disputed opportunity’s source and activity timeline. This prevents endless back-and-forth.
What Salesforce fields are essential to prevent future disputes? You need at least three proof fields on the Opportunity object: "BDR Assigned," "First Touch Date," and "Attribution Model" (e.g., first-touch, last-touch, or split). Also add a "Dispute Status" picklist (Open, Resolved, Escalated). These fields let you run a simple report to see which opportunities have missing or conflicting data before a dispute arises.
How do you handle a dispute where the BDR claims credit for an opportunity the AE sourced independently? Pull the opportunity’s "Activity History" report in Salesforce for the 30 days before the opportunity was created. If the BDR has no logged calls, emails, or meetings, the credit goes to the AE. If there is logged activity, apply a 50/50 split for that deal and flag the BDR’s source field for review. This is a fair, data-driven rule that both roles can agree on upfront.
What is a simple pilot to test a commission dispute resolution process? Pilot with one sales segment (e.g., your top 10 BDR-AE pairs) for 30 days. Define the three proof fields, have each pair log disputes in a shared Google Sheet with the opportunity ID and their proposed split, and review weekly. Measure the number of disputes resolved within 48 hours. If you hit 80% resolution in that window, the process is ready to automate.
How do you automate dispute resolution after the pilot? Use Salesforce Flow to auto-calculate the commission split based on the "Attribution Model" field. For example, if the field says "50/50," the flow updates a "Commission Split" field on the opportunity and triggers an email to both reps and the ops lead. Then run a weekly "Pulse Report" showing all opportunities with a split, any unresolved disputes, and the average time to resolution. This replaces manual spreadsheets.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.