Article
Three Cs of SDR Leadership
tenbound.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Salesforce's sales-leadership guidance emphasizes regular one-to-one coaching and clear goals. The practical implication is to review a small, representative sample every week: one strong interaction, one weak interaction, and one ambiguous interaction. The manager and rep should name the decision that made each different. “Generated research and messages can look polished while being wrong.” 3. Cadence: make the learning loop unavoidable
profile, and which disqualifiers should stop work? “The buying situation. What observable change makes outreach timely?” The quality bar. What must be true before a contact enters a sequence or
recurring exceptions that required manager intervention. “Coaching should improve the decisions visible in the sample.” That is the three-Cs test: the team knows what good looks like, gets better at producing it, and has a rhythm that keeps the definition current.
1. Clarity: define the work before measuring it “A rep cannot improve against a moving target. Write down four things before asking for more activity:” The account definition. Which companies are in the ideal customer
“Clarity defines the customer, the job, and the standard.” This is a useful 2026 update to the familiar "three Cs" idea because an SDR team now works with more automation, more data, and more AI-generated output than it did even a few years ago. The manager's job is no longer to supervise every task. It is to make the judgment layer explicit. Tenbound's Pipeline Architecture Standard provides the wider system these management practices operate inside.
“Coaching improves observable behaviors rather than waiting for a missed number.” This is a useful 2026 update to the familiar "three Cs" idea because an SDR team now works with more automation, more data, and more AI-generated output than it did even a few years ago. The manager's job is no longer to supervise every task. It is to make the judgment layer explicit. Tenbound's Pipeline Architecture Standard provides the wider system these management practices operate inside.
The account definition. Which companies are in the ideal customer “profile, and which disqualifiers should stop work?” The buying situation. What observable change makes outreach timely?
For an SDR team, the simplest useful artifact is a one-page operating contract: “target-account rules;” meeting-acceptance criteria;