Read enough sales development job postings for vertical software and a number starts repeating.
A legal software role advertises sixty five to a hundred cold calls a day. A veterinary software rep owns every independent clinic in a territory at roughly three hundred cold engagements a week. A salon and spa platform lists over two hundred fifty calls a week as the expectation. These are not outlier postings. They are the standard shape of the job when your customer is an owner-operated business.
Nobody designs a role around two hundred and fifty dials because dialing is efficient. They design it that way because the connect rate is low and the only lever available is volume.
What the volume is paying for
Work backward from the number. If a rep makes two hundred and fifty calls and has thirty real conversations, the two hundred and twenty that went nowhere were not all bad timing. A large share of them were structurally doomed before the rep picked up the phone, because the number on the record was the business line.
The business line reaches a receptionist, a front desk, an answering service, or a voicemail box that the owner checks on Sundays. A rep can be excellent and still lose that call, because winning it was never on the table.
An account executive selling into businesses under twenty employees described the incumbent database as having contact information for a couple of people per account. A revenue operations lead tested three hundred accounts and concluded the phone numbers could not be trusted. Neither of those is a complaint about a vendor being lazy. It is what happens when a data model built for companies with org charts gets pointed at companies with six employees and no website.
So the volume target is really a correction factor. It is the number of attempts required to overcome contact data that does not reach the decision maker.
The math of fixing the input instead
Say a territory has four hundred independent practices. Today the rep works a list where most rows carry a main line and a generic inbox, and a minority carry something better. The quota is expressed in dials because that is the only honest way to express it.
Now change one thing. Every row carries the owner’s name, a mobile that passed a carrier check, and an email a mail server accepted.
The dial count does not need to go up. It needs to go down, and the conversation count goes up anyway, because a much larger share of attempts reach someone who can say yes. The rep stops spending four days a week talking to people whose job is to absorb vendor calls.
That is the whole argument. It is not about a better dialer, a better sequence, or better talk tracks. The input is wrong, and everything downstream is compensating for it.
Why this category is harder than it looks
There is a reason the big databases have not simply fixed this.
Their coverage model begins with companies that publish themselves: a website, a team page, employees maintaining professional profiles. An independent veterinary clinic with nine staff publishes almost none of that. What it publishes lives in state filings, licence boards, permit records, ad libraries, and review replies. Those sources have no common identifier, spell business names four different ways, and were never designed to be joined.
Doing it properly means resolving a brand to a legal entity, the entity to its officers, and the officers to an actual human being, while refusing to promote a registered agent into an owner just to fill a column. Then it means verifying a contact for that human and typing it honestly, so an owner mobile and a front desk line are never presented as the same thing.
It is a lot of unglamorous work. It is also the only version of this that changes a rep’s week.
What to look at if you run one of these teams
Pull your last quarter and check what share of your accounts carry a contact for the owner personally, as opposed to the business. Not a title that sounds senior. The person who signs.
If that share is low, your dial target is not a performance standard. It is the interest you are paying on your data.