What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when sales on Outreach in 2027?

The two commission-split models compared

Most organizations running a BDR-to-AE handoff choose between two structurally different ways of resolving commission on a shared deal. The first is a first-touch attribution model: whichever rep's activity created the initial engagement — the BDR who booked the meeting through an Outreach sequence, typically — receives a fixed credit percentage regardless of how much work the AE later put into the close. This model is simple to administer and easy to explain in a comp plan document, but it creates a well-known failure mode: AEs who inherit a stale or cold lead from a BDR who has since moved on, changed territories, or left the company end up doing 100% of the selling work while the BDR (or their replacement) still collects a split. It also creates gaming incentives — BDRs sequencing contacts they have no real intention of qualifying, purely to establish a timestamp claim.

The second is a stage-weighted, shared-credit model: the split is calculated based on which specific milestone each rep is responsible for, rather than who touched the record first. A BDR is credited for the qualified-meeting stage; the AE is credited for opportunity creation through close. Splits under this model are typically asymmetric and skew toward the AE (since the AE owns discovery, negotiation, and contract execution), but they are explicit about what each role is being paid for. This model requires more Salesforce configuration — you need stage-entry timestamps, not just activity timestamps — but it removes almost all of the "who gets credit" ambiguity because credit is tied to a defined job function rather than a race to first contact.

Neither model is universally correct. First-touch attribution works better for high-velocity, transactional motions where the BDR's qualification work is the primary value-add and the AE's job is closer to order-taking. Stage-weighted credit works better for complex or enterprise sales cycles where the AE materially reshapes the opportunity after handoff — different buying committee, different use case, a multi-month evaluation the BDR had no visibility into. The RevOps playbook decision is which model matches your actual sales motion, not which model is easiest to build first. Building the wrong model and patching it with manual overrides is how most organizations end up with a commission dispute backlog instead of a working playbook.

A third, less common variant worth naming is the pooled-credit model, used by teams with heavy team-selling or account-based motions: BDR and AE are paid from a shared pool tied to the account, not the individual deal, and the split is fixed by role rather than negotiated per opportunity. This removes per-deal disputes almost entirely but requires comp leadership buy-in because it changes how quota attainment is measured, not just how commission is split.

How to decide which model fits your motion

The decision tree above is a starting filter, not a final answer — most RevOps leaders validate the choice against actual historical deal data before publishing a policy. Pull the last two quarters of closed-won opportunities and manually tag which ones would have been contentious under each model. If fewer than 5% of deals would generate a dispute under first-touch attribution, it's a reasonable default and you don't need the overhead of stage-weighted tracking. If BDR-to-AE handoffs routinely involve territory changes, long dormancy periods, or re-engaged past customers, the added Salesforce configuration for stage-weighted credit pays for itself in reduced dispute volume within a quarter.

A second factor that should weigh into the decision is how your compensation plan already treats BDR quota. If BDRs are paid purely on meetings-held or opportunities-created (not on revenue), a commission split is really a bonus layered on top of their primary comp — which argues for keeping it simple with first-touch attribution, since the split isn't their main income driver. If BDRs are paid meaningfully on closed revenue, the split becomes central to their earnings and deserves the more precise, defensible stage-weighted structure, because disputes over real money move faster to HR and leadership than disputes over a secondary bonus.

Concrete numbers: what splits and grace periods actually look like

There's no universal published rate for BDR/AE commission splits, but the following ranges are common starting points that RevOps teams adjust to their own comp philosophy — treat them as configuration defaults to test against your own deal data, not as a benchmark to copy blindly.

• First-touch model splits commonly run in the 10-20% BDR / 80-90% AE range on total deal commission, reflecting that the AE carries most of the closing risk and effort even when the BDR sourced the lead.
• Stage-weighted model splits are often structured as a flat bonus per qualified meeting (independent of deal size) rather than a percentage, precisely to avoid disputes over large-deal credit — for example, a fixed dollar SPIF per accepted meeting, with the AE's commission plan unaffected by BDR credit at all.
• Pooled-credit splits are typically defined at the team or pod level — for instance, a fixed 15% of a pod's aggregate commission pool reserved for BDR compensation, distributed by manager discretion rather than per-deal formula.
• Grace periods — the window during which a BDR's prior activity still counts toward credit even if the AE has since taken over engagement — commonly range from 5 to 15 business days. Shorter windows suit fast-cycle transactional sales; longer windows suit multi-month enterprise cycles where a lull in contact activity doesn't mean the BDR's groundwork was wasted.
• Dispute resolution SLAs worth setting as internal targets: peer-level resolution within 2 business days, RevOps-level resolution within 5 business days, and executive-tier review reserved for a monthly cadence rather than ad hoc, so it doesn't become a bottleneck for commission payout timing.
• Reasonable dispute-rate expectations: teams running a documented playbook with clear Salesforce fields typically see disputes on a low single-digit percentage of closed-won deals with BDR involvement. A materially higher rate usually signals the split rules themselves are ambiguous or unpublished, not that reps are behaving badly.

These numbers exist to give you a defensible starting configuration, not a compliance requirement — the right numbers for your team come from testing a draft policy against a quarter of real deal history and adjusting the thresholds where they produce results reps agree feel fair.

Implementation and sequencing in Salesforce and Outreach

The technical sequencing matters because building the wrong pieces first creates rework. Start with data, not policy enforcement — you cannot automate a split rule you can't yet observe.

Step 1 — Instrument the activity trail. Confirm your Outreach-to-Salesforce sync is capturing sequence membership events (when a contact was added to a BDR's sequence), not just email-open or reply activity. Standard field-level syncs often miss this; you may need to enable a more granular activity sync or build a middleware step that writes sequence-membership timestamps into custom Salesforce fields on the Contact or Lead object.

Step 2 — Build the ownership fields on the Opportunity. At minimum: BDR first-touch date, BDR last-touch-before-AE date, AE first-engagement date, and a picklist or formula field that classifies the opportunity into your chosen split category (first-touch, shared, AE-only). These fields are the backbone of the playbook — every downstream report, dispute review, and commission calculation reads from them.

Step 3 — Encode the default split as a formula, not a manual entry. Whatever model you chose above, express it as a Salesforce formula field so the default split is calculated automatically at the point commission would normally be run, before any human argues about it. Manual entry fields for split percentage are where disputes hide, because two different people can populate them with two different assumptions.

Step 4 — Publish the split before close, not after. A weekly report sent to both BDRs and AEs showing the calculated split for deals approaching close-won gives reps a chance to flag disagreement while the deal is still open and memory is fresh, rather than after commission has already been calculated and someone feels shorted.

Step 5 — Wire the escalation path. Tier one is peer-to-peer: BDR and AE review the Outreach sequence timeline together and agree within a short window. Tier two is RevOps mediation against the documented decision matrix from Step 3. Tier three is a periodic (monthly, not per-incident) leadership review that also functions as a policy-tuning session — patterns of repeat disputes should change the underlying rule, not just resolve individual cases.

Step 6 — Close the loop with documentation. Every escalated decision gets logged with the reasoning, and any resulting change to the split formula gets versioned. Without this step the playbook decays back into ad hoc judgment calls within a year, because nobody remembers why an exception was granted the first time.

Related questions

How long should a BDR's sourcing credit last after handoff to an AE?

Set an explicit grace period rather than leaving it undefined — commonly 5 to 15 business days depending on cycle length. Encode it as a Salesforce formula so credit expiration is automatic, not a judgment call made after the dispute has already started.

Should BDR commission be based on meetings held or on closed revenue?

Meetings-held keeps BDR comp independent of AE execution and reduces cross-role disputes; revenue-based BDR comp increases alignment but raises the stakes of every handoff dispute. Most first-time playbooks start with meetings-held and add a smaller revenue kicker later.

What Salesforce object should own the split percentage field?

Put it on the Opportunity, not the Contact or Lead, since a single contact can be associated with multiple opportunities over time with different BDR/AE pairings. The Opportunity is the object commission is actually calculated against.

How do you handle disputes when a BDR has already left the company?

Assign their historical credit to a house or team account so the formula field still resolves correctly, and route any dispute directly to Tier 2 RevOps mediation since peer resolution isn't possible.

Does this playbook change if the team uses a different sequencing tool instead of Outreach?

The model transfers directly — the requirement is any tool that timestamps sequence membership and activity completion, synced into the same Salesforce Opportunity fields. The specific vendor is an implementation detail, not a change to the underlying split logic.

FAQ

What is the first step when a commission dispute arises between a BDR and an AE? Pull the Outreach sequence timeline and the corresponding Salesforce activity history for the opportunity before anyone discusses percentages. Most disputes are actually disagreements about facts, not disagreements about the split policy, and the data trail resolves them faster than a conversation does.

Who should own the commission-split playbook inside RevOps? One named RevOps owner, not a committee, should own the formula fields, the escalation calendar, and the documentation log. Shared ownership is how split rules quietly drift out of sync with what the comp plan document says.

Can the split model change mid-quarter if it's producing too many disputes? Yes, but changes should apply to deals opened after the change date, not retroactively to opportunities already in flight — retroactive changes to an in-progress deal are themselves a common source of a new dispute.

What happens if BDR and AE activity both show up in Outreach for the same contact within days of each other? This is the core case for a shared-credit or 50/50 default rather than a winner-take-all rule. Trying to force a single-owner outcome on genuinely overlapping activity produces the most contentious disputes of any scenario.

How often should the split policy itself be reviewed? Monthly at the leadership-review tier is sufficient for most teams — frequent enough to catch a pattern of repeat disputes, infrequent enough that reps aren't chasing a moving target quarter to quarter.

Does a stage-weighted split model require different Salesforce permissions than a simple first-touch model? Not permissions, but it does require more fields and typically at least one additional validation rule to prevent a stage-entry timestamp from being backdated, since that timestamp becomes financially meaningful in a way it wasn't before.

Sources

• https://help.salesforce.com
• https://support.outreach.io
• https://www.gartner.com
• https://hbr.org
• https://www.saastr.com
• https://www.forrester.com
• https://www.thebridgegroup.com

Related on PULSE

• How do you structure BDR compensation when meetings held don't convert to pipeline?
• What Salesforce fields should track AE ramp time after a BDR handoff?
• How do you set SLAs for BDR-to-AE lead handoff response time?
• What's the right escalation path for territory disputes between AEs?
• How do you audit Outreach sequence data for commission accuracy?