Lead
A lead is a not-yet-qualified contact who has signalled interest in a product or service through a first interaction – such as an enquiry, a trade-fair visit or a newsletter download. The lead is thus the starting point of every sales process and the precursor to a qualified sales opportunity.
A lead is a not-yet-qualified contact who has shown interest in a company’s offering through a first interaction. This can be a contact request via a web form, a whitepaper download, a conversation at a trade-fair stand or a newsletter sign-up. Characteristically, at this point it is not yet clear whether real demand exists, nor whether the contact is able and ready to buy. The lead therefore marks the moment an interested party enters the sales or marketing process – the start of the chain that, ideally, leads through qualification and quotation to a customer.
In business terms, the lead is the smallest controllable unit of new-customer acquisition. An anonymous target audience becomes a concrete, named contact that marketing and sales can develop systematically. Whether a lead has value is decided only during qualification: does the contact fit the target group, is there a real problem, a budget and a decision-maker? Only when these questions are answered positively does the lead become a genuine sales opportunity. In the ERP and CRM system, the lead is therefore not a loose record but the starting point of an end-to-end process chain, tightly interlinked with the customer master, the sales pipeline and order processing.
At a glance
- Not-yet-qualified contact with a first, signalled buying interest
- Arises from an enquiry, download, trade-fair contact, newsletter or referral
- Starting point of the sales process – the precursor to a qualified opportunity
- Assessed and enriched via lead scoring and qualification
- In the ERP/CRM interlinked with the sales pipeline, quotation and customer master
What is a lead – and what is it not yet?
A lead is more than a mere address, but less than a solid sales opportunity. It typically consists of contact data – name, company, email, phone – supplemented by information on the channel and context in which the interest arose. This origin (the “lead source”) matters because it strongly influences later value and approach: a contact who has actively requested a quote is closer to a purchase than someone who has merely read a blog article.
What matters is what a lead is not yet. It is not a customer, because there is neither an order nor a contract. It is not yet a qualified sales opportunity either, because demand, budget and decision-making authority are untested. And it is more than a mere interested party in the anonymous sense, because it has identified itself through a concrete action. This intermediate status explains why leads are captured, assessed and developed separately – rather than being carried straight away as customers in the master data.
Components of a lead record
A properly maintained lead record contains, besides the contact data, at least the lead source, the capture date, the responsible handler and the current status in the qualification process. Often an area of interest or product reference, a lead score and a field for the next planned action (follow-up) are added. This structure makes the lead analysable: you can see which channels generate how many contacts and how they develop through handling.
How a lead is qualified
Qualification is the core of lead work. It clarifies whether a contact has the potential to close and determines the priority with which it is handled. In practice, two levels of maturity are distinguished: a Marketing Qualified Lead (MQL) has shown, through its behaviour – downloads, repeated website visits, response to campaigns – enough interest that marketing considers it worth passing to sales. A Sales Qualified Lead (SQL) has confirmed in direct contact that a concrete need, a budget and a timeframe exist; it is handed over to sales.
Assessment is often based on lead scoring, which awards points for characteristics (industry, company size, contact’s position) and for behaviour (opens, clicks, page views). Once the score exceeds a threshold, the lead changes status and is handled with priority. Established frameworks such as BANT (Budget, Authority, Need, Timing) structure the qualification conversation by probing the decisive questions of budget, decision-making authority, need and timing.
MQL, SQL and the handover to sales
Cleanly separating MQL and SQL prevents sales from spending time on immature contacts and stops valuable leads from getting stuck in marketing. The prerequisite is a clearly defined handover logic: from which score or which event does a lead count as sales-ready? Who takes it over, and within what deadline is it contacted? A process agreed between marketing and sales – often documented as a service-level agreement – ensures no lead lapses unhandled.
Lead nurturing for cold interest
Not every lead is ready to close immediately. Contacts with fundamental but not yet acute interest are developed through lead nurturing: automated, content-relevant communication keeps the contact warm until the need becomes concrete. This keeps a lead that is “cold” today in view so it can mature into an SQL months later, without being lost in the data.
Why leads matter for sales
Leads are the raw material of new-customer acquisition. Without a continuous inflow of new contacts, the sales pipeline dries up and tomorrow’s revenue fails to materialise. But because not every lead becomes a customer, the decisive figure is not sheer volume but quality and conversion: how many leads become opportunities, and how many of those become orders? From these ratios – the lead conversion rate across the individual stages – you can measure the performance of marketing and sales and derive the revenue forecast.
At the same time, every lead incurs costs. Cost per lead and cost per acquisition show how expensive it is to win a contact and a new customer. A company that cleanly analyses its leads by source and quality can steer its marketing budget towards the most profitable channels and shut down poorly converting sources. This turns the lead perspective from a purely sales topic into a business-management control variable.
Distinctions: lead, prospect, opportunity and customer
The terms of the sales chain are often mixed up in daily use, yet they denote clearly distinguishable levels of maturity. An anonymous prospect belongs to the target group but has not yet made itself known. As soon as it becomes identifiable through a concrete action, the lead arises. Once the lead is qualified – need, budget and decision-maker are established – it becomes an opportunity (sales opportunity), carried in the pipeline with a value, a probability of closing and an expected date.
The final step is the transition to customer: a won opportunity becomes a contractual relationship via quotation and order, and the contact is transferred into the customer master. This sequence – prospect, lead, opportunity, customer – is at the same time the logical structure on which CRM and ERP systems are based. Whoever mixes the stages loses control: carrying raw leads as customers dilutes the master data; treating qualified opportunities like leads deprives sales of prioritisation.
The lead in the ERP and CRM system
In an integrated ERP or CRM system, the lead is carried as its own object type, forming the precursor to customer and order. Incoming contacts from a web form, shop, trade-fair app or email land in the system automatically, are assigned to a handler and pass through defined statuses. Central to this is duplicate checking: so that an already known contact is not created twice, the system matches new leads against the existing base. Clean data quality at this point prevents multiple records for one customer from existing later.
The real benefit of integration lies in the seamless flow. When a lead is qualified, an opportunity and ultimately a quotation arise from it – without the data captured once having to be re-entered. If the customer accepts, the lead is transferred into a customer record, and the document chain continues via order, delivery note and invoice. Because all stages build on the same data, origin, history and communication trail remain fully traceable. It is precisely this traceability that makes lead analysis – from source to closed order – possible in the first place.
From lead to sales pipeline
As soon as a lead counts as sales-ready, it becomes an opportunity in the sales pipeline. There it is given an estimated value, a stage and a probability of closing, from which a weighted forecast is calculated. Sales can thus see at a glance which opportunities are close to closing and where follow-up is needed. The seamless connection from lead source to pipeline stage also provides the data basis for identifying the most effective marketing channels.
Example
Example: a B2B machine builder structures its trade-fair leads
A mid-sized machine builder collects around 300 contacts at a trade fair – business cards, stand conversations, completed prospect forms. In the past, these slips ended up in a drawer, were sporadically phoned round weeks later, and a large share fizzled out because no one followed up systematically. Which contacts really had demand could barely be reconstructed afterwards.
After introducing a CRM-supported lead process, all trade-fair contacts are captured on-site by tablet and automatically created as leads with the source “Trade Fair 2026”. A duplicate check matches them against the existing base, and simple scoring by industry and area of interest prioritises the most promising contacts. Sales works through the leads within a week, qualifies them in conversation by budget and timeline, and transfers mature contacts into the pipeline. The result: from the same 300 contacts, significantly more quotations arise, and the machine builder knows for the first time, reliably, what revenue the trade fair actually generated.
Frequently asked questions
Matching ERP systems
Related services
Questions about Lead in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.