Salesforce Leads: When to Use Them and When Not To
Should your sales team be using Salesforce Leads?
It's a surprisingly important question. We've seen organizations where using the Lead object would make their sales process considerably more effective. We've also seen situations where Leads add unnecessary complexity and create more work for salespeople.
The challenge is that Salesforce gives you the flexibility to use Leads in different ways. But that doesn't mean every organization should use them the same way.
The decision really comes down to how your business finds prospects, how you qualify them, and how your sales process works.
Let's take a closer look.
What Is a Salesforce Lead?
A Salesforce Lead represents a person or prospective customer your organization believes may be worth pursuing, but who hasn't yet been qualified or established as a customer relationship in your CRM.
Think of a Lead as a business card.
You may have someone's name, company, email address, phone number and perhaps a little information about their interests. But you probably don't know enough yet to determine whether there's a real sales opportunity.
Where did that Lead come from?
Someone filled out a form on your website.
Marketing purchased or generated a list of potential prospects.
A salesperson met someone at a trade show.
Someone responded to a campaign.
A referral or networking conversation produced a name worth following up with.
In each case, you have a person worth contacting, but you may not yet have a qualified sales opportunity.
That's the key distinction.
A Lead is a potential prospect. An Opportunity represents a potential sale that has progressed far enough to enter your defined sales process.
The distinction matters because your CRM should reflect where someone actually is in the buying journey.
What Happens to a Lead?
Once a Lead enters Salesforce, your sales process should determine what happens next.
There are three common scenarios.
1. The Lead Isn't a Fit
You attempt to contact the Lead, but there's no response after reasonable follow-up. Perhaps the person isn't interested, doesn't meet your target criteria, or simply isn't a viable prospect.
In this situation, the Lead can be marked as unqualified or closed out using the appropriate Lead Status in your Salesforce environment.
The important thing is to distinguish between a Lead that isn't a fit and one that simply isn't ready yet.
You don't want to waste time pursuing unsuitable prospects, but you also don't want to discard potentially valuable relationships prematurely.
2. The Lead Is Interested, but Not Ready to Buy
This is where things get a little more interesting.
You connect with the person. They're open to a conversation, perhaps interested in your products or services, but there's no immediate buying opportunity.
Maybe they're researching options. Maybe their budget isn't available until next year. Or perhaps they simply want to stay informed.
What should you do?
That depends on your qualification process.
If the person is still early in the buying journey, it may make sense to keep the record as a Lead and continue appropriate follow-up or marketing nurture.
If the person meets your organization's criteria for an established prospect relationship, you may choose to convert the Lead into an Account and Contact without creating an Opportunity.
The distinction is important. Converting every person who expresses mild interest can create unnecessary Accounts and Contacts and make your pipeline harder to manage.
Conversion should reflect a meaningful change in the relationship, not simply a desire to move a record somewhere else.
3. The Lead Becomes a Qualified Sales Opportunity
This is the outcome every salesperson wants.
You've established contact. There's a potential business need. The prospect fits your target market, and there's enough evidence to justify moving into your sales process.
This is where Lead conversion becomes particularly useful.
When you convert a Lead in Salesforce, you can create:
An Account representing the company or organization.
A Contact representing the person you're working with.
An Opportunity, if a potential sale has been identified and meets your criteria for entering the pipeline.
At this point, the Opportunity should be managed through your defined sales stages, with appropriate next steps, estimated value and a realistic close date as the information becomes available.
One important detail: Salesforce doesn't simply delete a converted Lead. The record is retained as a converted Lead, allowing the organization to preserve its history and recognize that the person has been converted into the appropriate CRM records.
The key is that the Lead has served its purpose. The ongoing sales relationship is now managed through the Account, Contact and, where appropriate, Opportunity.
So, Should Your Organization Use Salesforce Leads?
The answer depends largely on how your organization generates and manages prospects.
When Leads Make Sense
Leads are particularly useful when your organization has a large or constantly changing pool of potential prospects.
Consider a company that generates hundreds or thousands of new names every month through marketing campaigns, website inquiries, events, referrals and outbound prospecting.
Most of those people won't immediately become qualified opportunities.
Using Leads gives the organization a place to capture and work through that volume without creating an Account and Contact for every name that enters the system.
It also gives marketing and sales a way to manage early-stage prospecting before a person becomes part of an established customer or prospect relationship.
Leads can be especially useful when:
You have a high volume of inbound inquiries.
Marketing generates prospects that require sales qualification.
Your salespeople conduct substantial outbound prospecting.
You need to distinguish unqualified names from established business relationships.
You want a defined handoff between marketing and sales.
In these situations, the Lead object can help keep your CRM organized and give sales managers visibility into early-stage prospecting.
When Leads May Not Be Necessary
Now consider a different type of organization.
Perhaps your company sells to a relatively small, well-defined group of businesses. Your salespeople already know which companies they are targeting. They may have existing relationships with several people at each organization, and their work is focused on developing those accounts over time.
This is common in strategic account selling, enterprise sales and some relationship-driven industries.
In this environment, creating a separate Lead record every time a salesperson meets a new contact may introduce unnecessary steps.
Your organization may be better served by creating or maintaining the Account and Contact records directly, then associating Opportunities with those relationships when a potential sale is identified.
That doesn't mean Leads are inherently wrong for account-based selling. They can still be useful when new names enter the organization and require qualification.
But if your sales process is already built around a finite set of target accounts and established relationships, you should question whether a separate Lead qualification process adds meaningful value.
The goal isn't to use every Salesforce object. It's to use the objects that support the way your organization sells.
The Bigger Issue Is Your Sales Process
Here's where I think organizations often get this decision wrong.
They start with the Salesforce configuration.
Should we turn on Leads? Which Lead Status values should we use? Should we convert at this point or that point? What fields should be required?
Those are all reasonable questions. But they're not the first questions you should be asking.
Start with your sales process.
How does someone enter your sales organization? What makes a person worth pursuing? When do you consider a prospect qualified? At what point does a potential sale become an Opportunity? Who is responsible for each step?
If those questions aren't clearly answered, configuring the Lead object is largely guesswork.
You may end up with salespeople converting Leads too early, leaving them untouched for months, or bypassing the Lead object entirely because it doesn't fit the way they work.
That's not a Salesforce feature problem. It's a process problem.
Your sales process should determine how you use Salesforce, not the other way around.
If you need help defining or refining that process, our Sales Process Consulting approach starts with how your sales organization actually works.
Configure Salesforce to Support the Decision
Once you've decided whether and how to use Leads, the next step is to configure Salesforce accordingly.
That includes decisions such as:
Which Lead Status values are needed?
What information must be captured before a Lead can progress?
What makes a Lead qualified?
When should conversion take place?
Should conversion create an Opportunity automatically, or only when specific criteria are met?
What reports do sales managers need to monitor Lead volume, qualification and conversion?
Keep the design as simple as possible.
A Lead record should make it easy for salespeople to capture the information they need, take the next action and understand what is expected of them.
Avoid adding fields and required steps simply because the platform allows you to do so.
The more cumbersome the process, the more likely salespeople are to work around it.
That's why Salesforce Platform Optimization needs to be grounded in the actual requirements of your sales process.
Don't Forget About Adoption
Even a well-designed Lead process won't deliver much value if your salespeople don't use it consistently.
If Leads are supposed to be qualified within a certain period, managers need visibility into whether that is happening.
If conversion is based on specific criteria, salespeople need to understand those criteria.
And if Leads are being handed off between marketing and sales, both teams need to agree on what constitutes a qualified prospect and what happens next.
This is where training, communication, management and reinforcement become essential.
Salespeople need to understand not just how to create or convert a Lead, but why the process exists and how it helps them manage their work.
Managers need to reinforce the process by using Salesforce during pipeline discussions, prospecting reviews and coaching conversations.
That's the people side of the equation. Without it, even a well-configured Lead process can quickly become inconsistent.
Leads, Accounts, Contacts and Opportunities Need to Work Together
The Salesforce Lead object isn't inherently good or bad.
It is simply one part of a larger CRM structure.
Leads help you manage potential prospects before they become established relationships. Accounts and Contacts represent the organizations and people you work with. Opportunities represent potential sales that have progressed into your sales pipeline.
The important thing is knowing when and why a record should move from one part of that structure to another.
When those decisions reflect a well-defined sales process, Salesforce becomes easier to use, reporting becomes more meaningful, and managers get better visibility into what's happening across the sales organization.
This is exactly why we approach Salesforce through Process, Platform and People.
Process defines how your organization finds, qualifies and manages prospects.
Platform configures Salesforce to support that process without unnecessary complexity.
People ensure that salespeople and managers understand the approach and use it consistently.
If you're questioning whether your sales team should be using Leads, that's a good place to start.
Don't begin by asking which Salesforce object you should use.
Start by asking how your sales organization should manage prospects.
Then make Salesforce support that decision.
The right Salesforce configuration is the one that makes your sales process work better.
