The data isn’t the answer. Your interpretation is

A client receives five pitch responses to the same brief. Each one contains solid strategy, strong creative and a detailed budget. The data in every proposal is broadly similar: market sizing, audience demographics, benchmarking against comparable events. So: what makes them choose one over the others?

It is rarely the data itself. It is what the agency did with it. How they interpreted it, how they presented it and whether they had the confidence to tell the client what it actually means. Data without a point of view is a spreadsheet. And nobody ever won a pitch with a spreadsheet.

This is the third in a series. The first argued that strategy informs the plan. The second explored how confidence in the room is engineered. This one is about the evidence base underneath both: how to find, interpret and present data in a way that earns trust and moves clients to act.

Know What the Data Is For

Before you open a single research tab, you need to answer a question: what is this data supposed to do?

There is a difference between data that describes a situation and data that drives a decision. Most pitch responses are full of the first kind: market context, industry statistics, audience breakdowns. It is useful background but it does not tell the client anything they do not already know. The data that wins is the kind that reveals something: a gap between what the client wants and what they need, an opportunity they have not articulated or a risk that nobody else in the pitch has flagged.

This starts with understanding the client’s vision and objectives, not just for this project but for their broader strategic direction. Is this a new event or something with legacy? What are they trying to achieve in year one, and where do they want to be in three years? (If you have read the first article in this series, you will recognise my establish, expand, lead framework here.) The answers to these questions determine which data matters and which is filler.

The balance between client-supplied information and your own research is worth getting right. The brief will give you their version of the landscape. Your job is to validate it, challenge it where appropriate and fill the gaps they may not have known existed.

Have a View

Early in my career, before I moved into brand strategy, I worked as an oil trader on the International Petroleum Exchange (IPE). My boss at the time, a very experienced pro, had a phrase that has stayed with me ever since: “You have to have a view. Stay flexible but stand firm until proven wrong.”

That principle applies directly to how you handle data in a pitch. Too many proposals present information neutrally, as though objectivity is a virtue. It is not. The client is not hiring you to show them data. They are hiring you to tell them what it means and what they should do about it. If your recommendation section reads like a summary of the research rather than a clear position backed by evidence, you have missed the point.

This requires rigour. Every claim needs a credible source. Every statistic needs to be verified. If you cannot confirm a data point from a reputable origin, leave it out. Forming a view is not the same as forming an opinion: a view is built on evidence, tested against alternatives and defended with specifics. An opinion is something you had before you started looking.

Show, Don’t List

Robert E. Horn at Stanford University has spent decades researching how visual language affects comprehension and decision-making. His findings are striking: groups using visual language reached consensus 21% faster, solved problems 19% more effectively and shortened meetings by 24%. Written information was 70% more effective when paired with visuals. Separate research from MIT found that the brain processes visual information 60,000 times faster than text.

The implication for pitch responses is straightforward. If you are presenting complex data as paragraphs of text, you are making the client work harder than they need to. Charts, tables and infographics are not decoration: they are a delivery mechanism for clarity.

This matters even more in presentations. As I discussed in the second article in this series, you often have to compress a 100-page proposal into a 30-minute presentation. When it comes to data, that means condensing multiple slides into one or two highly visual summaries. The client should be able to look at a chart and understand the argument without reading a single word of supporting text. If they cannot, the chart is not doing its job.

Text is unavoidable in complex proposals. Some data requires detailed explanation. But even then, the principle holds: lead with the visual, support with the text. Not the other way around.

Write for the Room, Measure What is Yours

Don Norman, in The Design of Everyday Things, made the observation that there is no such thing as the average person. Audience personas are useful aggregates, but they describe a composite that does not actually exist. The challenge is writing for a real audience while knowing that every individual in it is different.

Stephen King has written that every novel is really a letter aimed at one person. For him, that reader is his wife, Tabitha. She is the first audience he writes for; everyone else comes after. Proposals and presentations are obviously not novels, but the principle holds. The best pitch responses are written as though they are speaking to one specific person in the client’s team: the decision-maker whose problem you are solving. If you have done the work described in the second article (researching who will be in the room, understanding their roles and concerns), you already know who that person is.

KPIs deserve particular care. There is a meaningful distinction between what the agency owns and what the client owns. Take MOUs as an example: in delivery, the agency can and should design the environments in which deals are facilitated (bilateral rooms, signing stages, matchmaking spaces). But the MOUs themselves, the partnerships and the capital deployed, are client outcomes. Conflating the two in a pitch makes you look like you are claiming credit for things you cannot control. Separating them shows the client you understand where your accountability starts and ends.

Let the Data Evolve

A common mistake in pitch responses is treating data as fixed. You research, you present, you move on. But the best data strategies are built to adapt.

Once work is secured, clients often grant access to resources that were unavailable during the pitch: CRM systems, internal databases, historical attendance data, stakeholder feedback from previous editions. This new information can materially change the strategic approach. The agencies that plan for this, that build flexibility into their frameworks, are the ones that deliver better results post-win. The ones that treat their pitch data as the final word get caught flat when reality diverges from assumption.

The argument for a three-year strategic framework (which I outlined in the first article) gains additional weight here. A multi-year view is not just about showing the client a trajectory; it is about creating the structure within which data can evolve. Year one establishes the baseline. Year two adjusts based on what the data revealed. Year three optimises. The framework is the constant: the data within it is designed to change.

Where the Data Leads

Data does not win pitches. Interpretation wins pitches. The agencies and professionals who consistently outperform their competitors are not the ones with more research or better statistics. They are the ones who know what the data means, who have the conviction to say so clearly and who present it in a way the client can act on without having to decode it first.

The next time you sit down to build a pitch response, ask yourself: am I presenting data, or am I presenting a view? The client already has access to most of the same information you do. What they are paying for is your ability to turn it into something useful.

How do you balance raw data with interpretation in your pitch responses?