In April 2026, we closed a $1.5M angel round. I want to be honest about what that means and what we're going to do with it — and honest about where we are, not just where we're headed.
Wanderglint has been running since 2022. We've been bootstrapped for most of that time, building slowly, testing with real users, figuring out what the product actually needed to be. We've planned roughly 2,400 trips at this point. That number sounds small compared to what venture-scale consumer apps claim, but it's been more than enough to understand — concretely — what works and what doesn't.
Why We Raised Now
There are two things that require capital to do at meaningful quality, and that we couldn't build well enough with the team and budget we had. The first is booking integration. The second is what I'd call travel style memory — the ability for the product to carry context about how you travel across trips, rather than starting fresh each time.
Right now, Wanderglint identifies what needs to be booked in advance and provides the best path to booking it. In some cases that's an in-app confirmation; in more cases, it's a flag and a direct link. The gap — between "here's what you should book" and "here's what we've confirmed" — is the most significant friction in the current product. Closing that gap is most of what the capital is for.
The travel style memory problem is subtler. Every time someone starts a new trip on Wanderglint today, the conversation begins from scratch. If you've told us six times that you prefer slow mornings and aren't interested in museums, you shouldn't have to tell us a seventh time. Building that continuity properly — so it actually serves you rather than constraining you — is a design and engineering challenge we've been working around until now.
What We're Building
The immediate priority is restaurant reservation integration. We have the architecture in place; what we're building out is the connection layer that turns a "you should book this" flag into an actual confirmed reservation without requiring you to leave the product and navigate a third-party booking flow. This is live for a limited set of destinations in the US and UK in test, and we expect to expand that to our most-requested European cities over the coming months.
Activity bookings are more complex. The fragmentation in the activity booking market — dozens of platforms, uneven API availability, wildly different inventory — means we're taking a pragmatic approach rather than a comprehensive one: start with the experiences that our travellers book most frequently, in the destinations they visit most often, and expand from there. We'd rather do a smaller set of bookings very well than claim comprehensive coverage we can't actually deliver.
The travel style memory feature is in early development. The current design stores your stated preferences — pace, accommodation type, dining priorities, activity interests — and uses them as the starting point for new trip conversations rather than rebuilding from zero. The hard part is making the memory useful without making it feel like you're being held to a profile you set eighteen months ago. We're working on a "confirm or update" moment at the start of each new trip that makes the memory visible and adjustable.
What Stays the Same
The core philosophy of the product isn't changing, and I want to be explicit about that. We're not building toward a comprehensive travel platform — the everything-travel-app with flights, hotels, activities, reviews, and community features that several well-funded companies have tried to build. We're building a trip planner with a specific point of view: that the best trips are built around your travel style first, destination second, and that planning should result in fewer things better experienced rather than more things catalogued.
The angel round gives us runway to hire a small number of people — we're currently three — and build the booking layer properly. It doesn't change what we're trying to build or who we're building it for. We're not in a growth-at-all-costs mode. We're in a "make the product meaningfully better for the people using it" mode, which is where we should be at this stage.
The Honest Caveat
Booking integration is technically tractable, but it requires partner relationships and API reliability that are genuinely outside our control in ways that pure software development isn't. We can build the integration layer; we're dependent on partners whose reliability and terms we can't dictate. I'm flagging this not to lower expectations but because I think users of a product deserve to understand where the hard parts actually are.
The goal for the end of 2026: a Wanderglint trip that results in a confirmed itinerary — not just a good plan but the specific bookings locked in — for the categories of experience where that's possible. Restaurants, certain activities, accommodation search with direct booking links. That's a meaningful improvement over where we are today, and it's achievable with what we have.
Thank You
To the travellers who've been using Wanderglint and telling us what works: this is the direct result. The people who funded this round were largely introduced to the product through users describing it to them. That chain — good product, real word of mouth, capital to build more of it — is how we'd like this to keep going.
The plan is on the product page if you want specifics. We'll keep writing here about what we learn, both about building Wanderglint and about how people actually travel well.
