A working Salesforce lead lifecycle gives every stage a written entry rule, a named owner and a defined exit. Keep Lead Status for the rep's working state, and track stages like MQL and SQL in a separate lifecycle field. Require a reason whenever a lead is disqualified or recycled. Date-stamp each stage, so funnel reports show where leads stall rather than who to blame.
Why do marketing and sales keep arguing about lead quality?
Usually because the two teams use the same words for different things. Marketing counts a lead as qualified when it crosses a score, while sales counts it qualified after a conversation.
The fix is not a better dashboard. It is a short document that defines each stage, plus Salesforce fields that enforce it.
Signs your lifecycle needs work:
- Lead Status has a dozen values, and half of them mean roughly the same thing.
- Nobody can say how many leads became MQLs last quarter without a spreadsheet.
- Disqualified leads have no reason recorded, so marketing cannot learn from them.
- Reps convert some leads on first contact and others only after a closed deal.
Which lifecycle stages should we define?
Most B2B teams land on six or seven stages. The list below is a common pattern, not a Salesforce standard, so rename stages to match how your teams already talk.
- Raw or new: a person entered Salesforce but nobody has judged them yet.
- MQL: marketing believes the lead is worth a sales conversation.
- SAL, or sales accepted: a rep has reviewed the lead and agreed to work it.
- SQL: the rep has confirmed a real need and a reason to open a deal.
- Converted: the lead became a contact, usually with an opportunity.
- Disqualified: the lead will never buy, for a recorded reason.
- Recycled: the timing is wrong, so the lead returns to marketing nurture.
Fewer stages are easier to govern. Add one only when a different person owns it or a different action follows.
Should lifecycle stage live in Lead Status or its own field?
Use both, for different jobs. Lead Status describes what the rep is doing now, while a lifecycle stage field records how far the person has progressed.
Lead Status is a standard picklist, and some of its values can be flagged as converted statuses. Those flagged values are what users choose when they convert a lead. If you use lead record types, a Lead Process controls which status values each type shows.
Cramming MQL and SQL into Lead Status causes trouble. A rep changes the value to Contacted, and the record no longer says it was ever an MQL. A separate Lifecycle Stage picklist, updated by Flow, keeps the funnel position intact while reps use Lead Status freely.
What enters and exits each stage, and who owns it?
Each stage needs a rule anyone can test against a record, plus a single owning team. If two teams own a stage, neither does.
| Stage | Entry criteria | Owner | Exit or next step |
|---|---|---|---|
| Raw | Record created by a form, import, event list or integration | Marketing ops | Meets the MQL threshold, or is disqualified on fit |
| MQL | Fit and engagement cross the agreed threshold | Marketing until assigned | Routed to a rep or queue, starting the response clock |
| SAL | Rep reviews the lead and accepts it within the agreed window | Sales development or the assigned rep | Qualified to SQL, rejected with a reason, or recycled |
| SQL | Rep confirms need, authority or timing in a logged conversation | Account executive | Converted, usually with an opportunity |
| Converted | Lead converted to a contact under an account | Opportunity owner | Opportunity stages take over from here |
| Disqualified | Fails a hard fit rule; reason required | Whoever disqualified it | Closed; reviewed in aggregate by marketing ops |
| Recycled | Not ready now; reason and recycle date required | Marketing | Back to nurture, can re-qualify as MQL later |
Write criteria as field conditions that Flow can check, never as opinions like "looks promising".
How do we set the MQL threshold?
Base it on fit and engagement measured separately, then agree a cut-off with sales. Our lead scoring guide covers the scoring models and how to review them.
For the lifecycle, the key decision is mechanical: what event flips the stage to MQL. Usually a record-triggered Flow watches the score and grade fields and sets the stage once both pass. Stamp the date at the same moment. Flag any MQL set by hand, so reviews can tell manual MQLs from automatic ones.
What should happen at the handoff from marketing to sales?
The handoff needs an assignment, a response window and an explicit acceptance step. Acceptance turns a lead marketing pushed into one sales agreed to work.
Assignment and response timing belong to routing; our lead routing guide covers rules, round robin and escalation. The lifecycle adds the acceptance decision. Give reps three choices on every MQL: accept, reject with a reason, or recycle with a reason. A quick action or a screen Flow makes this a single click.
Rejections are the most useful data the lifecycle produces. Report them by source and campaign. A run of rejections from one webinar tells marketing more than any score review.
How should disqualification and recycling work?
Make the reason required on both, using restricted picklists rather than free text. Then send recycled leads back to marketing with a date, not into a dead end.
Disqualification is for people who will never buy: a competitor, a student, a fake name or a company far outside your market. Recycling is for people who might buy later: no budget this year, a contract still running elsewhere, or no reply after the agreed attempts.
A validation rule can block saving a Disqualified or Recycled status without a reason. When a lead is recycled, a Flow can do the housekeeping:
- Set the lifecycle stage to Recycled and stamp the recycle date.
- Move ownership to a marketing queue, so the rep's open list stays honest.
- Add the lead to a nurture campaign that matches the recycle reason.
- Count recycles on the record, so leads that loop endlessly are visible.
When a nurtured lead crosses the threshold again, it returns as an MQL with its history attached.
When should a rep convert a lead, and what does conversion create?
Convert when the lead reaches SQL, meaning there is a real conversation about a possible deal. Converting earlier fills the pipeline with weak opportunities, and converting later hides real deals.
Conversion creates a contact and an account, or attaches the person to an existing account and contact. Creating an opportunity is optional, through a checkbox on the convert screen. When conversion does create an opportunity, the contact is added as an opportunity contact role, which matters for campaign attribution.
Standard lead fields map across automatically. Custom lead fields only carry over if an admin maps them under Map Lead Fields in the Lead object settings. Mapped fields must have compatible types, so plan the mapping when you create each lead field. Unmapped values stay on the converted lead, which most users cannot open afterward without the permission to view and edit converted leads.
Agree a few more rules up front. Decide which converted status values reps may pick, and whether converting without an opportunity is allowed. Then decide what the lifecycle field shows on the new contact.
What about leads from people who are already customers?
Check them against existing accounts before treating them as new business. A new lead from a current customer may be an upsell, a support request or a duplicate.
During conversion, Lightning shows possible matching accounts and contacts using your matching rules, so the rep can attach the lead to an existing record. Matching before conversion, at intake or routing, usually needs Flow, duplicate rules or an add-on tool. Which approach fits depends on your edition and tools, so confirm options with your Salesforce account team. Our duplicate cleanup guide covers the matching rules underneath.
Many teams report existing-customer leads separately, because their conversion rates distort new-business numbers.
How do we track time in each stage?
Add a date field for each stage and stamp it with Flow the first time a lead enters. Time in stage is then simple subtraction in a formula or report.
Never overwrite a first-entry date, or recycled leads erase their own history. Lead conversion has its own standard converted date, so you only need custom fields for the earlier stages. Field history tracking adds an audit trail, but it is harder to report on.
Which funnel reports should we build first?
Start with volume and conversion between stages, split by lead source and campaign. Leave benchmarks aside; your own trend line is the useful comparison.
- Leads entering each stage per period, by source.
- Stage-to-stage conversion: MQL to SAL, SAL to SQL, SQL to opportunity, opportunity to won.
- Median days in each stage, with the slowest tail shown alongside.
- Rejection and disqualification reasons, by source and campaign.
- Recycled leads that later re-qualified, to prove nurture is earning its keep.
Build these on the lifecycle fields and date stamps. Grouping leads by when they became MQLs keeps old and new leads out of the same rate.
Who should be allowed to change the definitions?
One owner, usually revenue operations, with marketing and sales leaders signing off on any change. Definitions changed quietly break every trend line built on them.
Log every change with a date, and annotate dashboards when a threshold moves. Restrict who can edit the lifecycle picklists and the Flows that set them.
Which of our projects involved lead handoff?
A marketing firm moving its cadences from Outreach to Salesforce Sales Engagement needed MQLs to reach reps cleanly. We automated assignment of Marketo MQLs into the right cadences with proper ownership timing, alongside High Velocity Sales call dispositions.
A compliance-software company migrating from HubSpot to Sales Cloud and Account Engagement came out with clear MQL-to-SQL handoffs. Scoring, grading and nurture programs in Account Engagement sat behind that handoff.
A business lender received far more leads than its sales team could work. Part of our work there was a prioritization framework that separates fit, as a lead grade, from progress, as a lead score.
What should phase one cover?
Phase one should agree the definitions and make the core stages visible in Salesforce. Automation beyond stamping and recycling can follow once the numbers are trusted.
- Write the stage definitions, entry criteria and owners, and get both leaders to sign.
- Trim Lead Status to a short list and mark the converted values.
- Add a Lifecycle Stage field and a first-entry date for each stage.
- Build the Flow that sets MQL from score and grade.
- Add the accept, reject and recycle step with required reasons.
- Map custom lead fields for conversion and test a conversion end to end.
- Publish one funnel dashboard by source, and review it with both teams.
If your current statuses have grown past repair, a Salesforce optimization project can redesign them without losing history. Our Sales Cloud team can then work with marketing and sales leaders on the definitions.
