Lead
A Lead is an unqualified prospect record in Salesforce: a person or company that has shown interest in what you sell but has not yet been validated as worth the sales team's time.
Definition
A Lead is an unqualified prospect record in Salesforce: a person or company that has shown interest in what you sell but has not yet been validated as worth the sales team's time. Leads carry name, company, email, phone, status, source, and any other discovery fields your org collects. They sit in a holding pattern (Open, Working, Nurturing, or whatever Lead Statuses your org configures) until they convert into an Account, a Contact, and usually an Opportunity, or they get disqualified out of the funnel.
The Lead object exists because Salesforce wants to keep prospects separate from customers until somebody on the team has decided they belong. A Lead is not yet an Account. A Lead is not yet a Contact. Mixing the two breaks reporting (your "active customers" count balloons with people who never actually bought) and breaks sharing (Account-team rules do not extend to prospects who have not been mapped to an Account yet). Lead conversion is the moment a prospect graduates into the customer schema, and the design of that conversion process is one of the best uses of a sales operations team's time.
Why Lead design shapes every funnel report you will ever build
Lead conversion
Lead conversion is the single most consequential thing that happens to a Lead. The conversion process takes one Lead record and produces up to three new records: an Account (or matches an existing one), a Contact (or matches an existing one), and optionally an Opportunity. The original Lead is marked Converted and effectively goes read-only. Field values on the Lead that map to Account, Contact, or Opportunity fields through the Lead-field-mapping setup carry over; everything else gets dropped. Custom fields that exist on Lead but not on Account or Contact (or vice versa) are the most common source of data loss at conversion, and most teams discover the gap a quarter after they wrote the validation rule that depends on the missing field. Build the conversion field map first, the validation rules second.
Lead Status
Lead Status is the field most of your reports key off. The default values (Open - Not Contacted, Working - Contacted, Closed - Converted, Closed - Not Converted) survive most implementations until somebody asks for "leads we tried twice and bounced." Then your status set expands. Each status maps to a Lead Status Category (Open, Working, Nurturing, Converted, Unqualified) that drives Marketing Cloud nurture pathing and most attribution reports. Keep the count short, and resist letting reps invent statuses for their own funnel slices, because every status you add is another bucket nobody is responsible for emptying. The biggest source of stale Leads in most orgs is statuses that mean "someone else's problem now," with no actual someone else.
Lead Source
Lead Source is the field that finance and marketing fight over for the rest of the company's life. Source captures where the Lead came from: trade show, web form, paid ads, partner referral, cold outbound, organic search, whatever your org tracks. Marketing attribution depends on this field being populated honestly, and the honest part is the hard part. Reps frequently overwrite Source to claim outbound credit on inbound Leads; marketing tooling occasionally writes Source on the wrong record. The healthiest orgs lock Lead Source against edit after the initial save and capture later attribution touches in custom multi-source fields or in Salesforce Campaign Influence. Single-touch attribution from Source alone is a known compromise, not a target.
Web-to-Lead
Web-to-Lead is the Salesforce-provided endpoint that lets a public web form drop a Lead into your org. It is free, it is fast to wire up, and it is also the easiest path to a Lead-spam disaster. The default endpoint accepts any POST without authentication and creates a Lead row, which means a single bot run can put fifty thousand Leads into your org overnight. Production Web-to-Lead implementations add reCAPTCHA, honeypot fields, server-side validation, and a duplicate rule that prevents the same email from creating ten Leads in a minute. Marketing Cloud, Pardot, and HubSpot offer their own form integrations that bypass Web-to-Lead entirely and are usually better choices for any org running marketing automation seriously.
ABM and account-matched Leads
Account-Based Marketing changed how some orgs think about Leads. Under ABM, marketing targets specific named Accounts rather than capturing anonymous Leads who happen to fill out forms. Leads still exist in the ABM model, but they are pre-mapped to a target Account at capture and routed differently. Salesforce has built-in features for this (Account Matching for Leads, Demandbase integration, 6sense integration through AppExchange) that let inbound Leads pair to their parent Account during ingestion rather than at conversion. If your sales motion is heavy ABM, set up Account Matching early; the cost of retrofitting it after a year of unmapped Leads is significant.
Disqualifying Leads
Disqualifying a Lead is just as important as converting one, and most orgs get the disqualification path wrong. The default Closed - Not Converted status drops a Lead out of working queues but does not delete the record. The Lead stays in the org forever, sometimes surfacing in stale-Lead reports years later. Healthy orgs build a Lead-disqualification flow that captures the reason (Bad Fit, No Budget, No Authority, Bad Timing, Already a Customer), routes the reason into reporting, and optionally reactivates the Lead after a defined nurture period. Disqualified Leads with no reason captured are a dataset Marketing cannot mine, which is exactly the opposite of why the team paid to capture them in the first place.
How to create a Lead
Creating a Lead is most often done by an automated capture path (web form, marketing tool, list upload) rather than by hand. The manual create flow still matters for outbound reps and for one-off captures, and the choices you make at create time shape what conversion looks like later.
- Open the Leads tab
From the App Launcher, search Leads and open the list view. Most orgs filter the default view to My Leads or My Open Leads to avoid surfacing the entire org's prospect pile.
- Click New
The New button sits at the top of the list view. If your profile lacks Create on Lead, the button is hidden; that is an admin conversation rather than a workaround.
- Fill the name and company
LastName and Company are the only platform-required fields. Most orgs add validation rules requiring Email or Phone too, since a Lead with no contact channel is not actionable.
- Set Lead Source
Pick the source honestly. The field gets read by marketing attribution and by sales-operations capacity planning. Default it to your team's primary channel only if you cannot determine the actual source, and audit Source distribution monthly to catch drift.
- Pick a Lead Status
Most orgs configure New or Open - Not Contacted as the default. Skip ahead only if you have actually contacted the Lead; reps who pre-promote Leads break the funnel report by hiding rep-side work.
- Save and assign
Click Save. Assignment rules fire on create if configured, routing the Lead to the right rep or queue based on territory, source, or named-account matching.
The platform-required name field on a Lead. FirstName is optional but most orgs require it via page layout.
Required. The buying organization the Lead represents. For B2C orgs, set this to a literal name like "Individual" or the Lead's full name; for B2B, use the company they work at.
- Web-to-Lead has no authentication on its default endpoint. Add reCAPTCHA, server-side validation, and a duplicate rule before you publish a public Lead form, or you will fight Lead-spam for a quarter.
- Lead conversion drops field values that do not have a corresponding mapping on Account, Contact, or Opportunity. Build the conversion field map in Setup before you write validation rules that depend on those fields surviving.
- Disqualified Leads stay in the org forever by default. Build a flow that captures the disqualification reason and routes long-stale Leads to either reactivation, archive, or hard delete.
- Lead Source edits after capture are the most common source of attribution noise. Lock Lead Source against post-save edits or layer Salesforce Campaign Influence on top to track multiple touches.
Trust & references
Cross-checked against the following references.
- LeadsSalesforce Help
- Convert Qualified LeadsSalesforce Help
- Set Up Web-to-LeadSalesforce Help
Straight from the source - Salesforce's reference material on Lead.
- LeadsSalesforce Help
- Lead (Object Reference)Salesforce Developers
Hands-on resources to go deeper on Lead.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. How does Lead support the sales process in Salesforce?
Q2. Which Salesforce Cloud is Lead primarily part of?
Q3. What metric would Lead typically help improve?
Discussion
Loading discussion…