Zero to AI Blog

The AI experiments that failed and what I learned.

Nobody talks about their AI failures. Everyone is too busy posting screenshots of perfect outputs and claiming they “10x’d their productivity.” So here are the AI projects that crashed, burned, wasted time, confused clients, and taught more than any success could.

Blog article AI experiments Lessons learned Practical adoption

Most failed AI projects start with the wrong question.

The mistake is starting with “AI can solve this” instead of “here is the problem, here is the outcome, and one part of this might be helped by AI.”

AI is not a solution It is a tool that only helps when the problem and outcome are clear.
Complexity is expensive APIs, automations and integrations create more places for things to fail.
Judgement still matters AI can inform decisions, but it cannot own context, accountability or meaning.
Simple workflows often win The best AI uses are usually assistive, clear and close to the work.

Nobody talks about their AI failures. Everyone is too busy posting screenshots of their perfectly formatted outputs and claiming they “10x’d their productivity.”

Let me tell you about the AI projects that crashed and burned. The ones that wasted my time, confused my clients, and taught me more than any success ever could.

If you are experimenting with AI and feeling like you are the only one who cannot get it to work, this article is for you.

The automated lead qualifier that qualified nothing

The vision

I was going to build an AI-powered lead qualification system that would score incoming enquiries, categorise them by fit, and automatically draft personalised responses. I would wake up to a tidy inbox full of pre-written replies ready to send.

What I built

A Google Form that fed into a Sheet, with a ChatGPT prompt that was supposed to analyse each response and populate scoring columns.

What actually happened

ChatGPT could not directly access my Google Sheet in any reliable way. I tried Zapier, Make.com, and Apps Script that would pass data to the API. Each integration had its own quirks, rate limits and mysterious failures.

When I finally got something working, the scoring was wildly inconsistent. One day it would give a consulting enquiry a 3/10. The next day, the same type of enquiry would get an 8/10. The AI had no memory, no consistency, and no actual understanding of what made a good lead for my business.

The personalised responses were generic garbage. I could have written that template in 30 seconds without AI.

What I learned
  1. AI cannot maintain context across disconnected systems. Each time the API runs, it starts fresh unless you feed it the right context every time.
  2. Simple automation beats complex AI. Basic Google Sheets formulas worked better because they were deterministic.
  3. Personalisation at scale is usually fake. Real personalisation requires knowing the person. AI personalisation is often just mad-libs with nicer wording.
What I do now

I use a simple form with smart conditional logic that routes people to different follow-up paths based on their answers. No AI. No scoring algorithms. Just clear questions and honest triage.

The content repurposing machine that produced garbage

The vision

Take my podcast episodes and automatically turn them into blog posts, LinkedIn posts, email newsletters and social media snippets. One episode becomes 20 pieces of content without lifting a finger.

What I built

A workflow where I fed ChatGPT the podcast transcript and asked it to create all these different formats in one go.

What actually happened

The blog posts read like they were written by a robot. Because they were. The tone was off, the flow was choppy, and key points got lost or over-simplified.

The LinkedIn posts were worse. They all had the same structure: provocative question, three bullet points, call to action. After posting three of them, people started asking if I had been hacked or had outsourced my content.

The email newsletters did not sound like me at all. Subscribers started unsubscribing.

What I learned
  1. Your voice is harder to replicate than you think. AI can mimic surface-level style, but not the rhythm, examples and small asides that make content sound like you.
  2. One-shot generation is lazy and it shows. Asking AI to do everything at once gives you AI’s default outputs.
  3. Repurposing is not automation. It is editorial judgement. You still need to decide which ideas are worth expanding and which formats need more context.
What I do now
  • I use AI to transcribe and create a rough outline of key themes.
  • I personally pick which themes deserve to become content.
  • I write the first draft myself or heavily edit what AI produces.
  • I use AI for specific tasks like shortening text or suggesting headline variations.
  • Every piece gets a final “does this sound like me?” check before publishing.

The result takes longer, but people actually read it.

The meeting summary bot that nobody read

The vision

I would record client meetings, have AI transcribe them, and automatically generate summaries with action items that I would send to the client. Professional, efficient, impressive.

What I built

I used Otter.ai for transcription and ChatGPT to create summaries from the transcript.

What actually happened

The summaries were technically accurate but completely useless. They captured what was said, but not what mattered.

AI would note that “Steve mentioned possibly updating the requirements document by next Friday” when what actually happened was that the client pushed back hard on that timeline and we agreed to revisit it in two weeks.

It would list every topic in chronological order, making a 45-minute meeting look like we covered 15 things, when really we spent 40 minutes on one core issue. Clients did not read them.

What I learned
  1. AI captures words, not meaning. It does not understand emphasis, pushback, body language or unsaid context.
  2. Summaries need editorial judgement. What matters is what changed, what was decided and what happens next.
  3. Clients want your interpretation, not a transcript summary. They were in the meeting too. They need clarity.
What I do now

I take notes during the meeting and spend 10 minutes afterward writing a short human email:

  • Here is what we agreed.
  • Here is what changed from our last conversation.
  • Here is what you are doing, and here is what I am doing.
  • Here is when we are talking next.

AI sometimes helps me structure rough notes, but the thinking and framing are mine.

Every failed project started with “AI can solve this.” None of them started with the actual problem.

Zero to AI blog

The AI writing assistant that made me lazy

The vision

Use ChatGPT to help draft everything: proposals, emails, reports. Write faster, write more, work smarter.

What I built

Nothing complex. Just me relying heavily on AI to write my first drafts.

What actually happened

My writing got worse. Not because AI writes badly, though sometimes it does, but because I stopped thinking before I wrote.

I would fire off a half-formed thought to ChatGPT and get three pages of professional-sounding but generic consulting speak. I would edit it a bit, send it off, and lose the work.

The proposal did not reflect any actual understanding of the client’s situation. It was a template with the company name swapped in.

What I learned
  1. AI cannot substitute for thinking. If you have not thought through what you are trying to say, AI gives you confident filler.
  2. Generic content loses to specific content every time. Clients can smell a template.
  3. The writing process is where you figure out what you think. When I handed that process to AI, I stopped developing my own ideas.
What I do now

I write the messy first draft myself. Then I might ask AI to help restructure it, tighten it, or check if I have explained something clearly. But the thinking comes from me.

The custom GPT that nobody used, including me

The vision

Build a custom GPT trained on my consulting frameworks, writing style and domain expertise. A personal AI consultant that could help clients even when I was not available.

What I built

I spent days uploading documents, writing detailed instructions and testing configurations. I created “Steve’s Business Analysis Assistant.”

What actually happened

I used it twice. Clients never used it at all.

It was not actually better than regular ChatGPT with a good prompt. All the “custom training” did was make it repeat phrases from my documents.

When I tested it with real client questions, the answers were either obvious or generic. Clients were not interested in talking to my AI assistant. They wanted to talk to me.

What I learned
  1. Custom GPTs are over-hyped for most use cases. Unless you have a very specific repeated workflow, you probably do not need one.
  2. Instructions matter more than training data. A well-written prompt to regular ChatGPT beat the custom GPT almost every time.
  3. People want human expertise, not AI proxies. Clients wanted me, not my assistant.
What I do now

I deleted the custom GPT. I keep a document with my best prompts and frameworks that I can paste into any AI tool when needed. Simpler, faster, more flexible.

The productivity tracking system that tracked nothing

The vision

Use AI to analyse my calendar, email activity and task completion to identify productivity patterns and optimise my schedule.

What I built

I tried several AI-powered productivity tools that promised insights into where my time was going.

What actually happened

The “insights” were useless:

  • “You spend a lot of time in meetings.” No surprise, I am a consultant.
  • “Your most productive time is 9 to 11am.” That is when I do not have meetings scheduled.
  • “You should batch similar tasks together.” Thanks. I read Getting Things Done in 2008.

The tools could not differentiate between valuable work and time-wasting. They just counted hours and categorised activities based on keywords.

What I learned
  1. AI can measure activity, not productivity. Productivity is about outcomes, not time spent.
  2. Optimisation requires judgement, not just data. Knowing you spend 40% of your week in meetings does not tell you which meetings to cut.
  3. Most productivity problems are not data problems. I do not need AI to tell me I am procrastinating. I need to fix why.
What I do now

I do a weekly review on Friday afternoon. I look at what I accomplished, what I did not, and what I want to change next week. It takes 15 minutes. No AI required.

The best AI workflows are assistive, not autonomous. I am still driving. AI just helps me get there faster.

Zero to AI blog

What all these failures taught me

Here is what I learned from watching my AI experiments crash and burn.

1

AI is a tool, not a solution

If you cannot clearly articulate the problem and desired outcome without mentioning AI, you are not ready to use AI.

2

Complexity is expensive

APIs, integrations, data flows and error handling create more ways for the system to fail.

3

AI cannot replace judgement

Every time I tried to automate judgement, it failed. AI can help inform judgement, but it cannot replace it.

4

Generic outputs are worse than no outputs

A template you wrote yourself beats AI-generated content that sounds professional but says nothing.

5

The best workflows are invisible

My most successful AI uses look like me working faster. AI helps me research, organise and articulate, but not replace thinking.

6

Start manual, then automate

Every successful automation starts after I have done the thing manually enough times to understand the pattern.

7

Your voice matters

People do not want content. They want your perspective, experience and judgement.

The experiments I am still running

Not everything failed. Here is what is actually working:

  • Research synthesis: I feed AI long documents and ask specific questions. It saves hours of reading.
  • First-draft editing: I write badly, AI helps me structure it better.
  • Example generation: Asking for five different ways to explain a concept is genuinely useful.
  • Format conversion: Turning meeting notes into action items, or brain dumps into outlines.
  • Brainstorming partner: Talking through ideas with AI helps me think, even when its suggestions are mediocre.

These all have something in common: they are assistive, not autonomous. I am still driving. AI is just helping me get there faster.

Your turn

If you are experimenting with AI and things are not working, that is not failure. That is learning.

The people posting their perfect AI workflows on LinkedIn are not showing you the ten failed attempts that came before, or the hours of manual cleanup they are doing behind the scenes.

Share your failures. Ask questions. Admit when something did not work.

That is how we all get better.

What AI experiments have you tried that did not work out? I would love to hear the honest stories, not just the highlight reel.

Zero to AI is built around honest, practical progress.

If your AI experiments are messy, inconsistent or disappointing, you are probably learning properly. The goal is not perfect automation. It is better judgement, useful capability and real progress over time.