The Gated Capacity Model: How Fello's CRO Engineered 90% Sales Attainment

Most revenue leaders operate from a spreadsheet fantasy: multiply target revenue by average quota, adjust for assumed attainment, output a hiring plan. The math looks clean. The reality rarely cooperates.

In a recent episode of The Sales Front Lines, Dustin Deno, Chief Revenue Officer at Fello, explained why he abandoned this approach entirely. Fello operates in vertical SaaS for real estate, solving a specific economics problem: agents spend heavily on new lead generation through Zillow and realtor.com while ignoring the monetizable relationships already in their databases. Fello enriches those existing contacts with mortgage data and homeowner insights, then runs engagement campaigns to generate seller listings.

When Dustin joined, the sales organization exhibited the classic failure pattern: lopsided attainment. A few top performers carried the team while the majority struggled. His solution wasn't more reps. It was engineering a system that forced the right management behaviors before permitting any headcount expansion.

Engineering the Forcing Function

Dustin's gated capacity model draws from Mark Roberge's Sales Acceleration Formula but adds operational constraints that change manager incentives fundamentally. Teams earn additional headcount only when meeting two thresholds simultaneously: 80% of existing reps must hit 80%+ of quota, and the team must hit its aggregate number.

"If each team gets 80% of those reps to above 80% of their number and the team hits their number, that team gets a free hit," Dustin explains. Fello achieved 90% team attainment last period, but that metric obscures the mechanism's actual innovation.

Traditional capacity planning creates perverse incentives. Managers optimize for their own quota attainment, which means riding top performers and chasing deals that move their personal number. Underperformers get ignored because coaching them consumes time better spent on closeable opportunities. Dustin's framework eliminates that calculus entirely.

If you want to grow your team, you must: coach every rep to competency, hire quality talent that actually ramps, and performance-manage the bottom tier before they drag for quarters. There's no alternative path to earning headcount.

The structural detail matters: managers don't carry quota for new heads—only the CRO does. This removes the empire-building incentive. A manager requesting headcount isn't padding their own number; they're demonstrating they've built a machine that successfully onboards and develops reps. The capacity gate becomes a forcing function for management quality, not just team performance.

The 60% Swarm Protocol

Standard sales org practice: watch underperformers decline for two quarters, then initiate a performance improvement plan designed primarily for legal documentation. By that point, the rep has mentally checked out, the team knows they're failing, and six months of capacity has evaporated.

Fello's "swarm" protocol activates at 60% attainment. "If you dip 60%, it's not a negative thing. We coach you up right away that next month you meet daily with your manager, weekly with the VP of sales, and then monthly with me," Dustin explains.

The intervention focuses on two to three specific, measurable improvements—not vague exhortations to "be more consultative" or "improve discovery." The 60% threshold is calibrated deliberately: early enough for genuine course correction but late enough to distinguish real struggle from normal performance variance.

The organizational benefit compounds. You eliminate the morale drain of obviously failing reps staying in role for half a year. You demonstrate actual investment in development rather than managing toward termination. And you compress the timeline for determining whether someone can succeed in the role from six months to one.

"I was always sick of seeing low performers stick in the business for six months. We're not giving them any help. We're waiting until the last minute to put them on this performance plan that they're never going to hit," Dustin says.

AI-Driven Pattern Diagnosis

When conversion rates declined, Dustin faced the standard diagnostic approach: sample calls manually, form hypotheses, implement changes, wait weeks for signal. Instead, he used Gong's theme spotter and AI builder to analyze thousands of conversations simultaneously.

"I call it kind of your time to diagnosis has as a revenue leader has shrunk like 100x. It's crazy. Like I can look at thousands of conversations and have AI pull out the relevant themes that I'm seeing," Dustin explains.

The pattern that emerged wasn't what call sampling would have suggested. Demo execution was fine. Objection handling was competent. The failure occurred earlier in the conversation flow: reps weren't conducting adequate discovery. They defaulted to "showing up and throwing up"—demoing features before understanding prospect-specific business problems.

"Most of the time it falls flat on the discovery. So reps will be really good at kind of demoing or you know, kind of showing up and throwing up and pitching. But they really don't take the time up front to learn what the business problems are for that specific agent or team," Dustin says.

The AI analysis also surfaced a systemic customer education gap. Real estate teams lack operational expertise to leverage Fello's full capability set. Once agents understood the operational model, they expanded rapidly. But getting to that understanding required more structured education than Fello was providing—a post-sale adoption barrier that only became visible through pattern analysis across thousands of interactions.

This insight redirected strategy toward scaled content creation. The discovery compressed diagnosis from quarters to days and identified a growth constraint that call sampling would have missed entirely.

The Discovery Taxation Problem

Fello's discovery failure illustrates a structural issue in transactional B2B sales. When training emphasizes product capabilities and feature differentiation, reps naturally regurgitate those elements in customer conversations. The demo becomes the conversation anchor, even when prospects haven't articulated the problem they're solving.

"If you just regurgitate features and functions to the rep in terms of the training, then they kind of regurgitate features and functions to the customer," Dustin explains.

The fix requires retraining sales methodology to extract business context before product presentation: What's your current database management process? Where does nurture break down? What happens to contacts after initial outreach fails? Only after establishing that context should product capabilities enter the conversation.

This is fundamental sales discipline, but it erodes predictably at scale. Demo skills are immediately observable in ride-alongs and easier to measure in onboarding. Discovery quality requires conversation analysis and understanding of customer context—harder to evaluate, easier to skip in training prioritization.

ICP-Tiered Revenue SLAs

The standard sales-marketing dynamic cycles through predictable accusations: marketing claims sales doesn't follow up on leads, sales claims marketing delivers unqualified garbage, both waste energy on subjective quality assessments.

Fello replaced this with ICP-tiered conversion economics. They segment inbound into three buckets, each with empirically measured ACV and conversion rates. Marketing delivers to a revenue target—100 lower-tier leads or 10 top-tier leads produces the same pipeline dollars if conversion economics hold. Sales commits to tier-specific follow-up activities based on conversion requirements.

"We break our ICP down into three different buckets and we know the ACV and the conversion rate of each one of those buckets," Dustin explains. "I don't care whether they give me 100 of the ICP minus or 10 of the ICP plus as long as the revenue number."

This framework converts subjective quality debates into quantitative optimization around conversion rates and activity efficiency. The implementation requirement: accurate tier-specific conversion data. Without empirical measurement of how each ICP segment converts and at what ACV, the SLA becomes another coordination theater exercise.

The shared language becomes revenue math, not lead quality opinions. Marketing can optimize for higher-tier lead generation if conversion efficiency justifies the volume trade-off. Sales can identify which follow-up sequences actually move conversion rates within each tier. Both orient around the same metric.

Stage-Specific Revenue Leadership

Dustin's final framework addresses a common founder hiring mistake: selecting the wrong leadership archetype for their current scale stage. The skill set that establishes product-market fit and initial repeatable motions at $10 million actively damages companies scaling from $25 million to $100 million.

"When you start to get to 25 million, it's kind of a, it messes with you a little bit as a founder," Dustin says. "Almost every thing that you did, the decision making framework, you had to get you from 0 to 1 and to 10 to 25, you have to kind of think opposite because everything has to scale at this point."

At $10 million, founders need someone who can establish go-to-market fit—proving which sales motion actually generates repeatable revenue. This leader optimizes the engine: identifying ideal customer profile, refining messaging, building initial playbooks.

At $25 million, the entire operating model inverts. Everything that worked must now scale without constant founder intervention. This demands operational systems thinking: process architecture, coaching frameworks, forcing mechanisms that drive consistent performance across expanding teams. The founder who "can walk into any room and close any deal" needs the operational complement who architects systems that function without heroic individual contributions.

"Look for the skill set that you don't have or that you don't want to deal with," Dustin advises. This isn't about hiring for weakness—it's about recognizing that the leadership requirements fundamentally shift at scale inflection points. The sales leader who builds repeatability at $10 million often lacks the operational discipline required to architect systems that scale to $100 million. Recognizing that transition point and making the hire accordingly determines whether companies successfully navigate the scaling phase or plateau at $25-30 million.