Resource

The SQL Playbook That Tripled Per-Rep Output: From 2 to 6 SQLs/Month

At GoComet, I helped improve SDR productivity from 2 SQLs per rep per month to 6 SQLs per rep per month. The lift came from building a stronger SDR operating system: clearer ICPs, better messaging, structured outbound motions, rep-level reporting, and weekly coaching.

This experience shaped one of my strongest GTM beliefs:

SDR output improves when the system around the rep improves.

A great rep inside a weak system still struggles. An average rep inside a strong system gets better faster.

The starting point

Most growth-stage teams already have the raw ingredients:

• Sales tools
• CRM
• LinkedIn Sales Navigator
• Prospect databases
• Email sequences
• A team willing to put in the work

But output stays flat because the system lacks clarity.

Reps target too many account types. Messaging sounds generic. Follow-ups become inconsistent. Managers review final outcomes instead of early signals. That creates activity, but weak conversion.

The playbook that changed output

1. ICP clarity before outreach

The first fix was sharper targeting.

Instead of asking reps to chase every possible account, we defined the right-fit accounts by industry, company size, geography, buyer role, use case, and urgency trigger. This made outreach more focused.

The question changed from:

"Who can we contact?"

to:

"Who has the highest probability of needing this now?"

That single shift improved rep focus.

2. Persona-specific messaging

Every buyer sees the problem differently.

So the messaging had to match the buyer's world.

The strongest outbound message was simple:

"You are likely facing this specific problem. Here is why it matters now. Here is a low-friction next step."

Clear beats clever.

3. Multi-channel sequences

Email alone rarely gives the full picture.

We used a structured mix of email, LinkedIn, and calling. Each touch had a purpose.

• Email created context
• LinkedIn built familiarity
• Calls created speed
• Follow-ups carried the business case forward

The goal was simple: make every touch feel connected, useful, and relevant.

4. Rep-level KPI visibility

One of the biggest unlocks was tracking the full funnel at rep level. Meetings booked were only one part of the view.

We looked at:

• Account quality
• Contact quality
• Connect rate
• Reply rate
• Positive reply rate
• Follow-up completion
• SQL conversion
• Pipeline movement

This helped diagnose the real issue.

• One rep had enough activity but weak targeting.
• Another had good replies but weak qualification.
• Another had strong calls but poor follow-up discipline.

Once the problem became visible, coaching became specific.

5. Weekly coaching and call reviews

The final layer was coaching.

Call reviews, mock sessions, objection handling, and sequence reviews helped reps improve every week. The aim was to build judgment, not just activity.

Good SDRs learn scripts. Strong SDRs learn patterns.

They know which accounts deserve time, which objections are real, which prospects need nurturing, and which signals show buying intent.

Unique insight: SQLs are created upstream

Most teams believe SQLs are created during the sales conversation.

In reality, SQLs are often created much earlier.

• They are created when the right account is selected.
• They are created when the right trigger is used.
• They are created when the first message lands with relevance.
• They are created when follow-up connects to a real business pain.

The call only reveals the quality of the upstream work.

That is why SDR productivity improves fastest when leaders coach the inputs before coaching the outcome.

The takeaway

Tripling SQL output was not about adding pressure.

It was about adding clarity.

The SDR team needed a better system around them:

• Sharper ICP
• Clearer messaging
• Structured sequences
• Better dashboards
• Weekly coaching
• Cleaner handoffs

That is how outbound becomes predictable.

At GrowthStack Advisory, this is the same operating model we help B2B teams build: ICP frameworks, outbound playbooks, SDR coaching, sequence optimization, CRM workflows, and reporting systems that convert effort into qualified pipeline. For execution-led engagements, see B2B lead generation consulting. For the broader GTM operating model, see GTM consulting. And if you're rebuilding the qualification side of the funnel, pair this with How to improve MQL to SQL conversion.

The question to ask your team

Trying to improve SQL output per rep?

Start with this question:

Are we coaching activity, or are we coaching relevance?

Because activity creates motion.

Relevance creates pipeline.