The BDR/AE split problem isn't a policy problem. It's a data problem.

Most teams with a BDR-sources, AE-closes motion have already had the argument that actually matters: what percentage does each side get. Fixed 70/30, proportional to effort, primary-vs-assist — split-commission structures are a solved, well-documented question. Pick one, write it down, move on. That’s not where these plans actually break.

Where they break is a month later, when someone has to figure out which BDR gets credit for which deal — and the CRM doesn’t actually know.

The policy was never the hard part

The three shapes split credit usually takes are simple enough to settle in one meeting: a flat percentage split (AE gets 70%, the sourcing BDR gets 30%, every time), a proportional split scaled to perceived contribution, or primary/assist credit where one rep is clearly first-chair. None of these require software. They require a decision, and most teams have already made one.

What they haven’t solved is the thing the policy assumes exists: a reliable, per-deal record of who actually sourced it.

Your CRM has one deal-owner field, and it’s never the BDR

Here’s the part that doesn’t show up in the split-policy conversation. HubSpot — like most CRMs — has exactly one native “deal owner” field, and by the time a deal is worth looking at, that field almost always holds the AE’s name. They’re the one working it, updating it, closing it. The BDR who booked the meeting that created the deal in the first place usually isn’t captured anywhere the CRM considers authoritative. Pull a report by deal owner and the BDR’s contribution is already gone, structurally, before anyone argues about the split percentage.

The fix most orgs land on isn’t a CRM feature, it’s a workaround: a custom property someone adds to track who actually sourced the deal, independent of who’s driving it now. Real language from a HubSpot admin setup, not paraphrased: “Most orgs don’t make the BDR the deal owner — pick the custom HubSpot field that identifies who sourced the deal.” That sentence is doing a lot of work. It’s an admission that the platform’s default data model doesn’t match how collaborative sales motions actually work, and every team running one has to patch around it themselves.

What the patch usually looks like, and what it costs

In practice, the patch is a person: someone cross-references a HubSpot export against a list of who booked what, by hand, once a month, and updates a spreadsheet before commission runs. It works until it doesn’t — a BDR leaves and their deals get silently reassigned, a stage gets skipped, someone forgets an edge case from three weeks ago. None of that is a policy failure. It’s a manual-reconciliation failure wearing a policy costume.

This isn’t a hypothetical productivity tax, either. Gartner surveyed 1,026 B2B sellers in early 2024 and found 50% feel overwhelmed by the amount of technology their job requires— and overwhelmed sellers are 45% less likely to attain quota. A manual bridge between your CRM and your comp tracker is exactly the kind of tool-sprawl tax that stat is measuring: one more system a human has to hold together by hand, every cycle, for as long as the motion exists.

Sourcing credit isn’t enough on its own

Even with a clean “who sourced this” field, one more gap remains: sourcing a deal and the deal actually counting toward commission aren’t the same event. A BDR can source a deal that stalls at the first call, or one that closes six months later after changing shape twice. The comp plan needs a real answer to which stage makes a sourced deal commissionable — a completed meeting, a qualified opportunity, whatever the plan actually says — not just a source field with no stage logic attached. The AE side of this is simpler by comparison: closed-won is closed-won, a fixed target every CRM already models natively. The BDR side needs the same stage-awareness the AE side gets for free, and most off-the-shelf integrations don’t build for it because most deals don’t need it.

What we built because this doesn’t exist off the shelf

This is the actual shape of Gordon’s HubSpot integration: connect once, and closed-won deals sync in on their own. For the AE side, that’s a straightforward owner-to-rep mapping. For the BDR side, it’s the field-mapping workaround made structural instead of manual — pick the custom property that identifies who sourced a deal, then, role by role, pick the exact pipeline stages that make a sourced deal commissionable. One HubSpot deal can credit an AE and a BDR independently, correctly, every sync, with nobody exporting a spreadsheet to make it true.

If your team’s already agreed on the split and is still doing the reconciliation by hand, it’s free to start— no sales call required.