What’s the most practical technique from *New Sales. Simplified.* for handling a “send me info” objection?

The 4:52 p.m. call that dies in an inbox

Picture a rep three weeks into a territory. She reaches an operations director at a mid-market distributor at 4:52 on a Thursday. He's cordial. He listens to twenty seconds of her opening, says "you know what, this sounds interesting — why don't you send me some information and I'll take a look," and the call ends at ninety-one seconds. She logs it as a positive outcome. In the CRM it becomes a stage-two opportunity. She spends forty minutes that evening assembling a PDF, a case study, and a link to a recorded demo.

Nothing happens. She follows up on day three, day seven, day fourteen. She gets one reply — "still reviewing internally" — and then silence. By day thirty the opportunity is stale, and closing it out feels like an admission of failure, so it sits in the pipeline as a phantom.

That ninety-one-second call is the exact moment *New Sales. Simplified.* is written about. Mike Weinberg's argument is blunt: the rep did not get a positive outcome. She got dismissed politely, and then she volunteered forty minutes of unpaid labor to make the dismissal comfortable for both parties. The prospect never said no. He never had to. "Send me info" let him end the conversation while the rep did the emotional work of pretending it was progress.

What makes this scenario so common is that it feels good in the moment. Reps are trained to hear objections as friction and requests as interest. "Send me info" sounds like a request. It comes with a warm tone. It often comes with a real email address, which reads as commitment. But look at what actually transferred: the prospect gave up nothing — no problem statement, no timeline, no calendar slot, no internal context — and the rep gave up her only leverage, which was being on the phone with a live human who had not yet said no.

Now widen the frame slightly, because this pattern is not confined to cold calls. The same dynamic shows up when an inbound lead downloads a whitepaper and replies to the SDR's outreach with "just send me pricing." It shows up in renewals, when a customer says "send over the new package details" instead of taking the QBR. It shows up in partner channels, when a reseller asks for a deck rather than a joint call. In every case, the structure is identical: a request for artifacts substitutes for a commitment of attention. Weinberg's technique generalizes cleanly across all of them because the underlying mechanic — trade information only for engagement — has nothing to do with cold calling specifically.

The distributor deal, incidentally, is the one nobody audits. It never appears in a loss report because it never becomes a loss. It ages out. A pipeline full of these is what makes a forecast unreliable long before anyone notices a conversion problem.

How the diagnostic pivot actually works

The technique is three moves, and the order matters more than the wording.

Move one: agree, don't defend. The rep says something like, "Absolutely, happy to send that over." No hesitation, no audible reluctance. This costs nothing and buys everything — the prospect's defenses stay down because there is nothing to defend against. Reps who skip this step and go straight to a question ("well, before I do that, can I ask —") trigger the exact resistance they're trying to avoid. The prospect hears a salesperson refusing a simple request. Agreement first is not politeness; it's mechanics.

Move two: attach a condition that sounds like service. "So I don't dump a generic packet on you — what's the piece of this you're actually trying to solve?" The framing is the whole trick. The rep is not asking for qualification data. The rep is offering to save the prospect the trouble of reading irrelevant material. That reframing is why the question lands as helpful rather than interrogative. It's also true: sending a curated one-pager genuinely does serve the buyer better than a full product library.

Move three: convert the answer into a calendar hold. If the prospect names a problem, the rep responds with, "That's exactly the situation in the piece I'll send. Rather than have you read it cold, give me fifteen minutes Tuesday or Thursday and I'll walk you through the part that maps to your setup." The material and the meeting travel together. This is the non-negotiable half of the technique and the half most reps drop, because move two feels clever and satisfying on its own. Asking a good diagnostic question and then still emailing a standalone PDF changes nothing.

The branch at D is where most of the value sits. A prospect who can articulate a specific operational problem in one sentence is materially different from one who says "just want to see what's out there." The first has done internal thinking. The second is being courteous. Weinberg's point is that you cannot tell them apart by tone, warmth, or willingness to give you an email address — you can only tell them apart by asking a question that requires a real answer.

The node marked I deserves attention too. Naming the stall out loud — "sounds like this isn't near the top of the list right now, fair?" — feels confrontational to most reps and almost never is. Prospects overwhelmingly confirm it, often with relief, and sometimes correct you, which is the outcome you actually wanted. Either way you leave with information instead of an obligation.

One adjacent note: this same structure powers the "takeaway" behavior throughout Weinberg's system and shows up in adjacent methodologies under other names — Sandler's negative reverse, the up-front contract, the mutual action plan in enterprise deals. The vocabulary differs; the mechanic is identical. Information and effort flow only against reciprocal commitment.

What the numbers look like when you run it

Be careful with benchmarks here — Weinberg's book is a practitioner's manual, not a research study, and it does not publish conversion tables. What follows is the arithmetic of the technique, which you can run against your own CRM rather than borrowing someone else's figures.

Start by measuring what the stall costs you today. Pull every opportunity created in the last two quarters whose first recorded next step was "sent information." Count them. Then count how many reached a scheduled second conversation, and how many closed. In most teams that runs this query for the first time, the second-conversation rate on standalone sends is the number that causes the silence in the room. Whatever yours is, that figure is your baseline, and it is the only benchmark that matters for this decision.

Then price the labor. A curated info package — pulling the right case study, writing a personalized note, attaching links — realistically runs fifteen to forty minutes. Add the follow-up sequence: typically four to six touches over three to four weeks, at three to five minutes each, plus the cognitive cost of tracking them. Call it one to two hours of rep time per stalled "send me info" record. A rep who generates twelve of these a month is spending twelve to twenty-four hours — roughly a full week of selling time per quarter — servicing conversations that produced no commitment. That is the number to put in front of a sales leader, because it converts a technique argument into a capacity argument.

Now look at what the pivot changes. It does not raise your win rate on real deals. It does two narrower things. First, it reallocates hours from phantom records to live ones. Second, it moves disqualification from day thirty to day zero, which shortens your average sales cycle on paper simply by removing corpses from the denominator. Expect your reported opportunity count to drop when you implement this. That drop is the point, and you should warn leadership before it happens, or someone will read the dashboard as a productivity collapse.

Set expectations on the pivot itself, too. A meaningful share of prospects will name a problem when asked — these were people with a real itch who defaulted to the stall out of habit. A second group will give you something vague and then decline a meeting; those are your polite dismissals, and identifying them in sixty seconds instead of thirty days is the entire return. A third, smaller group will genuinely be early-stage researchers with a real future need and no current urgency. Don't disqualify that group — put them on a dated recall with a specific trigger ("call me after your Q1 planning wraps") and send nothing in the meantime.

A practical measurement setup: add a single CRM field capturing whether the "send me info" moment produced a named problem, a booked meeting, both, or neither. Four values, one picklist. After sixty days you can compute the second-conversation rate for each bucket and stop arguing about the technique from anecdote. This is also the cleanest way to coach it — a rep whose picklist is 80% "neither" is either not running the pivot or running only move two.

One more range worth knowing: the curated single-asset send. When a meeting is booked and you do send material, one focused piece attached to a calendar invite outperforms a multi-asset packet, for a boring reason — the prospect reads it or doesn't, and a single page is likelier to get read in the two minutes before a call than a nine-page PDF. Keep the asset under two pages and reference one specific section in the invite body.

Where the technique costs you, and what else you could run

No technique is free, and pretending otherwise is how good ideas get discredited in a rollout.

The cost of the pivot. You will lose a small number of legitimate opportunities from people who genuinely wanted to skim something before spending time with a vendor. Procurement-driven buyers, technical evaluators building a longlist, and anyone operating under a formal RFP process often cannot give you a problem statement even when the need is real — organizational rules forbid it, or they haven't been told yet. Running the pivot hard against that population reads as evasive and can get you scratched from the list. Weinberg's method is built for outbound-created, seller-led conversations. In buyer-led, process-governed situations, comply with the request, comply fast, and fight for the meeting on a different axis.

The alternative that competes with it. The "give freely, track engagement" school says: send the material immediately, instrument it, and let behavior qualify the prospect. If they open the doc three times and forward it internally, you have a signal no verbal answer could give you. This works — but it requires content genuinely worth reading, tracking infrastructure, and enough volume for behavioral signals to mean anything. It also cedes timing control entirely to the buyer. For a rep working a defined territory with a quota and forty accounts, the pivot is the better bet. For a self-serve or PLG motion with thousands of touches, engagement tracking scales where a phone conversation cannot.

The middle path. Send a deliberately incomplete asset — a one-page framework, a diagnostic checklist, a short benchmark excerpt — that is useful on its own but obviously implies a conversation for the applied version. This preserves goodwill, satisfies the literal request, and manufactures a legitimate reason to call back. It's slower than the pivot and softer than pure engagement tracking, and it works well with senior buyers who resent being handled.

The routing question at B is the one to teach. Most rollouts of any objection-handling technique fail because reps apply it universally, hit the population it was never built for, and conclude the technique is broken. It isn't broken; it's scoped. A rep who can name which of the three lanes a conversation is in will outperform one who runs the same script into all of them.

There's a downstream effect worth flagging as well. Teams that adopt this consistently see their marketing content requests change shape. When reps stop sending generic packets, the demand shifts from "give us a brochure" to "give us six one-page pieces, each mapped to a named operational problem." That's a better content library, and it's a genuine strategy change the pivot produces almost as a side effect.

The failure modes that show up in week two

Running move two without move three. By far the most common. The rep asks a sharp diagnostic question, gets a good answer, feels the conversation improve — and then says "great, I'll send that over today." The pivot without the calendar ask is just a nicer-sounding version of the original mistake. In role-plays, score only the calendar ask; the question takes care of itself.

Turning the question into an interrogation. Two diagnostic questions is a conversation. Four is a screening call the prospect didn't agree to. The pivot is one question, maybe a clarifier, then the ask. Reps who love discovery tend to over-extend here and burn the goodwill that move one bought.

Weaponizing the takeaway. "Sounds like this isn't a priority" delivered with an edge is a threat, and prospects hear it instantly. Delivered flat and genuinely curious, it's an off-ramp that people take honestly. Tone carries this line entirely — the words are neutral and the delivery is not.

Sending nothing at all. Some reps read the technique as "never send information" and start refusing the request outright. That's a misread and it will cost deals. The rule is never send information *without a commitment*, and when a commitment exists, send promptly and send something good. A rep who books the meeting and then sends a sloppy packet has wasted the technique.

Skipping the frame upstream. The pivot is cleanest when it never has to fire. Openings that lead with capabilities — "we're a platform that does X, Y, and Z" — practically request a brochure, because you've described an artifact and the natural response is "show me the artifact." Openings that lead with a named problem in the prospect's world produce fewer info stalls in the first place. Audit your own call recordings: if the stall rate is high, the opener is usually the cause, not the objection handling.

No system for the "real but early" bucket. Reps trained hard on disqualification start throwing away legitimate future pipeline. Build a dated-recall habit with a specific trigger event, and hold the material until that date. Sending the packet to a not-yet buyer just guarantees they'll have forgotten you by the time the need is real.

Coaching it from anecdote. Without the CRM field described earlier, every conversation about this technique degenerates into competing war stories. Instrument it in week one and the coaching writes itself.

Related questions

Does the pivot work over email as well as on the phone?

Yes, with less leverage. Reply immediately: "Happy to — so I send the right thing, what's the piece you're trying to solve?" You lose real-time pressure and the prospect can simply not answer, which is itself a qualifying signal worth recording.

What if the prospect is a gatekeeper, not the buyer?

Adjust the question. Ask who internally raised the need and what they said, then offer to send material *they* can forward with a note. Gatekeepers rarely have the problem; they have the routing information, which is what you actually need.

How does this apply to renewals and expansion?

Nearly unchanged. "Send me the new package details" is the same stall. Trade the details for a fifteen-minute review of what changed in their usage, which is a legitimate reason to meet and a better setting to price anything.

Should managers script this word-for-word?

Script the structure, not the sentences. The three moves are fixed; the phrasing has to sound like the rep. Word-for-word scripts on this particular objection sound rehearsed precisely because the prospect is expecting a canned response.

FAQ

Is "send me info" ever a genuine request?

Sometimes — most often from evaluators building a vendor longlist under a formal process, or from technical staff who need specs before they can even frame a question. The pivot still costs nothing to try, but if the answer reveals a process-governed buyer, comply quickly and pursue the meeting on a separate track.

Won't asking a question make me sound like I'm dodging?

Only if you skip the agreement step. "Absolutely, happy to send that" followed by a service-framed question reads as thoroughness. Going straight to the question, or hedging before agreeing, reads as evasion. The order is doing the work.

What do I do when they insist on the info with no meeting?

Name the stall once, gently, and accept the answer. If they still want only the artifact, send one focused piece — not the full library — and set your own recall date rather than asking for theirs. You've spent five minutes instead of forty, which was the goal.

Does this apply to inbound leads who requested the info themselves?

Yes, though the pivot softens. They've already signaled intent by filling the form, so the question becomes narrower: "what prompted you to look at this now?" The timing answer is usually more useful than the problem answer for inbound.

How long before a team gets good at this?

Reps generally get move one and move two within a couple of weeks of role-play. Move three — the calendar ask under mild resistance — takes longer, because it's the part that risks a no. Coach to the calendar ask specifically and expect a slower curve there.

Will my pipeline numbers look worse after adopting this?

Almost certainly, in count terms. Fewer opportunities get created because the polite stalls stop converting into records. Tell leadership before you start, and pair the rollout with the second-conversation-rate metric so the drop reads as cleanup rather than decline.

Sources

• https://mikeweinberg.com/
• https://www.harpercollinsleadership.com/
• https://www.sandler.com/blog/
• https://blog.hubspot.com/sales
• https://www.rainsalestraining.com/blog
• https://www.saleshacker.com/
• https://hbr.org/topic/subject/sales
• https://www.linkedin.com/business/sales/blog

Related on PULSE

• [How can *New Sales. Simplified.* help you win back a prospect who ghosted you after the first meeting in 2027?](/knowledge/bs0387)
• [What's the main takeaway from *New Sales. Simplified.* for overcoming call reluctance in 2027?](/knowledge/bs0374)
• [What's the best cold-calling template from *New Sales. Simplified.* for 2027?](/knowledge/bs0360)
• [How do you use *New Sales. Simplified.* to overcome the "no decision" stall?](/knowledge/bs0346)
• [What sales script does *New Sales. Simplified.* recommend for cold calls in 2027?](/knowledge/bs0330)
• [New Sales. Simplified. by Mike Weinberg — Cliff Notes Summary for AEs](/knowledge/bs0230)