The Client
A founder in her early forties, four years into scaling a company through its hardest stretch. She had not taken more than four consecutive days off in three years. Japan had been on the list for a decade and had been postponed six times — twice after the flights were already booked.
She did not come to us for inspiration. She came because she had twice tried to plan this trip herself, had accumulated forty-one browser tabs and a half-finished spreadsheet, and had abandoned it both times at the point of sequencing Tokyo against Kyoto.
The Time Audit
Her intake answers determined the entire shape of the engagement. We reproduce them here because they matter more than the destination did.
Last Breakdown
A prior trip: a ninety-minute queue at a rail ticket office because she had bought the wrong regional pass. "I remember standing there doing mental arithmetic on what that hour and a half was worth."
Decision Threshold
Mixed. Shortlist the small decisions and simply handle them — build the consequential ones from scratch and explain the reasoning. She wanted to understand the logic, not to generate it.
Protected Hours
Escalating. Heavily scheduled for the first four days while her energy held, tapering to almost nothing by day eight. Most agencies front-load the rest. That would have failed her.
Decompression Breaker
The trip itself. She had historically become the group's de facto operations manager — the precise work she was trying to leave behind.
Cost of Failure
A board cycle beginning three weeks after her return. If she came back unrested, the next viable window was eleven months out.
The Build
Nine interventions, each one traceable to a specific line in the audit above.
01Rail passes issued and pre-activated before departure
Correct regional coverage confirmed against the actual routing, physical passes couriered ahead of the flight. Direct answer to the ninety-minute queue. She never entered a ticket office.
02Kyoto scheduled before Tokyo, against her own instinct
She had assumed Tokyo first. We inverted it and explained why: arriving jet-lagged into Kyoto's slower rhythm, then moving to Tokyo's intensity mid-trip when adjusted, then closing quietly. This was the consequential decision she wanted built from scratch.
03Early check-in cleared at both properties, in writing
Confirmed as a guaranteed hold rather than a request, so a 7:40am arrival did not become five hours in a lobby with luggage.
04Private temple access secured for two sites at opening
Arranged directly with each institution for entry ahead of general admission. The photographs she wanted exist because nobody else was standing in them.
05Dining locked ninety-one days out
Seven reservations placed the day each respective book opened, including two counters that release seats at midnight local time. Handled by our office in Japan Standard Time so she did not set a single alarm.
06Day eight through nine left entirely blank
No bookings, no recommendations, no suggested options. Deliberately empty, per the escalating-decompression answer. This was the hardest part of the plan to hold, and the part she later cited first.
07Luggage forwarded city to city
Bags moved Kyoto to Tokyo overnight by domestic courier. She travelled between cities with a single small bag and boarded the train with both hands free.
08A one-page card, and nothing else
Not an app, not a shared folder, not a fourteen-page PDF. One printed card per city: today's fixed points, the address in Japanese for taxi drivers, and one number to call. Everything else stayed with us.
09A single named contact, and a communications boundary
One person on our side owned the file for its duration. We contacted her twice across nine days — once to confirm a weather-driven substitution, once on the final morning.
The Intervention
On day five, a typhoon advisory closed the coastal excursion scheduled for the following afternoon. She found out about it after it had already been solved.
Our office rebooked the replacement — an indoor workshop she had mentioned once, in passing, during the intake call — rerouted the car, and cancelled the original inside the free window. The message she received was four lines long and required no decision from her. This is the entire product.
The Ledger
What the engagement actually returned, measured the only way that matters for a client whose scarcest asset is time.
26Client hours returned
0Queues entered
2Times we contacted her
31Reservations held on her behalf
Hours returned is our estimate of the research, booking, comparison, rebooking, and in-trip coordination the client would otherwise have performed personally — reconstructed from the engagement log.
Nine days. Two cities. Forty-one browser tabs that never had to be opened again.
In Her Words
Three weeks after her return, asked what she would tell someone considering the engagement:
"I keep describing it as the first holiday where I was a guest rather than the organiser. I did not realise those were different things until one of them happened to me."
On client privacy: identifying details in this case study — name, company, exact dates, and specific properties — have been altered or withheld at the client's request. The audit findings, the sequence of interventions, and the ledger figures are reported as they occurred.
