Case Study 03 — Self-Initiated

RoamRiot — Travel Planning Platform

A 0→1 consumer product solving multi-app fragmentation in travel planning. Full PM ownership from user research through build — demonstrating end-to-end product lifecycle management outside the enterprise context.

Pre-launch
Role
Founder & Product Manager
Timeline
Conceptualised 2025 · Built 2026
Status
Pre-launch
Type
Consumer · 0→1
Part 1 of 5

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

Part 2 of 5

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

Part 3 of 5

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:

0→1 product User research PRD Wireframes Roadmap Consumer
Part 4 of 5

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.

Part 5 of 5

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.

Why include a pre-launch project? The Diligent case studies demonstrate PM execution within an existing organisation — identifying problems, building tools, and shipping measurable outcomes. RoamRiot demonstrates the ability to conceive a product from scratch, conduct original user research, and own every stage of the product lifecycle independently. For PM hiring, the process matters as much as the outcome.

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.