In 2014, three of us started building a travel app.

We called it Veezeet. It was supposed to be everything — a trip planner, a memory keeper, a place where travelers could share something more honest than a five-star review. We were all engineers. We had ideas. We were ambitious.

We were also wrong about what it would take.

The spark was personal. I traveled, and the tools were bad. Spreadsheets for itineraries. Photos dumped into folders and never opened again. Trips I’d spent weeks planning and months saving for, reduced to a camera roll I’d scroll past. That frustrated me. The social angle frustrated me too — every travel platform felt transactional. Ratings, rankings, ads. Nobody was building something that felt like the trip actually felt.

So we started building. Not on the side — we were nearly dedicated to it for months. Paid a designer. Built the frontend, the backend, a trip planner, a trip diary, a forum. We shipped a real v1 — a working product, not a prototype. Three engineers who actually finished something.

And then we stopped.

The product worked. The problem was the flywheel. A travel platform needs content — dozens of trips, real itineraries, living examples — before anyone has a reason to show up. We tried blogging to seed it. It was time-consuming and not that good. Three engineers writing travel content.

We didn’t fail at building. We failed at filling. And then careers happened, families happened, and nobody made the decision to quit. We just stopped showing up.

The people didn’t fade. We’re still three. We still talk about it. But for twelve years, Veezeet was a domain name I renewed every year and a folder on a hard drive I never opened.

Every trip, though. Every single trip for twelve years, I thought about it.

I’d come back from somewhere with four hundred photos and do nothing with them. Scotland. Spain. Madeira. Saint-Nazaire. Paris. Mont-Saint-Michel. Eleven of those trips with my children. Thousands of photos. No story. No shape. Just files.

Every time, the same thought: you were supposed to fix this.

Two things changed.

The first: I’m moving back to Iceland. The trip that started Veezeet for me. But this time with my daughters. The same country, a different life.

The second: after twelve years of engineering work — other people’s products, other people’s startups — I’d seen enough to know what ships and what doesn’t. I know what to cut now. In 2014, I wanted to build everything. The planner, the social layer, the memory keeper, the community, the marketplace. All of it, all at once, all perfect. Now I know you start with the thing that matters. The rest waits or dies.

And for the first time, I had a way to fill the gaps we never could. Three engineers with no designer, no product eye, no growth instinct — that was the real problem in 2014. Not the code. The everything-around-the-code. That part is different now.

I don’t want to build Veezeet for the next trip. I want to build it for the ones that already happened. The ones sitting in folders. The ones my daughters were too young to remember.

Someone has to turn those photos into something worth keeping. Twelve years ago, I said I would.

I’m back.

Written by the founder of Veezeet. This is the first post in a series about rebuilding a twelve-year-old idea — and what’s changed since 2014.