Sales Development Process: What the Evidence Changes

Start With the Handoff Contract

I treat this rejection pattern as a control test, not a story about a real account. A rejected handoff exposes a process defect when the CRM shows completed calls and emails but no verifiable reason for an account executive to accept the opportunity. Treat this as a hypothetical failure pattern, not a customer case: qualification fields are incomplete, the buyer's need is paraphrased without a source, and the decision timeline is unknown. The corrective decision is to stop counting activity as progress and require stage-specific evidence before authority passes from the SDR to the AE.

The operating cost is duplicated qualification work and an avoidable dispute between roles. A rejection code should identify the missing evidence—fit, problem, stakeholder, timing, or agreed next step—without blaming the SDR. The rejected record then returns to a named stage owner within a defined feedback window. That mechanism turns a common failure pattern into process learning while avoiding any suggestion that this article observed a real employee, account, or commercial outcome. I want your reviewer to return this record when you cannot name your source, your missing field, and your next owner.

Define Admission and Account Priority

My boundary here is narrow: the SDR owns evidence collection through an accepted handoff, not the close. Define that boundary as an editorial operating rule, then test it. Gong Labs observed associations between seller-role participation and outcomes in 21,392 Gong-recorded B2B opportunities, but the platform sample is correlational and cannot prove that this role split improves performance.

• A sales development process should be evaluated by the clarity of its handoff contracts, because that is where qualified intent is most often lost or distorted.
• A rejected handoff exposes a process defect when the CRM shows completed calls and emails but no verifiable reason for an account executive to accept the opportunity.
• The corrective decision is to stop counting activity as progress and require stage-specific evidence before authority passes from the SDR to the AE.
• The rejected record then returns to a named stage owner within a defined feedback window.
• I want your reviewer to return this record when you cannot name your source, your missing field, and your next owner.

The team should name SDR and AE responsibilities, record handoff returns, and compare rework before and after the rule. Accepted opportunities and return reasons are suitable process measures; closed-won revenue remains downstream and cannot be attributed to the boundary alone. Salesforce's State of Sales, Seventh Edition surveyed 4,050 professionals in August and September 2025 and supplies directional context, not proof of this design. I would compare your SDR and AE decisions on the same evidence, then ask where our boundary produced disagreement rather than assume it saved time.

I would admit a record only when its source and initial fit rationale are visible. Salesforce's lead-management implementation guide separates status, assignment, qualification, conversion, fields, history, and reporting; it documents a configurable record process, not a universal SDR method. Use that distinction to make entry an explicit CRM event rather than an implied judgment.

For an inbound record, preserve the submitted action and time; for an outbound record, preserve the ICP rule version, source, observation date, and owner. These fields do not prove fit or prevent wasted work. They let a reviewer reproduce the admission decision, count exceptions, and revise the rule when admitted accounts repeatedly return for the same missing evidence. You should be able to show me your admission rule, and I should be able to reproduce your decision without reading your intent into a blank field.

OKKI Go is useful here as a reviewed operating layer: it can help a team move from company discovery to contact research without making the final outreach decision invisible.

Separate Sourced Observations From Account Hypotheses

For research, I separate sourced observations from the team's account hypothesis. Capture only information available from permitted sources, with its date and locator, then write the commercial inference in a separate field. A public expansion announcement may justify testing a capacity hypothesis; it does not establish a buyer problem, budget, or intent.

OKKI Go documents natural-language company search, candidate review, route correction, contact discovery, draft preparation, user confirmation before sending, and visible send status. That is product scope, not evidence of research accuracy or better engagement. The operator must verify the source, reject stale or irrelevant candidates, and keep the final account rationale attributable to a person. When you research, I ask you to preserve your source and your inference separately so we can correct one without rewriting the other.

Map Role Relevance and Buyer Response

My contact-map review asks whether role relevance and channel basis are documented separately. A title or reporting line is a hypothesis about relevance, not proof of authority or interest. Record the role rationale, the source and date, the permitted channel, and any suppression or objection before outreach.

For UK outreach, the ICO says rules vary by channel, recipient type, use of personal data, transparency, and objections. This is UK guidance rather than global legal advice. The process therefore routes jurisdiction and channel questions to the designated reviewer instead of treating a role match, content download, or vendor record as a universal lawful basis. I would not let your role map become buyer fact; you show me your rationale, and we keep your authority and interest assumptions open.

At engagement, I look for a buyer response or explicit disposition rather than an activity total. Delivered messages and clicks are delivery or interaction events; they are not buyer-confirmed need. Preserve the exact reply, its channel and time, the operator's classification, and the next permitted action.

The proposed rule is to advance only on a written evidence class, such as a buyer-stated problem, request for information, agreed meeting, objection, or disqualification. Measure classification disagreements and corrections during review. Do not claim that personalization or another message feature caused engagement unless a controlled comparison and adequate sample support that conclusion. You give me the buyer's words, your classification, and your next action; I return your record when those three do not connect.

Qualify With Allowed Unknowns and Close the Loop

I return qualification when fit, problem, stakeholder, timing, or the agreed next step is missing. BANT and MEDDPICC may supply question categories, but they do not prove readiness and should not force a buyer to manufacture an answer. Mark unknowns as unknown and state which are permitted at handoff.

The qualification package contains buyer-attributable statements, source fields, open questions, and the next-step commitment. The AE applies the written acceptance rule and may return QUAL-GAP with the missing field. Track acceptance and return by reason code; use those observations to revise the rule without claiming that the framework itself improves revenue or efficiency. I expect you to state your allowed unknowns, and we should record why your AE accepted or returned each qualification package.

We can audit the handoff only when acceptance, return, and disqualification use named codes. The AE reviews the same evidence fields shown in the stage table, records a decision, and returns a missing-field code within the proposed one-business-day service window. That window is a local control to test, not an industry benchmark.

A weekly review groups returns by code, compares reviewers, and selects one rule for investigation. A rising QUAL-GAP count may reflect weak discovery, an over-strict acceptance rule, or inconsistent review; the count alone identifies no cause. Preserve the original state, the correction, the owner, and the next review date so changes remain traceable.

The review becomes useful only when it changes a named control. Tighten an admission field, clarify an allowed unknown, revise a return code, or retrain reviewers on the same evidence example. Then watch the next cohort. A meeting about bad handoffs is commentary; a revised contract with an owner and a follow-up date is process improvement.

Illustrative control record—not an observed customer case: an outbound account enters with an ICP rationale and a dated source. Research records a public expansion signal, but the first buyer reply confirms no current project. The SDR must use NO-SIGNAL or disqualify, not infer a need. If a later reply confirms a problem but no stakeholder or next step, the AE returns QUAL-GAP within one business day. The record advances only after those missing fields contain buyer-attributable evidence.