The 2014 version of Veezeet failed for reasons I didn’t understand until I tried again.
We shipped a working product — three engineers, months of near-dedicated work, a real trip planner, a real diary, a real forum. We didn’t fail at building. I said that in the first post. But “we failed at filling” was only half the truth. We failed at thinking.
Here are three mistakes I only recognized twelve years later.
We built what engineers build
The first feature we worked on was a messaging system.
A messaging system. For a travel app that had zero users. We built a way for people to have conversations inside our tool — conversations that could have happened on any social network. Nobody asked for it. Nobody needed it. But it was a technically interesting problem, and we were three engineers in a room with no one to ask the obvious question: would anyone use this?
It became an inside joke. The messaging system we built for no one. We laughed about it, but we didn’t learn the lesson. The lesson wasn’t that we built the wrong feature. It was that our team was structurally incapable of catching that mistake. Three engineers with no designer, no product instinct, no one who thought about people before systems. We could build anything. We just couldn’t tell what was worth building.
We didn’t know what mattered — and we didn’t ship to find out
We built six things at once. A trip planner. A trip diary. A social layer. A forum. A community system. The beginning of a marketplace. All in parallel, all equally important, all moving forward together.
I know now which one was the heart. But in 2014, I couldn’t see it — and we built six things instead of one.
But I didn’t know that in 2014. None of us did. And here’s the mistake: we thought we could figure out what mattered by thinking harder. By building more. By covering every angle until the answer revealed itself.
It doesn’t work that way. You have to ship something small and watch what people reach for. We never did. We just kept building.
We waited for “ready” — and “ready” never came
The trip planner had to handle every use case. Long trips, short trips, single-destination, road trips. A weekend in Paris and a month across Southeast Asia had to work in the same interface, with the same logic.
That’s not a feature. That’s an infinite problem. And we wouldn’t launch until it was solved.
There was never a launch date. No line in the sand. No moment where we said: this is live, come look. We posted on social media a few times. A handful of people stumbled onto it. That’s not a launch — that’s leakage.
We had a working product. We had real features. We had months of work behind us. But we never committed to putting it in front of strangers and seeing what happened. Because it wasn’t ready. It was never going to be ready. We kept moving the line. Because once you ship, strangers get to tell you it’s not good enough.
Three mistakes. Build what engineers find interesting, not what people need. Build everything instead of the one thing. Wait for completeness instead of shipping for one person with one trip.
I didn’t understand any of this in 2014. I understand it now — and this time, I knew exactly where to start.
Written by the founder of Veezeet. This is the second post in a series about rebuilding a twelve-year-old idea — and what’s changed since 2014.