What is the first concrete step in The Sandler Rules by David Mattson for running a discovery call in 2027?

The outcome you should expect

When a seller opens a discovery call by negotiating an up-front contract rather than launching into rapport-then-pitch, four things change measurably, and they change in a predictable order.

The first change is call length variance collapsing. Discovery calls without an agreed time box tend to run either short (the buyer bails at eight minutes because nothing has been established) or long (the seller keeps talking past the scheduled thirty because no one named an end). With an up-front contract, the call runs approximately as scheduled because both parties agreed to the boundary aloud. Sellers who adopt this consistently report their thirty-minute discovery calls actually ending near thirty minutes, which matters less for the call itself than for the calendar math behind it — a rep running six discovery calls a day with a twelve-minute average overrun loses over an hour of selling time daily.

The second change is a rise in clean, early "no" outcomes. This is the outcome most sellers resist and the one *The Sandler Rules* treats as the point. When you say at minute two, "at the end of this, one of three things happens — we agree there's a fit and set a next step, we agree there isn't and we part cleanly, or we're not sure and we name what would resolve it," you have made "no" a legitimate, socially permitted answer. Buyers who were going to disappear into a three-month non-response instead tell you inside the call. Your pipeline shrinks. Your forecast accuracy improves. Sandler's framing is that an unqualified opportunity sitting in your pipeline is a liability that costs you follow-up cycles, not an asset.

The third change is that the buyer starts answering harder questions. An up-front contract that includes "I'm going to ask you some direct questions about what this is costing you today, and if any of them are out of bounds just say so" pre-authorizes the pain questions that follow. Without that authorization, a seller asking "what has this problem cost you in the last twelve months?" at minute six sounds intrusive. With it, the same question sounds like the agreed agenda.

The fourth change is on next steps. The up-front contract's closing element — agreeing in advance on what a successful outcome of *this call* looks like — means the last ninety seconds of the call are a confirmation, not a negotiation. You are not improvising "so, uh, what do you think makes sense next?" You are saying "we agreed we'd end with either a next step or a clean close; which is it?"

What you should not expect is a higher raw conversion rate from discovery to opportunity. It usually drops, because you are disqualifying earlier and more honestly. The number that should improve is conversion from opportunity to closed-won, and the total cycle time on the deals that survive. If you measure only top-of-funnel conversion, an up-front contract will look like a regression for the first quarter.

What drives that outcome

The mechanism has almost nothing to do with the words themselves and everything to do with who holds the frame of the conversation. This is the core insight running under *The Sandler Rules* and the reason David Mattson treats the up-front contract as step one rather than as an etiquette flourish.

In a default discovery call, the buyer holds the frame. They control what gets asked, what gets answered, how long it runs, and — crucially — what happens afterward, which is usually nothing communicated. The seller is in the position of asking permission implicitly at every turn: permission to ask another question, permission to ask about budget, permission to ask for a next meeting. Sandler's rule about never begging for business describes exactly this posture. A seller who has not established a mutual agreement about the call is, structurally, begging for every inch of it.

The up-front contract inverts this by making the terms explicit and mutual before any information changes hands. Once the buyer has verbally agreed — "yes, thirty minutes works, and yes, I'm fine telling you no" — the seller is no longer requesting; the seller is executing an agreed plan. Sandler's related rule about not doing the prospect's thinking for them depends on this. You cannot stop doing a buyer's thinking for them if you have no license to ask the questions that would make them do it themselves.

The second driver is the elimination of what Sandler calls mutual mystification: both sides leaving a conversation believing different things happened. Sellers hear "this is really interesting, let me take it to the team" and record a positive signal. Buyers say it to end a call politely. An up-front contract that names the possible outcomes in advance removes the vocabulary of polite ambiguity, because "let me take it to the team" is not one of the three outcomes you both agreed to.

The third driver is pressure removal. Sandler's stance is that pressure applied by the seller produces reactance in the buyer — the buyer's guard goes up and the information you get degrades. By explicitly granting the buyer the right to say no, you remove the thing they were bracing against. The counterintuitive result is that buyers disclose more, not less, because there's no longer a trap to defend.

The fourth driver is sequencing discipline. Because the contract names the agenda, it also names the order. In a Sandler-shaped discovery call the order is pain, then budget, then decision — and each of those is a later step. The up-front contract is what makes that order enforceable rather than aspirational, because when the buyer jumps ahead ("so what does this cost?") you can point back at the agreement: "budget's on our list, and I want to make sure I understand the problem first — is that alright?"

Benchmarks and realistic ranges

Concrete numbers are where up-front contracts either become a habit or get abandoned, so here are the ranges practitioners actually operate in. Treat these as operating heuristics from field practice, not as published research findings.

Length of the contract itself. Sixty to ninety seconds on a thirty-minute call. Under thirty seconds and it reads as a scripted throat-clear the buyer waves through. Over two minutes and you have spent seven percent of the call on procedure and the buyer starts wondering when you'll say something. On a sixty-minute call, ninety seconds to two minutes is reasonable because you have more agenda to enumerate.

Number of elements. Five is the working set: purpose (why we're both here), time (how long, agreed aloud), the buyer's agenda (what they need to get out of it), your agenda (what you need), and outcome (what we do at the end, including the explicit no option). Sellers who try to compress to two elements — time and agenda — lose the outcome clause, which is the element that actually does the work. Sellers who expand past six start sounding like they're reading terms and conditions.

Where it goes. After a brief rapport exchange, not before. Thirty to sixty seconds of genuine rapport, then the contract, then discovery. Opening cold with the contract before any human exchange lands badly on a first call, particularly with buyers who did not initiate the meeting.

Adoption ramp. Expect three to four weeks before a rep sounds natural doing it. The first ten calls sound recited. This is the single most common point of abandonment: the rep tries it twice, feels awkward, decides "it doesn't fit my style," and reverts. Managers who require it on recorded calls with a checklist for the first thirty calls get durable adoption; managers who introduce it in a workshop and never inspect it get roughly zero.

Expected disqualification shift. In the first sixty days after adoption, a team should see a meaningful increase in discovery calls that end without a next step — because the seller is now asking for a decision rather than accepting "send me some info." The corresponding signal that it's working is a *drop* in the number of opportunities sitting in stage two with no activity for over thirty days. If disqualification goes up and stale-stage-two count doesn't come down, the reps are disqualifying but still logging the dead deals.

Re-contracting frequency. Every meeting in the cycle gets its own up-front contract, not just discovery. A six-meeting enterprise cycle should have six contracts. The one that matters most after discovery is the demo, because unset demos are where the most calendar time leaks.

Time box overrun tolerance. If you're at the agreed thirty and not done, you ask: "we're at time — do you want to keep going for another ten, or should we book a follow-up?" Asking is the point. Silently running over destroys the credibility of every future time box you set with that buyer.

Risks, edge cases, and failure modes

The up-front contract fails in specific, recognizable ways, and most of them are execution errors rather than problems with the method itself.

Reciting it as a script. The most common failure. The contract has five elements but no fixed wording, and a rep who memorizes one paragraph will deliver it identically to a warm inbound lead and a cold outbound skeptic. It should sound like the rep talking. If a manager can transcribe the contract once and match it word-for-word across a rep's recordings, that rep is reciting and buyers can hear it.

Setting the frame and then abandoning it. A rep agrees to a thirty-minute time box, agrees that either party can say no, and then at minute twenty-eight — when the buyer says "I don't think this is a fit" — argues with them. This is worse than never having set the contract, because you've now demonstrated that your agreements are decorative. If you grant the right to say no, you must accept the no when it comes. You may ask one clarifying question ("fair enough — so I learn from it, what made it not a fit?"). You may not relitigate.

Using it as a control device. Some reps weaponize the contract: "well, we *agreed* we'd cover budget today." The contract is mutual, not a lever. The moment it becomes a way to force a buyer through an agenda they've lost interest in, it produces exactly the reactance Sandler's approach exists to avoid.

Wrong-context deployment. A formal five-element contract is disproportionate on a ten-minute inbound chat-to-call, at a trade show booth, or on a genuinely social introduction from a mutual contact. In those settings you compress to two elements — time and outcome — and skip the rest. Applying the full structure everywhere is a sign the rep learned the form, not the reason.

Cultural and seniority mismatch. Directness lands differently across regions and levels. A buyer in a culture with high indirectness may verbally agree to "you can tell me no" and still never use it. Executives with fifteen-minute windows often want the agenda compressed to one sentence. Adjust the delivery; keep the outcome clause, which is the load-bearing element.

Multi-stakeholder calls. With five people on the buyer side, "agree we can each say no" is ambiguous — whose no counts? On group calls, name the decision explicitly: "at the end, I'd like to know from whoever owns this whether it's worth a next conversation." Otherwise you get four polite nods and no decision.

Procurement-led or RFP-driven processes. When the buyer runs a formal process, your discovery call is often a scripted vendor interview. The contract still helps but shrinks — you're agreeing to time and to what you'll each provide, and the "we can both say no" element may be genuinely unavailable to your counterpart, who has no authority to end the process.

Manager-driven over-measurement. Turning up-front contracts into a scored compliance line item on every call review produces performative delivery. Inspect it for the first thirty calls to establish the habit, then inspect outcomes — clean nos, stale-stage-two count, next-step booking rate — rather than the ritual.

The "no" that arrives too early. Occasionally a buyer takes the permission and says no at minute four, before you've asked anything. That is usually a real signal, but ask one question: "understood — is that because the problem isn't there, or because the timing's wrong?" Those are different outcomes and only one of them is a genuine disqualification.

A practical rollout plan

Rolling this out across a team is a coaching problem, not a training problem. The distinction matters: training changes what reps know, and this requires changing what reps do while under mild social discomfort. Here is a workable four-week sequence.

Week one — define and script the five elements per segment. Do not hand out one universal paragraph. Build three variants: inbound (the buyer asked for the meeting, so purpose is short and outcome is emphasized), outbound (you asked, so you earn the time box and explicitly grant the exit), and executive (compressed, one sentence of agenda, hard outcome clause). Each rep writes their own wording inside each variant. Manager reviews the wording, not the delivery, this week.

Week two — role-play and record. Pairs, ten minutes each, with the partner instructed to be mildly resistant: interrupt, jump to pricing, be vague. The rep's job is to set the contract and then use it once when the partner jumps ahead. Record every rep delivering all three variants. The goal is to burn off the recited-paragraph sound before it hits a live buyer.

Week three — live calls with a checklist. Every discovery call gets a five-box checklist: purpose, time, their agenda, my agenda, outcome including no. Rep self-scores; manager pulls two recordings per rep per week and scores the same boxes. Disagreements between self-score and manager score are the coaching conversation — reps almost always believe they delivered the outcome clause when they delivered a softened version of it.

Week four — inspect outcomes, drop the checklist. Stop scoring the ritual. Start looking at three numbers: discovery calls ending with an explicit decision (next step or clean close), count of opportunities stalled over thirty days in early stages, and average discovery call duration versus scheduled. Those three moving together is the proof; the checklist was scaffolding.

Operational plumbing. Two small CRM changes make the strategy stick. First, add a required "next step agreed" field on discovery-stage records with a date — not a checkbox, a date, because a checkbox lets reps record intent. Second, add a disqualification reason picklist with a "clean no on discovery" option so that reps are rewarded for producing them rather than quietly leaving deals open. Without the second change, reps face a real incentive to keep dead opportunities alive, and no amount of contract training beats a compensation and reporting structure that punishes honesty.

What to extend next. Once discovery contracts are habitual, apply the same structure to the demo — the single highest-value place to use it, because unset demos default to feature tours. The demo contract adds one element the discovery contract doesn't have: what specifically the buyer needs to see in order to make a decision. Then extend to proposal review calls.

Sequencing with the rest of the call. The up-front contract is step one, not the whole method. What follows it in a Sandler-shaped discovery call is pain (the specific, quantified cost of the current situation), then budget, then decision process. The contract exists to make those three sequential rather than tangled. A team that installs the contract and then still opens with a capabilities pitch at minute three has installed the form and skipped the substance.

Related questions

Does the up-front contract work on inbound leads who already want to buy?

Yes, in compressed form. Inbound buyers still leave calls with different understandings of what happened. Keep the time box and the outcome clause, shorten the purpose statement, and skip most of the agenda enumeration since they set the agenda by reaching out.

What comes after the up-front contract in a Sandler discovery call?

Pain — the specific, quantified cost of the buyer's current situation, reached through questions rather than assertions. Budget and decision process follow. The contract's job is to pre-authorize the pain questions so they land as agenda rather than intrusion.

How is this different from just sending an agenda beforehand?

A sent agenda is one-directional and unacknowledged. The contract is verbal, mutual, and confirmed aloud in the moment, and it includes the outcome clause — the explicit right to end with no — which no emailed agenda contains.

Should the up-front contract be repeated on every meeting?

Yes. Each meeting in the cycle gets its own, sized to that meeting. The demo is the most valuable one after discovery, because unset demos reliably become feature tours and end without a decision.

What if the buyer refuses to agree to the terms?

That is useful information at minute two rather than week six. Ask what part doesn't work and adjust. A buyer unwilling to agree that either party may say no is often signaling they have no authority to say either yes or no.

FAQ

Is the up-front contract really the first step, or is rapport?

Both, in that order, but rapport is not a step so much as a precondition. Thirty to sixty seconds of genuine human exchange precedes the contract. The first *concrete, structural* step of the call — the first thing you deliberately do that shapes the rest — is the contract. Sandler's material treats bonding and rapport as an ongoing posture across the whole call, not a discrete opening move.

Doesn't giving the buyer permission to say no cost you deals?

It costs you the deals that were never real, which is the point. What it protects is the follow-up capacity you would have spent chasing them. The reps who lose real deals to it are usually the ones who granted permission and then treated the buyer's yes as automatic — the contract removes pressure, it does not remove the requirement to establish genuine pain.

How do I set an up-front contract without sounding like a robot?

Write your own version of the five elements in your own words, then vary the wording every call. Never memorize a paragraph. The reliable tell of a robotic delivery is that the rep says it at the same speed regardless of what the buyer just said. Respond to the buyer's actual opening, then move into the contract conversationally.

Does this apply to short calls and cold call-backs?

Yes, compressed. On a ten-minute call the contract is two sentences: the time you have and what you'll do at the end. The outcome clause is the element you never drop, at any call length, because it is the one that produces decisions.

What is the single most common mistake with this step?

Setting the frame and then abandoning it — agreeing that the buyer can say no, then arguing when they do, or agreeing to thirty minutes and running to fifty without asking. Either one teaches the buyer that your agreements don't hold, which makes every later commitment you ask for less credible.

How do I know if it's actually working?

Look at three numbers over sixty days: the share of discovery calls ending with an explicit decision, the count of early-stage opportunities with no activity past thirty days, and actual versus scheduled call duration. Explicit decisions up, stale opportunities down, duration variance down. If only the first moves, reps are asking for decisions but not logging the negative ones.

Sources

• https://www.sandler.com/ — Sandler Training, publisher of the methodology and the source of the rules discussed here.
• https://www.sandler.com/books/the-sandler-rules/ — Publisher page for *The Sandler Rules* by David Mattson.
• https://www.mheducation.com/ — McGraw Hill, publisher of several Sandler titles.
• https://hbr.org/topic/subject/sales — Harvard Business Review's sales topic hub, for research on buyer behavior and discovery practice.
• https://www.gartner.com/en/sales — Gartner's sales research practice, covering buying-group behavior and sales process design.
• https://www.salesforce.com/resources/articles/discovery-call/ — Salesforce's practitioner guidance on discovery call structure.
• https://blog.hubspot.com/sales/sales-discovery-call — HubSpot's sales blog on running discovery calls.
• https://www.gong.io/blog/ — Gong's research blog analyzing recorded sales conversations.
• https://www.forbes.com/sites/forbesbusinesscouncil/ — Forbes Business Council, for practitioner commentary on sales methodology adoption.

Related on PULSE

• How do you run a discovery call that ends in a decision instead of a follow-up?
• What is the difference between a sales methodology and a sales process?
• How do you build a disqualification stage into a CRM pipeline?
• What does a demo up-front contract include that a discovery one doesn't?
• How should sales managers coach a new methodology past week two?
• What early-stage pipeline metrics actually predict forecast accuracy?