What an Org Map Should Tell You Before a BD Call

Most BD calls fail before they start, not because the consultant lacks skill, but because they go in knowing almost nothing useful about the person on the other end of the phone. An organisational map is supposed to fix that — and when it is built properly, it does.

The problem is that what gets called an organisational map varies enormously. Some are genuinely useful. Others are little more than a LinkedIn printout with a job title and a phone number, dressed up to look like research. Understanding the difference matters because it determines whether your consultant sounds like someone worth talking to, or someone who could have sent an email.

What a useful organisational map actually contains

A map worth having does more than confirm that a person exists. Before a BD call, your consultant needs to understand the structure around their contact, not just the contact themselves. Who does this person report to? Who reports to them? Where do hiring decisions actually get made — at the line manager level, at HR, at the director level, or does it depend on seniority of the role?

That structural context changes the entire conversation. If your consultant knows that the person they are calling sits two levels below the real decision-maker, they can position the call accordingly — building a champion rather than pitching for a mandate that was never going to be agreed on that call anyway. Without that context, they pitch to the wrong level and then wonder why nothing progresses.

Beyond structure, a useful map captures the signals that suggest a company is actively in motion. Growth into a new market, a department that has been publicly restructuring, a leadership hire that typically precedes a wave of team builds — these are the details that let a consultant open with something specific. Not flattery, not a generic value proposition, but a genuine reason why the timing of this particular call makes sense.

Good organisational mapping also identifies the gaps: roles that are open or likely to open, functions that appear understaffed based on public signals, or areas where the company has historically used agencies. A consultant armed with that kind of intelligence is not guessing. They are working from a foundation.

What a useless one looks like

A weak organisational map has a few consistent traits. It lists names and titles without any sense of how those people relate to each other or to the hiring process. It tells your consultant who the HR Director is, but not whether HR controls recruitment budget for technical hires or whether that sits with the hiring manager directly.

It is also typically flat — a snapshot with no sense of movement. No indication of whether the company is growing, contracting, or stable. No context from recent news, funding, or leadership changes. Just a static list of people that could have been found in under a minute by anyone with a LinkedIn account.

That kind of output does not help a consultant — it just gives them the illusion of preparation. They go into the call feeling ready, and then run out of anything specific to say within the first thirty seconds, because everything they have was already visible to the prospect before the phone rang.

The other failure mode is depth without direction. A map that catalogues every person in a business without flagging who matters for this conversation is almost as unhelpful as having nothing. Volume is not intelligence. Your consultants do not need a directory; they need a brief.

The connection to leads and market research

Organisational mapping does not sit in isolation. It works best when it is built on top of solid leads and market research that has already identified which companies are worth targeting and why. When that upstream work is done properly, the organisational map becomes a focused document about a shortlisted target — not a speculative exercise carried out on every name in a database.

The two together create something your consultants can actually use: a prioritised target list with enough structural and contextual intelligence on each account that the BD call has a clear shape before it begins. That is when RPO services add real weight to a recruitment agency's business development function, because the research work is being handled by people whose only job is to do it thoroughly, while your consultants stay on the phone.

What this means for how your team works

Ask yourself how long your consultants currently spend before a BD call trying to piece together context about a prospect. Ask how often they go in with a name and a title and little else. And ask what proportion of those calls produce a second conversation worth having.

The map is not a magic fix for BD performance. A consultant still needs to run the call well. But there is a meaningful difference between a consultant who opens with something specific and relevant, and one who is winging it from a LinkedIn profile. The first one sounds like someone who has done their homework. The second one sounds like everyone else who calls that day.

If the quality of your pre-call intelligence is something you want to improve without pulling consultants away from the work that bills, it is worth looking at how a dedicated research function could support your delivery. That is exactly the kind of work Logix RPO is set up to handle — thoroughly and at a cost that does not erode the margin you are trying to protect.