SellYourBoat · YachtBrokersAsia

For YachtBrokersAsia, I built a streamlined listing submission and review system that turns a messy, email-and-WhatsApp intake process into a structured, reviewable workflow. The goal was to make it effortless for owners to submit a high-quality listing, and fast for the brokerage team to review, approve, and publish — without chasing missing details, broken images, or inconsistent data.

In brokerage environments, listings arrive incomplete: unclear specs, missing ownership details, inconsistent pricing, and photos that aren't web-ready. That creates slow turnaround, extra admin, and a lumpy publishing cadence. This system standardises the intake and creates a clean path from raw submission to published listing.

Product Design · Workflow Systems · Admin UX · Data Normalisation · Media Management

Deep dive01 / 12

The problem

Listing intake was creating avoidable friction at every stage. Sellers don't know what 'good' looks like, so submissions arrive incomplete or inconsistent. Brokers repeatedly chase the same missing information. Photos are a constant failure point — wrong sizes, too heavy, missing, poorly ordered. Review and publishing is hard to manage at scale without clear statuses and a single source of truth. The result: slower time-to-publish, lower listing quality, and operational drag right where the business needs speed.

Strategic approach

I optimised for operational throughput, not just UX polish. A brokerage listing engine wins when it reduces admin time per listing and increases publish consistency. Every design and architecture choice was made to keep the pipeline moving — from submission structure to review workflow to status management. The measure of success isn't how the form looks, it's how many listings go live without a human chasing missing details.

Listing wizard

I designed a multi-step submission flow — not a generic form — that captures the minimum viable data for a publishable listing. Category selection, key details, features and specs, seller information, photo upload with ordering, and a final review step that mirrors the published layout so sellers self-correct before submitting. The UX priority was speed and confidence: sellers should feel like they're completing a professional listing, not filling out admin paperwork.

Self-correcting submissions

The final review step is the most important design decision in the wizard. By showing sellers exactly how their listing will appear before it reaches the team, most formatting issues and missing details get resolved without human intervention. Combined with the step-by-step structure, this dramatically reduces the number of submissions that require clarification. That's operational leverage disguised as UX.

Data normalisation

Behind the wizard, the system normalises the common failure points: consistent price and currency handling, trimmed and sanitised inputs, required-field validation where it matters, and flexibility where reality demands it — because boats vary wildly. The visible UI is important, but the real unlock is consistent structured data: categories, pricing formats, locations, and specs that don't need rework before publishing.

Admin review dashboard

I designed the admin surface around how brokerage teams actually work. Status tabs — pending, published, rejected, drafts — give at-a-glance pipeline visibility. Each listing row surfaces the key fields: title, year, location, price, category, created date. The detail view mirrors the listing content and highlights gaps. Explicit approve, reject, and draft actions create accountability and prevent the 'lost in inbox' problem that kills operational speed.

Status as system design

Clear states — Pending, Published, Rejected, Draft — turn the workflow into a system. Without explicit status, everything becomes Slack messages and manual memory. I designed status transitions to be deliberate and auditable: every listing has a clear position in the pipeline, every action is recorded, and nothing falls through the cracks. This is infrastructure, not UI decoration.

Media as first-class workflow

Media is where listing systems usually fall apart, so I treated it as a first-class workflow. Multi-photo handling with ordering support ensures the cover image and gallery make sense. Admins can update listing media without reopening the entire submission. The system handles the most common failure points — wrong sizes, broken links, poor sequencing — so the team spends time reviewing content, not reformatting images.

System architecture

SellYourBoat is built as a structured publish pipeline: guided intake → validation/normalisation → admin QA and status transitions → publish-ready output. The architecture separates submission UX, listing data, and review operations so the brokerage team can move fast without sacrificing quality — and so the system can scale to higher volume without turning into inbox chaos.

Actors
Listing Wizard — Structured Intake
Self-Correct + Submit
Admin Review Pipeline
Publishing + Media
Data Layer
SellerOwner / Broker
AdminYBA Team
ReviewerToken Link / QA
CategoryBoat Type Selection
DetailsBrand · Model · Year
FeaturesSpecs · Equipment
LocationCountry · Marina
PhotosUpload · Order
DescriptionCopy · Price
Seller InfoContact · Provenance
Review
ListingSelf-Correct Before Submit
Submit→ Pending Review
Admin
DashboardPending · Published · Rejected
Listing
DetailFields · Gaps · Media
ActionsPublish · Reject · Draft
Review
LinkToken-Based QA
WordPress
PublishSync to Live Site
Media
PipelineBlob Upload · Ordering
Email
NotifyStatus Updates
HTML
ExportListing Embed
Prisma / DBListings · Reviews · Status
Blob StorePhotos · Assets
Wizard flow
Admin pipeline
Data flow
QA feedback

Review links

A lightweight but high-leverage feature: token-based review links that let stakeholders verify a listing without needing admin access. Internal QA before publishing, seller confirmation of details, partner or broker sanity-checks — all handled through a shareable link. It's a small surface area that materially reduces publishing mistakes and removes the team as a bottleneck for verification.

Taxonomy as the real product

The most important design work isn't visible. Standardised categories, consistent specs fields, normalised pricing formats, structured location data — this is what makes the listing engine scale. Without it, every listing requires manual reformatting. With it, the system can support batch processing, automated QA, and eventually programmatic distribution to partner platforms. The taxonomy is the product; the UI is the access layer.

Outcome

SellYourBoat shipped as a complete listing pipeline — submission to review to publish — replacing email threads and WhatsApp chains with a structured workflow. Listings arrive more complete, get reviewed faster, and publish at a consistent quality. The brokerage team can process submissions in batches with confidence. The business can scale listing volume without scaling headcount linearly. One system replacing an entire category of operational chaos.

Next project

Lead Founding Product Designer · 2024