Between September 2025 and October 2026, we had the "should we build or buy a reporting stack?" conversation with 87 marketing agencies.
I went through the calls and synthesized the key findings and patterns to help you decide.
Here are the key things they told us:
- Building a reporting stack isn't the hard or expensive part. Maintaining the connectors and dashboards is.
- Most DIY setups depend on one person. When the person who built it leaves or goes on holiday, nobody else knows how to run it.
- AI can hallucinate the important numbers if you don't have a governed data layer to define metrics, blend data, and standardize dimensions.
- Building the entire stack works for agencies with developers on staff who can maintain connectors and dashboards full-time.
- Most agencies end up with a hybrid setup. They buy the data layer and the reporting layer that clients see and build their skills and scripts on top.
Not sure whether to build or buy? This scorecard can help.
Or skip to 5 key things to consider before building a reporting stack. Or see the case for a hybrid.
What agencies are actually building, and what they’re buying
From what we’ve seen from 87 agencies, there are four key things they’re building:
- Claude (or ChatGPT, or Gemini) as the workspace. This is the most common starting point, and the cheapest. You set up a Claude project for each client, load it with the brief, past reports and exported data (or connect it straight to the ad accounts), then ask it to write the monthly summary or dig into what changed.
- Vibe-coded dashboards. A lot of agencies strap the data connectors on or use MCP connectors to ship data to Claude or Lovable and vibe-code dashboards there. To share, they just send an HTML artifact, or a "screenshot", as one agency told us.
- A marketing data warehouse. This usually looks like BigQuery or Snowflake underneath, Looker Studio, Power BI or Tableau on top. Agencies typically need a dedicated data person or a team of developers to pull this off.
- AI agents. The newest group. From our calls, we saw a Finnish agency built an agent framework in Claude Code that reads and writes client files in SharePoint. A UK integrated agency started building its own reporting suite on top of an LLM. Others wire things together with n8n. See how agencies are using AI agents for marketing.
But is that it? Not really. These agencies were still buying the data layer underneath the dashboards and agents.
A lot of these agencies still had to find a way to bring their cross-channel data from multiple platforms into one place, and have that data be standardized, cleaned, and defined.
A French e-commerce agency tried building that data layer with an outsourced data team but ended up stopping the project. One of the agency’s founders told us why:
“You need people in your company to manage [the data setup], and we don’t have those people.”
It helps to think of any AI reporting stack in four layers:
- Data: connections to every ad platform, and somewhere to store what they pull
- Definitions: what counts as a conversion, how blended ROAS is calculated, which campaigns are brand
- Agent logic: the instructions, playbooks and house style
- Delivery: where the output goes, and who checks it before a client sees it
Most of the builds above start at the agent logic or delivery layer, because that’s the fun, visible part. The data and definitions layers are where things get painful later (more on that below).
5 key things to consider before building a reporting stack
Before you build your reporting stack, there are five things to consider according to the 87 marketing agencies we talked to:
- The cost of the initial build
- Maintaining connectors, dashboards, and client reports
- AI inaccuracies and the governed data layer that fixes them
- The setup, prompts, and knowledge living in one person’s head or account
- Client data privacy and security
Let's go through each of them.
1. The cost of the initial build
How much does it cost to build your own reporting setup? Here’s what the agencies told us about the initial build itself:
- 400 hours. That’s what a Dutch agency estimated it would take to build its own reporting platform. They bought one instead.
- $10,000 to $12,000. That’s what a US full-service agency spent on a contractor to build its dashboards. The agency lead said it got them “65 to 70% of the way there.”
- About a year. That’s how long a US automotive agency spent building its own data warehouse, with a developer and a freelancer.
AI setups have their own version of this. The founder of a UK agency built dashboards with Claude and Manus, then dropped them because the setup “used something insane, like 1,000 credits every day.”
2. Maintaining connectors, dashboards, and client reports
Then comes the maintenance upkeep. APIs change, metrics deprecate, connectors break, dashboards crash, and someone has to fix all of these on a regular basis so clients will get accurate and reliable reports.
In fact, across all major ad channels like Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads, there were 19 major releases and 65+ feature updates in 2025 alone*.
When it comes to metrics deprecation, across the major ad platforms, over 140 individual metrics and measurement fields were deprecated or phased out in 2025*, with Meta accounting for the vast majority.
*Research with Whatagraph IQ Agents. See sources here.
Every time an API updates or a metric gets deprecated, you’ll need to update your reporting stack. In fact, metric deprecations are more disruptive than API version updates since they not only break data pipelines, but also your data transformations, dashboards, and worst of all, your client reports.
With 140 metric deprecations plus 65 API updates, that’s 205 times you’ll need to update your reporting stack in a year. You simply won’t be able to keep up with this maintenance unless you have a dedicated dev team.
That’s exactly what we hear from agencies too. A director at a Dutch agency said their dev team keeps having to step in because their dashboards crash every now and then. A partner at a US agency said their head of Media Strategy spends “between five and 30 hours a month just maintaining Looker Studio, which is not his job.”
This Redditor in r/adwords has also experienced this firsthand. They say “unless someone on the team actually enjoys maintaining automations, buying ended up being way cheaper in the long run.”

In a dedicated tool like Whatagraph, connectors, dashboards and reports are maintained by a dedicated team of in-house engineers so you don’t have to. All you get and see are the end output: the dashboards and client reports automatically updated.
Plus, if you want to update reports, like swapping out a metric, adjusting attribution windows, or changing date ranges, you can simply get agents to do so across all your reports (whether that’s 10 or 100) in seconds. See how here.
→ So what’s the total cost of building?
Let’s put some rough numbers on it.
Say you build in-house, using the figures agencies gave us: about 400 hours to build, then 5 to 30 hours a month to keep it running. The median US data scientist earns $57.80 an hour and the median marketing analyst $37.87, according to the US Bureau of Labor Statistics (May 2025). That’s wages only, before benefits and overhead.
| Data person ($57.80/hour) | Marketing analyst ($37.87/hour) | |
|---|---|---|
| Build (400 hours) | $23,120 | $15,148 |
| Upkeep, year 1 (60 to 360 hours) | $3,468 to $20,808 | $2,272 to $13,633 |
| Year 1 total | $26,588 to $43,928 | $17,420 to $28,781 |
| Every year after | $3,468 to $20,808 | $2,272 to $13,633 |
Hiring a contractor instead? The US agency above spent $10,000 to $12,000 and got 65 to 70% of the way there. At that rate, finishing the job would come to roughly $14,000 to $18,500, and you’d still need someone to maintain it.
Going the AI route? The UK agency’s setup burned through about 1,000 credits a day. At Manus’ launch pricing of $39 for 3,900 credits, that’s roughly $300 a month, or $3,600 a year, before anyone’s time.
These are rough estimates built from what agencies told us, but you can plug in your own hourly rate in this cost calculator (built with Whatagraph IQ Agents):

3. AI inaccuracies
14 of the 87 agencies brought up this problem: the AI gives you a number or an analysis, but it doesn't match the way you define metrics or the logic your agency uses.
Why? Usually because it’s guessing at decisions your team made:
- Which date range and time zone to use
- Whether a conversion means the ad platform’s number or GA4’s
- How ROAS is calculated for different channels
- Which campaign names are part of the same campaign or different
- What currency everything should be in
Typically, when you build a report in a marketing agency reporting tool, you have these built in. But when you connect AI straight to raw ad platform APIs without these definitions, AI has to guess and make up a ROAS number, for example.
The real fix is to agree on your metric definitions before sending your data to AI, and building a governed data foundation for your cross-channel data.
This is where Whatagraph comes in. In Whatagraph, you:
- Bring data from all your sources and channels in one place. You can connect to 60+ native integrations, or build your own using agents.

- Tag sources by Account Manager, client, or whatever makes sense for your agency, assign them to specific client folders, and set default currencies.
- Define metrics, build custom ones, standardize dimensions, blend data to create one governed data foundation.

- Build and automate client reports off of this data foundation so your numbers always agree.

And Whatagraph’s IQ Agents read the same governed data foundation your reports use, so a custom metric like ROAS is calculated the same way everywhere: in reports, AI tools, and in the agent's analysis. Here’s how agencies are using IQ Agents for marketing.

You can then connect the data foundation from Whatagraph to AI assistants like Claude and ChatGPT through our MCP server so AI isn't hallucinating numbers, they're reading your logic.

4. The setup, prompts, and knowledge living in one person’s head or account
This is what I like to call the “one person problem”: the whole setup lives in one person’s head, and when they leave, nobody else knows how to run it.
14 of the 87 agencies are worried about this, and 16 talked about Claude turning into the place their team’s knowledge lives.
A US agency had a data engineer on staff for about nine months who set up their whole BigQuery instance. Then he left. And they had to bring in a whole outside team just to figure out how it all works.
A specialist at another Finnish agency put it bluntly: “Let’s say I leave the company. Then nobody knows how to manage this agent framework.”
Another US agency was moving off a Slack reporting pipeline one employee had custom-coded because they didn't know how long that employee would stay and they didn't want to be "stuck" with the workflow they didn't understand.
Then there’s the knowledge. As more of the team works in Claude, the prompts, client context and house style end up living there too.
This is fine if knowledge is shared across the entire team through a different harness (like GitHub). But if it's not, keeping knowledge consistent across the entire team becomes a series of updating "Skills", downloading them, uploading them to each individual Claude account. This can get chaotic, and there's no guarantee these "Skills" would be up-to-date in everyone's account.
A few agencies also worried about getting stuck with one AI model. A Belgian agency group put it simply: when another AI comes along, “we don’t want to move everything around.”
So before you pick a tool, decide:
- Who else can run the setup if the person who built it leaves
- Where your prompts, client context and house style live, so the whole team can see them and not just one person’s account
- How easily you could switch AI models later
This is pretty much what we built Whatagraph IQ Agents around: democratizing knowledge across the entire organization.
IQ Agents are multiplayer by default, meaning everything is shared across the whole organization: the agents, their instructions, knowledge and memory, the connections, the outputs, and even the conversations.
For example, once one of the team members connect a platform, they can enable it for the rest of the team instead of having to re-add the connection in every account.

The same works for agents. Once someone on the team built an custom agent for a specific purpose, the entire organization can automatically use it without having to download and upload things.
For instance, the Head of Search at a UK agency built a "SEO Narrative" agent to write commentary in reports in their brand style. He then duplicated this agent across the agency's other service lines: PPC and email marketing, and every specialist could now use the agents.
Anyone on the team can also open a conversation and see how a result was produced. You can also tag certain people inside conversations so you can co-work together.

Sensitive work still has a place: conversations can be marked private, and an admin can take over a private conversation when someone leaves, so nothing stays locked in a departed employee's account. The same goes for agents and connections - even when the person who built them left, an admin can still take over and use them.
5. Client data privacy and security
Is it safe to put your client data into ChatGPT or Claude? It depends who you ask, and your clients may already have an answer.
A UK agency group told us some of its clients “do not want us to use... the data on Claude or any other AI models.” A European agency admitted “a lot of clients will be a bit uneasy knowing that we sometimes make Gemini or Claude work on their data.”
When you build your own setup, you own that problem too: who can see what, where the data goes, and what happens if someone asks the agent to do something it shouldn’t.
So before you decide whether to build or buy, think about:
- Which clients are okay with you using AI models, which ones, and which clients are not
- Where client data is processed and stored
- What an agent can do on its own, and what needs a person’s approval
With Whatagraph, client data is processed in the EU, nothing gets uploaded into ChatGPT or Claude, and it’s never used to train AI models. And you decide, per agent, what it can do on its own, what needs your approval and what’s off limits.
Whatagraph is also GDPR-compliant and ISO 27001 certified. There’s also SSO.
When building works: what the builders have in common
It’s not all doom and gloom to build your own stack.
14 of the 87 agencies built their own setup and were happy with it, or told us they’d rather build than buy.
What most of them had in common: a team of developers.
A US performance agency with a five-person dev team built its own dashboards, its own attribution and even its own MCP. The CEO said one of their tools “was built in three days,” and that keeping one of their in-house products running costs them about the price of one customer a month.
If you have a dev team, or at least a dedicated super technical person, a lot of things get easier to build.
The other thing the builders had in common: they built a workflow that is genuinely unique to their agency.
A commenter on r/adwords had a good rule of thumb for this: Buy if you’re automating a common, repetitive task (like reporting). Build when the workflow is specific to your agency, relies on internal data, or needs logic that off-the-shelf tools can’t support.

Here’s how that looks like in practice with agencies our team talked to:
- It’s specific to your agency. A Dutch AI-first agency is running its own agentic system on paid search, built and maintained by its own team.
- It runs on your internal data. An Australian agency built its own client dashboards on BigQuery, with AI on top that reads the data and flags when something looks off.
- Off-the-shelf tools can’t do it. A UK recruitment-marketing agency runs its basic reports in a platform and keeps the more complex client work in its own BigQuery.
- You have someone to keep it running. Which, if you’ve read this far, you already knew.
Size matters too. A Dutch agency told us: “We’re not that big to build our own system right now. If we had 200 clients, that’s a different story.” A media lead at a UK integrated agency did the math out loud: a platform at 30 to 40 grand a year is “a wearable cost,” but at a quarter of a million, “we might as well build something custom.”
The case for a hybrid: build and buy
So, build or buy? The answer might be both.
After going through all 87 agencies, we've seen this pattern: agencies buy the data foundation underneath, and build workflows and playbooks unique to their agency.
The data foundation means:
- Native integrations that you don’t need to maintain or fix when they break (the platform maintains and fixes them for you)
- Custom API integrations you can build with agents
- Data sources tagged by dimensions that make sense for your data like clients, Account Managers, or location
- Defined metrics so conversions mean the same thing and ROAS calculations are correct
- Blended data from different channels - like GA4 and Google Ads
- Data from similar sources (like Google Ads and Meta Ads) combined into “Source Groups” so your reports are faster to load and more holistic
- Standardized dimensions and campaign names so everything means the same thing everywhere
That’s what Whatagraph was built for. On top of this data foundation, you’ll also get native reports and dashboards, and AI agents that do the busywork for you. This means:
✅ You don’t need to spend hours and money maintaining your stack.
✅ Your client reports, dashboards, and AI all show the same numbers and analysis.
✅ Everything becomes shared across the entire organization instead of being stuck in one person’s set up - connections, knowledge, data definitions, agents, conversations.
On the flip side, we’ve seen agencies build the context and playbooks. The playbooks are what clients pay you for: how you read the numbers, what you flag, and what you tell them to do next.
A digital growth marketing agency based in the Netherlands did exactly this.
Two years ago, one of the agency’s co-owners noticed that a lot of his team’s work was looking at numbers and checking whether one number matched another. AI could do that part.
So the five-person team started building. They pulled data into Looker Studio, paying extra for the Meta Ads connectors, then tried Funnel as a connector. He also built his own connectors on the Meta Ads and Google Ads APIs.
What they bought: the data layer. The co-owner could keep his own connectors running. He decided not to because it's a "hassle". And the hassle is maintenance.
"I can use the API from Meta Ads and the API from Google Ads, but it’s a hassle. Every couple of months, they change how the connectors work, and then you have to update them. We have six or seven channels, and they all have their own connectors. And you’re showing that data to a client, so it needs to be right."
What they built: the playbook and the skills. The agency keeps everything that’s specific to them in their own hub: folders for every client and workflow, each with an agent.md file of instructions. Every skill is its own GitHub repo with a script inside. The skill tells the agent how a performance marketer thinks. The script does the math so Claude wouldn't hallucinate numbers.
He does the coding in Claude Code or Codex and connects it to Whatagraph’s agents, which do the work:
“I still do the same job. I still use Claude and I also connect [the skills and scripts] to the agents in Whatagraph, and those do the work.”
Here’s how that works for their weekly Meta Ads reporting:
- Every week, an agent copies each client’s report and updates the week number. Whatagraph pulls in that week’s data.
- The Meta Ads specialist agent they built in Whatagraph runs the script from its skill. The script pulls the data, including metrics the client never sees in the report, like link clicks compared with all clicks on the ad. It gives every ad and campaign a score and passes only the top results to the LLM, so the agent isn’t buried in context.
- The agent writes up what happened, where the specialist should look and which optimizations to make, in the agency’s own format. It splits this across several markdown files, because one large file won’t fit in the agent’s context window, and adds the optimizations to the client’s report.
- A specialist reviews the optimizations. They keep the good ones in the report and make those changes in the ad platform themselves, and delete the rest.
- The next week, the agent checks which optimizations stayed in the report and which were removed, and learns what the team actually uses. The agency can also export how many recommendations were accepted per client and update the skill with what it learns.
The agency doesn’t let the agent make the changes itself yet. “It’s already possible to do that, but I don’t trust it. We have a lot of big clients.”
But Whatagraph's agents are helping specialists do deeper analysis and focus on strategy and optimizations.
“The first layer of optimizations can be done by the agent, and now the specialist can go deeper, like which locations or age groups perform better. They're not necessarily working less but they're working smarter and doing the big stuff.”
And because the playbooks live in the agency’s own hub, not inside one AI tool, they can switch models whenever they want. The agency owner advises:
“Anthropic is doing really well, but they’re not that old. If they’re gone next year and all your stuff is in Claude, your stuff is gone. So keep everything you make in your hub, put AI on top as the brain, and when a new model comes along, just plug it in.”
And it's not just this one case either. 11 of the 87 agencies told us they were going hybrid, and 10 of them split it the same way: buy what the client sees, build what stays inside the agency.
On the rest of the calls, that looked like:
- Buy the pipes, keep the data. A head of technology at a UK agency was “looking at a hybrid, which would be to bring the data into our own warehouses.”
- Build the internal tools, buy the client reporting. An exec at a US agency with property-management clients vibe-codes internal tools for the exec team, but was very clear: “I’m not trying to build a reporting system.”
- Build the warehouse, keep client reporting on a platform. A US automotive agency spent a year building its own data warehouse, but keeps a platform for everything its external clients see.
The exception is the builders from the last section. If you have developers on staff, you can certainly build the entire thing. But just know that you’ll also be responsible for the maintenance, which is much more difficult than the initial build.
Build vs buy vs both scorecard for your agency
If you're still on the fence, here's a framework to help you decide where you lean - build, buy, or both.
Score your agency on these seven questions. Give each one 1, 2 or 3 points, then add them up.
| Question | 1 point | 2 points | 3 points |
|---|---|---|---|
| Who fixes the setup when it breaks? | A dev team with time set aside for it | One person who knows how it works | Nobody yet |
| Have you budgeted for maintenance after the initial build? | We’ve budgeted the upkeep | We have a rough idea | We haven’t thought past the build |
| Do the numbers need to match the client report? | No, it’s for internal use | Mostly, and we check by hand | Yes, every number |
| Is the workflow common or specific to your agency? | Specific: our own IP, internal data or custom logic | A mix of both | Common, repetitive reporting work |
| Do you have developers on staff? | Yes, more than one | One, or a contractor | No |
| How fast do you need results? | We can wait six months or more | Within a few months | This quarter |
| Will clients see it? | No, it’s internal only | Some of it | Yes, it’s client-facing |
Your score:
- 7 to 11: lean build. You have the people and a workflow nobody sells. Check you have what the builders above had, and decide now who maintains it.
- 12 to 16: hybrid. Buy the plumbing, build the parts that make your agency different.
- 17 to 21: lean buy. Buy first, then build on top once you know what your team actually uses.
Here’s an interactive scorecard built with Whatagraph IQ Agents on this methodology to help you decide.

Final thoughts
I went into these calls expecting a clear winner. But the verdict is, as always, "it depends".
- Build the entire reporting stack if you have a team of developers on staff or if your workflow is extremely niche to your agency.
- Buy a marketing reporting software if you want a governed data foundation, have tedious, repetitive tasks to automate, want to get it live fast, and see if it actually saves your team's time for bigger things that matter.
- Go for a hybrid where you buy the data foundation and reporting your clients see, and build your workflows and playbooks on top.
If you want to hear it straight from agency owners, two of them go deeper in our online event - sign up here.
And if you want to see what it looks like to have a governed data foundation, reporting, and AI agents all in one, get a demo.

