Plan Karo Chalo — Group Trip Coordination

Section 01

Discovery Insights

This product is grounded in primary research across 132+ unique data points: 27 interviews spanning structured deep conversations, consolidated Q&A-format interviews, qualitative retrospective write-ups, and cross-group interviews — plus 105 survey responses across three independent surveys.

Respondents covered friend groups, multi-family trips, women's treks, couples groups, motorcycle touring clubs, and three-generation family vacations. Group sizes ranged from 2–3 to 22+. Secondary research validated primary findings: the global group travel market reached ~$168B in 2024 at 7.2% CAGR. India's travel market: $22.5B with 2.5 billion domestic tourist visits in 2023 (up 45% YoY).

We entered this research expecting itinerary building to be the core pain point. We were wrong. The trip journey dies much earlier, and the kill zone is remarkably consistent across every group type.

80%+

named date alignment as #1 friction point

67%

groups have 1–2 people doing all the planning work

6–8

apps used per trip on average; information scattered

2 users

independently described identical solution: "one link, no download, tap and done"

Trip Journey — Where It Dies

Spark

"Let's go somewhere!" in WhatsApp. 12 destinations across 3 conversations.

Date Alignment 🔥 KILL ZONE

Manual availability checking. 2–4 weeks of back-and-forth. Trip stalls here most often.

Destination Decision 🔥 KILL ZONE

WhatsApp debates, expired polls, decision paralysis. Trips get canceled during discussion.

Budget Agreement 🔥 KILL ZONE

Rarely discussed explicitly. Silent misalignment surfaces later as dropouts.

Accommodation

One person researches across 3–5 OTAs. Siloed, competing preferences.

Itinerary

3–4 days of calls + blog research. AI is now commoditizing this fast.

On-Trip

Organizer becomes GPS + concierge + accountant. Activity splits, food friction.

Post-Trip

Expense settlement drags. Small amounts leak. Splitwise friction.

Critical insight: If a group survives past budget agreement (stage 4), the trip almost always happens. The highest-leverage intervention is collapsing stages 2–4 into a single, structured flow.

Key Assumptions Overturned

Assumption	Status	What Changed
Itinerary building is the core pain	Overturned	Trip dies at dates, not itinerary. AI itinerary is commoditizing — 56% already use AI. The coordination layer is the white space.
Users want an all-in-one platform	Overturned	Both interviewees explicitly rejected feature-heavy tools. Users want one problem solved well.
Everyone needs to use the tool	Overturned	Must work even if only the organizer creates an account. Proxy input and link-based participation are essential.
Anonymous budget ranges solve misalignment	Partially wrong	Survey response was lukewarm. Families handle budget implicitly. Simple budget field for V1.

Section 02

Problem Statement

The "default planner" in Indian friend groups and families of 4–10 people needs a way to move their group from "let's go somewhere" to "dates locked, destination chosen, everyone confirmed" because the pre-booking coordination phase is entirely unstructured — currently managed through weeks of WhatsApp back-and-forth, manually piecing together availability, chasing non-responders, and absorbing all cognitive load alone — resulting in 35% of planned trips never happening, organizer burnout across 5–15+ hours per trip, late bookings at higher prices, and compounding social friction.

Pain Point Disposition

Pain Point	Status	Rationale
Date & Schedule Alignment	V1	#1 universal pain (80%+). No tool solves it for informal groups.
Trip Status + Momentum	V1	No shared dashboard = no visible progress = momentum death. 20% of failed trips.
Organizer Tax Reduction	V1 Design Principle	67% of groups = 1–2 planners. Tool reduces burden via automation + proxy input.
Destination Convergence	V1	60%+ frequency. WhatsApp polls fail — no context, structure, or lock mechanism.
Budget Misalignment	V1.1	Validated (55%+) but anonymous range concept unvalidated. Simple budget field for now.
Itinerary Effort	V2	AI commoditizing fast. Group-aware AI needs V1 data.
Expense Tracking	Eliminated	$512.5M mature market. Splitwise/UPI adequate. Both interviewees explicitly rejected it.
Booking Integration	Never	Architectural boundary. We're coordination, not booking.

Section 03

Proposed Solution

Plan Karo Chalo is a link-based trip coordination tool that guides Indian groups through the pre-booking decision sequence — dates → budget → destination → commitment — via a shared dashboard, with no app download required.

📝 Create Trip

→

🔗 Share Link

→

📅 Pick Dates

→

💰 Set Budget

→

📍 Vote Destination

→

✅ Hold to Confirm

→

🎉 Locked!

Core Features

📅 Date Alignment

Members tap individual dates on a calendar — each date turns green. Overlap algorithm finds the best N-day window automatically. If no window fits, system suggests longest available overlap. No From/To pickers — just tap the calendar.

📍 Destination Convergence

Anyone can propose or quick-add from 10 curated "Popular Picks" (Goa, Manali, Jaipur, etc.). Live vote counts and voter avatars create social momentum. Ties trigger "Shake to decide." Organizer locks the result.

💰 Budget Alignment

Optional bottom sheet after dates. Members drag a dual-handle slider (₹2K–₹2L). System computes anonymous "sweet spot" — the intersection of everyone's ranges — without revealing individual numbers.

✋ Hold-to-Confirm

Members press-and-hold for 2 seconds. Green fill animation creates intentionality. Casual "I'm in" becomes a deliberate 2-second commitment. The instruction is inside the button — nothing floats above it.

📊 Trip Status Dashboard

"Since you were here…" card shows what changed between visits. Progress bar shows how close the trip is to locked. "Waiting on 3 people" removes the ambiguity that lets trips quietly die.

📣 6-Tone Nudge Library

Pre-written WhatsApp messages with dynamic member counts. Friendly → Shady → Urgent. "This trip is waiting on flaky energy 👀" vs "Locking tomorrow with or without you 🔒." One tap copies with the trip link.

Section 04

Competitive Landscape

Group travel has no shortage of tools. Each solves exactly one piece of the problem and assumes someone else will handle the rest. None of them touch the pre-booking coordination phase — the stage where most trips die.

Capability	WhatsApp	Wanderlog	Any OTA	Plan Karo Chalo
Group date overlap calculation	✕	✕	✕	✓ Auto-calculated
Structured destination voting with lock	Polls (expire)	✕	✕	✓ Vote + shake + lock
Anonymous budget alignment	✕	Partial	✕	✓ Sweet spot calculation
Stage-gate trip progression	✕	✕	✕	✓ 4-stage dashboard
Commitment checkpoint	✕	✕	✕	✓ Hold-to-confirm (2 sec)
No download / link-based join	✓	✕	Partial	✓ Zero friction
India-context nudges (Hinglish, WhatsApp format)	Manual	✕	✕	✓ 6-tone nudge library

The moat is not a feature — it's a workflow. WhatsApp handles chat. Wanderlog handles itineraries. Splitwise handles settlements. Plan Karo Chalo owns the layer between the idea and the booking: structured decisions, visible progress, and a commitment mechanism that makes it harder to drop out than to confirm.

Section 05

Success Metrics

Target Metrics

>40%

Trip Completion

vs ~20% WhatsApp-only

<5 days

Time to Lock Dates

vs 2–8 weeks currently

>70%

Member Activation

join rate from shared links

>70%

Response Rate 48h

vs days of partial responses

>30%

Return Visit Rate

members revisiting the link

Live Test Data — From Production (Cohort Testing)

These aren't projected numbers. The metrics below were queried from the production Supabase database after cohort testing. Small sample, early signal — but real data, not estimates.

24.0%

Trip Completion

Below target — most test trips had no real travel intent. Signal to watch in the wild.

1.5 days

Avg Days to Lock

Well inside the 5-day target. Calendar + nudges working as designed.

91.7%

Member Activation

Link-based join flow is working. Most important V1 signal.

85.2%

Response Rate 48h

Significantly above target. Calendar UX has near-zero comprehension friction.

54.1%

Return Visit Rate

Above target. "Since you were here…" card is doing its job.

Honest read on 24% completion: Test trips created with no real travel intent naturally die mid-flow — not a product failure, it's a sample composition issue. The meaningful signals are 91.7% activation and 85.2% 48h response rate. Once someone lands on the link, they engage. Getting them to the final lock step is the V1→V2 retention problem, not an activation problem.

Section 06

Key Design Decisions

✓ ChosenLink-based participation — no account required for members

✗ RejectedRequire all members to create accounts

Every interviewee said the same thing: asking people to install an app or create an account is where adoption dies. The family coordinator's father "still calls to ask how to download a PDF." Howbout requires universal app install — that's their bottleneck and our differentiator.

✓ ChosenStage-gate progression — dates → destination → commitment

✗ RejectedFreeform dashboard — any decision in any order

Flexibility is what WhatsApp already provides, and it produces chaos. One interviewee described 7–8 destination suggestions flooding in before dates were even discussed. Stage gates enforce the discipline groups need but cannot self-impose.

✓ ChosenTap-to-select individual dates — no From/To range pickers

✗ RejectedDate range input with unavailable date constraints

Building revealed the cognitive load: members had to think in ranges ("I'm free from X to Y, except Z"). Switching to individual day taps — like filling a heatmap — was immediately intuitive. Members just tap the days they're free. Gaps, weekends, split availability all handled naturally without constraint management.

✓ ChosenHold-to-confirm for commitment (2-second press)

✗ RejectedInstant-tap "I'm In" button

The hold gesture borrows from payment confirmations — it forces intentionality. A casual "yeah I'm in" tap becomes a deliberate 2-second commitment. Members said it felt "serious" and "real." The green fill animation provides satisfying feedback. Moving the instruction inside the button as a subtitle ensured no one missed it.

✓ ChosenPre-written nudge messages with 6 tones and dynamic counts

✗ RejectedSingle generic reminder copy

Generic "add your dates" messages don't create urgency. Dynamic counts ("3 of 6 people have voted") create social pressure. Six tone variants let organizers match their group's vibe — some groups respond to humor, others need urgency.

Section 07

Feature Roadmap

Feature	V1	V2	Never	Why
Date alignment + per-day calendar	✓ V1			Core — highest-leverage pain point
Dashboard + 4-stage progression	✓ V1			Core — visible momentum prevents trip death
Destination voting + shake tiebreak	✓ V1			Core — structured convergence with lock
Hold-to-confirm commitment	✓ V1			Core — intentional commitment mechanism
Budget range slider + group overlap	✓ V1			Moved up from V1.1 — needed for full coordination loop
Nudge modal (6 tones, dynamic counts)	✓ V1			Organizer tax reduction — #1 stated need
"Since you were here…" return card	✓ V1			Retention — #1 qualitative feedback highlight in testing
AI itinerary from locked trip data		V2		Budget sweet spot + destination + duration feeds AI prompt
WhatsApp bot		V2		Needs V1 adoption data; Meta BSP approval required
Booking integration			Never	Architectural boundary — we're coordination, OTAs are partners
Expense splitting			Never	$512M mature market. Both interviewees explicitly rejected it.
In-app messaging			Never	WhatsApp is where 500M+ Indian users talk. Duplicating chat = abandoned channel.