From my work and conversations with newsroom teams, the same obstacles keep coming up when we talk about AI adoption: high cost, weak technical infrastructure, fragmented tools that barely talk to each other, poor access to usable data, and limited human resources.
These are real problems. Many newsrooms are already working with tight budgets and small teams. So when AI enters the conversation, it can easily feel like another expensive thing they are expected to adopt.
But I think one of the biggest issues newsrooms need to pay more attention to is the data foundation that makes AI useful in the first place.
Many newsrooms are looking at AI because they want to improve operational efficiency, streamline workflows, increase revenue, improve content distribution, understand their audiences better, reduce repetitive work, and make better decisions.
But to achieve these goals, AI cannot work in isolation. It needs context. It needs organised data. More importantly, it needs connected data.
AI becomes more valuable when it can connect the dots across the newsroom, not when it is trapped inside one tool or one department.
For example, website traffic alone can tell a newsroom which stories got clicks. But when that data is connected with newsletter data, subscription data, advertising data, social distribution data, and editorial production data, the newsroom can begin to ask better questions.
Which stories are bringing readers back?
Which topics attract attention but do not build loyalty?
Which newsletters are driving meaningful engagement?
Which formats are helping subscription growth?
Which distribution channels are bringing valuable readers, not just empty traffic?
These are the kinds of questions AI can help newsrooms answer when the underlying data is connected. This is why scattered data is such a big problem.
A newsroom may have its website analytics on Google Analytics, advertising data on Ad Manager, content data inside the CMS, newsletter data on another platform, subscription data somewhere else, social media performance in separate dashboards, and print circulation data in spreadsheets.
Each of these tools may be useful on its own. But when they do not communicate with each other, the newsroom cannot see the full picture.
So the issue is not that newsrooms do not have data. Many of them do. The issue is that the data is scattered. And a newsroom with scattered data will get scattered insights.
As AI becomes more advanced, this becomes even more important. The issue is not collecting more data for the sake of it. The issue is connecting the right data so AI can produce useful insight.
If AI only sees traffic data, it may push the newsroom toward chasing clicks. If it sees traffic data and newsletter data, it can help identify stories that bring people back. If it sees traffic data, subscription data, and content categories, it can help identify the topics and formats that convert casual readers into loyal readers. If it sees editorial production data, it can help identify where workflows are slow, which desks are overloaded, and which processes are wasting time.
This is where the future of AI in newsrooms becomes more interesting. The next phase is not only about using AI to write drafts or summarise documents. It is also about AI agents that can help newsrooms take action across different systems.
An AI agent is useful when it can do more than answer a question. It can help prepare an editor’s briefing, monitor story performance, suggest newsletter placements, flag underperforming stories, recommend content for redistribution, prepare audience reports, or help teams follow up on workflow tasks.
But for agents to be useful, they need access to connected systems. An agent that can work across the CMS, website analytics, newsletters, subscriptions, advertising, social distribution, and editorial workflow data can help the newsroom see patterns and act on them faster.
What newsrooms need is not another AI writing tool. They need a data foundation.
This could be a system that connects CMS data, website analytics, newsletter performance, subscription data, advertising data, social distribution, and editorial production data so the newsroom can see the full picture of its work. A platform like WhiteBeard’s News Suite fits into this conversation as one example of the kind of integrated newsroom system that can help. I have also been working with the WhiteBeard team on improving the News Suite, so this is a problem I am thinking about not just from a theory perspective, but from the practical challenge of helping newsrooms connect their data better. Still, the priority here is not the product itself. The priority is the principle: connected data, better insight, and stronger organisational control.
This is also where having a reliable data layer or API becomes important. When newsroom data can be accessed through one well-governed layer, it opens up new possibilities for distribution and product development.
The data foundation is not just for reporting. It becomes infrastructure for future newsroom products and distribution. It can power personalised newsletters, topic-based alerts, reader dashboards, automated audience reports, smart content recommendations, archive resurfacing, subscription nudges, partner content feeds, and internal AI assistants for editors and managers.
AI adoption should not begin with the question, “Which AI tool should we use?” A better question is, “Is our newsroom ready to benefit from AI?”
Because without a strong data foundation, AI will mostly help with surface-level tasks. It may write drafts, summarise documents, or generate headline ideas. These can be useful, but they will not transform how the newsroom understands its audience, revenue, distribution, editorial production, or operational efficiency.
The bigger opportunity is not just using AI to produce more content. It is using AI to help newsrooms make better decisions, build stronger audience relationships, improve reader engagement, diversify revenue, and reduce waste in their operations. And that starts with connected data.

/file/attachments/1/Untitled-design-31-2_733618.png)
/file/attachments/1/WB-NovemberLinkedinContent2025-visual1-o2-v11_924225.png)
/file/attachments/1/WB-SeptemberLinkedinContent2025-visual1opt1-v1_340983.png)
/file/attachments/1/WB-August2025Content-visual6-v13_653299.png)