How do you coach a hunter to handle account management duties?

What account management actually asks of a hunter, and why the gap shows up

A hunter is optimized for a specific loop: identify a target, create urgency, compress a decision, move on. That loop has a clean finish line — signature, commission, next name on the list. Account management has no finish line. It has a renewal date that arrives whether or not anyone did the work, and an expansion opportunity that only exists if somebody went looking for it. When you ask a hunter to own a book of business, you are not asking them to work harder; you are asking them to work on a timeline that gives them no dopamine for eleven months and then punishes them in month twelve.

That mismatch produces four recognizable failure patterns, and you should name which one you are looking at before you open your mouth in a 1:1.

Post-close disappearance. The rep closes, does a perfunctory handoff to onboarding or CS, and vanishes. The customer's next contact from the account owner is a renewal email sixty days out. By then the champion may have changed roles, the original use case may have quietly stalled, and the rep is negotiating from zero information.

Transactional QBRs. The rep does show up quarterly, but the meeting is a usage-stats slide and a "how's everything going?" The customer nods, says everything's fine, and the meeting ends in twenty minutes. Nothing was discovered, no new problem surfaced, no next deal created. A QBR that generates no pipeline is a calendar entry, not a motion.

Single-threading. The account has exactly one relationship: the person who signed. Hunters are frequently excellent at building one deep champion relationship — that's how they closed the deal — and terrible at the unglamorous work of meeting the champion's boss, the champion's peer in another division, and the operations person who actually uses the product daily. When that one contact leaves, and in most B2B categories a meaningful share of buyer contacts change roles within a year, the account is effectively cold.

Expansion blindness. The rep genuinely does not know what else the customer could buy, because they stopped being curious the day the contract was signed. They can tell you what the customer bought. They cannot tell you what the customer's CFO is worried about this year, which division just got a budget increase, or which competing vendor is up for renewal in Q3.

The diagnostic question is not "is this rep good or bad at account management." It's *which of four things is broken*: will (they find the work boring and choose new logos instead), skill (they'd do it if they knew how to run a real QBR or build an expansion business case), knowledge (they don't understand the customer's business well enough to see the opportunity), or system (the comp plan and the CRM and the territory design all tell them accounts don't count). Those four demand completely different responses, and coaching a system problem as if it were a will problem is the single most common manager error in this scenario. If comp pays 100% on new logos and nothing on expansion or retention, the hunter is behaving rationally. You cannot coach someone out of responding correctly to their incentives.

There's a related trap worth naming: sometimes the honest answer is role design, not coaching. Some reps are genuinely better deployed as pure new-logo acquisition, and forcing a book of business onto them produces a mediocre farmer and a wasted hunter. That's a legitimate conclusion — but you should reach it after a real coaching attempt with a real plan, not as a first-week shrug. The bar is roughly one full quarter of structured coaching with an inspected cadence before you conclude the person is miscast.

The step-by-step coaching process, from diagnosis to independent operation

Run this as a sequenced program, not a series of pep talks. The sequence matters because reframing without a plan produces enthusiasm that evaporates in nine days, and a plan without reframing produces compliance theater.

Step one: gather evidence before the conversation. Pull three things. First, the account's activity history from the CRM — when was the last logged proactive touch, and was it substantive or a "just checking in" email? Second, a recorded QBR or customer call from the last quarter (Gong, Chorus, whatever your team records with) — you want to hear the rep's actual conversational pattern, not their self-report. Third, the account's contact map — how many people, in how many functions, have been engaged in the last ninety days? Walking into the 1:1 with observed specifics changes the conversation from an opinion exchange into a review of facts.

Step two: run a GROW conversation anchored to one real account. Do not coach the abstraction. Pick one neglected-but-promising account and make the whole session about it. Speak the hunter's language throughout — pipeline, target, territory, prize — and avoid the words that will lose them instantly: maintenance, upkeep, relationship management, checking in.

For *Goal*, reframe: "You're excellent at the chase. What if your easiest pipeline this year is sitting inside three accounts you already won — would you want to go get it?" Follow with the arithmetic: what would doubling three existing accounts do for your number versus closing three cold logos, and which takes less effort?

For *Reality*, surface the facts you gathered without prosecution: "When did you last talk to this account, and what do you actually know about where their business is heading?" Then: "How many teams or divisions there could use us that you've never touched?" And the risk question that lands hardest: "If your champion left tomorrow, who else there knows us, and what does that do to the renewal?"

For *Options*, convert the account into targets: "What's the whitespace here — a new team, a new use case, an upsell — and which is the biggest prize?" Then: "What would a QBR look like if you ran it as a discovery call for expansion instead of a status update?"

For *Will*, get a specific commitment with a date: "Which account do you re-engage this week, and what expansion are you going after?" Mirror it back verbatim so there's no ambiguity about what was agreed.

Step three: install the account plan the same week. Momentum decays fast. The plan should take thirty minutes to fill out, not three hours — more on the format below.

Step four: practice the motion before it goes live. Role-play the QBR with you playing a skeptical customer exec. Run it repeatedly until the rep opens with the customer's business outcomes rather than a product usage chart, and until they can surface a new problem without it sounding like a pitch.

Step five: inspect on a fixed cadence. Weekly for the first month, biweekly after. Inspect the artifacts — the plan, the booked meetings, the new stakeholders — not the rep's feelings about the work.

Step six: measure and graduate. When expansion pipeline is being created without your prompting and the account plans update themselves monthly, move from coaching to normal pipeline review.

The one-page account plan and the QBR that generates pipeline

Hunters do not fill out heavy account plans. Hand a rep a template with a SWOT grid, a stakeholder influence matrix, and a competitive landscape section and it will be completed once, badly, and never again. The plan has to be short enough to finish in a single sitting and structured so that filling it out *feels like building a target list* — which is the one form of planning hunters do voluntarily.

Three sections. The Target: what new problem, department, or use case is the most likely expansion path, stated as a specific sentence — "the marketing ops team is unhappy with their current tool and their contract ends in Q3" beats "explore marketing." The Allies: two or three named people inside the account who already see value and can open a door, with what each one cares about. The Win: the specific next deal — approximate size, approximate timing, and the one thing that has to be true for it to happen.

That's it. One page. Updated monthly in the 1:1, which takes ten minutes because the rep is editing, not authoring. The plan's real function is psychological: it converts an account from a maintenance obligation into an opportunity with a target on it, and it gives the rep a legitimate reason to call the customer that isn't "just checking in" — the single phrase that makes both parties dread the meeting.

The QBR is where the plan gets executed, and most QBRs are broken in the same way: they're reporting exercises. The rep presents usage numbers, the customer confirms the numbers are accurate, and everyone leaves. Nothing was learned.

A QBR that creates pipeline follows a different shape. Open with the customer's business, not yours: what changed in their world this quarter, what the priorities are for next quarter, what's getting funded and what's getting cut. Spend the first third of the meeting asking rather than presenting. Only then connect what you've heard to results the customer has achieved, framed in their metrics rather than your feature names. Close by explicitly asking about the adjacent problem — "you mentioned the support team is drowning in tickets; who owns that, and would it be useful to bring them into a conversation?" That question, asked consistently, is the entire mechanism by which expansion pipeline gets created.

Practically: book QBRs at least three weeks out, send an agenda that asks the customer what *they* want covered, and bring one person from your side who isn't the rep — a solutions engineer, a CS lead, an executive sponsor. That last move does double duty: it improves the meeting and it starts multi-threading on your side of the table, which matters when the rep eventually changes roles.

Three drills accelerate all of this. The expansion-discovery drill: give the rep an account and thirty minutes to list every team, use case, and adjacent problem, then rank them — this is target-list building, their native skill, pointed inward. The multi-thread drill: map the single-threaded accounts and draft the actual outreach to a second and third stakeholder, including the specific reason that person should care. The call-review drill: pull a recorded QBR and have the rep identify the exact moments where they took a status-update path instead of a discovery path. Self-identification sticks far better than your correction.

Costs, timelines, and what good looks like on a real calendar

The honest cost of this coaching is manager time, and it's front-loaded. Budget roughly two to four hours per rep in the first month: the evidence-gathering pass on a couple of accounts, one extended GROW session, a plan-building session, and two or three QBR role-plays. After the first month it drops to about thirty minutes a week — ten minutes of plan review inside the existing 1:1, twenty minutes of call review every other week. That's a real cost for a manager carrying six to eight reps, which is why you sequence reps rather than launching the program across the whole team simultaneously.

On the rep's side, the time commitment is smaller than they fear, and telling them the number up front removes a lot of resistance. Thirty minutes to build each account plan, ten minutes monthly to update it, and roughly ninety minutes of prep and delivery per QBR. For a rep carrying fifteen to twenty accounts where only the top five to eight warrant a formal plan, that's a few hours a month — a fraction of what they spend on cold prospecting for equivalent pipeline.

The timeline runs on a rough 30/60/90 rhythm. In the first thirty days you're co-building plans for the top three accounts, reframing each one as a hunt, and reviewing one recorded QBR together. Expect the rep to be skeptical and slightly performative — that's normal. In days 31 to 60 the rep runs a value-led QBR with you observing, builds a multi-threading plan, and you start tracking proactive touches and new stakeholders engaged. This is where the behavior either takes or doesn't. By days 61 to 90 the rep runs plans independently, and you shift from coaching the motion to auditing outcomes: expansion pipeline created, renewal engagement lead time, retention on their book.

What to measure, in rough priority order. Net revenue retention and gross retention on the rep's book — the outcome metrics, lagging by a full renewal cycle, so useful for annual assessment but useless for weekly coaching. Expansion pipeline created — opportunities sourced inside existing accounts; this is the leading indicator that tells you within a few weeks whether the coaching is working. Proactive touches — substantive contacts made well before renewal, not the reflexive check-in email. Multi-threading depth — stakeholders engaged beyond the original champion, counted per account. QBR completion and quality — held on schedule, and scored against whether a new customer problem surfaced. Renewal engagement lead time — how many days before expiry the renewal conversation actually starts; neglect shows up here first and most reliably, because neglected accounts always produce late, panicked renewals.

Watch one specific pattern in the data: if proactive touches climb but expansion pipeline stays flat, the rep is *visiting* accounts rather than hunting inside them. They've complied with the cadence and skipped the substance. That's a coaching signal pointing directly at whitespace discovery, not at effort.

On comp — and this is where RevOps has to be a partner rather than a bystander — you rarely need a full plan redesign. A modest accelerator usually does the job: pay expansion revenue in an account the rep originally won at the same rate as new business, or add a retention multiplier where a book renewing above a defined threshold earns a bump on that quarter's new-logo commission. The design point is that the incentive should make account work feel like a lever that helps the rep hunt better, not a tax on their real job. The message a good plan sends is: you're still a hunter, your territory just got bigger. Any change here goes through RevOps and finance for modeling before it's announced — a well-intentioned accelerator that's mispriced creates worse problems than the neglect it was meant to fix.

Where teams get this wrong

Calling it maintenance. The vocabulary problem is not cosmetic. Words like maintenance, upkeep, servicing, and babysitting tell a hunter the work is beneath their skill level, and reps calibrate their effort to the status signal they're given. Land-and-expand, territory, whitespace, portfolio growth — same work, entirely different energy. Managers who fix nothing else but their vocabulary sometimes see behavior shift on that alone.

Diagnosing attitude when the problem is arithmetic. Covered above, but it bears repeating because it's the most expensive error. Before you coach a single behavior, read the comp plan and the territory design. If accounts don't pay and don't count toward quota, you're asking someone to volunteer.

No plan, so no target. A hunter without a target drifts, and drifting looks like neglect from the outside. The plan isn't bureaucracy; it's the thing that converts an obligation into a chase.

Coaching the account instead of the motion. If you spend six weeks rescuing one specific at-risk relationship, you have saved one account and taught nothing. The next account will be abandoned identically. Coach the repeatable pattern — how to find whitespace, how to run a QBR, how to multi-thread — using the specific account as the practice ground.

Inspecting nothing. If you never look at the plans, never review a QBR recording, and never ask about new stakeholders, the rep correctly concludes account work is optional. Inspection isn't distrust; it's the signal that the work counts.

Handing off to CS and calling it solved. A common structural move is to give accounts to customer success and let hunters hunt. That's a legitimate model, but it fails when the handoff is a wall rather than a seam. If CS owns adoption and the rep owns expansion, they need a shared account view, a shared definition of a qualified expansion signal, and a rhythm for passing them back and forth. Without that, expansion signals surface in CS conversations and die there because nobody's compensated to act on them.

Ignoring the CRM's role. If your system has no field for whitespace, no way to log a proactive touch distinctly from a deal activity, and no view that shows a rep their book by renewal date, then the tooling is quietly telling reps this work isn't real. That's a RevOps fix, and it's usually a small one — a couple of fields, one saved view, one dashboard.

Assuming the enterprise pattern transfers. Coaching a hunter on a book of eighty transactional SMB accounts is a fundamentally different problem from coaching one on six strategic enterprise accounts. The SMB version needs triage rules and a tiering system so the rep knows which twelve accounts get a plan and which sixty-eight get a light-touch motion. Applying an enterprise account-planning cadence to a large book produces either burnout or, more commonly, quiet abandonment of the entire program.

Decision framework: coach, restructure, or redesign the role

Not every version of this problem should be solved with coaching, and knowing which lever to pull saves a quarter. Work the decision in order — systems first, because a system fix is cheap and instant relative to behavior change, and because coaching against a broken system burns your credibility with the rep.

Start with comp and quota design. If expansion and retention carry no weight, fix that before anything else; the conversation you have afterward is a completely different conversation. Next, check territory and book size. A rep with too many accounts isn't neglecting them out of preference — they're triaging, correctly, and what they need is a tiering framework rather than a mindset intervention. Then check tooling and data: if the rep can't see their renewal calendar or log whitespace anywhere, fix the system.

Only after those three is it worth asking whether the gap is skill or will, and skill is the more optimistic and more common answer than managers assume. Plenty of hunters have simply never been taught what a good QBR sounds like, because nobody ever showed them one. That's a training problem with a two-week fix.

If systems are clean, skill has been taught, and the rep still won't do the work after a full quarter of inspected coaching — then you're looking at either a genuine role mismatch or a motivation issue that account coaching won't reach. Role redesign is a legitimate outcome: some organizations run pure hunters against new logos and hand every closed account to a named account manager, and that structure wins when new-logo volume is high and expansion motion is genuinely specialized. The mistake isn't choosing that structure; it's choosing it by default because coaching felt hard.

Related questions

How long before I know whether the coaching is working?

Roughly six to eight weeks. Expansion pipeline created inside existing accounts is your earliest reliable signal, well before retention numbers move. If proactive touches rise but no opportunities appear by week eight, the rep is complying with the cadence without doing the discovery.

Should hunters own accounts at all, or should CS take them?

Both models work. Hunters owning accounts wins when expansion is sales-led and the buying committee overlaps with the original deal. A split model wins at high new-logo volume. The failure mode isn't the model — it's a handoff with no shared account view or agreed expansion-signal definition.

What if the rep says account management isn't what they signed up for?

Take it seriously rather than treating it as insubordination. If the role genuinely changed after hire, acknowledge that plainly and negotiate. If it didn't, walk through the arithmetic of expansion pipeline versus cold pipeline for their number — that argument persuades hunters more reliably than appeals to customer relationships.

How many accounts can one rep realistically plan for?

As a rough working range, five to eight accounts can carry full plans with a quarterly QBR cadence. Beyond that, tier the book: full treatment for the top tier, a lighter check-in rhythm for the middle, and automated or CS-led coverage for the tail.

Does this coaching approach change for a rep who's been in the role for years?

The sequence is the same, but a tenured rep's neglect is more likely a system or will issue than a skill gap, so weight your diagnosis accordingly. Tenured reps also respond better to peer examples than to manager instruction — have them review a colleague's strong QBR recording.

FAQ

What's the single biggest mindset shift a hunter needs to make?

Seeing an existing account as pre-qualified territory rather than finished business. They already have a map, a guide, and permission to explore — everything cold prospecting lacks. The reframe that lands most reliably is asking them how they'd approach the account if they'd just inherited it as a brand-new territory.

How do I tell whether it's a will, skill, knowledge, or system problem?

Look at behavior and incentives together. Chasing new logos while accounts sit idle points to will. Inability to run a real QBR or build an expansion case points to skill. Not knowing where the customer's business is heading points to knowledge. Comp paying nothing for retention or expansion points to system — and that one you fix before coaching anything.

What's the fastest first step that produces visible movement?

Build one account plan, in the 1:1, together, in thirty minutes. Pick the account with the most obvious whitespace. Getting one concrete target on paper does more than three weeks of conversation about the importance of retention.

Can I coach this if the comp plan won't change?

Partially, and you should be honest with the rep about the limitation. You can teach the motion and appeal to their number — expansion pipeline is cheaper to create than cold pipeline, which is a genuine argument. But you'll get compliance rather than ownership, and it will decay whenever new-logo pressure spikes. Keep pushing RevOps on the accelerator in parallel.

How do I run a QBR that isn't a status update?

Spend the first third asking about the customer's business — what changed, what's funded next quarter, what's under pressure. Present results in their metrics, not your feature names. Close by naming an adjacent problem you heard and asking who owns it. That last question is what turns the meeting into pipeline.

When should I conclude the rep just isn't suited to this?

After a full quarter of structured, inspected coaching with the systems verified clean. If the plans exist, the motion has been taught and practiced, comp rewards the work, and the behavior still hasn't moved, role design is the honest answer — not a harsher version of the same coaching.

Sources

• Harvard Business Review — The New Sales Imperative
• Harvard Business Review — Sales coaching and performance research
• Gong Labs — sales conversation research
• RAIN Group — strategic account management research and insights
• Winning by Design — revenue architecture resources
• Gainsight — customer success and net revenue retention guides
• Salesforce — customer success and account growth articles
• McKinsey — growth, marketing and sales insights

Related on PULSE

• [How do you coach reps to handle silence and pauses on calls?](/knowledge/cg0180)
• [How do you coach salespeople to handle rejection?](/knowledge/cg0144)
• [Top 10 questions to assess a sales rep's pipeline management skills](/knowledge/cg0857)
• [Top 10 Questions to Assess a Rep's Time Management and Prioritization](/knowledge/cg0927)
• [Top 10 questions to assess a sales rep's time management habits](/knowledge/cg0877)
• [Top 10 questions to explore a rep's time management habits](/knowledge/cg0832)