Skip to content
All work

Strategy

Coverage matched to sales capacity

A tiered coverage plan that started from two BDRs' hours instead of a lead target.
  • Salesforce Sales Engagement
  • HubSpot
  • ZoomInfo

Summary

Challenge
Account values vary widely and seller hours are fixed. Treating every account the same spends the scarcest attention on the accounts least likely to close.
What I built
Four account tiers with a depth of coverage each, cadences in Salesforce Sales Engagement, a BDR work surface, and nurture and a self-serve calculator below the line.
Result
The team's hours went to the accounts most likely to become pipeline, and nothing below the line was dropped.
Role
Planned the coverage model and built the BDR work surface; led the two BDRs
With
Two BDRs and the sales team
Status
Ran in production at Anova

The situation

Capacity sets the ceiling, not lead volume.

In a long consultative sale, the number of accounts a team can work properly is fixed by the hours it has. Two BDRs can only research, call and follow up with so many accounts, and senior sellers' time is scarcer still.

Account values vary widely from one deal to the next, and the effort each account deserves varies with them. Treating every account the same spends the most expensive attention on accounts that were never going to close, and leaves the best ones waiting in the same queue as everyone else.

The decision

Start the demand plan from the hours available.

I planned coverage from capacity instead of from a lead target. The account tiers from the fit score decided how much human attention an account would get, and everything below the line the team could cover went to automation rather than to a list nobody worked.

The tiers also changed how the offer was delivered. The same free fleet assessment, pre-filled with our own estimate, was delivered by a person for tiers A to C and by a self-serve calculator for tier D, so every tier received the offer at a cost the team's capacity could carry.

What I built

Four tiers, four depths of coverage.

The tier decides how much of a person's time an account receives. Everything is logged against the plan.

  • Tier A: research and direct outreach

    The highest-value accounts got personalized research, tailored outreach and direct seller or BDR attention. These were the accounts where an hour of preparation before a first conversation paid for itself.

  • Tier B: structured BDR cadences

    Strong-fit accounts entered Salesforce Sales Engagement cadences carrying enrichment, intent and campaign context, so the BDRs could run a consistent sequence at scale without losing each account's situation.

  • Tier C: targeted nurture, selective follow-up

    Developing accounts went into targeted nurture, with BDR follow-up when engagement rose and the fleet assessment delivered by a person. Human time went in when the account earned it.

  • Tier D: automated nurture and self-serve

    Lower-priority accounts stayed warm through automated nurture and self-serve conversion paths, including the calculator version of the fleet assessment. No rep time was spent until the account moved.

The plan

Human time scales with account value.

Illustrative Solid lines are seller and BDR time; dashed lines are automation. Tier C keeps a person in reserve for when engagement rises, and tier D runs on automation until the account moves. The tier sets the depth of coverage, not whether an account is covered.

The work surface

What the BDRs worked from.

The tiers only work if the people working them can see them. The BDRs worked from a custom Lightning app in Salesforce that put enrichment, engagement history, intent and event context for an account on one screen, instead of across ZoomInfo, Sales Navigator, HubSpot and Popl in separate tabs.

Sales Engagement ran the cadences, Work Queue held the day's steps, Sales Dialer handled the calls, and Einstein Activity Capture logged emails and meetings without anyone typing them in. Building it inside Salesforce, rather than buying a separate engagement platform, kept the budget for programs and kept the BDRs in one CRM, synced with HubSpot.

How it ran

When a tier outgrew the hours, it showed.

Einstein Activity Capture and Sales Engagement logged calls, emails and cadence steps against each account, so coverage could be checked against the plan instead of assumed. If a tier needed more coverage than the BDRs had hours for, it surfaced as a resourcing conversation with activity data behind it, rather than as missed follow-up.

In a market where the cycle runs in quarters, that kept the demand plan honest. Campaigns were sized to what the team could work, and the accounts most likely to become pipeline got attention first.

Result

The team's hours went to the accounts most likely to become pipeline.

The top accounts received the most prepared, most personal attention the team could give. Nothing below the line was dropped: it moved through nurture until it earned a person's time.

Takeaways

What carries over.

  • Count the hours before counting the leads.
  • Automate the bottom of the market instead of ignoring it. Some of those accounts grow.
  • Change how an offer is delivered by tier, and keep the offer itself the same.

The stack

What it ran on.

Sales engagement

  • Salesforce Sales Engagement cadences
  • Work Queue
  • Sales Dialer
  • Einstein Activity Capture

Nurture and scoring

  • HubSpot workflows
  • Account tiers
  • Self-serve calculator

Research

  • ZoomInfo
  • LinkedIn Sales Navigator

Open to senior and manager-level roles

Need the demand engine built, or someone to run it?

Demand generation, marketing operations and RevOps roles in complex B2B, remote or hybrid from Omaha. I also take on a small number of scoped builds.