Re-planning when the trip breaks: inside Gonav Wander
Anyone can generate an itinerary. The hard part is the second one — the one you need at 6am when the train is cancelled.
The first itinerary is a demo. The product is the re-plan.
The disruption graph
Wander holds each trip as a graph of commitments — flights, stays, bookings, buffers. When one node fails, it knows what depends on it.
Budget-aware recovery
A re-plan respects the original budget envelope. If recovery costs more, Wander says so, and shows where the money went.
In the language people use
"Push everything a day, keep the Tuesday dinner." That sentence is the whole interface.
More insights
How Gonav Ledger cut a two-week close to four days
A finance team was losing the first half of every month to reconciliation. Here is what actually moved the number — and what didn't.
Wayfinding, not roadmaps: how we plan across five industries
A roadmap is a hypothesis with a date attached. Here is the planning practice we use instead when the terrain keeps shifting.
What “embedded” really means when Gonav Build joins your team
Staff augmentation and embedded delivery look similar on an invoice. They are not the same thing. A field guide.