# The Meeting Acceptance Standard for SDR-Sourced Opportunities

*You will be able to grade any booked meeting as accept, send-back, or reject against a written bar covering both the account and the named contact, so two graders score it identically.*

- Canonical URL: https://www.refolk.ai/guides/meeting-acceptance-standard-sdr-opportunities
- Pillar: Sales and go-to-market
- Format: Standard
- Published: 2026-09-08
- Last reviewed: 2026-09-08
- Reading time: 17 min
- Keywords: when to accept an SDR meeting, sales accepted lead criteria, meeting to opportunity qualification checklist, SDR to AE handoff acceptance rules, reject a booked sales meeting reason

## Key takeaways

- Acceptance rate has two failure edges: below 70% signals loose SDR qualification or ICP miss, and above 85% signals AEs rubber-stamping that surfaces later as weak SQL-to-opportunity conversion.
- A meeting is not gradeable until seven fields are present: prospect-stated pain, trigger event, thread context, buying role, meeting purpose, next-step confidence, and qualification notes against ICP.
- Send-backs must carry a taxonomy code from a capped list of 6 to 8 reasons, never free-text 'bad fit', or the returned record is impossible to act on.
- Compensation predicts the acceptance number more than SDR skill: paying only on booked meetings produces AE rejection above 40% and a collapsed handoff within two quarters.
- Refolk's index shows a US SDR:AE ratio near 1:10.7 against 1:4.85 in the UK, so a leaky US acceptance gate pushes junk across a far wider surface.
- Some rejections are contact-data failures wearing a qualification costume: 'went dark' and 'champion left' need their own codes so they do not tax the acceptance rate or trigger the wrong fix.

A meeting an SDR just booked is not yet an opportunity. It is an account plus a named person, held on a calendar, waiting for a decision: accept it as qualified pipeline, send it back to be fixed, or reject it to nurture. This guide gives sales development leaders, account executives, SDR managers, and founders running their own outbound a written bar for that decision, precise enough that two graders score the same meeting the same way and the opportunity-acceptance-rate number becomes something you can trust.

Other standards cover the stages around this one: cutting accounts before outreach, clearing a single contact to send. This one defines the acceptance gate itself, where a held meeting either converts into a qualified opportunity or bounces. It states the required fields, the grading dispositions, the send-back window, and the rejection taxonomy so that "accept" stops meaning whatever the AE feels that morning.

## What "accepted" has to mean before you can measure it

An accepted meeting is one where the AE can run the first call immediately with qualification, deal context, intent, and a clear next step already in hand, and where both the account and the named contact clear a written bar. If either grader would score the same meeting differently, you do not have a standard yet, you have two opinions sharing a metric.

The number this standard protects is the opportunity acceptance rate: the share of SDR-sourced meetings an AE converts into a qualified opportunity. It is the handoff number. Holding both roles to it is what stops the volume-versus-quality argument from repeating every quarter, because a low number can be pinned on SDR quality or AE conversion separately rather than argued about in the abstract.

The most common way this metric lies is definitional drift. In one documented case, one team counted any deal created in the CRM as an opportunity while another counted only deals with confirmed budget and timeline. Two teams, two definitions, one meaningless benchmark. The fix is the first artifact this standard demands: a single written definition of "opportunity" that both graders apply, with binary factors, living in the CRM where nobody can quietly reinterpret it.

> **Rule:** One written definition, both graders
>
> The opportunity definition and the accept/reject bar must be a single signed document in the CRM. If the SDR lead and AE lead have not both signed it, meetings are not gradeable, they are negotiable.

## The gradeable-fields gate: what must be present before you grade

A meeting is not gradeable until seven fields are populated. Missing fields do not make a meeting bad; they make it impossible to score, which is worse, because an ungradeable meeting corrupts the acceptance rate no matter which way you call it. Enforce the gate in the CRM: the record cannot move to "AE" status until the form is complete.

The documented minimum package is seven fields. Each proves something specific, and each has a failure signature when it is faked or left thin:

| Required field | What it proves | What it looks like when it lies |
|---|---|---|
| Prospect-stated pain | There is a reason to buy, in the buyer's words | Restates a product feature, not a problem the buyer named |
| Trigger event | Why now, not someday | "Seemed interested" with no dated event behind it |
| Buying role | The contact can influence or decide | Title pasted in with no authority signal |
| Meeting purpose (buyer's view) | The buyer expects this conversation | Purpose the SDR wants, not one the buyer agreed to |
| Outreach thread context | The AE can pick up mid-conversation | Blank or a single "booked via email" line |
| Next-step confidence | The meeting will actually hold | High confidence with no confirmation from the buyer |
| ICP qualification notes | The account clears the fit bar | Generic notes that would fit any account |

Salesforce, HubSpot, Outreach, and Salesloft all support required custom fields per deal stage, so this gate is a configuration, not a wish. When Economic Buyer, Pain, Champion, and Decision Process are required fields, reps fill them in. Empty fields then become a signal in their own right: if Economic Buyer is still blank after three calls, that blank is the deal risk, and a weekly "which fields stay empty" review turns the gap into a coaching item instead of a surprise.

**20-40% - The conversion drop when the handoff package is incomplete**

Forrester-cited; a 4-hour AE response SLA improved qualified-to-opportunity conversion by 34% in one case study.

The reason to hold the line here is speed on the other side of it. A lead contacted in 5 minutes is 21 times more likely to qualify than one contacted after 30 minutes, and 25 to 40 percent of qualified leads receive no AE follow-up within 48 hours. A complete package is what lets the AE act inside the window instead of chasing context first.

## Grading the account and the contact against a written bar

Every meeting gets graded on two independent axes: does the account clear ICP, and does the named contact clear the buying-role bar. Both must pass to accept. This is deliberate, because the two most common false positives, a great contact at a wrong-fit account and a perfect-fit account with a contact who cannot influence anything, both look like wins until the deal stalls.

Use a lightweight qualification framework as the field structure, not as a debate. BANT (Budget, Authority, Need, Timeline) is a four-criteria framework best for deals under $25K. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is a six-element framework for complex deals above $50K, born in the 1990s at PTC; MEDDPICC adds Paper Process and Competition. Whichever you pick, make each element a CRM field with fixed values so grading is selection, not prose:

- Budget: Confirmed / Likely / Unknown
- Authority: Decision-maker / Influencer / Unknown
- Need: Critical / Nice-to-have / Unclear
- Timeline: under 90 days / 3-6 months / over 6 months / Unknown

The gating rules keep two graders aligned. For BANT, 3 of 4 criteria met equals qualified. For MEDDIC, Identify Pain, Economic Buyer, and Champion confirmed is qualified enough to advance. Write which rule you use into the SLA so nobody grades against a private threshold.

#### The two-axis accept decision

Horizontal axis runs from Account off-ICP to Account clears ICP. Vertical axis runs from Contact off buying-role bar to Contact clears buying-role bar.

| Quadrant | What it means |
| --- | --- |
| Off-ICP, wrong role | Reject to nurture with a fit code |
| On-ICP, wrong role | Send back to find the right contact |
| Off-ICP, right role | Reject; a good contact does not fix fit |
| On-ICP, right role | Accept as a qualified opportunity |

*Both axes must clear before a meeting is accepted; a strong contact never rescues a wrong-fit account.*

The single hardest discipline here is refusing to let a strong contact rescue a wrong-fit account. A great champion at a company that will never buy is a rejection, not an accept, and the matrix above exists to make that call the same every time.

> A perfect contact at a wrong-fit account is a rejection wearing a win's clothing.

## The calibration bands: what a healthy acceptance rate looks like

Healthy AE acceptance of SDR-booked meetings sits near 60 to 70 percent, and the metric has two failure edges, not one. A single "higher is better" target hides the second edge and quietly rewards rubber-stamping. Read the acceptance rate against a band, never against a floor alone.

| Metric | Too low (upstream/ICP problem) | Healthy band | Too high (rubber-stamp) |
|---|---|---|---|
| Meeting-to-opportunity, outbound | below 25% | 10-30% typical, aim 30%+ | n/a |
| AE acceptance of SDR meetings | below 70% | 60-70% | above ~85% |
| SAL acceptance (Forrester) | below 90% | 90%+ | n/a |
| SAL acceptance (practitioner) | below 60% | 60-75% | above 85% |

Below 25 percent meeting-to-opportunity, or acceptance below 70 percent, usually means SDRs are booking meetings that do not meet ICP or the qualification criteria is not clear enough. Above roughly 85 percent acceptance, sales is typically rubber-stamping, which surfaces later as poor SQL-to-opportunity conversion. That is why you never read acceptance rate alone: pair it with the downstream number so a suspiciously high figure gets caught before the pipeline reveals it.

For upstream context, the most defensible published MQL-to-SQL average is 13 percent for B2B SaaS, drawn from client data gathered between 2019 and 2025. Use it as a reality check on inbound volume expectations, not as your acceptance target.

> **Note:** The comp design usually sets the number
>
> Paying SDRs only on booked meetings produces AE rejection above 40% and a collapsed handoff inside two quarters. Fix the acceptance gate as a compensation question before you fix it as a grading question.

## The procedure: from booking to graded disposition

Run every booked meeting through the same eight steps, in order. The point is not ceremony; it is that the same inputs produce the same disposition regardless of who is grading.

#### Grading an SDR-booked meeting

1. **Publish the SLA before any meeting is booked** - The SDR lead and AE lead co-write a one-page definition of qualified and unqualified, with binary factors. Both sign it and it lives in the CRM, revisited quarterly.
2. **Require the gradeable-fields form at booking** - The SDR populates the seven required fields at booking. The CRM blocks the record from reaching AE status until the form is complete.
3. **Start the acceptance clock at handoff** - Automation starts the SLA timer the instant the record hits AE status, with escalation wired. The window is 4 to 8 hours for an outbound meeting, up to 24 hours for an MQL.
4. **AE grades accept, send-back, or reject** - Within the window, the AE grades the account against ICP and the contact against the buying-role bar. One of three dispositions is recorded, each with a reason code.
5. **Route send-back to the SDR with a specific code** - A send-back returns to the SDR with a taxonomy code, not "bad fit", and opens a re-work window. The code names exactly what is missing.
6. **Let timeout auto-resolve** - If the AE does not act within the window, automation returns the record to the SDR or moves it to nurture. No record sits in limbo.
7. **Audit rejections against the SLA** - The manager reviews every AE "not qualified" weekly to confirm the bar was applied. No AE dodges accountable pipeline through a loose disqualification.
8. **Review acceptance rate by SDR and by AE** - RevOps reviews the rate split by both roles monthly. Outliers on either side, too low or too high, are flagged for coaching.

#### The acceptance gate, end to end

1. **Booked with fields** - Seven-field form complete, record gradeable
2. **Handoff clock starts** - SLA timer running, 4-24 hours
3. **AE grades** - Account against ICP, contact against role bar
4. **Disposition recorded** - Accept, send-back, or reject with a code
5. **Route or auto-resolve** - Send-back to SDR, reject to nurture, or timeout auto-return

*Every held meeting exits through exactly one of three dispositions, each with a code and a timer.*

## The window and the timeout: where pipeline silently dies

Set an explicit acceptance window per lead type, and default the timeout to auto-return so no meeting sits in limbo. The send-back window is where pipeline quietly dies: with 25 to 40 percent of qualified leads getting no AE follow-up within 48 hours, a timeout-to-nurture default is load-bearing, not administrative.

| Lead type | AE first-touch window | Timeout default |
|---|---|---|
| Inbound demo request (hot) | 4 hours | auto-return to SDR/nurture |
| SDR-booked outbound meeting | 4-8 hours | auto-return to SDR/nurture |
| MQL to sales | up to 24 hours | auto-return to SDR/nurture |
| Reject-to-nurture routing | 24-48 hours | moved to nurture |

The reject-to-nurture SLA matters as much as the acceptance one. Set it at 24 to 48 hours so rejected meetings route back into nurture fast instead of stalling. A rejected lead with no route is not a decision, it is a leak.

Who owns the final "qualified" call is genuinely contested in the sources, so state your choice explicitly. One view frames a unilateral AE "qualified" decision as a serious power imbalance; another removes AE discretion entirely by making a system, not judgment, qualify the opportunity. I favor the system where the fields are complete: if the seven fields and the framework thresholds are met, the meeting is accepted by rule, and disagreement routes to the weekly audit rather than a live veto. Where your fields are thinner, keep the AE call but audit it hard.

## The rejection taxonomy: making a send-back gradeable

A send-back or rejection must carry a code from a capped list, never free-text. "Bad fit" is ungradeable: it returns a meeting nobody can act on, and it hides whether the fault was the account, the contact, or the data. Cap the list at 6 to 8 primary reasons for early-stage rejects, with a required single-select primary and an optional secondary tag.

**Send-back and rejection reason codes**

```
PRIMARY CODE (required, pick one)
- OFF_ICP        Wrong industry, size, or territory; never a viable fit
- NO_BUDGET      No budget path identified for this account
- NO_NEED        No business need identified in the buyer's words
- WRONG_ROLE     Contact cannot influence or decide; on-ICP account, wrong person
- TIMING         Real need, no decision window inside the horizon
- FIELDS_MISSING Send-back: a required field is blank or unverifiable
- NO_SHOW        Buyer did not attend the held meeting (data code)
- WENT_DARK      Buyer non-responsive after booking (data code)

SECONDARY TAG (optional, free short note on what to fix)
```

*Single-select primary required; add a secondary tag if it helps. Keep the list to 6-8 codes and do not allow free-text.*

Note two distinctions the taxonomy has to preserve. First, disqualified means never viable, wrong industry, no budget, outside territory, or off-ICP, and it routes to nurture rather than back to the SDR for rework. Second, and this is the one teams get wrong most: NO_SHOW and WENT_DARK are contact-data problems, not sales-skill problems. Coding "champion left" as a qualification miss taxes the acceptance rate unfairly and drives the wrong fix. Keep data-quality codes separate from fit codes so the number reflects what it claims to.

I ran this search: `Account Executives at US B2B SaaS companies with 50-500 employees who previously worked as SDRs` - [see the full result list](https://www.refolk.ai/s/k01a3etsxp).

*Returns AEs who have sat on both sides of the handoff, the people best placed to co-write and pressure-test your acceptance bar.*

When the bar keeps failing on WENT_DARK codes, the fix often lives in contact data rather than qualification. Finding graders and champions who are reachable, and re-verifying that a named contact is still in role before the meeting is even booked, is exactly the friction [Refolk](/) removes: ask for the people you want in plain English and get current profiles back across LinkedIn, GitHub, and the open web, so a "champion left" surprise gets caught upstream of the acceptance gate.

## How this goes wrong: failure modes and false positives

Most acceptance-gate failures are not grading errors; they are the metric being fed something it cannot measure honestly. Learn these eight, because a standard that ignores them produces a clean-looking number over a broken handoff.

- **Booked-not-held masquerades as acceptance.** A high booked count with a low held count usually means the SDR is booking people who agreed to end a conversation, not people who wanted the meeting. Grade held meetings only, and watch the booked-to-held gap per SDR.
- **A too-high acceptance rate is a failure, not a win.** Above roughly 85 percent means rubber-stamping that surfaces later as weak SQL-to-opportunity conversion. Always pair acceptance rate with the downstream number.
- **"Bad fit" send-backs are ungradeable.** The false positive is a returned meeting nobody can act on. Require a taxonomy code and reject free-text.
- **AE over-rejection to dodge pipeline.** An AE disqualifies to avoid owning the opportunity. Have the manager audit every "not qualified" against the SLA weekly, and overturn ones that met the bar.
- **Over-handoff to be safe.** The SDR passes every lead through to avoid a fight. The fix is strict qualification criteria enforced at the field gate so sub-threshold leads stay in nurture.
- **Silent field gaps.** Empty fields are the signal: a blank Economic Buyer after three calls is the deal risk. Run a weekly review of which fields stay empty.
- **Definitional drift on "opportunity."** Two teams counting different things share a meaningless benchmark. One written definition, applied by both graders.
- **Ghost or no-show mislabeled as a qualification failure.** "Went dark" and "champion left" are data problems. Separate data-quality codes from fit codes so they do not tax the acceptance rate.

> **Watch out:** Two edges, not one floor
>
> An acceptance rate that keeps climbing toward 90% is not improving, it is decaying into rubber-stamp. If the number rises while SQL-to-opportunity conversion falls, your AEs stopped grading and started nodding.

There is a structural reason to police the low edge especially hard in the US. In Refolk's index of professional profiles, the SDR-to-AE ratio runs near 1:10.7 in the United States against 1:4.85 in the United Kingdom. Each US SDR feeds far more AEs, so a leaky US acceptance gate pushes junk across a much wider surface than the same leak in the UK.

| Market | SDR-titled | AE-titled | SDR:AE ratio (derived) |
|---|---|---|---|
| United States | 22,476 | 239,930 | 1 : 10.7 |
| United Kingdom | 3,543 | 17,168 | 1 : 4.85 |
| US-vs-UK multiple (derived) | 6.3x | 14.0x | - |

## Adopt it as policy and keep it honest

Before you call the standard live, verify the gate holds end to end. This checklist is the acceptance test for the acceptance test.

#### Before you call the standard adopted

- [ ] The opportunity definition and accept/reject bar are one signed document, in the CRM, signed by SDR and AE leads.
- [ ] The seven gradeable fields are enforced as required per stage; the record cannot reach AE status incomplete.
- [ ] The framework threshold is written down (BANT 3 of 4, or MEDDIC Pain plus Economic Buyer plus Champion).
- [ ] Acceptance windows are set per lead type with a wired auto-return on timeout.
- [ ] A reject-to-nurture SLA of 24 to 48 hours routes rejected meetings out of limbo.
- [ ] The rejection taxonomy is capped at 6 to 8 codes, single-select primary, with data-quality codes separated from fit codes.
- [ ] A manager audits every AE "not qualified" weekly against the SLA.
- [ ] Acceptance rate is reviewed monthly by SDR and by AE, and read against a band, not a floor.
- [ ] Acceptance rate is paired with a downstream SQL-to-opportunity number so rubber-stamping gets caught.

Keep the standard current by re-checking the mechanism, not the numbers. Revisit the SLA quarterly and ask three questions. Is the acceptance rate inside its band on both edges? Do the same fields keep coming back empty, and if so does the gate need tightening? Are the rejection codes clustering on data problems, which points at contact quality rather than qualification skill? When the answers change, the document changes with them, because a standard that never gets revised stops describing how the team actually grades and quietly becomes fiction.

The payoff for the discipline is not just a cleaner number. Organizations with mature loss-reason analysis are 2.5 times more likely to hit revenue targets, and the acceptance gate is where that analysis begins: every send-back and rejection code you capture here is the raw material for knowing, later, why deals were won and lost.

## Frequently asked questions

### What acceptance rate should I expect from a healthy handoff?

Aim for AE acceptance of SDR-booked meetings near 60 to 70 percent, with meeting-to-opportunity conversion of 10 to 30 percent on outbound. Below 70 percent points to loose SDR qualification or an ICP miss. Above roughly 85 percent is a warning too: it usually means AEs are rubber-stamping, which shows up downstream as poor SQL-to-opportunity conversion. Pair the acceptance rate with that downstream number before you celebrate a high figure.

### How long should an AE have before a meeting auto-returns?

For an SDR-booked outbound meeting, a common window is 4 to 8 hours for the AE to grade and prepare; for an MQL, up to 24 hours. If the AE does not act inside the window, the record should auto-return to the SDR or move to nurture so nothing sits in limbo. Set a separate reject-to-nurture SLA of 24 to 48 hours so rejected meetings route back fast rather than stalling.

### What fields must be present before I can grade a meeting at all?

Seven: prospect-stated pain, the trigger event driving timing, outreach thread context, buying role, the meeting purpose as the prospect understands it, next-step confidence level, and qualification notes against ICP. Until these are present the record is not gradeable, only a calendar invite. Enforce it by making the form a mandatory CRM step so the record cannot reach AE status incomplete.

### How do I stop AEs from rejecting meetings just to avoid pipeline responsibility?

Hold both roles to the same opportunity-acceptance-rate number and have a manager audit every 'not qualified' weekly against the written SLA. If the audit shows a meeting met the bar, the rejection is overturned. Track rejection rate by AE: an AE with a persistently high rate needs coaching or a territory adjustment, not a rubber stamp from the SDR team.

### What is the difference between a send-back and a rejection?

A send-back is a fixable gap: the account fits and the contact may qualify, but something in the required package is missing or wrong, so it returns to the SDR with a code and a re-work window. A rejection means the lead was never viable, wrong industry, no budget, outside territory, or off-ICP, and routes to nurture. Keeping these separate stops repairable meetings from being lost as dead leads.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/meeting-acceptance-standard-sdr-opportunities*