What we’re building next.

Ask for a city we have never built and you get a guide for it — there is no queue and no admission list, and every place built for you joins the library for the next traveller. The quality work runs behind that rather than in front of it: every month we re-verify every venue website, re-resolve the map pins that only ever landed on a neighbourhood, and check the photographs still load. Venues we find have shut for good are marked closed and left out of every guide built afterwards — though that audit is still something we run city by city rather than on a clock. A place you asked for last week is thinner than Amsterdam; both get better on the same sweep.

You can already tell us a venue has closed, moved, or was never right — and we act on it. What you cannot do yet is see that we did. We are working on the other half of that loop, so something you flag from a café in Lisbon comes back to you as an answer rather than disappearing into our inbox.

The website, the dashboard and the guide in your pocket grew up separately and still look it. They now share a single set of colours, type and spacing, and we are partway through repainting each surface onto it. Quieter, more readable, less of the generic app-template feel — and legible in dark mode without a second design.

Partner guides already carry your logo, your colours and your support address. The link still says ours. Next up is serving those guides from a domain you control, so what you hand a guest is yours end to end.

The business pilot is run by hand today: you talk to us, we set up your organisation, we agree a price. That does not scale past the pilot and it makes you wait on our office hours. Next up is a plan you can pick, change and pay for without an email thread — with your own quotas and invoices visible in the dashboard.

Hotels and operators already know who is arriving and when — the booking exists long before anyone opens our dashboard. An API would let a guide be created from that booking automatically, so the traveller has their link before they have packed. Next up, and shaped by what pilot partners actually ask for.

Guides are written in English, Dutch, French, Flemish, German or Spanish. Adding a seventh is not hard technically — it is a commitment to keep every venue description, every interface string and every legal notice correct in it forever. We will add one when there are travellers waiting for it.

Right now a guide waits quietly on your phone until you open it. A nudge the evening before you fly, or a note when something in your plan closes, would be genuinely useful — and is also the fastest way to become one more app that pesters you. Later, and only if we can find the version that does not.

We maintain a record of what data we process and why, a breach procedure, and a running account of where we stand on accessibility. Today those live in our own repository and you have to take our word for them. Later we would like them published as they are — including the parts that are not finished yet, because a page that only lists the passing checks is marketing, not a trust centre.

A hotel group with a hundred staff should not be managing a hundred passwords with us. SAML and SSO are the honest answer to that, and they are a long way from a pilot that currently measures its partners in single digits. Later, when somebody actually has that problem.