Skip down to the research record

5 lead rules to settle before a deal enters your pipeline

Quota Forecast Editorial Team · Published · 12 min read

Settle five shared rules before a lead becomes a deal: its definition, entry criteria, conversion, ownership, and disqualification. Most pipeline arguments are really definition arguments. A sales rep says a prospect is "basically a deal." Marketing says the same prospect is a lead that came in last week. Finance wants to know why the forecast jumped by a number nobody can trace. Each person is using the same words, but they mean different things.

Key takeaways

  • Write one definition of a lead and keep it to one screen.
  • Set entry criteria that two reps would answer the same way.
  • Convert a lead into an account, contact, and opportunity once enough information has been gathered.
  • Give every lead one owner and one system of record.
  • Write down disqualification and aging rules before the pipeline fills up.

At a small B2B software company, this confusion is easy to miss. The founder knows every prospect personally, so nobody writes anything down. That works until the team grows, a second rep joins, or a board member asks how many deals are really in the pipeline. Then the gap between a lead and a deal becomes expensive.

A quick test can show whether your team has a problem. Ask three people who touch revenue to define a lead and a deal, separately and without looking anything up. If the answers differ in wording, scope, or the stage at which a record changes, the pipeline is measuring different things for each person.

This post covers five rules to settle before a lead moves into your pipeline as a deal. None of them requires special software, though your CRM will make them easier to enforce. Each one is a decision your revenue leaders should make once, write down, and revisit as the business changes.

Define what a lead is, and what it is not

Start with the basic definition. A lead is not a customer, and it is not yet a deal. EspoCRM describes a lead as a person or organization that is not currently a customer but has the potential to be. That is a useful starting point because it describes potential, not commitment.

The same source describes creating a lead record as usually the first step in the sale process. A lead is therefore the earliest record of a relationship, and a lot can happen before it becomes something you forecast against.

Your version of this definition should answer three questions:

  • What qualifies someone as a lead? A name from a conference badge scan may not count. A person who replied to a sequence, requested a demo, or filled out a form probably does.
  • What is the lead's status before it becomes a deal? Teams often skip this and let every record sit in the same list, mixing curious visitors with people who have a budget and a timeline.
  • What is the difference between a lead and an opportunity in your system? If your CRM tracks both, each should have a clear meaning. If it does not, decide whether you need both.

Be specific about sources as well. A webinar attendee, a referral from a current customer, and an inbound demo request may all be called leads, but they carry very different levels of intent. Your definition should say whether the team treats them the same or handles each source differently from the first touch.

Write the answers into a short internal page that everyone can read. Keep it to one screen. If nobody can recite the definition from memory, the team does not yet share one. Revisit the page when you add a new channel or change how you sell, because definitions tend to drift when the business changes faster than the paperwork.

Set entry criteria for the pipeline

Once you know what a lead is, decide what makes it ready to enter the pipeline. This is the most important rule in the list because it controls what your forecast means.

A common mistake is to treat the pipeline as a list of hopes. Every lead with a company name goes in, and the total value looks impressive. The forecast then misses every quarter because most of those records never had a real chance.

Entry criteria should be a short checklist that a rep can answer honestly. Useful questions include:

  • Has the prospect confirmed they have a problem your product addresses?
  • Has someone with authority to buy or influence the buying decision engaged?
  • Is there a stated reason to act in a rough timeframe?
  • Has the rep confirmed the company fits the customers you actually serve?

The last question matters more than many teams expect. The prospecting approach Nutshell describes starts with the same idea: users set filters for their ideal customer profile and then start working the matching contacts as leads. The sequence is deliberate. Define who you want before you go looking. If your ideal customer profile is fuzzy, your lead list will be fuzzy too, and every downstream stage will inherit that problem.

Write each criterion so that two reps would answer it the same way. "Strong interest" is hard to verify. "The prospect has shared a current process and named the cost of the problem" is something a manager can check in a call recording or a note. Vague criteria produce inconsistent pipelines, and inconsistent pipelines are hard to fix after the fact.

You do not need a perfect scoring model to start. A written list of required facts, agreed by sales and marketing, is enough. Review it after the team has used it for a while, and adjust based on which deals actually closed and which entered the pipeline and stalled.

Illustrative example: one entry rule in practice

Suppose a team receives 16 inbound leads in one month. Under the entry rule above, 5 of them have a confirmed contact and a stated need, so they enter the pipeline as opportunities. The other 11 stay on the lead list with a review date. The forecast then counts 5 opportunities, not 16.

Decide how and when leads convert

Entry is one step. Conversion is the next. Your team needs a rule for when a lead stops being a lead and becomes the records that actually drive revenue work.

The EspoCRM documentation says that as more information about the lead is gathered, the lead is expected to be converted into an Account, Contact, and/or Opportunity. That sentence contains a useful idea. A lead is not supposed to stay a lead forever. Information accumulates, and at some point the record should split into the parts that matter for selling: the company, the person, and the potential deal.

For a small B2B team, the practical version looks like this:

  • The account: the company that might buy. It should exist once, even if several people at that company are involved.
  • The contact: the individual you are talking to. One company can have several contacts with different roles, such as an end user, a technical evaluator, and a budget holder.
  • The opportunity: a specific potential purchase with an expected value and a stage. This is what goes into the pipeline.

The same source also notes that leads cannot be converted to Accounts if the system is set to B2C mode. That detail is worth noticing even if you use a different CRM. Your data model should match your business model. If you sell software to other businesses, you need a structure that treats companies as first-class records.

Consider a simple example. A prospect fills out a demo form using a personal email address. The rep researches the company, finds the right person to talk to, and learns that the company has a specific workflow problem. At that point the team can create one account for the company, one contact for the person, and one opportunity for the workflow problem. If the rep instead creates a new record for every person who replies, the same company appears three times, the forecast counts it three times, and nobody knows which record holds the real history.

Write down what conversion requires. For example, you might require a company name, a confirmed contact, and a stated need before creating an opportunity. Then make sure everyone uses the same conversion step. Unplanned conversions are how duplicate accounts and orphaned contacts appear.

Assign ownership and pick one system of record

Every lead needs an owner, and there needs to be one place where the lead's status is authoritative. This sounds obvious, but small companies often keep leads in a spreadsheet, a shared inbox, a sales engagement tool, and somebody's notebook. When the same prospect appears in four places with four different statuses, the pipeline stops being reliable.

Ownership answers a few questions. Who is responsible for following up? Who can change the stage? Who decides when a lead is disqualified? Each should have one answer. Shared ownership usually means no ownership, because when two people are responsible, each assumes the other will act.

The system of record question is closely related. Tools matter here, and the right choice depends on how your team already works. The CRM market has split into products built for different team shapes. One vendor's guidance warns that a platform that fits well at 10 people often fits poorly at 30, because the gaps show up faster than most teams expect. Copper describes its own product as one that teams use to run their whole client lifecycle without leaving the tools they already have open. Both approaches can work. The mistake is choosing a tool without thinking about how many people will touch leads, and whether they will update records in it.

Practical steps:

  • Pick one system where lead status lives. Other tools can feed it, but they should not replace it.
  • Give every lead a single owner, with a reassignment process for when someone leaves or changes roles.
  • Require that stage changes happen in the system, not in side conversations or chat messages.
  • Review the setup when your team size changes. A process that works for a small group may not survive the next round of hiring.

If a rep can change a lead's stage without anyone else knowing, the forecast is a guess. Ownership and a single source of truth are what turn a list of contacts into a pipeline the business can manage. For how stage changes feed the forecast, see Pipeline, Best Case, Commit: Forecast Categories Explained.

Define disqualification and aging rules

The last rule is the one teams avoid most often: when do you stop working a lead? Without a clear answer, leads accumulate. They sit in early stages for months. Reps keep them alive because deleting them feels like admitting failure. The pipeline grows, but its value shrinks.

Disqualification rules protect the pipeline from this drift. They say what counts as a dead lead and what action is required. Common triggers include:

  • The prospect is outside the ideal customer profile.
  • The prospect has no active need and has declined to revisit the topic.
  • The prospect has not responded after a defined set of follow-up attempts.
  • The prospect is a duplicate or has been merged into another record.

Each trigger should have an action. The usual options are to move the record to a nurture list, mark it lost with a reason, or archive it. The reason matters. Over time, lost-reason data tells you which lead sources and profiles produce poor fits, which is far more useful than a raw win rate. If most lost leads came from one channel, that channel needs a different entry rule, not more follow-up.

Aging rules are the companion. Decide how long a lead can stay in an early stage before someone must review it. You do not need to pick a perfect threshold on day one. Choose a review interval your team can actually keep, such as a weekly review of stale records, and treat anything that misses it as a flag for a conversation. A stale lead is not a problem by itself. A stale lead that nobody notices is. If you also need to track why a close date moved, see Close date change log: why the date moved.

These rules also make your forecast honest. When leads are removed on a predictable basis, the remaining pipeline reflects real opportunities. Leaders can then look at the numbers and trust them.

Common mistakes to avoid

Teams that struggle with these rules tend to make the same few errors. The first is changing definitions silently. A rep who decides that a lead now includes anyone who attended a webinar has changed the meaning of the pipeline, and the change will not show up in the numbers until someone compares quarters. Any change to a definition should be announced, written down, and dated.

The second mistake is creating records faster than they can be maintained. Every duplicate account adds noise to reports and makes it harder to see the real history with a customer. Duplicate checks at creation time are cheaper than cleanup later, and a short review before merging records keeps the data usable.

The third is treating the pipeline as a reporting tool rather than a management tool. A pipeline that is only reviewed at month end will always lag reality. Short, regular reviews of stage changes, stale records, and new entries catch problems while they are still small.

The fourth is skipping the people who do the work. Rules written without input from reps tend to be ignored, because they describe a process nobody actually follows. Involve the people who will use the rules, and make it easy to ask questions when a case does not fit.

Putting the five rules together

These rules are connected. Your definition of a lead determines your entry criteria. Entry criteria determine what converts into an account, contact, and opportunity. Ownership determines who makes those decisions and where they are recorded. Disqualification keeps the whole structure from filling with records nobody will close.

You do not need to settle all five in one afternoon. A reasonable order is to write the lead definition first, then the entry criteria, then conversion, then ownership and tooling, and finally the disqualification and aging rules. Each step builds on the last, and each produces something you can put in front of the team.

Involve the people who will live with these rules. The sales team will tell you where the entry criteria are unrealistic. The marketing team will tell you which lead sources produce qualified prospects. The finance team will tell you which definitions the forecast must support. Get their input before you publish the rules, and expect to revise them after a period of real use.

Above all, write the rules down. A shared meaning exists only when it is written and used. The goal is not to create bureaucracy. It is to make sure that when someone says "we have a deal," everyone in the room means the same thing.

Next step: today, write a one-sentence definition of a lead and send it to the three people from the quick test above. Ask each one to name any word they would change.

Frequently asked questions

Do we need a CRM before we can settle these rules?

No. The rules are written decisions, and a CRM only makes them easier to enforce.

Who should decide the entry criteria?

Sales and marketing should agree on them together, then review them against deals that closed and deals that stalled.

How often should the rules change?

Revisit them when you add a lead channel, change how you sell, or when the team changes size.

Sources