Public relations

What client-aware news intelligence is, and why nobody has built it

Monitoring platforms know the news, not your clients. The comms product request Sam Polstein described, the nine requirements, and the gap for builders.

Client-aware news intelligence monitors news, social and broadcast sources in real time and filters them against a specific organization's context — its business, competitors, positioning and active campaigns — to surface what creates an opportunity or a risk for that organization. Nobody has built it, because vendors solved the news half and handed the client half back to the user. Sam Polstein, who leads communications and content for deep tech startups at HAUS, described the missing product to Artificial Reality.

What did the operator actually ask for?

A tool that reads the news the way he does, with his clients in mind. Sam Polstein leads communications and content for deep tech startups, and his request was specific:

"If I had a tool that was really powerful with really recent information, and could also connect that to the context of my clients and flag the most relevant pieces for me — even if it's not in the newsletters that I read or the outlets that are my go-tos — that would be very helpful."

Galina Fendikevich described the identical problem from her own side: subscribing to more newsletters than anyone can read, and needing something that thinks like her to pick out the good stories.

Why is the deadline hours rather than days?

Because reactive opportunity is where the commercial value sits, and the window has closed to a fraction of what it was. "News cycles move so fast these days that even waiting twenty-four hours to turn around something like that is make or break," Sam Polstein said. The trigger is usually indirect — a competitor stumbling, or a government announcement that lands on a client's market.

His general recency standard for AI tools is the same one he applies to media databases: "If there's a three week long lag in the information that's feeding into Claude, well, that's basically useless." He used Perplexity for a period and found it "a little stronger" for queries he previously took to Google, but describes up-to-date information as still "not quite built into" the model he otherwise relies on.

What would the product have to do?

Six requirements come straight from the operator, and three more from Artificial Reality's analysis. Stated by Sam Polstein:

Operate on genuinely current information, not a lagging index.
Know each client's business, positioning and active campaigns.
Surface relevant items from outlets outside the user's habitual reading.
Prioritize by relevance to the client roster rather than by general newsworthiness.
Augment the morning read rather than replace it — the ritual has professional value.
Support fast reactive turnaround, where the useful window is now hours.

Artificial Reality adds three. Distinguish an opportunity from a threat, since a competitor stumbling and a client being criticized require opposite responses on similar signals. Route to a person, because in an agency the right output is often "flag this to the account lead," not a dashboard entry. And stay quiet on ordinary days — a monitoring tool that surfaces something every morning trains people to ignore it.

Why hasn't the existing category solved it?

Because these systems are excellent at the news half and empty on the client half. PeakMetrics, Truescope, NewsWhip and NewsCatcher ingest millions of sources, detect narratives, predict engagement — genuinely hard problems, well solved. Then they ask you to configure a profile: keywords, competitors, topics.

A configured profile is a thin, static approximation of what a senior practitioner carries in their head about an account after two years of running it. The relevance judgment is the product, and it is the part being handed back to the user. This is the most mature category Artificial Reality has surveyed in the Season 1 product requests, and it still does not deliver what the operator asked for.

Where is the opening for a builder?

In the context layer, not the feed. Sam Polstein maintains a rich, curated context library about every client in markdown files, and builds his own dashboards in Claude Code. The missing piece was never a monitoring platform. It was fresh, structured news matched against context he already owns — which is why the most interesting entrant may be the one that is not a product at all. NewsCatcher's API, with scheduled monitors, company watchlists and entity resolution, is the input for exactly that.

Artificial Reality's read: client-aware news intelligence is a context problem wearing a monitoring problem's clothes. Whoever lets an agency point a real-time news feed at their existing client knowledge — rather than re-entering it as keywords in yet another platform — solves the request. The news infrastructure exists and is commoditizing. The value has moved to the context layer.

One design decision worth getting right

Do not take the newspaper away. Sam Polstein wants this to augment his morning reading, and that preference is worth respecting rather than engineering around:

"I still love sitting down and reading through the newsletters that I have in my inbox. There's a comms person ritual in that. You're having your coffee, you're catching up on the news, you're clicking on the articles you find that are interesting, responding to journalists and sending notes to folks that are relevant, or flagging things for the team."

The reading is how a comms professional stays calibrated on tone, on what a beat feels like this month, on which reporters are writing well. A summary delivers information and strips the calibration. Build the thing that adds two stories he would have missed, and leave the ritual alone.