Last week I wrote about how AI is finally closing the loop between insight and action for revenue teams. Another revolution happening in parallel that deserves attention is how the consumption model is forcing a complete restructuring of revenue teams.
The Hunter-Farmer Debate Is Dead
I've been having this conversation with revenue leaders for the better part of a year. The traditional dichotomy of "hunters" who land new business and "farmers" who grow existing accounts is becoming obsolete, and a more nuanced view of sales roles is needed.
The hunter-farmer model made sense in a seat-based world. You had hunters focused on landing large, upfront contracts. You had farmers focused on annual renewals and basic account expansion. The lines were clear, the handoffs were clean, and everyone knew their lane. Consumption pricing throws all of that out the window.
When customer value scales directly with usage, you need roles that can think strategically about the entire customer lifecycle. A customer might start small, grow exponentially, plateau, then expand into new use cases.
The New GTM Motion
Here's how we're seeing the best consumption-based companies structure their revenue teams:
1. Land Small, Grow Fast
The initial sale is often small — a proof of concept, a limited deployment, a single use case. The goal isn't to maximize the initial contract value; it's to get a wedge in the door and prove value quickly. This requires sellers who are comfortable with smaller initial deals and focused on time-to-value.
2. Product-Led Expansion
The best consumption expansions happen without a sales conversation. A team tries the product, loves it, and starts using it more. Usage grows. Revenue grows. The role of the CS team is to make sure customers are getting value, identify natural expansion opportunities, and remove friction from the path to using more.
3. Usage-Informed Sales
When expansion does require a sales conversation, it should be informed by usage data. Which teams are using the product most? Which use cases are working best? Where are the natural expansion opportunities? The sellers who win in consumption models are the ones who can have consultative conversations informed by deep product usage data.
What This Means for CS
Customer success is the biggest organizational change in consumption-based models. In a seat-based world, CS is primarily a renewal function — keep customers happy enough to sign the next contract. In a consumption world, CS is a revenue function.
Usage is the revenue signal. CS teams need to be monitoring usage across their entire book of business, identifying patterns, and taking proactive action before issues become visible to the customer.
The best CS teams in consumption-based companies are doing three things:
- Monitoring usage signals continuously, not just at QBR time
- Segmenting their book by usage health, not just by ARR
- Automating interventions for common patterns so they can focus on the highest-leverage conversations
The Data Problem
All of this requires data infrastructure that most companies don't have. Usage data lives in your product. Customer health data lives in your CRM. Support data lives in Zendesk. Financial data lives in your billing system. Making sense of all of this across hundreds or thousands of accounts requires either significant engineering investment or tools built specifically for this purpose.
This is exactly what we're building at Quivly. We integrate with your usage data, CRM, billing system, and support tools to give your CS and revenue teams a single view of account health — and automated workflows to take action on the signals that matter.
The Organizational Implication
The companies that get this right will have a significant competitive advantage. They'll be able to grow revenue without proportionally growing headcount. They'll catch churn before it happens. They'll identify expansion opportunities that their competitors miss.
The companies that don't get this right will find themselves with a model that looks attractive on paper but is operationally exhausting in practice — manually tracking usage across hundreds of accounts, constantly in reactive mode, unable to scale.
The shift to consumption isn't just a pricing change. It's a fundamental rethinking of how revenue teams operate.