Why Your AI Projects Fail: The Critical Role… | The AI Briefing
The AI Briefing Episode 14 December 3, 2025 · 5:19

Why Your AI Projects Fail: The Critical Role of Data Integrity

0:00 / 0:00

What you'll learn

  • Companies are burning $40k-$50k a month on AI with poor results. The root cause is almost always data quality, not model choice. Fixing the model doesn't fix bad inputs.

  • 'Garbage in, garbage out' is not a slogan for LLMs, it's an accounting reality. Every wrong answer still costs you the tokens, and the more you retry the more you spend.

  • Structured data with repeating patterns improves LLM coherence noticeably. Taking time to organise the data upfront saves cost and improves reliability for the whole life of the project.

  • Treat data integrity as a prerequisite for AI, not an afterthought. Audit current quality, map existing structures, and identify where you can improve before the model is even chosen.

By the end of this episode you should be able to (a) benchmark your organisation's current AI spend against the $40k-$50k pattern, and (b) commission a data audit before you commission the next model.

In this episode

  1. Why data integrity is the actual predictor of AI success
  2. The 'garbage in, garbage out' cost in tokens
  3. Structured data and LLM coherence
  4. Action steps: audit, map, improve

AI projects often fail due to poor data quality. Tom Barber explores why data integrity is crucial for AI success and how to avoid costly mistakes that lead to unreliable results.

Episode Notes

Key Topics Covered

  • The importance of data integrity in AI projects

  • Why 'garbage in, garbage out' is critical for LLM success

  • Common mistakes leading to expensive AI failures

  • How to structure data for better AI results

  • The relationship between data engineering and AI effectiveness

Main Points

  • Companies are spending $40-50k monthly on AI with poor results due to data quality issues

  • Structured data with repeating patterns improves LLM coherence

  • Taking time to organize data upfront saves costs and improves reliability long-term

  • Data accuracy, completeness, and structure are prerequisites for successful AI implementation

Host Background

  • Tom Barber brings data engineering expertise to AI discussions

  • Experience in business intelligence and data platform engineering

Action Items for Listeners

  • Audit your current data quality before implementing AI

  • Map out existing data structures and identify improvement opportunities

  • Consider data integrity as a prerequisite, not an afterthought

Have thoughts or questions? Leave them in the comments - Tom reads every one!

Chapters

  • 0:00 - Introduction & Setting the Scene

  • 0:19 - The Problem: AI Project Failures

  • 0:51 - Data Engineering Background & Expertise

  • 1:23 - The Garbage In, Garbage Out Principle

  • 2:03 - The Cost of Poor Data Quality

  • 2:42 - Strategic Approach to AI Implementation

  • 4:25 - Action Steps & Wrap-up

Subscribe to our newsletter: https://newsletter.concepttocloud.com/

Want to apply AI to your engineering workflows? We build production ML pipelines, not demos.

Explore AI Services

Transcript

[sighs] Hello, and welcome to another AI Briefing. My name is, uh, Tom Barbo. And, uh, as you can see, if you're watching a video version of this, I'm, uh, walking through some rather lovely countryside here in, uh, the South of England. Um, what's turning out to be quite a nice autumn day. Whilst I was out and about, I was mulling over, uh, AI projects and how there's always some interesting stats about the likelihood of failure and the...

Obviously, conversely, the chances of success when it comes to running a successful AI project, especially, you know, now there's so many different LLMs and, you know, other ways to be able to leverage AI in the workplace. And so whilst I was taking this stroll, a little bit of my background, I should probably explain, comes from data engineering. Like by trade, uh, originally, and still to an extent to today, I am a data engineer. I started doing business intelligence. I started doing data platform engineering.

And so what I felt like was worth discussing was just the importance of data integrity and data structures when it comes to using data in an AI-based environment. Because no truer word has been said with garbage in, garbage out, especially if you're starting to leverage the, uh, power of LLMs and the inherent complexities that go with it. Because the more you can structure your data, the more that you can give it repeating patterns and things that it can take hold of and grasp, the more likelihood is you're gonna get a coherent answer out at the end of it all. If you just chuck it a bunch of things, sure, sometimes it'll figure it out. I mean, it's not like, uh, you can't chuck a bunch of jumbled data at an LLM and ask it for insights.

Absolutely, you can. But you see the, uh, experiences of companies where they're running up like forty, fifty thousand dollar a month AI bills trying to leverage AI capability over certain platforms without really thinking about what it takes to get the insight that you want out the far end. And so rather than jumping in with two feet, rather than going hell for leather in building out the latest AI concept that you're trying to leverage for technological gain with inside your organization, maybe the first thing you should do is just think more about what is it you want? How are you gonna get it? What data do I have access to that will really help the language models or the deep learning models and all those types of things more effectively and more efficiently that will help me reduce my costs, speed up the operation, reduce the complexity in the long term, but also make the results more reliable to you as a business owner?

Because if you start sticking things into an LLM and you rely solely on the output, you want to make sure that the output you're getting is both coherent from a technological standpoint, but obviously coherent from a, from a data perspective as well. And so just take a step back. Just have a think and just ask yourself, "Is the data that I'm putting into this LLM or into this model that I'm using to help decipher or discern more information out this platform, is it as accurate and as complete and as structured as it could possibly be? " Because it may slow you down in the very short term, but going forwards, it'll put you in a much better position to ensure that you get the data integrity. Because that way you'll make sure that you've got the data reliability, the consistency, and the accuracy that you need to be able to use that data and those insights going forward within your business in the project in a way that you would desire.

So have a think about that. Just sit down and map out what you've got and how you would go about doing it and see if there are any improvements you can make that would amplify and work better with the projects and the platforms you're putting in place. Food for thought. As ever, this is the AI Briefing. If you have anything you would like to discuss, thoughts, feel- feelings, opinions, ideas about this podcast, I know they're just brief daily-ish podcasts about news and insight and thoughts and that type of stuff, but if there is anything you would like me to tackle, feel free to stick it in the comments.

Um, and I will see you on the next one. [upbeat music] Why hire when you can partner? Concept Cloud's leading engineers build your startup's prototype without the overhead. Launch faster. Conceptcloud.

com.

Subscribe to The AI Briefing