One of the biggest mistakes I see in business development is the assumption that a good BDR needs to sell the product.
I don’t believe that’s the job.
Especially when you’re selling complex B2B solutions such as ERP, engineering software, SaaS, telecommunications, cybersecurity, manufacturing technology, or other high-value solutions, trying to sell the entire solution during the first conversation can actually make it harder to get the prospect to take the next step.
The BDR’s job is to sell the meeting.
That distinction sounds simple, but it changes everything about the conversation.
Instead of trying to convince a prospect to buy something they may know very little about, the BDR needs to give them a compelling reason to spend time learning more.
The objective isn’t to close the deal.
The objective is to create enough relevance and curiosity to earn the next conversation.
A prospect who answers an unexpected sales call is not sitting there waiting for a product demonstration.
They are working.
They have meetings.
They have problems to solve.
They have priorities.
And they probably weren’t expecting your call.
That means the first few minutes of the conversation need to accomplish something very specific: establish enough relevance that continuing the conversation makes sense.
This is where many sales reps go wrong.
They immediately begin explaining the product.
“We have a platform that…”
“Our software allows you to…”
“We help companies with…”
“Our solution has…”
The prospect may have no reason to care yet.
The problem isn’t necessarily the product. The problem is that the conversation has started with the solution instead of the business problem.
When I think about effective business development, one of the most important concepts is curiosity.
You don’t need to tell a prospect everything.
In fact, you shouldn’t.
You need to give them enough information to make them think:
“That’s interesting. I didn’t realize that was something other companies were dealing with.”
That is a much stronger position than trying to explain every capability of a product.
Think about the difference.
A weak approach might be:
“Our software provides automated reporting, workflow management, real-time analytics, and integrations with your existing systems.”
A curiosity-driven approach might be:
“We’ve been speaking with organizations that are dealing with a surprising amount of manual work around reporting and operational visibility. Some of them didn’t realize how much time it was costing them until they actually measured it. I’d be interested in showing you what we’re seeing and how other organizations are addressing it.”
The second approach doesn’t attempt to sell the software.
It sells the opportunity to learn something.
That’s what gets the meeting.
One of the best ways to position an appointment is to make the prospect feel that they are going to receive something of value whether or not they ultimately purchase.
That is important.
If the only value the prospect receives from the meeting is information about your product, they have every reason to assume the meeting is going to be a sales pitch.
But what if they are going to learn something useful?
What if they are going to see how companies in their industry are addressing a problem?
What if they’re going to discover an inefficiency they didn’t realize they had?
What if they’re going to learn about a new approach that could save time, reduce costs, improve productivity, or create additional revenue?
Now the meeting has a purpose.
The BDR can legitimately say, in effect:
“You don’t have to make a decision. Take the meeting, learn something, ask some questions, and decide whether it’s relevant to you.”
That is a much easier proposition for a prospect to accept.
One question I believe every BDR should have in their toolbox is:
“What is the cost of doing nothing?”
It’s a deceptively simple question.
Most prospects can tell you what they don’t like about their current situation.
They may say their system is slow.
Their team spends too much time entering data.
Their salespeople aren’t generating enough opportunities.
Their engineering team is dealing with inefficient processes.
Their current provider isn’t meeting expectations.
But identifying the problem isn’t enough.
The next step is understanding what that problem actually costs the organization.
What happens if nothing changes?
Does the company continue spending hundreds of hours on manual work?
Does the sales team continue missing opportunities?
Does the engineering department continue losing productivity?
Does the company continue accepting unnecessary operating costs?
Does management continue making decisions without accurate information?
The cost of doing nothing can create more urgency than the product itself.
This is particularly important when selling complex solutions.
Sometimes your prospect doesn’t know they have a problem.
They may know something is inefficient, but they don’t know there is a better way to approach it.
That’s where a good BDR can create enormous value.
Your job isn’t simply to identify problems the prospect already knows about.
Your job is also to introduce them to challenges they may not have considered.
That might sound like:
“Something we’ve been hearing from other companies in your space is that their teams are spending far more time managing this process manually than they realized. Is that something you’ve looked at?”
Now you’re not pitching.
You’re educating.
You’re giving the prospect a reason to think.
And that is exactly what a strong business development conversation should do.
There’s another balance that experienced BDRs learn.
You need to provide enough information to create interest without providing so much information that the meeting becomes unnecessary.
Think of the initial conversation as a preview.
Give the prospect enough to wet their whistle.
Then give them a reason to want the rest of the story.
For example:
“We’ve helped organizations address this in a few different ways, and there are a couple of approaches that might be relevant to you. Rather than try to explain everything over the phone, I’d like to get you in front of someone who can show you exactly what we’re seeing and how other companies are approaching it.”
Now there is a reason for the meeting.
The prospect knows what they might learn.
They know there is more information coming.
And they haven’t been asked to make a purchasing decision.
When you ask someone to take a meeting, you’re asking them to make an investment.
Their currency isn’t necessarily money.
It’s time and attention.
That’s why the value proposition for the appointment needs to be clear.
A weak appointment sounds like:
“Would you have some time next week for a demo?”
A stronger appointment sounds like:
“I think it would be worthwhile to spend some time showing you how other organizations are addressing this problem and what options are available. You can ask questions, see whether any of it applies to your environment, and if it doesn’t make sense, at least you’ll have a better understanding of what’s available.”
The second approach reduces perceived risk.
The prospect isn’t committing to buy.
They’re committing to learn.
Once the prospect agrees, the job isn’t finished.
This is another area where small details can make a significant difference.
In my own business development experience, I’ve seen how quickly meeting attendance can change based on how the appointment is handled after the call.
If a calendar invitation is delayed for several hours, the prospect can lose momentum.
They may get distracted.
They may forget the conversation.
They may accept another meeting.
They may simply move on with their day.
When we began sending meeting invitations immediately after appointments were scheduled, or within the hour, we saw meeting show rates improve.
In our experience, meetings that previously showed in roughly the 50–60% range moved closer to 60% or better when the invitation was sent immediately.
The exact numbers will vary from organization to organization, but the lesson is universal:
Don’t create unnecessary friction between the prospect saying yes and the meeting appearing on their calendar.
The second lesson is equally simple.
Confirm the meeting.
A short confirmation call the day before can make a meaningful difference.
For Monday meetings, a confirmation call on Monday morning can be particularly valuable.
In our experience, adding confirmation calls produced another roughly 15–20% improvement in show rates.
Again, these aren’t universal industry benchmarks. They’re results we’ve observed through our own outreach efforts.
But the principle is important.
If someone agreed to a meeting three weeks ago, there’s a good chance they’ve forgotten exactly why they agreed.
The confirmation call gives the BDR an opportunity to reconnect the prospect with the original value proposition.
“Just wanted to confirm we’re still good for tomorrow. When we spoke, we talked about X, and the team is going to walk you through how other organizations are addressing that. I wanted to make sure you still had it on your calendar.”
That’s not annoying.
That’s professional follow-through.
Another reason BDRs fall into the product-pitch trap is that product knowledge feels productive.
It’s easy to measure how much information you gave the prospect.
It’s much harder to measure whether you created curiosity.
But curiosity is what moves the prospect forward.
A successful BDR conversation should ideally produce one of several outcomes:
The prospect identifies a problem.
The prospect recognizes a problem they hadn’t considered.
The prospect becomes curious about a different approach.
The prospect agrees to learn more.
The prospect agrees to a meeting.
Those are meaningful outcomes.
Simply explaining the product isn’t.
I’ve always believed that the best BDRs are educators.
They aren’t walking encyclopedias of product features.
They are able to connect a prospect’s business situation to a relevant conversation.
They understand the market.
They understand common problems.
They know what other organizations are doing.
They ask thoughtful questions.
And they create enough curiosity to earn another conversation.
That’s especially important in complex software sales.
You don’t need the BDR to be the technical expert.
You need them to understand enough to recognize an opportunity and communicate why the prospect should explore it further.
The technical expert can handle the technical conversation.
The BDR needs to get them into the room.
The answer will vary depending on the product and market, but the framework is relatively simple:
Identify a relevant problem.
Create curiosity around how other organizations are addressing it.
Ask a question that gets the prospect thinking.
Establish that the problem may have a measurable cost.
Offer a meeting where the prospect can learn more.
Make it clear that there is no obligation to buy.
For example:
“We’ve been working with organizations that are struggling with [problem]. One thing we’ve found interesting is that many of them don’t realize how much that issue is actually costing them until they take a closer look. I’m not suggesting you need to change anything today, but I think it would be worthwhile to show you what we’re seeing and how other organizations are approaching it. If nothing else, you’ll walk away with some ideas you can evaluate internally. Would you be open to taking a look?”
That’s selling the meeting.
Not the product.
At the end of the day, a BDR doesn’t control whether a prospect buys.
They don’t control the budget.
They don’t control the procurement process.
They don’t control the competition.
They don’t control the timing.
But they do control whether the prospect has a compelling reason to continue the conversation.
That is the skill.
The BDR creates the bridge between a prospect who may not know your company exists and a sales professional who can eventually determine whether your solution is a fit.
That’s why I believe the most effective BDRs don’t try to close the sale.
They earn the conversation that makes the sale possible.
Complex B2B sales require patience.
A prospect isn’t going to understand the full value of an ERP system, engineering platform, SaaS solution, telecommunications service, or other sophisticated technology in a five-minute cold call.
And they shouldn’t have to.
The first conversation has a different job.
Create relevance.
Uncover pain.
Challenge the status quo.
Create curiosity.
Demonstrate value.
And earn the appointment.
Then make sure the appointment actually happens by sending the invitation immediately and confirming it before the meeting.
The best BDRs understand something that is easy to forget:
You don’t have to sell the solution to sell the meeting.
You simply have to give the prospect a good enough reason to believe that the meeting will be worth their time.
If you can consistently do that, you’re no longer just generating activity.
You’re creating qualified conversations—and qualified conversations are where predictable pipeline begins.
Chameleon Group helps technology and B2B organizations build consistent business development programs through a combination of outbound prospecting, inbound support, appointment setting, and sales development. Our approach is built around creating meaningful conversations and becoming an extension of our clients’ sales teams.
"*" indicates required fields