Context & Problem Space
The problem
Travel planning is fragmented across multiple apps and platforms. A single trip touches Google Flights for airfare, Booking.com or Airbnb for accommodation, Google Maps for itinerary routing, TripAdvisor for reviews, spreadsheets or notes apps for budgeting, and group chats for coordination. There is no single surface that holds the full picture of a trip.
Who this affects
Primary users: Independent travellers and small groups (2–6 people) planning multi-day trips who currently juggle 4–6 apps to coordinate a single trip.
Why existing solutions fall short
- No platform consolidates flights, stays, itineraries, budgets, and group coordination in one place
- Existing travel planning apps focus on discovery (where to go) but not execution (how to plan and book)
- Group trip planning relies on fragmented chat threads and shared documents
- Budget tracking requires a separate spreadsheet — no travel app handles this natively
Discovery & Technical Constraints
User research
Conducted user research to validate the fragmentation hypothesis and identify which pain points were severe enough to drive adoption of a new platform.
Competitive analysis
Mapped the competitive landscape across travel planning apps, identifying gaps in feature coverage. Key finding: most competitors optimised for the inspiration/discovery phase — "where should I go?" — rather than the execution/planning phase — "how do I organise and book this trip?"
Technical constraints
- Solo founder — PM, design, and development done by one person
- No external funding — built within personal resource constraints
- Must integrate with existing booking platforms (aggregation, not replacement)
- Group features require real-time collaboration architecture
Solution & Product Ownership
Product vision
An all-in-one travel planning platform that consolidates itinerary building, accommodation search, budget tracking, and group coordination into a single surface. The goal: a traveller should never need to leave RoamRiot to plan a complete trip.
PM ownership
Full end-to-end product lifecycle ownership — from problem identification through delivery:
- User research & personas: Defined target user segments and validated pain points
- PRD: Authored full product requirements document with feature specifications and acceptance criteria
- Roadmap: Prioritised features across phases using effort/impact framework
- Wireframes: Designed user flows and screen-level wireframes for core workflows
- Build: Hands-on development of the platform
Execution & Cross-Functional Leadership
Solo execution model
Unlike the Diligent projects where PM and development were distinct hats worn by one person within a larger team, RoamRiot is a solo venture. Every role — research, product, design, and engineering — is held by one person. This tests a different PM muscle: ruthless prioritisation when there's no team to delegate to.
What this demonstrates
Full product lifecycle fluency. Moving from user research → PRD → wireframes → roadmap → build on a consumer product shows the complete PM toolkit — not just the subset used in an enterprise internal-tooling context.
Consumer product thinking. The Diligent case studies showcase enterprise internal tooling with clear, measurable operational impact. RoamRiot demonstrates the ability to think about consumer UX, acquisition, retention, and product-market fit — a different set of PM skills.
Outcomes & Key Takeaways
Current status
Pre-launch. The product has been conceptualised (2025) and built (2026) but has not yet launched publicly. No usage metrics or adoption data are available.
Key takeaways
1. Consumer PM requires a different discovery muscle. Enterprise internal tooling has a captive user base — the problem and the user are right in front of you. Consumer product requires going out and finding the user, validating the problem, and competing for attention against established alternatives.
2. Solo execution forces prioritisation discipline. With no team to distribute work across, every feature decision is a direct trade-off against personal build capacity. This sharpens the "what do we cut?" instinct that matters in any PM role.
3. End-to-end ownership builds conviction. Having touched every stage — from initial research interviews through wireframe iterations through code — creates a level of product intuition that doesn't come from managing stages you haven't personally executed.