01:30 PM — Lunch at Hubli
06:30 PM — Resort Check-in
The plan for most group trips lives in three places at once: a WhatsApp thread, a saved map pin, and someone's memory that "we said 11 for chai." None of it is shared, none of it updates — so the moment the group splits, there's nothing to regroup around.
Built one shared surface that holds the plan, the people, and the live position — mapped to the trip's actual lifecycle (before, during, after) instead of a feature list — so "the plan" is something the whole troop can point to, not a mental model everyone carries differently.
Built around the person who ends up planning it anyway
In most friend groups, one person always ends up owning the plan — booking the stay, sharing the pin, answering "are we stopping for lunch" nine times over. Wagn is designed for that person first (the organizer), and for everyone riding along who wants visibility without having to ask.
Two needs stay in tension across the whole product: the organizer needs the plan to be provable and shareable, so the questions stop landing only on them. Everyone else needs to feel like they're in the trip, not managed by it.
Getting people in
Phone number, not a password
Nobody wants to invent a password to go on a road trip. Sign-in is phone number + OTP — the format most people in this audience already use for food delivery, banking, everything — so it needed zero explanation on first launch.
Ask for location like you mean it
Location access is the one permission Wagn cannot work without, and it's usually where trust breaks. Instead of letting the generic system prompt land cold, the ask is framed first — naming exactly who sees the location and why ("shared with your troop members," not "shared with Wagn") before the OS dialog even appears.
Home base
One screen, three questions
When a trip is live, home has one job: answer where is everyone, how much longer, and is anything wrong — without a tap. The ongoing-trip card leads with a live map, member avatars, and time/distance remaining as the very first thing on screen. A weather alert sits right on top of it when there's one worth showing, because a warning nobody sees isn't a warning.
Two doors, not a menu
Below that, home narrows to exactly two intents — start a new plan, or join one someone shared. Past trips sit underneath as a plain list: proof the app works, not something to manage.
Planning a trip, three steps instead of one wall
Planning an entire group trip in one sitting is the kind of task that gets postponed forever. Wagn breaks it into three short steps, each finishable in the time it takes to order chai, with progress shown the whole way so committing to step one doesn't feel like committing to the whole trip.
Where are you headed?
Search a destination, or use your current location as the start. That's the only decision this step asks for.
Who's coming along?
Pull people in from contacts, search by name or number, or skip straight to a shareable link — the troop doesn't have to be final before the plan starts.
Stops & stay
The route auto-suggests waypoints — chai, fuel, a meal, a photo point — instead of asking someone to think of them, then moves into where the troop stays.
The first Partner placement — and the first guardrail
This is the first screen where a sponsored listing appears, sitting next to two organic results. It's covered properly in the Business Center section further down, because the rule that keeps it fair gets decided right here, not bolted on afterward: a paid listing only ever shows up if it already belongs in this exact result set — same destination, same price band the group filtered for.
Skip the steps entirely: the AI itinerary planner
Not every troop wants to build a plan turn by turn. Sitting alongside the manual flow above, the AI planner takes the same three inputs — destination, troop size, rough dates — and returns a full day-by-day plan with stops, stay, and drive times pre-filled, ready to edit rather than built from a blank step. It's a shortcut into the same structure the manual flow produces, not a separate product: an AI-built plan and a hand-built one land on the identical trip-detail screen and edit the same way. The design position I kept coming back to — automation should hand someone a draft to argue with, not a decision to accept.
Dec 20 – 25, 2025
Stay: The Leela
Sharing is a step, not an afterthought
The last step of planning is turning the plan into a link, sitting front and center — not tucked into a menu. A plan nobody outside the organizer can see isn't a group plan. It's the organizer's plan, with extra steps.
From a shared card to a booked seat
01:30 PM — Lunch at Hubli
06:30 PM — Resort Check-in
Stay (Per Night) ₹3,200
Total / Person ₹7,700
The detail screen does the convincing
Tapping a trip card — your own, or one a friend shared — opens the full case for it: distance and duration up top, the troop's members, and a day-by-day travel plan built straight from the itinerary, followed by an honest cost breakdown split into fuel & tolls, stay per night, and total per person. Someone deciding whether to join should never have to ask "so what's this actually going to cost me."
UPI first, the fee shown in the open
Booking asks for traveler details, then payment — UPI listed before card or net banking, because that's how this audience actually pays. The price breakdown itemizes the platform fee separately from the base cost and tax instead of folding it in — a small transparency choice that costs a bit of margin-looking-good and buys trust in a product where friends compare notes.
Base Cost ₹4,900 · Taxes (GST 18%) ₹800 · Platform Fee ₹200 · Confirm & Pay ₹5,900 → Booking Confirmed, ID TRP-2024-8734.
A booking engine for partners, not a banner ad
Group planning stays free for the people actually planning the trip — this audience is friend groups splitting fuel money, not a market that tolerates a subscription. Revenue comes from the Business Center: a self-serve dashboard where hotels, resorts, and restaurants get placed at the single highest-intent moment in the whole product — the few minutes a troop is actively deciding where to stay or where to stop — instead of a generic ad slot nobody's looking at on purpose.
The guardrails I held to:
Same bar, or it doesn't show. A sponsored listing has to already clear the destination, price band, and route filters the troop set — paying for placement never means a worse option outranks a better one.
Labeled like a rating, not hidden like a footnote. Every sponsored card carries a "Partner" tag at the same visual weight as a star rating — never quieter, never easier to miss.
One per screen. A single sponsored card per step, so it's a suggestion in the mix, not a wall of ads.
An organizer can turn it off. Partner suggestions have a per-trip toggle in settings — the moment a choice needs an escape hatch to stay honest, build the escape hatch.
The Leela Goa
Partner☕ Chai Break — Woodside Cafe
PartnerWhat every screen had to answer to
The plan is the source of truth
Not a screenshot, not a memory of what someone said at a fuel stop.
"Where's everyone, what's next" first
Every screen answers that before it answers anything else.
Trust before the ask
Permission framing, fee transparency, and partner labeling all come before the moment they're needed — not after something goes wrong.
Automate the tedious part, not the decision
Auto-suggested stops and the AI planner both hand over a draft, never a final answer.
What held up, and what I'd push on next
What held up
- Breaking planning into three short steps turned "plan a whole trip" from a task people postponed into one they'd finish waiting for chai.
- The Partner guardrails held up under my own stress-testing — I couldn't construct a scenario where a sponsored card beat a genuinely better option.
What's next
- Splitting costs is the natural next feature — the cost breakdown shows "total per person" but stops short of actually settling who owes whom.
- The AI planner's first draft needs real usage data before its stop suggestions can get sharper than "technically along the route."
- Haven't stress-tested the Partner ranking against an actual hotel sales team trying to game it — that's a conversation for before this ships, not after.