A trip that runs itself
Private travel planning

The plan keeps itself current.

A researched, day-by-day trip that lives on the traveler's phone — and quietly updates as restaurants answer, hours change, and trains get booked. She reads it. She doesn't maintain it.

Built for one traveler at a time. In use right now on a three-week trip through France.

Thursday 17 September · Chamonix
Dinner — La Table de l'Index, 7:30pm
They hold the table with a card. Nothing is charged today.

Approve a card hold?

If you don't turn up€58 a head
Two people, so at most€116
Free to cancel untilWed 16, 22:30
Charged today€0
A single-use card, for this one booking.
What it does

Three things a paper itinerary can't.

It answers back

She taps a question on any row — "is this too far to walk?" — and the plan itself changes. No email thread, no version two, no wondering which copy is current.

It chases the bookings

Restaurant replies land where the plan can see them. A request that hasn't been answered stays visible; one that's settled stops asking her for anything.

It knows what's shut

The museum closed Tuesdays, the lift that stops running in shoulder season, the restaurant that only takes bookings by phone. Checked against the day she's actually there.

The card hold

Some restaurants want a card to hold the table.

Nothing is charged — it's an imprint against a no-show. But it means handing a card number to a booking form, and the figure that matters isn't the one on the form. It's what they can charge if she doesn't turn up.

The exposure is read from the venue, not guessed

Each restaurant publishes its own no-show figure. It's fetched at the moment of asking, cross-checked against a second source, and the run refuses outright if the two disagree.

She sees the real number before she decides

Per head, total for the party, and the exact moment cancelling stops being free — in her own currency and her own words, on the row the booking belongs to.

One tap creates a single-use card

Good for that booking and nothing else. The number is written straight to the venue's form and never passes through a chat, a log, or an inbox.

On card numbers

No card number is ever stored, displayed, or written to a log by this system. Card credentials go directly from the issuer to the venue's booking form. What's kept is the decision: what she was shown, what she approved, and when.

Her controls

She can end it at any point, and nothing recurs.

Connected on purpose

She connects her own wallet once, from her own phone, and the app shows a standing "your card is connected" state — never a notice that disappears. One button disconnects it, and disconnecting removes the session on our side, not just the note on her phone.

One card, one booking

Every approval creates a card for that single reservation, capped at that venue's own no-show figure. Nothing is standing, nothing repeats, and no card outlives the booking it was made for.

Nothing happens silently

No hold is ever requested without her seeing the venue, the figures and the deadline first, and declining is a single tap that closes the request. What she was shown is recorded alongside what she decided.

What this is not

Not a marketplace and not a storefront. No merchants sell through it, nothing is resold, and no commission is taken on a booking. The only money that moves is between the traveler and the restaurant she chose, on the terms that restaurant publishes.

Who it's for

One traveler, looked after properly.

This isn't a booking site and it isn't a marketplace. It's the work a good travel agent used to do — reading ahead, holding the tables, noticing the Tuesday closure — done continuously, for one trip, by someone whose only job is that trip.