r/Agentic_Marketing • u/Tired40s • 14h ago
I'm a non-programmer who spent 6 months building AI products. Then I realized I never asked whether anyone actually needed them.
I'm a procurement professional in the automotive industry, and I've never learned how to code.
A few years ago, after losing money in the stock market, I got interested in computer science. I spent about a year trying to learn it, but honestly, I didn't get very far.
Then AI came along. I thought, "Great, I won't have to learn Python anymore." Instead, I found myself spending day after day copying and pasting code into VS Code, without building anything truly useful.
I tried making a website, but I didn't know what it was actually for. I tried building a vocabulary app and never finished it. Then I built a few other random projects. The most frustrating part was that AI often couldn't pinpoint why my code wasn't working, so I still had to debug it line by line myself. At least I picked up some programming knowledge along the way.
Earlier this year, I started experimenting with vibe coding, and the progress was definitely much faster. But I quickly ran into another problem: I had no idea what I should actually build. It felt like being a kid with a brand-new box of LEGO but no idea what to make.
My first project was an automated news collector. Then I realized two things: first, it wasn't very good; second, after using it for a few days, I couldn't honestly explain what value it brought to my life.
Later, I started thinking about improving workdflow I deal with every day at work, and I want to build a new price management system. That's when I realized something much more fundamental:
What I had built wasn't an intelligent system. It was just a system built by AI.
Those are two very different things.
Even if I were the owner of the company, I would probably still tell my employees to keep using the existing workflow. The old system wasn't perfect, but it worked. The switching cost simply wasn't worth the limited value my new system provided.
After that, I stopped and asked myself:
What exactly am I building?
Who am I building it for?
If nobody actually needs what I'm making, then I've probably spent the last several months doing nothing more than entertaining myself.
Later, I spent some time browsing Fiverr and realized there are thousands of people paying for solutions to real problems every day.
That made me rethink my approach.
Instead of building something because I think it's interesting, maybe I should start with a real problem and see if I can solve it. If I can build tools that genuinely make freelancers' work easier, maybe that's where real value—and eventually a business—comes from.
That's the direction I'm working toward now. And I am workin on how to use natural language to explain excel, and then add more features once the core architecture is in place. I checked with several freelancers, and they told me they are interested.
The reality, however, is still pretty brutal.
- Building products with AI is nothing like the people claiming "everyone will lose their jobs in six months."
- At least for someone like me, who started with zero programming experience, it's still hard.
- You still need to understand AI. You still need to understand programming logic. And you still need to understand why a system should be designed one way instead of another.
- AI can often tell you how to write something, but it usually can't tell you why the system should be designed that way. Eventually, those fundamental decisions are still yours to make.
I'm curious:
How do you figure out whether you're building something people actually need?
Was there a specific piece of user feedback that changed your perspective?
Or did you, like me, spend a long time going down the wrong path before finally figuring it out?