How to split SDR and AE credit on a facility-expansion sourced deal

Exterior of a large modern distribution center with multiple loading dock doors.

Most comp plans were written for a world where "sourced" means an SDR booked the first meeting off a cold call or an inbound demo request. Facility-expansion signals don't fit that mold cleanly, and that's exactly where the credit arguments start.

Here's the typical scenario: an SDR notices a target account is building out a new DC or adding a line to an existing plant, works that into an outreach sequence, and books a meeting. Three months later it's a $400K deal and both the SDR and the AE think they "found" it. The SDR found the trigger. The AE found the budget, the champion, and the actual buying process. Who gets sourced credit, and does the other person get anything at all?

Why facility-expansion deals break the standard sourced/worked split

Most comp plans define two buckets. A deal is "sourced" by whoever generated the first qualified meeting, and "sourced-and-worked" or "self-sourced" applies when one rep did both the prospecting and the closing. That binary assumes the originating activity is a logged, timestamped action: a dial, an email reply, a form submission in the CRM.

A facility signal is an observation. The SDR saw a planning filing, a job posting for a new plant, a LinkedIn post about groundbreaking, or a satellite image someone forwarded in Slack, and none of that carries a native timestamp in Salesforce the way a logged call does. So when the deal closes and RevOps pulls the sourced-deal report, there's nothing tying the SDR's observation to a date. It's the SDR's word against the activity log, and activity logs almost always favor the AE, because the AE's calls and emails are the only things that got logged.

This is the root cause of most SDR/AE credit disputes on these deals: the trigger event, the thing that made this account worth touching now instead of six months ago, was never captured as a dated record in the first place, and the gap gets mistaken for someone stretching the truth.

A credit framework that works when the trigger is a capex signal

Three things make this fixable without rewriting the whole comp plan:

Define the trigger as a dated event, not a conversation. If your comp plan already gives sourced credit to "first logged touch tied to a qualifying signal," extend that definition to include expansion signals the SDR flagged, provided the flag itself gets logged with a date and a source. A Slack message doesn't count. A CRM note or task created the day the SDR spotted the signal does.

Split, don't award winner-take-all. The cleanest plans split sourced credit (commonly in the 20-30% range) to the SDR for surfacing the account and the signal, and full closed-won credit to the AE for running the deal. This mirrors how most orgs already handle inbound-to-AE handoffs. The dispute usually centers on whether the SDR's claim of "I saw it first" can be verified; splitting credit itself is rarely contested.

Put the verification outside the rep's own activity log. If the only proof an SDR has that they spotted an expansion signal is their own memory or a screenshot they took three months ago, every dispute turns into a credibility contest. A third-party, dated record of when a given site first showed new construction removes that argument entirely. If the SDR's CRM note says "flagged capex signal, new building started at Plant 4" and the date on that note predates the actual groundbreaking announcement by weeks, the sourced credit isn't in dispute anymore.

The source of truth question

RevOps leaders who've been through this a few times stop treating "who gets credit" as a people problem and start treating it as a data problem. The fix is a dated, external record of when the facility signal first appeared, independent of either rep's say-so. A monthly feed of dated expansion events tied to a specific site gives you exactly that: a timestamp that existed before your SDR ever touched the account, which is the only thing that actually settles a sourced-credit argument.

If your comp plan still runs on logged activity as the only proof of who sourced what, it's worth building in a way to credit the rep who caught the signal first, before the deal closes and the argument starts.

Start a pilot

← Back to the blog