BDR (Business Development Representative)

A BDR (Business Development Representative) is the sales role that specializes in cold prospecting (outbound): going out to find companies that do not know the business yet, opening a conversation with them and turning that initial interest into qualified meetings that an account executive then takes over. A BDR does not close deals; their job is to open the top of the funnel with accounts that fit the ideal customer profile.

Unlike the SDR, who usually handles the demand that is already coming in (marketing leads, forms, downloads), the BDR creates new demand: they build lists of target accounts, research the decision-maker, set up a cadence of emails, calls and messages, and work to land the first meeting. In practice, many companies use both terms almost as synonyms; the line that matters is inbound (responds) versus outbound (goes out and finds).

The BDR's activity lives inside the CRM, where the contacts, accounts, cadence tasks and opportunities they create are logged. In the Vantegrate ecosystem, that prospecting and pipeline operation is part of what Sellium organizes on top of Salesforce.

What a BDR does day to day

The BDR works on accounts that match the ideal customer profile (ICP): companies of the right size, sector and maturity for the product. They build a list, research who makes the purchase decision and start the cold outreach. The unit of work is the cadence: a planned sequence of touches (email, call, LinkedIn message, WhatsApp) spread over time to reach the prospect without overwhelming them. The concrete goal of each sequence is a meeting booked and accepted with an account executive.

The result of their work is not the closed sale but the qualified opportunity that enters the pipeline. That is why the BDR is the first hinge of the sales process: the better they qualify at handoff, the healthier the funnel stays downstream. Poor qualification inflates the pipeline with meetings that never move forward and wears out the closing team.

BDR vs SDR vs AE: who does what

The most common confusion is between BDR and SDR. The operational difference, as practiced in Latin America, is the source of the lead more than the job title.

In small companies, one person fills all three roles. As the team grows, they split so each one can specialize: the BDR in opening, the AE in closing. This division is the foundation of the stage-based sales model that SaaS made popular.

Why it matters for a business in Argentina

In a B2B market where the sales cycle is long and the ticket is high, having a role dedicated to prospecting changes how predictable the business is. A concrete example: a management software company that sells to wholesale distributors in Buenos Aires and the rest of the country. Without a BDR, the reps close whatever comes in and revenue depends on word of mouth. With a BDR who prospects 50 target accounts a month with an organized cadence, the company starts to generate pipeline predictably instead of waiting for customers to show up. That predictability is what lets you build the sales forecast on solid ground.

How a BDR is measured

The typical metrics for the role cover activity and results:

• Meetings booked per period (the main goal)
• Conversion rate from contact to meeting
• Qualified opportunities created that the AE accepts
• Contribution to pipeline coverage: how much of the pipeline needed for the quota comes from their prospecting

What matters is not measuring only activity volume (emails sent, calls made) but the quality of what they deliver. A BDR who books lots of meetings that the AE rejects for poor fit is not generating value, they are generating noise.

Common mistakes

The first is prospecting without a clear ICP: contacting any company instead of the ones that really fit, which fills the funnel with meetings that do not convert. The second is abandoning the cadence too early: getting a first meeting with a new prospect takes eight touches on average (RAIN Group, 2025), and many BDRs without discipline stop at the second. The third is over-qualifying to inflate the number: passing weak meetings to the AE to hit the activity target, which erodes trust between teams and muddies the pipeline. The antidote to all three is an agreed qualification process (for example BANT or MEDDIC) and a CRM where every handoff is logged and auditable.