Hunter or farmer: is your B2B SaaS big enough to split the roles?

Every article about hunters and farmers asks the same question: which type should you hire?

I think it is the wrong question for most B2B SaaS companies, because it quietly assumes you are large enough to have both. Below a certain size you are not, and trying anyway gives you two half-busy people and a handoff where deals go to die.

The question worth asking is whether you are big enough to split at all.

What is the difference between a hunter and a farmer in sales?

A hunter brings in new business. Prospecting, first meetings, new logos.

A farmer grows what you already have. Onboarding, renewals, expansion, the relationship after the signature.

A full-cycle rep does both. They find the customer, close them, and keep them. One person, start to finish.

It is worth separating this from a different split you will also hear about, because people use the two interchangeably and they are not the same thing.

Split	What it separates	The two sides work on
Hunter vs farmer	New business vs existing accounts	Different customers
SDR vs AE	Prospecting vs closing	The same new deal

A B2B SaaS company can face both decisions independently. Both come down to the same thing: whether you have enough volume to keep a specialist busy.

Should one person do both jobs?

Below roughly $10M ARR, usually yes. And this is the thing most founders get backwards: they treat one rep doing both as a stage to escape, when it is the correct structure for their size.

Full-cycle reps are standard in B2B SaaS below roughly $5M to $10M ARR. Not because those companies cannot afford specialists. Because specialising at that size usually makes things worse.

The reason is coordination. Every split creates a handoff, and a handoff is not free. It needs three things:

• a shared definition of what counts as ready to hand over
• somebody to check whether each one meets that definition
• a way to settle it when the receiving side says the quality is poor

That machinery costs real time. Below roughly eight to ten sellers, it generally costs more than the specialisation returns.

Splitting roles before the volume supports it is the most common structural mistake early sales teams make. Not under-hiring. Splitting too soon.

Hunter vs Farmer Sales: When is a B2B SaaS team ready to split?

Four tests. You want at least three of them to pass, not one.

1. Is your deal size above $20,000 to $30,000?

The clearest single signal, and the one I would weight highest.

Above roughly $20,000 to $30,000 per contract, specialisation starts to pay, because the value of each deal covers two salaries and the time spent coordinating between them. Below that, the economics favour one person running the whole thing.

This is the same arithmetic that decides whether you sell product-led or sales-led, where the thresholds sit at roughly $5,000 and $25,000. Price point decides your structure more than preference does, and we set that out in the post on GTM motion.

2. Do you have eight or more sellers?

Specialists need volume. A prospector with four deals a quarter to feed is not a specialist, they are an expensive helper.

Under eight to ten sellers, you are usually paying for coordination you do not get back. Above it, the handoff starts earning its cost.

3. Is your sales process written down?

If your reps still need you in the room before a deal moves forward, there is nothing to hand off.

Splitting roles before the process is documented means splitting something that only exists in somebody’s head. The handoff gets improvised every time, which is the same as not having one. We covered how to build the written version from your own won and lost deals in the sales process post.

4. Can you point at the constraint?

“We should be more efficient” is not a reason. One of these two should be observably true:

• Your closers are losing measurable selling time to prospecting, and pipeline is the bottleneck rather than close rate.
• Your existing accounts are churning while everyone chases new logos, and nobody owns the base.

If you cannot say which one is happening, you do not have the problem that splitting solves.

The four tests at a glance

Test	Ready when
Deal size	Above roughly $20–30K per contract
Team size	Eight or more sellers
Process	Written stage criteria somebody else can apply without you
Constraint	You can point at one, with evidence

If fewer than three of those pass, one rep doing both jobs is still the right answer, and splitting will cost you a quarter.

What happens if you split too early?

I want to be specific here, because “it does not work” is not useful. It fails in two recognisable ways, and the second is worse.

Failure one: the SDR who books meetings you still have to take

A founder at around $500K ARR decides they are too busy to prospect, and hires an SDR.

For three to six months, the SDR books meetings the founder has to attend anyway, because the SDR cannot qualify against an ideal customer profile nobody has written down. Both sides get frustrated. The SDR leaves without producing meaningful revenue.

Failure two: the pipeline that quietly disappears

This one costs more, because it looks like progress while it is happening.

1. You split an existing rep off prospecting so they can focus on closing.
2. They stop self-sourcing, which is reasonable. It is somebody else’s job now.
3. The new prospector does not replace the pipeline that rep was generating alone.
4. Pipeline collapses, roughly a quarter later.
5. The closer blames the prospector, and neither is wrong.

The second one is harder to spot because the damage lands a quarter after the decision, by which point nobody connects the two.

What goes wrong when you separate hunters and farmers?

There is a specific trap on the farmer side, and it is the part of this I would most want you to take away.

Split hunters and farmers, give each their own target, and you have built two teams measured on different things:

• Hunters are paid for new logos.
• Farmers are paid for retention.
• Nobody is accountable for whether the customers the hunters sign are the kind the farmers can keep.

That is how a B2B SaaS company ends up with record new business and flat revenue. The hunters hit their number by closing poor-fit accounts. The farmers inherit a book that churns.

Leads, sales and retention are one engine, and separating the people does not separate the problem. We set out what that looks like across the whole motion in the GTM strategy guide, and what the early warning signs look like in the churn signals post.

How to fix a split that is already in place

Give both sides one shared number.

Net revenue retention on accounts acquired in a given quarter works well, because it makes the hunter’s sourcing quality visible inside the farmer’s results. If the accounts a hunter signed in Q1 are leaking by Q3, that is the hunter’s problem too, not just the farmer’s.

How reliable are these numbers?

Less than I would like, and I would rather tell you that than present them as settled.

Sources disagree on when the first split should happen:

Source	First split at
devcommx	$1M–$3M ARR
Allston Labs	$3M–$5M ARR

A threefold spread on the lower bound.

That spread exists because ARR is the wrong trigger in the first place. A B2B SaaS company selling $80,000 contracts needs specialists earlier than one selling $6,000 contracts at identical revenue, because the value per deal is what pays for the second role.

Use deal size and the four tests above. Treat the ARR figures as rough context rather than a rule.

Common questions