Let’s talk AI.
Everyone is obsessed with the "Build vs. Buy" debate. But after seeing how these projects actually play out, I’ve realized the decision isn’t the hard part, it’s admitting whether you actually understand how your own system works.
If you don't have clarity, you're just creating technical debt with better vibes.
Let’s get into it.
Build or Buy?
Everyone keeps asking the same question. “Should we build or buy AI?” That question sounds smart. It’s not.
Because it assumes the hard part is the decision. It isn’t.
The hard part is admitting whether you actually understand how your system works.
What I see right now is two kinds of teams.
Buy AI. Add it to a broken GTM motion. Act shocked when the output is just faster nonsense.
Or “build with ChatGPT” and end up with prompts instead of a system.
Both are making the same mistake.
You build to figure out how the work actually gets done. What goes in. What comes out. Where judgment matters. Where it fails. What “good” even means.
If you can’t explain that, you’re not building leverage. You’re just creating technical debt with better vibes.
Maybe I'd frame it like this:
If you’re building AI because you think it’ll save you from thinking, stop.
If you’re buying AI because you don’t want to understand your own system, that’s probably worse.
Build when you’re forced to learn. Buy the second someone can do it better than you.
And if you’re not sure which camp you’re in… that’s your answer.
AI doesn’t reward effort or ambition. It rewards clarity. Everything else is make-believe.
That’s it for today. Connect with me on Linkedin if you actually want to understand what an Autonomous Organization looks like in the real world.
