Asking junior business managers to make lists of 500 prospects is pointless

Sales Navigator, AI assistants, and enrichment tools can produce lists in minutes that Business Managers would have previously taken several days to compile. The file arrives faster. The understanding of the market, however, does not download along with it.

THE PARADOX
Requesting 500 names from a junior Business Manager is pointless if the goal is only to obtain 500 lines. The value of the work lies in what the junior learns by building, verifying, and prioritizing their prospecting field.

The file gives an immediate impression of progress

In many IT services companies and consulting firms, creating a prospecting portfolio is one of the first tasks assigned to a junior Business Manager. The exercise seems simple: identify several hundred companies and contacts likely to purchase services.

Today's tools have made this production extremely fast. A few filters in Sales Navigator, a request sent to an AI assistant, automatic enrichment, and the junior gets a clean table: company, sector, function, workforce, contact details, and sometimes even a suggested approach.

The result is tangible. It can be shared, counted, and integrated into the CRM. Management sees 500 lines and readily considers the commercial field ready. However, this file does not prove that the accounts are relevant, nor that the contacts are well-chosen, nor that the junior understands what they are going to say to them.

A list can be perfectly presented and commercially poor. For example, it may group together IT directors from large companies without distinguishing those who really manage the areas where the IT services company has expertise, those who buy directly, and those who exclusively go through a procurement department or a closed panel.

Having data is not knowing your market

Knowing a market involves building links between pieces of information that, taken separately, say little. It is necessary to understand the dominant players, the challengers, the decision-making chains, ongoing investments, recurring constraints, and when a company becomes more receptive to an offer.

A Business Manager who receives a list of 500 accounts may know that the company employs 8,000 people and that a program director works there. They do not necessarily know if the organization is centralized, if projects are driven by business units, if providers are referenced at the group level, or if a subsidiary has its own purchasing autonomy.

This difference appears from the first exchange. A junior who only knows the profile delivers a generic pitch. The one who has studied the market can link their approach to a transformation, an organizational model, or an observable tension. They do not just say they provide consultants; they show why the conversation can make sense for this interlocutor.

THREE LEVELS TO DISTINGUISH
Having a list means possessing data. Building a list means acquiring knowledge. Knowing how to exploit it means transforming this knowledge into commercial decisions.

The work of building teaches what matters

Spending time building a portfolio is not intended to verify if a junior knows how to use a search engine. The educational interest lies in the questions they must solve and the judgments they learn to make.

By studying a sector, they discover, for example, that the most visible companies are not always the best targets. A large group may have significant potential while remaining inaccessible to a young IT service company due to lack of referencing. Conversely, a lesser-known mid-sized company may launch a transformation, recruit new management, or quickly seek skills it does not possess internally.

The junior also learns to distinguish a title from a real role. A director may have high visibility but little operational involvement, while a program manager, domain manager, or architect directly influences the use of consultants. This understanding does not arise from accumulating names. It is built by cross-referencing information.

Consider an industrial company that announces a modernization program for its sites. An automated list will bring up the CIO, the transformation director, and a few IT managers. The junior's analysis must go further: which sites are involved, who is leading the program, what expertise will be needed, which entity is contracting, and which partners are already present?

Automating too early deprives the junior of some learning

The challenge does not come from the tools. They are useful for broadening research, verifying a hypothesis, enriching information, or updating a portfolio. The problem arises when they perform the entire intellectual work that the junior should learn to conduct from the start.

If an assistant immediately provides segmentation, the main actors, and a list of contacts, the junior may accept this structure without knowing how it was built. They may take for a fact what is just a hypothesis, ignore missing accounts, and fail to spot inconsistencies.

For example, a tool may classify a company in healthcare based on its primary activity, while the IT services company's offer only concerns an industrial subsidiary. The account seems relevant in the table, but the prospecting angle remains unclear. Without critical reading, the error is simply industrialized across hundreds of lines.

The junior must therefore learn to work without a crutch on a limited sample before accelerating. Studying twenty accounts manually, explaining their classification, and defending the chosen contacts builds more competence than immediately receiving 500 results impossible to verify seriously.

THE RIGHT ORDER
The tool should accelerate an already understood method. When it replaces the discovery of the method, it produces a faster result but slower learning.

A list of 500 names is rarely a commercial priority

The volume reassures because it gives the feeling of not lacking opportunities. But a junior cannot seriously work on 500 accounts at once. They must choose where to focus their attention, in what order, and with what level of effort.

A useful segmentation can distinguish, for example, twenty priority accounts to analyze in-depth, fifty accounts to monitor, and a broader set to maintain or test. Each of these groups requires a different approach.

For priority accounts, the Business Manager can map out the departments, projects, current suppliers, and entry points. For secondary accounts, they can look for a trigger signal before engaging in more in-depth work. For the rest, a lighter approach can verify interest without unnecessarily consuming time.

Without this hierarchy, the list becomes a reservoir from which the junior randomly draws. They contact the easiest people to find, repeat the same message, and mainly measure a volume of activity. The file is dense; the prospecting remains scattered.

The pitch cannot replace understanding

Many organizations ask juniors to quickly learn the company's presentation, its offers, and some suggested lines. This preparation is necessary but becomes sterile if it precedes a full understanding of the field.

A pitch gains value when it selects what is relevant for the contacted person. Faced with a data manager dealing with a migration, the Business Manager doesn't present the entire catalog. They mobilize references, skills, and questions that match the situation.

Conversely, a junior unfamiliar with their market clings to their speech because they have no other reference point. They may recite a very polished value proposition while being unable to adapt when a prospect mentions a different organization, an already engaged project, or a sourcing constraint.

The problem is not that the junior poorly masters their pitch. It is that they are sometimes asked to speak before being taught to read what is in front of them.

WHAT THE PROSPECT HEARS
A generic speech rarely reveals a lack of eloquence. It often reveals that the Business Manager does not know enough about the account, its market, or the issues their interlocutor is facing.

Transforming portfolio construction into a learning exercise

The creation of a list can become a true skill-building sequence if the manager sets a goal different from sheer volume. Instead of asking for 500 names, they can ask the junior to produce an initial argued reading of their market.

The junior starts by defining what makes an account relevant: size, sector, locations, technologies, projects, accessibility, relationship history, or compatibility with available expertise. They then select a small number of accounts, search for missing information, and formulate their hypotheses.

During a debrief, they not only present their file. They explain why three accounts take priority, why a major player was left out, and what signals could change their ranking. The manager can then correct the logic, contribute their field knowledge, and make their own criteria visible.

A second step involves mapping a few accounts: decision-makers, influencers, users, procurement departments, partners already present, and accessible contacts. Finally, the junior prepares a specific conversation angle and tests it in the field. The feedback gathered helps enrich or adjust their initial reading.

Tools then become true accelerators

Once the method is understood, automation finds its rightful place again. It allows for extending a validated segmentation, quickly enriching selected accounts, detecting changes, and keeping information up to date.

A Business Manager can, for example, define with their manager the criteria for a priority account, analyze fifteen companies themselves, and then ask a tool to identify one hundred similar organizations. They no longer receive a ready-made truth; they obtain a set of candidates that they know how to evaluate.

AI can also help them summarize reports, compare structures, detect public projects, or prepare questions. But the junior must remain capable of explaining the source, checking for consistency, and linking information to a commercial decision.

The objective is not to revert to entirely manual research. It is to preserve the moments when effort produces understanding and then automate what no longer brings additional learning.

THE ROLE OF THE MANAGER
Do not just ask how many accounts have been added. Ask what the junior understands better, which choices they can now defend, and how this understanding alters their prospecting.

Execution speed and learning speed are not the same

A list generated in ten minutes accelerates data availability. It does not automatically reduce the time needed to understand a sector, recognize the right signals, and build a relevant approach.

To truly accelerate skill development, the company must organize analysis, hypothesis confrontation, practice, and debriefing. A junior who has studied thirty accounts in-depth can become more quickly autonomous than another who has been given a file of 500 lines and a call objective.

Asking for a large list is neither modern nor outdated in itself. It all depends on what the exercise aims to produce. If the company wants only data, the tools will do the job very well. If it wants to train a Business Manager capable of reading a market and choosing actions, it must maintain an intellectual effort component and provide guidance.

The file can arrive in minutes. Knowledge still requires work. And wanting to eliminate this work in the name of productivity often results in saving a few days of research only to lose several months of learning.