How to Say Sales Development: A Practical Guide

The phrase comes up constantly — in job interviews, org chart discussions, go-to-market planning, and outbound strategy decks. But a surprising number of people who work in or adjacent to sales development are not entirely sure how to say it, what it precisely covers, or how to use it correctly across different contexts.

This guide closes that gap. Pronunciation comes first. Then meaning, job titles, in-context usage, and the frameworks that make the term operationally useful.

What This Guide Covers

This post is for anyone who wants to speak confidently about sales development — job seekers entering the field, marketers working with SDR teams, founders hiring their first outbound rep, or executives updating their GTM org charts.

The guide covers pronunciation, definition, job title conventions, in-conversation usage, the key frameworks SDRs use, and the most common terminology mistakes. For a deeper look at what the day-to-day role involves, see is sales development representative a good job — a ground-level breakdown of what the function actually demands.

How to Pronounce Sales Development

The pronunciation is straightforward. Say it like this:

Word by word

The only place people stumble is "development." Say all four syllables deliberately until it becomes automatic: de — vel — op — ment. Once you have it at normal speed, the phrase flows naturally.

The abbreviation: SDR

In fast-moving B2B conversations, "sales development" often shortens to SDR (ess-dee-ar). Each letter is pronounced individually. SDR is universally recognized in SaaS, RevOps, and GTM contexts. Using it in conversation signals you are already inside the field.

When speaking: use "SDR" in peer-to-peer or practitioner conversations. Use "sales development" in formal contexts — job descriptions, board decks, org chart presentations — where abbreviations may need unpacking for an unfamiliar audience.

What Sales Development Actually Means

Sales development is the B2B revenue function responsible for pipeline generation at the top of the funnel. It sits between marketing and closing sales.

The function exists because closing deals and generating meetings require different skills. Closing requires deep discovery, negotiation, and relationship management over months. Generating meetings requires high-volume outreach, fast qualification, and consistent follow-up at scale. Sales development isolates the second set of activities so account executives can focus on the first.

The three core activities of sales development

• Prospecting: Identifying accounts and contacts that match the ideal customer profile (ICP). This includes building lists, using data enrichment tools, and applying intent or signal data to prioritize outreach.
• Engaging: Making first contact through cold email, cold calls, and LinkedIn messages. The goal of the first touch is a response — not a sale.
• Qualifying: Running a structured discovery conversation to determine whether the prospect has the budget, authority, need, and timeline to become a real opportunity. Qualified prospects are then handed to an account executive as a meeting or a SQL (Sales Qualified Lead).

According to Predictable Revenue, the concept of separating pipeline generation from closing was formalized at Salesforce in the early 2000s and has since become the standard GTM structure for B2B SaaS companies. The function generated the concept of the dedicated SDR role.

What sales development is not

For a longer look at how sales development fits into the broader revenue org, see how business development differs from sales.

Job Titles and How to Say Them Correctly

Sales development spawns a consistent set of job titles. Each follows the same naming convention: the function name comes first, then the seniority or role type.

Standard title progression

BDR vs. SDR: which term to use

BDR (Business Development Representative) is a close variant. At most companies, BDR and SDR are interchangeable — both do outbound prospecting and meeting booking.

Some companies reserve BDR for outbound-only roles and SDR for inbound lead follow-up. Others use BDR for roles focused on enterprise or new-market accounts, where the "business development" framing feels more appropriate given the deal size.

If you are unsure which term a specific company uses, check their job postings. The title they post publicly is the one they use internally. For a breakdown of what entry-level SDR roles look like in practice, see entry-level sales development representative guide.

How to Use the Term in B2B Conversations

Knowing how to say the words is one thing. Knowing when and how to deploy the term in real conversations — job interviews, leadership meetings, sales calls — is what signals genuine fluency.

In a job interview

Use "sales development" as a noun phrase to describe the function you are targeting: "I am focused on building a career in sales development." Use "SDR" when discussing the specific role: "I have been studying the SDR motion at companies like [X] and [Y] and want to run that workflow here."

Avoid "sales developer" — it is not a job title in B2B and sounds like software development. The correct term is always "sales development representative" (full) or "SDR" (abbreviated).

In a leadership or planning meeting

"Sales development" works as both a department name and a functional descriptor. Examples: "The sales development team booked 47 qualified meetings last quarter." "We are restructuring sales development to separate inbound and outbound motions."

When talking about the function in aggregate, "sales development" is cleaner than "the SDR team" in formal documents. In verbal communication with peers, "SDR team" is faster and universally understood.

In outbound prospecting copy

SDRs sometimes reference their own role in cold outreach. "I run sales development at [Company]" is a clean way to introduce the function without sounding like you are selling. It tells the prospect exactly where you sit in the org — which builds immediate context.

For a broader look at how SDR teams communicate externally, see how to personalize sales emails that get replies.

When talking to a prospect during discovery

Prospects occasionally ask what your role is. "I am in sales development" is a natural answer — it positions you as someone whose job is to understand their situation, not to close a deal on the first call. This framing reduces pressure and increases the chance of an honest conversation about fit.

Core Sales Development Frameworks (and Their Terms)

Sales development has its own vocabulary of qualification frameworks. These come up in interviews, team training, and pipeline reviews. Knowing the terms — and being able to say them confidently — is part of speaking the language of the function.

BANT

Pronounced: "BANT" — rhymes with "ant." One syllable. It is an acronym, not a spelled-out abbreviation.

BANT stands for Budget, Authority, Need, and Timeline. It is the oldest and most widely recognized qualification framework in B2B sales development. An SDR running BANT asks four questions: Does the prospect have budget? Are they the decision-maker? Do they have a clear need? When do they plan to buy?

BANT is criticized for being too rigid — prospects do not always know their budget upfront, and the framework can feel interrogative. But it remains the baseline that most sales development teams teach to new SDRs. A G2 analysis of qualification frameworks found BANT is still the most widely used, appearing in the onboarding playbooks of over 60% of surveyed B2B sales teams.

MEDDIC

Pronounced: "MED-ik" — like the word "medic." Two syllables.

MEDDIC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. It is more rigorous than BANT and is common at enterprise-focused sales development teams. MEDDIC-trained SDRs qualify deeper before passing a lead — which means fewer but better meetings for account executives.

According to Gartner's buyer enablement research, enterprise B2B buyers involve an average of 6–10 stakeholders in a purchase decision. MEDDIC helps SDRs map that group early.

SPICED

Pronounced: "SPICED" — like the adjective. One syllable.

SPICED stands for Situation, Pain, Impact, Critical Event, and Decision. It was developed by Winning by Design as a more conversational alternative to BANT. The framework emphasizes understanding the prospect's current situation and the business impact of their pain before moving to timeline or decision process.

SQL and MQL

SQL: "ess-kyoo-el" — Sales Qualified Lead. A lead that sales development has qualified and passed to an account executive.

MQL: "em-kyoo-el" — Marketing Qualified Lead. A lead generated by marketing and passed to sales development for follow-up.

The handoff between marketing (MQL) and sales development (SQL) is one of the most common sources of misalignment in B2B revenue teams. See B2B marketing and sales alignment for how to close that gap.

Pipeline and quota terminology

• Qualified meeting (or "booked meeting"): A meeting that has been confirmed with a prospect who meets ICP criteria. The primary metric for most SDR roles.
• Sequence: A multi-touch outreach cadence — typically a combination of emails, calls, and LinkedIn touches over 2–4 weeks.
• Cadence: Often used interchangeably with sequence. Some teams distinguish the two: a cadence is the timing pattern; a sequence is the full set of messages.
• Waterfall enrichment: A data enrichment method where multiple providers are queried in sequence to maximize contact data coverage. SyncGTM uses waterfall enrichment across 75+ sources to give SDRs verified email and phone data on ICP accounts.
• ICP: Ideal Customer Profile. The description of the company or buyer type that sales development targets.

For a practical view of what sales development reps do day-to-day with these terms, see how many activities should sales development reps do daily.

Common Usage Mistakes to Avoid

These errors appear frequently among people new to the function. Each one signals unfamiliarity and can cost credibility in an interview or planning conversation.

• "Sales developer" or "sales develeper." Neither is a real job title. "Sales developer" sounds like software development. The correct title is "Sales Development Representative" or "SDR." In conversation, "sales dev rep" is acceptable shorthand.
• Treating "sales development" and "business development" as synonyms. They overlap in some companies but describe different scopes. Sales development is execution-focused (outbound volume, meetings booked). Business development is strategy-focused (partnerships, market expansion). Using them interchangeably in a senior conversation signals you have not worked in the function.
• Saying "SDR" when the company uses "BDR." Both abbreviations exist for real reasons. If a company uses BDR internally, defaulting to SDR in a job interview suggests you did not read the job posting carefully — which is ironic for a role that requires meticulous research before every outreach.
• Dropping syllables in "development." The spoken error "dev-ment" instead of "de-vel-op-ment" is minor but noticeable to people who live in the function. It suggests the speaker is less familiar with the term than they appear.
• Confusing the acronyms SQL and MQL. Both are pronounced as letter-by-letter abbreviations: ess-kyoo-el and em-kyoo-el. Mixing them up in a pipeline discussion is a meaningful error — SQL is what sales development produces; MQL is what they receive from marketing.
• Saying "SDR team" and "sales team" interchangeably. The SDR team is one part of the sales organization. In most B2B companies, the sales team includes SDRs, account executives, account managers, and sales operations. Using "sales team" when you mean "SDR team" obscures which part of the funnel you are discussing.

FAQ

This post was last reviewed in May 2026.