The Data Layer

Published following The Structural Crisis in PR, a six-part series on the forces reshaping communications.

Every communications engagement in the history of the discipline has started from the same place: someone's best guess.

A good guess, usually. Informed by years of experience, deep relationships, pattern recognition built across dozens or hundreds of campaigns. The best comms strategists in the world operate on a kind of trained intuition that's genuinely hard to replicate. They read rooms. They read markets. They know which reporters care about which narratives, which angles have legs, which moments to push and which to let pass.

But it's still a guess. And the gap between intuition and ground truth is where most of the waste in communications lives.

PR has never lacked information. Coverage databases exist. Media monitoring platforms exist. Sentiment tools, social listening dashboards, competitive intelligence services. The industry spends billions on data infrastructure annually. The global PR analytics market is projected to exceed $14 billion by 2030.

What's missing isn't the data. It's the connection between the data and the moment where strategy gets made.

When you sit down to build a pitch strategy for a new client, you don't start by querying a database. You start by thinking. You recall past campaigns. You draw on relationships. You pattern-match from experience. The data, if it enters the process at all, arrives after the strategy is already formed, as validation or as post-hoc justification for decisions that were already made on instinct.

One of the best PR agencies in the country has a dedicated data analyst. They pull coverage reports, run sentiment breakdowns, map media landscapes, build competitive audits. They're good at what they do. They're also slow, because the work is manual. And what they produce are spreadsheets that the comms team can't easily digest. So the reports get emailed around, someone skims the summary tab, and the team goes back to running campaigns the way they were already going to run them. The analytical work and the strategic work happen on separate timelines, in separate tools, in separate languages.

That gap isn't a talent problem. It's the normal result of an industry where analysis and strategy have always operated as separate functions.

The architecture that's emerging

The infrastructure shift happening across professional services is making a different model possible. Not better dashboards. Not faster reports. A structural change in where data lives relative to the work.

When analysis and strategy share the same environment, something specific happens: your judgment starts operating against live ground truth instead of memory.

You're still the strategist. You're still bringing the relationships, the instinct, the pattern recognition that makes comms work an art as much as a discipline. But every intuition you bring gets tested, in real time, against what's actually happening in the conversation space right now. Not what happened last quarter in a coverage report. Not what a dashboard showed you last Tuesday. What's happening today: who's talking, what they're saying, where sentiment is moving, where the white space sits.

The data arrives in the language of strategy, not in pivot tables. When you're building a media approach, the intelligence layer surfaces which reporters are actively covering adjacent stories, what angles they've taken in the last 30 days, where the narrative gaps are that no one has filled yet. When you're choosing a campaign angle, it shows you which conversation spaces are crowded and which are open. When you're advising a client on positioning, it maps the competitive landscape as it exists this week, not as it existed when someone last ran an audit.

The analyst's expertise feeds directly into this. They're not producing documents that get handed off and reinterpreted. They're shaping the intelligence layer itself: deciding which signals matter, how conversation spaces should be mapped, what thresholds trigger attention. Their analytical depth and your strategic instinct operate in the same space, on the same information, at the same time. The translation problem disappears because there's nothing left to translate.

What you actually need when you build a campaign

A new client signs. Before the first onboarding call, the data layer is already running.

It's mapping the client's category: who the relevant actors are, what the active conversation threads look like, where coverage has clustered, where it hasn't. It's baselining sentiment. It's identifying which media contacts have covered this space in the last 90 days and what their recent angles were. It's flagging where the client's competitors are getting mentioned and where they aren't.

By the time you get on the phone, you already have the map. The onboarding call shifts from "tell us about your business" to "here's what we see in your landscape; tell us what we're missing." The client experiences a team that showed up already knowing the terrain. That's a trust signal that no amount of credentials can replicate.

The strategy you build afterward isn't starting from a blank page and a gut feeling. It's starting from a documented picture of the current conversation space, with your judgment applied on top of it. You still decide the angle. You still choose which relationships to activate. You still make the calls that only experience can make. But every one of those calls is grounded in something that was true this morning, not something you remember from a similar engagement two years ago.

The layer that runs while you're not looking

Most data in comms is reactive. You go to a tool, you pull a report, you analyze what happened. The data layer described above changes the starting conditions, but it still depends on someone initiating the work.

The more consequential shift is what happens when the intelligence layer runs persistently.

A conversation space the client cares about experiences a sudden sentiment shift. A reporter who covers their category publishes something that opens a window for commentary. A competitor announces something that creates a positioning opportunity. A trending topic intersects with the client's narrative in a way that wasn't on anyone's content calendar.

In the current model, catching these moments depends on someone noticing. Someone scanning their feed, checking a dashboard, hearing about it from a colleague. The window for action is narrow, and most of these moments pass without anyone on the comms team registering them until they show up in a retrospective report.

A persistent data layer surfaces these in real time. Not as raw alerts that require interpretation, but as contextualized opportunities: here's what happened, here's why it matters for this client, here's the window for action, here's a proposed response. The intelligence layer doesn't just answer questions you asked. It raises questions you didn't know to ask. It notices the pattern break before you notice the pattern.

Trendjacking is the obvious example, but it's the smallest version of this. The bigger version is a comms strategy that adapts continuously to what's actually happening instead of executing against a plan that was built on last month's assumptions. When a client's competitive landscape shifts mid-campaign, you know the same day, not at the next check-in. When a narrative window opens, the opportunity reaches the team while it's still open, with enough context to act on it without starting from scratch.

This is what separates a data layer from a data tool. Tools wait for you to use them. A layer runs underneath everything, feeding the work whether anyone is actively looking at it or not.

Where this goes

For most of the history of communications, strategic thinking and data analysis have been performed by different people, in different rooms, on different timelines. The strategist works in conversations, relationships, and narrative instinct. The analyst works in data sets, coverage metrics, and competitive mapping. They meet occasionally, usually through a document that one of them produced for the other to review.

The emerging architecture collapses that separation. Analysis and strategy share the same substrate. Your judgment and the data that informs it operate in real time, together, each making the other more precise.

But there's a further horizon. When the intelligence layer runs persistently and the strategic reasoning runs at the same scale, the comms function stops being something that happens when humans are at their desks. Market intelligence, opportunity identification, adaptive strategy, competitive monitoring: these can run continuously, proactively, at a depth and speed that no team could sustain manually. The humans set the direction. The infrastructure keeps pace with the market in between.

The strategic intuition that makes great comms people great isn't going away. It's getting a substrate that makes it more precise, more responsive, and more connected to what's actually happening. The question for the industry isn't whether data matters. Everyone already agrees that it does. The question is whether the data and the strategy will keep living in separate worlds, connected by handoffs and slide decks, or whether they'll finally share the same space.

The answer is already starting to become obvious. What's less clear is what judgment looks like when it's no longer working from a guess, and what becomes possible when it isn't.