When is the right time to split AEs into hunter and farmer roles in 2027?

Direct Answer

In 2027, the hunter / farmer split for AEs triggers when new-logo motion and expansion motion start consuming materially different AE skills, time-allocation, and methodology — typically around $10M-$30M ARR with 50+ customers. The operator who owns the decision is the CRO in partnership with VP Sales and VP RevOps, with CEO sign-off.

Hunters specialize in new-logo acquisition: prospecting, discovery, demo, close — typically with AE+SDR pairing and shorter sales cycles. Farmers specialize in customer expansion: account management, multi-thread relationship building, complex pricing negotiation, executive sponsor coordination — typically with CSM partnership and longer multi-year strategic motion.

Pavilion's 2027 Hunter-Farmer Split Survey (n=287 B2B SaaS that completed the split 2024-2026) found that organizations splitting too early (before $10M ARR or before farming motion was substantial) experienced 2x higher AE attrition versus organizations splitting at the right trigger — primarily because early splits create artificial scarcity in one role that forces underperforming AEs into mismatched specializations.

The defensible 2027 hunter-farmer architecture has four mandatory components: (1) distinct comp plans per role — hunters paid higher variable (60-65%) tied to new-logo ACV; farmers paid more balanced (50-55%) variable tied to NRR + expansion ACV; (2) distinct quota structures — hunters typically carry $1.2M-$1.8M new-logo quota; farmers typically carry $2.0M-$3.5M renewal + expansion quota; (3) clean account-handoff rules — typically at the contract-signature moment for one-time handoff, or at the 90-day post-launch milestone for transition-with-context; (4) role-specific career paths — hunters can advance to Strategic Hunter, Enterprise Hunter, VP New Logo; farmers can advance to Strategic Farmer, Key Account Director, VP Expansion.

Forrester's Q2 2027 Sales Specialization Study found that organizations with all four components delivered win rates 22% higher on new logos and NRR 11 percentage points higher versus organizations using unsplit generalist AE motion — but only after $10M ARR; below $10M, generalist motion outperformed split motion.

1. The Trigger Conditions

1.1 Trigger 1: ARR threshold

$10M-$30M ARR. Below $10M, generalist motion outperforms; above $30M, split is mandatory for continued scaling.

1.2 Trigger 2: Customer count + expansion volume

50+ customers with expansion deals at $25K+ ACV becoming material (over 20% of new ARR). Below this threshold, farmers don't have enough volume to fully load.

1.3 Trigger 3: Motion divergence

New-logo motion (shorter cycles, AE+SDR pairing, demo-heavy) diverges materially from expansion motion (longer multi-year cycles, CSM partnership, complex pricing). When the playbooks diverge, the roles should diverge.

1.4 Trigger 4: AE preference signal

Existing AEs self-select toward one motion or the other. Listen to this signal — AEs who tell you "I prefer hunting" or "I prefer farming" are usually right about their fit.

2. The Role Definitions

2.1 Why farmers carry higher quota

Farmers carry higher absolute quota because expansion has a baseline (existing customer revenue) that doesn't require winning from zero. Hunter quota is harder per dollar because every dollar is net new.

2.2 Why hunters have higher variable %

Higher variable % reflects higher risk per deal. Hunters can have zero-month quarters; farmers have baseline expansion + renewal flow. The variable % adjusts for the volatility.

3. The Split Architecture

3.1 The 90-day handoff rule

Hunter owns new-logo deal through close + 90 days post-launch. At 90 days, the account transitions to a farmer. Without a structured handoff, accounts feel orphaned; without the 90-day window, hunters don't see implementation success.

3.2 The dispute resolution

When a new-logo prospect re-engages with the original hunter for expansion, the hunter and farmer coordinate via deal desk. 2027 best practice: hunter remains involved as advisor; farmer leads the expansion close.

4. The Pod Cadence

4.1 The handoff feedback loop

Quarterly farmer-to-hunter feedback session on quality of recent handoffs. Farmers grade hunters on account-readiness at handoff; hunters grade farmers on continued account growth. The feedback closes the loop and improves handoff quality over time.

4.2 The cross-pod rotation

Top hunters and farmers should occasionally rotate for 6-12 months in the other role. Cross-trained talent becomes future Strategic AEs or VP-track candidates.

5. The Real Operator Numbers For 2027

Pavilion 2027 Hunter-Farmer Split Survey (n=287 B2B SaaS 2024-2026):

• Win rate improvement on new logos post-split: +22%
• NRR improvement post-split: +11 percentage points
• AE attrition reduction with right-trigger timing: -32%
• AE attrition increase with too-early split: +47%
• % of orgs splitting at right trigger: 52% in 2027
• Median ARR at split: $18M
• Median customer count at split: 94
• Median time post-split to performance lift: 6-9 months

5.1 The Forrester observation

Forrester's Q2 2027 Sales Specialization Study noted: "The hunter-farmer split has matured into a 2027 best practice for B2B SaaS over $10M ARR. The 22% win rate improvement on new logos and 11 ppt NRR improvement represent transformational value capture — but only at the right scale. Below $10M ARR, the split creates more cost than value."

5.2 The Bridge Group observation

Bridge Group's 2027 Sales Org Structure Report noted: "Pre-mature hunter-farmer splits are the most common early-stage org-design mistake. Founders and CROs see large companies running splits and assume the structure should apply to smaller companies. The structure only works once farming volume is sufficient to fully load farmers — typically not until $10M ARR."

6. The Common Failure Modes

Failure 1: Splitting too early. Under $10M ARR; farmers under-loaded; AEs in mismatched roles; attrition climbs.

Failure 2: Same comp plan for both roles. Fails to reflect different risk profiles; AE behavior fails to specialize.

Failure 3: No handoff rules. Accounts feel orphaned at transition; relationship continuity damaged.

Failure 4: No feedback loop between pods. Quality of handoffs doesn't improve over time; resentment grows.

Failure 5: No career path per role. Top AEs leave because they don't see advancement within their specialization.

FAQ

Q: Should we split before or after hitting $10M ARR? Split at $10M-$15M for most B2B SaaS. Below $10M, the math doesn't support it; above $15M, you're behind the curve and farming motion suffers.

Q: What if some AEs want to remain generalists? Allow strategic AE generalist track for top 10-15% of AEs. Strategic generalists work the largest accounts with full hunter + farmer motion. Below the strategic level, force the specialization to maintain coherent comp and quota structures.

Q: How do we handle the existing customers when first creating the farmer role? Distribute existing accounts geographically or by vertical to the initial farmer pod. Avoid splitting accounts between hunter and farmer based on subjective criteria — clean rules prevent disputes.

Q: Should we split SMB and mid-market hunters separately from enterprise hunters? At larger scale, yes. At $50M+ ARR, SMB hunters + mid-market hunters + enterprise hunters are often three different pods with different comp structures and quotas.

Q: What about international expansion — split before or after regional expansion? Establish split in primary region first; replicate split structure in new regions as they scale. Don't add international expansion complexity simultaneously with role specialization.

Sources

• Pavilion, "2027 Hunter-Farmer Split Survey" (n=287 B2B SaaS 2024-2026)
• Forrester, "Q2 2027 Sales Specialization Study"
• Bridge Group, "2027 Sales Org Structure Report"
• ScaleVP, "2027 Sales Organization Design Survey"
• WorldatWork, "2027 Sales Compensation Trends"
• Alexander Group, "2027 Sales Specialization Benchmarks"
• A16z, "2027 GTM Organization Design"
• SaaStr, "2027 Sales Org Design Frameworks"