Trivo: group travel,
finally coordinated.
An AI-native group trip coordination platform that solves the silent coordination failures of group travel, budget misalignment, organiser burnout, and fragmented planning, from the first “let’s go!” to final expense settlement.
This page is the full Product Requirements Document for Trivo, covering the group travel coordination problem, primary user research, the AI conflict-detection layer, and the MVP scope shipped for Mastering AI Product Management, Cohort 7 (Rethink Systems).
Executive
summary.
Overview
Group travel planning is a $168.7 billion global market growing at 7.2% CAGR, faster than solo travel, yet the coordination layer that helps groups decide, plan, and execute trips together remains almost entirely unsolved.
Today, groups stitch together 4–5 disconnected tools (WhatsApp, Google Sheets, Splitwise, Airbnb, Google Maps) and one person absorbs the entire coordination burden. The result: the organiser has the worst trip experience, silent misalignments around budget and diet surface mid-trip as conflict, and 2–3 weeks of planning inactivity kill group energy before departure.
The core insight from 6 user interviews and deep secondary research: group travel planning is fundamentally a social and emotional challenge, not a logistical one. The hardest part isn’t finding hotels, it’s getting six people to agree on anything without social awkwardness.
Built for logistics.
Not for people.
01 · Problem
| Metric | Value |
|---|---|
| Global Travel Gross Bookings (2024) | $1.6 Trillion |
| Global Group Travel Market (2024) | $168.7 Billion |
| Group Travel CAGR (2025–2033) | 7.2% (outpacing solo travel) |
| Projected Group Travel Market (2033) | $314.7 Billion |
| India Online Travel Market (2024) | $51 Billion |
| Non-Metro Share of India Outbound Travel | 63% |
| India Travel Tech Funding Jump (2024) | $600M (+182.2% YoY) |
Why now: the strategic window
AI disruption window
Travel tech VC hitting AI-focused tools at 45% of all travel investment (mid-2025). AI-native products can absorb group preferences privately and synthesise shared options, directly addressing social friction.
Incumbent gap
MakeMyTrip acquired Flamingo Transworld (group packages), signalling recognition of the gap, but through M&A, not product innovation. A 12–24 month window exists before incumbents move decisively.
India mobile infrastructure
660M+ smartphone users, mobile data at ₹9/GB, UPI-native payments. Non-metro cities now drive 63% of outbound travel. WhatsApp at 550M+ users means zero onboarding friction.
The typical group trip failure journey
| Stage | What happens |
|---|---|
| Step 1 | Someone says “let’s go!” on WhatsApp |
| Step 2 | 12 destinations suggested across 3 different conversations |
| Step 3 | WhatsApp poll created, 3 of 7 vote, poll expires unresolved |
| Step 4 | Dates debated across days; someone can’t make shortlisted dates, group splinters |
| Step 5 | Budget never discussed; one person assumes ₹5,000/day, another assumes ₹15,000/day |
| Step 6 | One frustrated person builds a Google Sheet alone and shares it |
| Step 7 | Booking done in a rushed final sprint, double-bookings, sold-out options, price spikes |
| Step 8 | During trip: nobody knows the day’s plan; organiser becomes GPS + concierge + accountant |
| Step 9 | Post-trip: Splitwise is messy, some expenses undocumented, unpaid debts linger |
The three root problems
Root Problem 1, Silent Budget Misalignment. Budget is the #1 source of group trip friction and the least openly discussed topic. No tool creates a “socially safe” mechanism for budget disclosure. The mismatch surfaces mid-trip as resentment, not pre-trip as planning input.
Root Problem 2, The Organiser Tax. 1–2 people absorb 80%+ of all coordination load, research, booking, reminders, expense tracking, and live itinerary management. The irony: the organiser consistently has the worst trip experience.
Root Problem 3, No Single Source of Truth. Information is scattered across WhatsApp threads, Google Docs, booking confirmation emails, Instagram saves, Notes apps, and Splitwise. Every interaction adds friction; none builds shared context.
Core insight: Group travel coordination is a fundamentally social and emotional challenge, not merely a logistical one. Users avoid direct conversations about money and preferences, leading to silent misalignments that surface during the trip itself and degrade the collective experience.
Six trips,
one pattern.
02 · Research
| Parameter | Details |
|---|---|
| Method | Semi-structured user interviews (video call, transcribed via Otter.ai) |
| Total Interviews | 6 core interviews (cross-validated across two research phases) |
| Interview Period | March 28–30, 2026 |
| Geographic Coverage | 1 US-based, 5 India-based, across metro and non-metro cities |
| Group Types | Multi-family (2), Office colleagues (2), Friend groups (2) |
| Trip Types | Domestic leisure, international, mountain treks, beach, family vacation |
| Cross-Validation | 2 interviews independently describe the same mountain trip |
Key verbatim quotes
“No one was kind of upfront… through the selection of places, people were exposing their budgetary preferences in a way.” Senior PM, US-based group traveller
“I want all the organiser’s responsibility to go away.” Group trip participant, India
“People tend to avoid talking about their budget or dietary restrictions upfront. If there was some way to make those people comfortable in saying those things early on… it would have been really nice.” Group traveller, India
“Multiple sub cuts, and then it was a mess, Splitwise me or challenge, because you have to enter it manually every time.” Multi-day trip participant, India
“Since we had paid for like three days in advance, so now you are stuck. You have paid a hefty price, and you are stuck.” Multi-day trip participant, India
Cross-cutting themes
Validated across 4+ of 6 interviews.
T1: WhatsApp + spreadsheet cobbling
All 6 interviewees used WhatsApp as primary coordination. Critical decisions are scattered across chat threads, Google Docs, booking confirmations, and Splitwise. No single source of truth.
T2: Budget is the first conversation, hardest to have
Budget discussion is universally acknowledged as the starting point, yet groups consistently avoid stating actual constraints. Mismatch surfaces during the trip as resentment, not as planning input.
T3: Dietary misalignment discovered too late
6/6 interviews referenced dietary restrictions as a coordination failure. Ranges from veg/non-veg to Jain food, onion/garlic-free, and kid-friendly needs. No current tool prompts or collects this information.
T4: Planning load is asymmetric
In every trip described, 1–2 people did the majority of research, booking, and coordination. Others are “along for the ride” during planning, then vocal during execution, creating organiser resentment.
T5: Sub-group divergence during trips
4/6 interviewees described instances where the group naturally split during the trip. Viewed positively, but entirely unplanned and managed ad hoc via WhatsApp.
T6: Splitwise is standard, but effortful
Mentioned by 3/6 as the go-to expense tracker. Pain: manual entry is tedious; people forget or stop logging. Best workaround: split fixed costs upfront so Splitwise only handles variable expenses.
Pain points ranked by severity
| Pain Point | Severity |
|---|---|
| Silent budget misalignment | Critical |
| No upfront preference collection (dietary, mobility) | Critical |
| Asymmetric planning burden | Critical |
| No real-time road / ground truth data | High |
| Hotel quality mismatch vs. reviews | High |
| Expense tracking fatigue | High |
| Last-minute cancellations disrupting plans | High |
| No structured itinerary for sub-groups | Medium |
| Children-specific logistics | Medium |
Competitive landscape
No single product handles the full group travel coordination lifecycle. Users are forced to stitch together 4–5 tools.
| Tool | Core Strength | Key Gap |
|---|---|---|
| WhatsApp / Telegram | Real-time comms, link sharing | Polls expire, messages buried, no structure |
| Wanderlog | Visual itinerary + map planning | Weak group voting, no budget split |
| TripIt | Email-to-itinerary import | Single-user focused; no group budgeting |
| Splitwise | Expense splitting + settlement | No planning features; manual entry fatigue |
| Google Travel | Inspiration, saved places | Zero group coordination whatsoever |
| MakeMyTrip | Search and book flights, hotels | Individual booking only; no group decision layer |
| Google Sheets | Budget tracking, shared lists | Not mobile-first; no travel features |
Critical gaps: what no tool solves
Anonymous budget preference collection
No tool creates a socially safe mechanism for budget disclosure. Groups proxy preferences through accommodation price selection.
Upfront dietary / constraint onboarding
No tool prompts or collects dietary restrictions, mobility needs, or kids’ requirements before planning begins.
Single group dashboard / source of truth
No product shows: where are we going, when, what’s the plan each day, what’s the cost, what’s confirmed.
Four archetypes,
one traveller.
03 · Users
Four distinct archetypes emerged from interview analysis. Most users exhibit more than one archetype depending on group composition and trip type.
The Delegator Approver
Takes no active lead; participates in validation. Waits for 2–3 options to be shortlisted, then picks one. Voices dissatisfaction after the fact if not consulted before final booking.
The Reluctant Organiser
Becomes de-facto planner by default, due to local knowledge, seniority, or history. Books accommodation, manages expenses, drives the car. Bears disproportionate cognitive load.
The Budget Whisperer
Acutely aware of group financial dynamics. Silently calibrates preferences to implied budget. Uses Airbnb price selection as an indirect budget signal. No socially safe mechanism to communicate limits.
The Experience-First Traveller with Constraints
Wants a rich trip but constrained by family needs, young kids, dietary restrictions, physical limitations. Filters heavily for kitchen access, stroller-friendliness, kid-friendly itineraries.
Primary persona: Aarav Sharma
The Connected But Constrained Group Traveller
Aarav Sharma, 32, Mid-senior PM / Software Engineer · Bangalore / Jaipur
| Life Stage | Recently married or young parent (child 0–5 years). Transitioning from spontaneous to planned, constraint-driven group travel. |
| Travel Frequency | 2–3 domestic trips/year; 1 international trip every 1–2 years. Group size: 4–8 adults + kids. |
| Travel Style | Comfort-first. Prefers Airbnb for family flexibility. Values experiences and calm over itinerary density. |
| Planning Role | Passive-to-moderate participant. Comfortable delegating planning but wants to be consulted before decisions are finalised. |
| Budget Behaviour | Has a clear private budget floor but won’t state it openly. Uses indirect signals (price of suggested options) to indicate affordability. |
| Core Frustration | Silent misalignments (budget, food, activities) are baked in before the trip starts. No safe, early mechanism to surface and resolve them. |
From chaos
to consensus.
04 · Solution
Value proposition
| Customer Job | Current Pain | Our Solution |
|---|---|---|
| Get the group to agree on a budget | Social awkwardness; indirect proxy signals; mid-trip conflict | Anonymous budget range poll with AI-synthesised group consensus |
| Coordinate dietary and trip style preferences | Discovered on-ground; leads to conflict and bad experiences | Upfront constraint onboarding at trip creation |
| Distribute planning work fairly | 1 person does everything; others critique after arrival | Task assignment with completion tracking; role-based expense ownership |
| Track and settle expenses | Manual Splitwise entry abandoned mid-trip; post-trip disputes | Category-based pre-assignment; auto-tracking; 1-tap UPI settlement |
| Maintain one shared plan everyone can see | Decisions buried in WhatsApp; no one knows the current plan | Single group dashboard: destination, dates, itinerary, costs, tasks |
Core user loop
| Step | Action | System Response | Outcome |
|---|---|---|---|
| 1. Create | One person creates a trip and invites group via WhatsApp link | Trip workspace created; all members receive one-tap join link | Group enters a shared coordination space in under 30 seconds |
| 2. Align | Each member completes an anonymous preference survey | AI synthesises responses into group-level insights without revealing individual answers | Budget ranges and preference overlaps visible to all; no awkward conversation needed |
| 3. Decide | Group votes on destination shortlist, dates, and accommodation | AI generates contextual options matching preference synthesis; voting with deadlines and nudges | Decisions made within days, not weeks |
| 4. Plan | Organiser assigns planning tasks to group members | Task tracker shows status; automated reminders; AI suggests itinerary based on preferences | Planning load distributed; no single point of failure |
| 5. Trip | Group accesses live itinerary; expense logging; sub-group coordination | Shared day-by-day itinerary; category-based expense tracking; sub-group schedule view | Organiser can enjoy the trip |
| 6. Settle | Post-trip expense settlement | Automatic calculation based on category ownership + variable expenses; one-tap UPI settlement | No lingering debts; Splitwise-level clarity with zero manual entry |
Feature roadmap by priority
P0: MVP
- Anonymous preference polling (budget, dietary, trip style)
- Upfront constraint onboarding checklist
- Planning task board with assignment + tracking
- Single group dashboard
- WhatsApp-based group invite flow
P1: Growth
- Integrated category-based expense tracking
- Structured sub-group itinerary planning
- AI Trip Concierge for group decisions
- Passive member nudging (push + one-tap WhatsApp actions)
P2: Scale
- Mountain / off-grid travel advisories
- Ground truth hotel scoring (last 30-day reviews)
- Kids-friendly trip filter layer
- Platform-level service guarantee
MVP scope (V1: P0 features only)
V1 ships only P0 features. The goal is to validate the core thesis: that removing the social friction of preference collection changes group planning behaviour.
V1 in scope
- Anonymous preference polling (budget range, dietary, trip style)
- Upfront constraint onboarding checklist
- Planning task board with assignment + tracking
- Single group dashboard (destination, dates, itinerary, task status)
- Basic expense tracking (category-based pre-assignment)
- WhatsApp-based group invite flow (zero onboarding friction)
V1 cut
- Mountain / off-grid advisories (requires data partnerships)
- Ground truth hotel scoring (requires review aggregation pipeline)
- Platform service guarantees (requires vendor contracts)
- AI Trip Concierge (ship preference polling first; AI layer in V2)
- Kids filter layer (not core to thesis)
- Sub-group itinerary planning (design complexity; V2)
Tech stack
| Layer | Technology | Why |
|---|---|---|
| Frontend (Mobile) | React Native | Mobile-first; one codebase for iOS + Android |
| Backend / API | FastAPI (Python) | Fast iteration; Python ecosystem for AI integration |
| Database | PostgreSQL (Neon) | Relational data model for trip/task/expense; serverless scaling |
| AI Layer | Claude API (Anthropic) | Preference aggregation; group decision framing; itinerary generation |
| Authentication | Auth.js (OAuth) | Google + WhatsApp number login; zero friction for Indian users |
| Payments | Razorpay (UPI) | UPI-native for India; expense settlement flow |
| Hosting | Railway / Vercel | Simple deploy; auto-scaling; zero DevOps overhead for MVP |
How we’ll know
it worked.
05 · Metrics & Roadmap
North Star: Trips completed without silent misalignments surfacing mid-trip, measured via post-trip survey: “Did any surprise conflict arise?”
Phased implementation plan
| Phase | Deliverable | Duration | Test Gate |
|---|---|---|---|
| Phase 1: Foundation | Trip creation, WhatsApp invite flow, group dashboard skeleton | Week 1–2 | Can a group of 5 create a trip and all join via WhatsApp in under 2 minutes? |
| Phase 2: Preference Layer | Anonymous preference survey, AI synthesis of budget + dietary inputs | Week 2–3 | Do 60%+ of invited members complete the survey? |
| Phase 3: Planning Tools | Task board, assignment, tracking, itinerary builder | Week 3–4 | Can organiser assign 5 tasks to 5 members and all receive notifications? |
| Phase 4: Expense Layer | Category pre-assignment, variable expense logging, settlement calculation | Week 4–5 | Can group settle all expenses in under 5 taps post-trip? |
| Phase 5: Polish + Launch | UI polish, error states, onboarding flow, beta testing with cohort | Week 5–6 | End-to-end test: create trip → preference poll → task assignment → expense settlement |
Release strategy
V1 (MVP, 6 weeks): P0 features only. Ship to cohort group + 2–3 real friend groups as beta users. Validate preference survey completion rates and decision velocity metrics.
V2 (4 weeks post-V1): Integrated expense tracking, AI Trip Concierge, passive member nudging with one-tap WhatsApp actions.
V3 (8 weeks post-V2): Sub-group itinerary planning, mountain/off-grid advisories, ground truth hotel scoring, kids-friendly filter layer.
V4 (Strategic): Platform accountability layer, service guarantees, B2B corporate group travel.