What goes in a market map (and how to present it)

A market map can be built on exactly the right data and still die in the meeting. The client nods through forty rows, says "this is great, leave it with us", and nothing happens. The research was sound, but the deliverable failed it.

The difference is rarely the data and almost always the packaging: what you chose to include, what you led with, and how it was presented in the room. This guide covers all three, section by section. It is about the output; for the method that produces the underlying data in the first place, see how to do talent mapping.

What is a market map report?

A market map report is the client-facing deliverable of a mapping exercise: a structured document showing the companies, people, pay and dynamics of a defined external market, with the agency's read on what it means.

That last clause is what distinguishes a report from research. The rows are evidence. The product is the judgement sitting on top of them, organised so a client can make a decision. If the terminology around mapping is blurry, talent map versus market map versus pipeline, the distinctions are unpacked in talent mapping vs market mapping; in practice the deliverable for either looks like what follows.

The anatomy of a client-ready market map

Seven sections, in this order. Not every brief needs all seven at full depth, but a client-ready map should account for each one, even if only to say it was out of scope.

1. Executive summary. One page, written last, read first. The headline on market depth, the two or three findings that surprised you, the pay picture in a sentence, and your recommendation. Most senior readers will form their view of the whole engagement here.
2. Market overview. The shape of the landscape: how many companies, how the talent clusters geographically, which firms are growing or shedding, and any structural shifts worth naming. This is where the client learns things they did not ask for, which is what makes the map feel bigger than the brief.
3. The company universe. Every company in scope and the rule that put it there, with the adjacent pools flagged as such. Showing the inclusion rule does quiet work: it tells the client the map is defensible rather than assembled from memory.
4. The people. The core asset: everyone in scope, one consistent row each, grouped so the market is legible, by company, seniority or readiness. Consistency is what makes this section feel like data rather than notes.
5. Compensation and availability. Pay in bands, clearly labelled as estimates where they are estimates, and soft availability signals: tenure patterns, recent restructures, visible movement between firms. Clients fund maps to answer "what would this cost and who could we actually get", so this section often carries the meeting.
6. The diversity view. What the available market actually looks like against the client's representation goals. A truthful baseline here saves a search from being briefed against a fiction.
7. Recommended next steps. What you would do with this map: who to approach first, where the brief should flex, what a search would look like. One page. This section is also, not incidentally, where the next piece of work comes from.

Raw data vs intelligence: what actually earns the fee

Every section above can be filled two ways: with collected facts, or with what the facts mean. A client can buy collected facts from a database. They can only buy meaning from someone who knows the market.

The difference shows up sentence by sentence:

Writing the right-hand column takes nerve, because interpretation can be wrong in a way a list cannot. Commit anyway, and label your confidence honestly. A hedge-everything map reads as data entry, and data entry has a data-entry price.

How to present a market map to a client

The meeting is part of the deliverable, and it deserves the same structure as the document.

Lead with the headline, not the methodology. Open on the executive summary: the depth, the surprise, the recommendation. The temptation is to walk through how the map was built first, to justify the fee before showing the result. Resist it. The result justifies the fee; the methodology is for the questions afterwards.

Structure it as findings, not pages. "Three things to show you" beats a page turn. Walk each finding from headline to evidence, dipping into the rows only to prove a point. Reading rows aloud is how a strong map loses the room.

Anticipate the three questions that always come. Who are the best five people here? Could we actually get them? What does this mean for what we pay? Have crisp answers staged, because they are the bridge from this map to the next assignment.

Leave silence after the recommendation. You have just shown a client their market with the lights on. Let them tell you what they want to do about it, because the answer is usually the brief for the next piece of work.

Formats: PDF, deck or live

The format question is really a question about how the map will travel after the meeting.

A branded PDF is the default for a reason: it reads as a finished product, prints cleanly, and holds its formatting wherever it is forwarded. A deck earns its place when the map will be presented, by you or by your client to their board, since slides force the findings-first structure anyway. A live document or portal suits ongoing engagements where the map refreshes, though it trades the sense of a finished deliverable for currency.

Many agencies ship two formats from the same data: the deck for the meeting, the PDF as the record. This is the part of the workflow TalentMaps handles directly: the structured map exports as a branded PDF or PPTX, so producing the second format is not a second job. The judgement, the narrative and the meeting remain yours; the tool's job is to make the packaging cost nothing.

Why presentation justifies the price

It is tempting to treat everything in this guide as garnish on the real work of research. The market disagrees.

Two agencies can hold identical data. One sends a spreadsheet attachment; the other walks the client through a branded report that opens with what the data means. The second agency charges multiples of the first, and the client is right to pay it, because what is being bought is a decision made confidently, not rows. Presentation is not vanity; it is the difference between research the client files and intelligence the client acts on.

It is also what makes mapping sellable as a product at all. A deliverable that looks and reads like something worth paying for is the precondition for charging for it, and the commercial playbook built on that fact is in how to sell talent mapping as a service.

The pre-flight checklist

Before a map leaves the building, check it against the anatomy:

• Executive summary states depth, surprises, pay and a recommendation in one page
• Market overview says something the client did not ask for
• Company universe shows its inclusion rule
• People section: consistent rows, grouped legibly, no orphan gaps
• Compensation banded and labelled honestly; availability signals included
• Diversity baseline against the client's goals
• Next steps written as actions, not options
• Branded, in the format the meeting needs, and forwardable without you

To see these sections filled in on a real market, end to end with figures, read how to market map a sector. For where the deliverable sits in the wider agency picture, the pitch, the search and the service, see the complete guide to talent mapping for recruitment agencies.

And when the research is done and the packaging is the last thing between you and the meeting, build the map in TalentMaps and export the deliverable in the format the room needs.

Frequently asked questions

What should a talent map include?

Seven sections cover a client-ready map: an executive summary with the headline read and recommendation, a market overview, the company universe, the people in consistent structured rows, compensation and availability, a diversity view of the available market, and recommended next steps. The summary and the recommendation matter most; the rows are evidence, not the product.

Should a talent map be a PDF or a PowerPoint?

Match the format to how it will be used. A PDF reads well as a standalone document the client studies and files; a deck works when the map will be presented in a meeting and forwarded internally afterwards. Many agencies deliver both from the same data. Either way it should carry the agency's branding, because the deliverable is part of what was paid for.

How long should a market map report be?

As long as the evidence requires and shorter than you think. A focused single-function map usually reads as one summary page, a handful of pages of market and company analysis, then the structured people data. If the front section runs past ten pages the insight is being diluted; depth belongs in the rows and appendices, not the narrative.