I Paid €2,000 for an App. My Colleague Vibe-Coded the Same Thing for Free. And He Won.

I remember the exact moment I realized I was an idiot. It was a Tuesday afternoon, and my colleague pulled up a chair, opened his laptop, and showed me a working app. He’d built it over the weekend. For free. I had spent €2,000 and 19 months on the same thing.

He didn’t know a single line of code. He just talked to an AI. And the app worked. Not perfectly, not elegantly, but it worked. Users were already signing up. I felt my stomach drop. That feeling — the one where you’ve been grinding while someone else just skipped to the finish line — is what this article is about.

The price of software has dropped to zero. The value of knowing what to build has skyrocketed.

You’ve probably felt it too. That nagging suspicion that all the hard work you’ve put into mastering frameworks, optimizing pipelines, and negotiating cloud costs is suddenly worth less than a single prompt. You’re not wrong. The game has changed. And if you’re still playing by the old rules, you’re already losing.

Let’s be clear: this isn’t a story about AI taking your job. It’s a story about the nature of your job changing. The traditional moat of execution speed, capital efficiency, and engineering rigor has been obliterated. My colleague didn’t have a faster algorithm. He didn’t have a better architecture. He had a better question: What do people actually need?

He spent zero time on infrastructure. Zero time on tech debt. He spent his weekend talking to potential users, then feeding their complaints into a chatbot. The app was a direct response to a real pain point. I spent 19 months building something I thought people wanted. That’s the difference.

Capital is no longer a moat. Speed is no longer a moat. The only moat left is the one AI can’t fake: understanding a market so deeply that you know exactly what to build.

Andrej Karpathy called this ‘vibe-coding’ — building software by describing what you want, not by writing instructions. It’s terrifying if you’re a developer who thinks your worth is in your syntax. But it’s liberating if you’re someone who cares about outcomes over outputs.

Here’s the twist: my colleague isn’t a better founder. He’s just a better listener. He has a distribution channel (a popular newsletter), he owns a dataset of user frustrations, and he has deep domain expertise in a niche market. AI gave him the execution in a weekend. But the direction — that came from years of paying attention.

This is the new reality. The moat has shifted entirely out of the code. It now lives in things AI cannot generate on demand: proprietary data, real-world relationships, distribution networks, and the kind of insight that comes from doing the boring work of talking to customers.

So what does this mean for you? If you’re a founder, stop optimizing for build speed. Start optimizing for discovery. If you’re a developer, stop treating your code as your identity. Start treating your ability to solve problems as your currency. If you’re an investor, stop asking “How fast can they ship?” and start asking “What do they know that no one else does?”

My colleague’s app will probably break in six months. It’s fragile, unmaintainable, and full of bugs. But by then, he’ll have pivoted three times, because he can rebuild in a weekend. Meanwhile, my €2,000 app is stable, tested, and perfectly engineered — but nobody cares, because I solved yesterday’s problem.

The next billion-dollar company will be built by someone who can’t code but knows exactly what people need.

If you’re still measuring your worth by lines of code or dollars spent, you’re running a race that’s already over. The new race starts with a question: What do you know that the AI doesn’t?