A multi-product Bosphorus commerce platform I structured around three different buying decisions: shared cruises, dinner products, and private-yacht charters.
Visit live product
Public customer interface. Private operational screens and customer data are intentionally excluded.
Observed in production
Evidence, with a date attached.
GA4 and GSC snapshot for 29 June–26 July 2026. The 89 AI referral sessions are observed GA4 referrals from ChatGPT and Gemini for 19–25 July 2026. Referral traffic is a measurable floor, not total AI visibility, attribution, or revenue.
- GA4 sessions · 28 days
- 2,807
- GSC clicks · 28 days
- 438
- AI referral sessions · 7 days
- 89
Context
The product behind the interface.
Context
A shared cruise, a dinner cruise, and a private yacht are not just three landing pages. They have different price units, capacities, timings, confirmation paths, and operator decisions.
Problem
The product needed to make broad discovery simple without flattening different commercial and operational rules into one generic form.
My role
I defined the product structure and owned the customer and operational flow: experience comparison, reservation and quote paths, server-side rules, multi-locale presentation, measurement, and the reusable foundation shared with related cruise products.
Public product evidence
More than a homepage.
These public screens show the product flow and presentation. Private operations, customer records, and administrative data stay out of the case study.
What I built
A complete working flow.
- A comparison path for sunset, dinner, and private-yacht products
- Direct reservation and quote flows for different purchase models
- Server-side pricing and package rules
- Localized confirmations, documents, and operator approval
- A reusable product core adapted across related cruise brands
- GA4, GSC, and AI-referral measurement with explicit limitations
- 01Discover
- 02Compare
- 03Choose product
- 04Price or quote
- 05Reserve
- 06Operator confirmation
Product and technical decisions
The choices that shaped the system.
Model products by buying decision
Shared tickets and whole-yacht charters should not pretend to be the same checkout. The interface changes with the decision while common infrastructure stays reusable.
Keep approval in the workflow
Private events may require vessel and operator confirmation. The product represents that state instead of promising instant certainty it cannot guarantee.
Measure AI referrals conservatively
Observed sessions can be reported. Unobserved citations, assisted decisions, and revenue cannot be inferred from that number alone.
What the system enables
What the system makes possible.
- Customers can compare distinct Bosphorus products before entering a narrower flow
- Different price and confirmation models share a reliable operational core
- Search, product usage, and observed AI referrals can be reviewed together
Challenge
Reuse is valuable only when it does not erase the differences between products, audiences, and operator commitments.
What I learned
A platform is not one interface repeated across brands. It is a set of reliable primitives with enough room for each product decision to stay honest.