What question should I ask a struggling rep to assess their prospecting efficiency versus effort?

What the question measures and why it matters

This single question works because it collapses three hidden variables into one narrative the rep cannot fake: selection quality, reach breadth, and response velocity. An efficient rep can name the trigger behind every account—a funding round, a new VP hire, a competitor's product sunset, a G2 comparison view, a job posting that implies a tooling gap. A struggling rep who is merely busy will say "it was on my list" or "the territory got assigned to me." That single difference is most of the diagnosis, and you hear it in the first two minutes.

Effort is easy to see and easy to fake. Activity dashboards in Salesforce, Outreach, and Salesloft happily show 300 emails and 60 calls a week, and a struggling rep will point at those numbers as proof of hard work. But activity volume is a vanity metric when reply rates sit under one percent, which is common for untargeted cold outreach in crowded B2B categories. The question you ask has to route *around* the activity counter and land on the decisions upstream of the activity—because that is where prospecting efficiency actually lives, and where effort and efficiency finally diverge.

For a RevOps leader, the stakes are practical. A rep working 45 hours a week on the wrong 100 accounts will almost always lose to a rep working 30 hours on the right 40. If you manage only the effort number, you push the struggling rep to spray more, which lowers reply rates further and burns the domain reputation of your whole sending team. The right diagnostic question reframes the conversation from "do more" to "choose better," and it hands you evidence—the rep's own account list—instead of opinion or a defensive story.

Crucially, this is a coaching instrument, not a gotcha. When you ask a rep to walk you through ten real accounts, you are not testing whether they hit a quota; you are watching how they think. You learn whether they understand their own funnel, whether they can articulate a buying thesis, and whether they treat prospecting as a search problem (find the accounts already in motion) or a persuasion problem (convince cold accounts to care). The former is efficient and compounds; the latter is exhausting and rarely scales past a lucky quarter.

The step-by-step process for running the conversation

Run this as a structured 30- to 45-minute working session, not a drive-by in a standup. Have the rep pull their actual CRM and sequencer data on screen so you are reacting to reality, not memory. The flow below moves from a neutral opening through signal, breadth, and velocity, and ends on a concrete two-week experiment so the session produces evidence rather than advice.

Step one — set the frame. Tell the rep plainly: "I'm not counting your activity today. I want to understand how you pick and work accounts." This lowers defensiveness so the answers are honest instead of rehearsed. Ask about their *best* account first, not their worst—it primes an open, non-cornered tone.

Step two — probe selection. For each account ask, "What made you choose this one?" Listen for a *specific, recent, account-level* reason versus a generic firmographic filter ("they're mid-market SaaS"). Specific triggers are the marker of efficiency because they mean the rep is hunting accounts already showing motion, not working an alphabetized territory list top to bottom.

Step three — probe breadth. Ask, "How many people did you actually reach at this account, and in what roles?" A struggling rep almost always over-indexes on one friendly contact—often a champion with no budget authority. Efficient reps multi-thread deliberately across an economic buyer, a technical evaluator, and a champion before they expect real momentum, typically three-plus contacts per target account.

Step four — probe velocity. Ask, "In the first few days after your first touch, who responded?" You are looking for whether outreach *lands*, fast. Slow or single responses usually mean the message wasn't relevant to that role, or the account wasn't actually in a buying window when the rep touched it. Fresh intent decays quickly, so first-week reply behavior is the tell.

Step five — convert to an experiment. Whatever the gap, end with a bounded test: "Pick 20 accounts that each have at least one real trigger signal. Spend more of your week on research than on sends. Multi-thread three roles per account. We review the reply pattern in two weeks." Bounded experiments beat abstract advice because they produce a data point you can both look at, and they tell you fast whether the rep can adapt.

Costs, timelines, and typical ranges

The direct cost of this diagnostic is close to zero—it's one recurring 1-on-1 slot—but the surrounding decisions carry real budget and time implications, so set expectations honestly with the rep and with your own leadership.

Time to first signal. You will usually know within the *first three or four accounts* whether the rep's problem is selection, breadth, or velocity; the pattern repeats. You do not need to grind through all ten if the first several already show, say, no nameable trigger on any account. That repetition *is* your answer, and stopping early keeps the session a coaching moment rather than an audit.

Time to behavior change. Plan for a realistic ramp. Shifting from send-first to research-first typically takes several weeks of deliberate practice before it feels natural, and one to two full sales cycles before it shows in pipeline. Do not expect a struggling rep to flip in a week; expect the *inputs* (signal quality, multi-threading) to change fast and the *outputs* (meetings, pipeline) to follow with a lag you should not panic over.

Research-to-outreach split. A useful rule of thumb: struggling reps often invert their time to roughly 70% sending and 30% researching. Nudging that toward a 50/50 or even 60/40 research-heavy split is where efficiency gains come from. More research means fewer, better-aimed touches rather than more identical touches—the entire point of the exercise.

Tooling costs. If the diagnosis reveals a genuine *data* gap—the rep has no way to see intent or map an org chart—then you're looking at stack spend, not a performance plan. Intent and data platforms such as 6sense, Demandbase, ZoomInfo, Cognism, Apollo, or Clari range widely in price by seat and data volume, and enterprise intent tools are a meaningful annual line item. Try the cheaper path first: free and near-free signals—LinkedIn job changes and hiring posts, company blog and press announcements, public funding news via Crunchbase, and product-review activity on G2—can carry a rep a long way before you commit budget.

Effort ceiling. Be candid that effort has diminishing returns. Past a certain weekly volume, adding more sends to untargeted accounts lowers reply rates and can degrade deliverability for the whole team's domain. The honest framing for a rep: extra hours only pay off if they go into *better selection*, not more *identical sends*. That reframes overtime from virtue to potential liability.

Where teams get it wrong

The most common mistake is managing the activity number instead of the decision behind it. When a rep struggles, the reflex is "increase your call and email targets." This treats a precision problem as a volume problem and usually makes things worse: lower reply rates, damaged sender reputation, and a demoralized rep now working harder for the same or worse results.

A second failure is accepting a friendly single-thread as progress. Reps love a warm champion, and managers often reward the resulting activity. But a champion without an economic buyer and a technical evaluator is a stalled deal waiting to happen. If the diagnostic reveals the rep reached only one person at nine of ten accounts, the coaching is breadth, full stop—no amount of extra sends to that one champion fixes a missing committee.

Third, teams confuse effort with commitment and inefficiency with laziness. These are different problems with different fixes. A rep spending 20+ focused hours a week prospecting but getting nowhere is inefficient—coach the process. A rep spending under 15 hours a week actually prospecting has a focus or motivation problem—coach the calendar. The walk-through-ten-accounts question surfaces inefficiency; a calendar audit surfaces the other. Applying the wrong remedy wastes weeks.

Fourth, leaders run the conversation as an interrogation. If the rep feels the exercise is a setup for a PIP, they'll rationalize every account and you'll learn nothing real. Frame it explicitly as joint problem-solving. The goal is to make the rep's own reasoning visible so you can improve it together, not to build a case file.

Fifth, and subtly, teams skip the bounded experiment and end on advice. "Be more targeted" is not actionable. "Pick 20 signal-backed accounts, multi-thread three roles, and let's review the reply pattern in two weeks" is. Without the experiment, you have a pleasant conversation and no evidence of whether the rep can actually adapt—which is the exact thing you most need to know before deciding their future.

Finally, teams assume the gap is always the rep. Sometimes the walk-through reveals that no one gave the rep intent data, a defined ICP, or working sequences—that's a RevOps and enablement gap, not a performance gap. If three reps all fail the same way, stop coaching individuals and fix the system feeding them; individual coaching cannot out-run a broken input layer.

Decision framework: when to choose what

Once you've run the diagnostic, the gap you found dictates the intervention. Don't reach for a performance plan when the real issue is missing data, and don't buy a new tool when the issue is a coachable habit. Use the branch logic below to match the fix to the finding, then re-run the identical walk-through to judge progress on inputs first.

The decision rule is simple: isolate the single biggest gap, fix that one thing, re-run the same walk-through in two weeks, and judge on inputs first. If the rep's *selection and breadth* improved—even before meetings do—you have a coachable rep and a lagging output. Keep going. If the inputs did not move and the rep genuinely had access to signals, targets, and working sequences, then you're looking at a fit or effort issue, and a structured improvement plan is the honest next step. The framework keeps you from firing a coachable rep or coaching a systemic problem forever—the two most expensive errors a RevOps leader makes here.

Related questions

How is this different from just checking a rep's activity metrics?

Activity metrics count outputs—emails sent, calls dialed. This question interrogates the *decisions* upstream of the activity: which accounts, how many contacts, how fast the replies. Two reps with identical activity can have opposite efficiency, and only the walk-through reveals which is which.

What if the rep gets defensive during the walk-through?

Reframe openly: "I'm not counting your activity—I want to see how you pick accounts so I can help." Ask about their *best* account first, not their worst. Curiosity, not judgment, gets honest answers and turns the session into shared problem-solving instead of a tribunal.

Should I ask this to my strong reps too?

Yes. Running it with top performers surfaces the patterns worth teaching and gives you a benchmark for what "good" looks like on your team. It also normalizes the exercise so struggling reps don't feel singled out when their turn comes around.

How often should I run this diagnostic?

For a struggling rep, every two weeks during a turnaround so you can see whether inputs move. For the broader team, monthly is usually enough. Running it too often turns coaching into surveillance and erodes the trust the exercise depends on.

What single follow-up question reveals the most?

"What did you do to pull in the second and third stakeholder?" Reps who say "I waited for my champion to loop them in" are relying on hope. Reps who describe a deliberate multi-thread are working efficiently, regardless of their raw activity numbers.

FAQ

Isn't asking about ten accounts too time-consuming for a regular 1-on-1? You rarely need all ten. The pattern—strong signals or none, multi-threaded or single, fast replies or silence—usually shows by the third or fourth account. Budget 30 minutes, and treat the walk-through as periodic deep coaching, not a weekly ritual.

What if the rep genuinely has no intent data or tools? Then the gap is your stack, not the rep. Before buying anything, teach free signals: LinkedIn job changes and hiring posts, funding announcements, leadership moves, and public product-review activity. If the whole team is blocked the same way, prioritize the tooling or enablement fix over individual coaching.

How do I tell an inefficient rep apart from a lazy one? Pair this question with a calendar audit. A rep spending 20+ real hours prospecting with poor results is inefficient—coach the process. A rep spending under 15 hours actually prospecting has a focus problem—coach the calendar and motivation. Same symptom, different root cause, different fix.

Won't a savvy rep just tell me what I want to hear? That's why you make them open the CRM and sequencer live. Narratives can be polished; the account records, contact counts, and reply timestamps can't. React to the data on screen, not the story around it.

Does this apply to inbound or product-led motions, not just cold outbound? Yes, with a twist. For inbound and PLG, the "signal" is often a first-party action—a trial sign-up, a pricing-page visit, a usage threshold. The same three lenses hold: did the rep pick high-intent accounts, reach the full buying group, and respond fast while intent was fresh?

What if the whole team fails this diagnostic the same way? Stop coaching individuals and fix the system. Uniform failure means a missing ICP definition, no shared signal source, or broken sequences. That's a RevOps and enablement problem, and no amount of one-on-one coaching will out-run a broken input layer.

Sources

• Gartner: The B2B Buying Journey
• Forrester: Sales Research and Insights
• Gong Labs: Data-Backed Sales Research
• MEDDIC Academy: The MEDDPICC Sales Qualification Methodology
• HubSpot: What Is Sales Prospecting
• 6sense: Buyer Intent Data Guide
• McKinsey: Growth, Marketing, and Sales Insights
• Harvard Business Review: Sales

Related on PULSE

• [How do you frame a question that encourages a struggling rep to self-identify their weakest skill without feeling blamed?](/knowledge/cg0866)
• [What specific question can you ask a new sales rep in their first week to assess their understanding of your product's top three differentiators?](/knowledge/cg0856)
• [Top 10 Questions to Ask a Struggling Sales Rep During a 1-on-1](/knowledge/cg0909)
• [What are the most effective open-ended questions to ask a struggling sales rep during a coaching session?](/knowledge/cg0806)
• [How do you spot a struggling remote rep before it's too late?](/knowledge/cg0190)
• [How do you coach a rep who's struggling during onboarding?](/knowledge/cg0014)