Hunter vs. Farmer

What the Hunter vs. Farmer Model Is

Hunter vs. farmer is a sales org design framework that splits account executives into two roles based on motion: hunters close net-new logos, and farmers grow and retain existing accounts. The model exists because acquisition and expansion require different skills, different compensation structures, and different daily behaviors. Most companies separate the roles once the install base is large enough to warrant a dedicated expansion motion — roughly $3M–$8M in ARR for a SaaS business, though the threshold shifts based on average contract value and churn risk.

The hunter carries a net-new ARR quota. No credit for renewals, no credit for expansion in accounts they didn't originate. The farmer carries an expansion and renewal target — measured in net revenue retention, upsell ARR, or gross renewal rate depending on the org. Assign both motions to the same rep and they will quietly deprioritize whichever motion is harder that quarter.

How the Split Works in Practice

The dividing line is the account handoff point. A hunter closes a logo, the customer signs, and — depending on the model — the account moves to a customer success manager or a dedicated farmer AE anywhere from 30 days to 12 months post-close. Earlier handoffs protect hunter time but increase knowledge-transfer risk. Later handoffs keep the hunter embedded through implementation but bleed prospecting hours.

Pure hunter roles are rarer than job postings suggest. Most "hunter AE" titles include some named-account coverage, which is farming by another name.

Worked Example

A SaaS company at $9M ARR runs 7 AEs in a full-cycle model — each rep owns new logo and expansion. Average quota attainment sits at 58%. The VP of Sales segments the team: 5 hunters carrying $850k new-ARR quotas each, 2 farmers owning $4.5M in ARR across 38 accounts with a 112% NRR target.

Six months later: hunter attainment moves to 71% (no QBRs pulling them out of prospecting weeks). Farmer NRR climbs from 103% to 116% (focused coverage of at-risk accounts they previously ignored). The company didn't add headcount — it redirected existing attention.

When Sales Orgs Use the Hunter vs. Farmer Model

Series B and later, when install-base revenue is meaningful enough to protect. Before that, splitting the team fragments product intuition — hunters who never see customers post-sale sell features, not outcomes.

Revenue operations uses the model to separate pipeline creation metrics from expansion metrics. Pipeline sourced by hunters and pipeline sourced by farmers comes from structurally different motions. Mixing them obscures where growth is actually originating.

Recruiters and hiring managers use the distinction to set candidate expectations. "Hunter AE" signals cold prospecting, outbound sequences, and a territory with no existing customers. "Account Growth Manager" signals a book of business with relationships to manage. These are different jobs that attract different people.

Limitations and Common Gaming Patterns

The model collapses when territory design is wrong. A hunter assigned a 200-account territory where 80 are existing customers is doing account management whether the org admits it or not. Define "net-new logo" explicitly — some orgs count expansion into a new business unit of an existing parent as a new logo, which inflates hunter attainment without actually acquiring new revenue relationships.

Farmers face the opposite pressure. A farmer who manages accounts conservatively — keeping renewal rates high and upsell velocity low — can consistently hit 110% NRR on accounts that could reach 140%. Deal velocity in expansion accounts surfaces this: long time-to-upsell with high gross retention often signals deliberate underperformance, not healthy account stewardship.

The framework's deepest flaw: it assumes hunters can't farm and farmers can't hunt. In practice, the top 15% of reps in any cohort are competent at both. Rigid segmentation sometimes routes high performers into the wrong motion and calls the resulting underperformance a fit problem.