Sales Accepted Opportunity

A sales accepted opportunity (SAO) is a meeting or lead that a quota-carrying rep has reviewed and formally agreed to work as a real deal. It is the receipt in the SDR-to-AE handoff: the SDR books the meeting, the AE shows up, verifies it against agreed qualification criteria, and either accepts it into pipeline or rejects it with a reason code. Until that acceptance happens, the meeting is marketing's claim, not sales' pipeline.

How Sales Accepted Opportunity Is Calculated

The SAO rate measures how much of what gets handed over actually survives inspection:

SAO Rate = Opportunities accepted by sales ÷ Meetings or SQLs handed over × 100

Acceptance criteria are defined in the SDR-AE service-level agreement and usually require four things: the account fits ICP, a real pain or initiative surfaced on the call, a next step is scheduled, and the contact has some proximity to the buying decision. Acceptance must happen within a set window — typically 5-7 days or after the first meeting occurs — so SDRs can't claim credit for meetings that never happened.

A Worked Sales Accepted Opportunity Example

A five-SDR team books 120 meetings in a quarter. 96 are held (an 80% no-show rate inverse), and AEs accept 61 of them as SAOs. SAO rate on held meetings: 64%. SAO rate on booked meetings: 51%. Of the 61 accepted, 19 become qualified pipeline worth $1.4M. Now the org can do real math: each SAO is worth roughly $23K of pipeline, each held meeting $14.6K, each booked meeting $11.7K — and the SDR comp plan can be tied to the number that actually predicts revenue instead of the one that's easiest to inflate.

When Sales Teams Use Sales Accepted Opportunity

RevOps owns the definition and audits the acceptance reasons, because the SAO checkpoint is where attribution fights get settled. VP Sales watches SAO rate as a leading indicator of SDR quality — a team booking 30 meetings a month at a 40% SAO rate produces less pipeline than one booking 18 at 85%. SDR managers use rejection reason codes to coach: "wrong persona" and "no pain" are training problems; "already a customer" is a list-hygiene problem. Finance cares because SDR headcount ROI is only calculable once there's a trusted conversion number between activity and pipeline generation.

Limitations and Common Sales Accepted Opportunity Gaming Patterns

The classic exploit is acceptance sandbagging: AEs reject borderline meetings to keep their win rate clean, because a rejected meeting never enters the funnel they get graded on. The mirror pattern is acceptance inflation — AEs accept everything to keep SDR relationships warm, then quietly close-lost the junk as "no decision," which corrupts the no-decision rate downstream. A subtler game is criteria drift: reps apply stricter standards in months when their pipeline is full and looser ones when they're short, so the SAO rate reflects quota pressure rather than lead quality. The structural fix is reason-coded rejections reviewed monthly by RevOps, plus a re-acceptance path so a wrongly rejected meeting can be recovered. SAO also says nothing about deal size or speed — a team can hit a 70% SAO rate on $8K deals and lose to a team at 45% on $90K deals. The metric governs the handoff, not the outcome.