How Do You Write Rules of Engagement Between SDRs and AEs?

How do you write rules of engagement between SDRs and AEs?

Write down who owns each account and lead, when ownership transfers, what counts as a qualified handoff, and how credit is shared, then encode those rules in your CRM so they enforce themselves. Keep the document to one page. Rules that need a meeting to interpret will cause the conflicts they were meant to prevent.

Rules of engagement are the agreements that decide who works which accounts, who gets credit, and what happens when two reps want the same deal. Small teams often skip them because everyone gets along. Then the team grows from two sellers to five, an SDR books a meeting with an account an AE thought was theirs, and a friendly team turns tense overnight.

This article covers what to put in rules of engagement, how to make them enforceable in a CRM, and how to handle the edge cases that cause most disputes.

Why do SDR and AE teams need written rules?

Because unwritten rules are interpreted differently by everyone. Ownership disputes, credit fights, and dropped handoffs almost always trace back to an assumption one person made and another did not share. Writing the rules down turns those assumptions into a shared agreement that can be checked.

The cost of no rules is not just conflict. It is lost pipeline. When two reps are unsure who owns an account, sometimes both reach out and confuse the buyer. More often, neither does, because each assumes the other has it. Either outcome hurts the company more than it hurts the reps.

Written rules also make the system fair to new hires. A new SDR joining a team with unwritten norms has to learn them by making mistakes. A one-page document lets them start working accounts on day one without stepping on anyone.

What should the rules say about account ownership?

Define how accounts are assigned, how long an owner keeps an account without activity, and what happens when an account goes untouched. Ownership should be based on clear criteria like territory, segment, or a named account list, and it should expire if the owner does not work it.

The expiry rule is the most important and the most often missing. Without it, reps claim accounts and sit on them. A simple rule, such as ownership lapses after a set number of days with no logged activity, keeps accounts moving. The exact window depends on your sales cycle, but it should exist and be written down.

Named accounts deserve special treatment. If AEs hold a strategic account list, SDRs need to know whether they can prospect into those accounts and how. A common approach is that SDRs can work named accounts only with the AE's agreement, and any meeting booked goes straight to that AE. I covered how to split territory itself in how to split territories between two account executives.

When should a lead move from SDR to AE?

A lead moves when it meets an agreed qualification bar, usually a confirmed problem, a relevant buyer, and agreement to a next meeting. Write the bar in concrete terms. If the AE has to guess whether a handoff is real, the bar is too vague, and handoffs will be disputed.

The qualification bar should be something both sides helped write. If SDRs set it alone, AEs may reject handoffs they see as weak. If AEs set it alone, the bar may be so high that SDRs cannot hit it. A short working session to agree on criteria pays off quickly.

The handoff itself should carry context. Who the buyer is, what problem they described, what they were told, and what the next meeting is for. A written handoff note in the CRM, attached to the deal, means the AE walks into the first call prepared. I wrote a practical version in write a lead handoff checklist for SDRs and AEs.

How should credit be shared?

Decide in advance what the SDR gets credit for and what the AE gets credit for, and tie each to a measurable event in the CRM. Typically, SDRs are credited for qualified meetings held or opportunities created, and AEs for closed revenue. Write it down so nobody has to argue after the fact.

Credit fights usually happen on the edges. An inbound lead that an SDR qualified. An expansion deal at an existing customer. A meeting booked by an SDR at an account an AE was already working. Each of these needs a rule, and the rule should be decided when nobody has a deal at stake.

Simpler is better. Complex credit-splitting formulas create spreadsheets, disputes, and distrust. A clear rule that occasionally feels slightly unfair is usually better than a precise rule nobody understands. Revisit the rules each quarter if they create consistent friction.

How do you handle the common edge cases?

List the situations that cause most disputes and decide each one in writing: two reps contacting the same account, an inbound lead at an owned account, a contact who changes companies, and a lost deal that comes back. A rule for each of these prevents most conflicts before they start.

Duplicate outreach is the most common. The rule I recommend is that the account owner wins, and the other rep's activity is logged and handed over. If there is no owner, the first rep with logged activity takes ownership. Both rules are simple to check in the CRM.

Job changes and returning deals are trickier. When a champion moves to a new company, the rep who had the relationship often wants to follow them. Decide whether relationships travel with the rep or with the territory, and write it down. Same for closed-lost deals that revive months later: decide whether they return to the original owner or go back into the pool.

How do you make the rules enforceable in the CRM?

Turn each rule into a field, a workflow, or a report. Ownership lives in the account owner field. Expiry runs as a scheduled workflow that flags or reassigns stale accounts. Handoffs use a required field set when a deal is created. When the CRM enforces the rules, nobody has to police them.

In HubSpot or Salesforce, a few automations cover most of this. A workflow that alerts or reassigns when an owned account has no activity for the agreed window. A required handoff note field on new opportunities. A report that shows SDR-created opportunities by AE, so credit is visible and uncontested.

Duplicate checks help too. Before an SDR adds a new contact or account, a match against existing records shows whether the account already has an owner. Tools like Clay or the CRM's own duplicate management can flag conflicts before outreach goes out, which is far better than sorting them out after.

Who should own the rules of engagement?

The sales leader should own the document, with input from both SDRs and AEs, and the RevOps or operations person should own how the CRM enforces it. Disputes should go to one named person whose decision is final. Without a clear tiebreaker, small disputes turn into ongoing resentment.

On very small teams, the founder often plays all of these roles. That is fine, as long as the rules are still written down. It is easy for a founder to remember every exception in their head. It is impossible for a new hire to guess them.

Review the rules on a schedule, ideally each quarter. Look at which disputes came up, which rules were unclear, and whether any rule is slowing the team down. Small adjustments keep the rules useful as the team and the market change. The ownership question at a structural level is covered in should marketing or sales own the SDR team.

What mistakes make rules of engagement fail?

The common failures are rules that are too long, rules that the CRM does not enforce, rules that nobody reviews, and rules that the leader ignores when a big deal is at stake. The last one is the most damaging. One visible exception tells the whole team the rules are optional.

Length is a quiet killer. A ten-page rules document will not be read. A one-page document with clear headings for ownership, handoff, credit, and edge cases will be. If a rule needs a paragraph of explanation, it probably needs to be simpler.

Consistency matters more than perfection. A rule applied consistently, even if it occasionally produces an odd result, builds trust. A rule bent for the top performer destroys it. If a rule produces bad outcomes repeatedly, change it openly at the next review rather than making quiet exceptions.

What should you do next?

Write a one-page draft covering ownership, expiry, handoff criteria, credit, and the four most common edge cases. Review it with your SDRs and AEs together, agree on a tiebreaker, and then encode the ownership and handoff rules in your CRM before the next hire starts.

Start with the rules that cause the most friction today. You do not need every edge case solved on day one. You need the team to know where the rules live and who decides when something is unclear.

I design GTM systems for B2B teams, including the CRM rules that keep sales handoffs clean. If your team is arguing about ownership more than selling, reach out and let's chat.