Feature scope - proposed scope
YachtWorld Clone Features: The Listing Is Not the Asset
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
Feature Set by Role
Six working surfaces on one Express API and one PostgreSQL schema.
The Buyer
- Keyword search across text, make and model, then range filters on price, year, length, beam, draft and engine hours, plus country, state and geospatial radius. Favourites, side-by-side compare, saved searches with named criteria, and daily or weekly alert emails when new matches land. Six display currencies and five UI locales.
The Private Seller
- A sell-lead intake capturing the vessel, contact details and price expectation as structured fields rather than a contact-form message. Listing create, update and delete, ordered photo management with captions and a primary flag, a video tour URL that plays inside the gallery, and a printable specification sheet.
The Broker
- A listing manager with photo and upgrade control, a kanban inquiry pipeline carrying status, stage and private notes, inquiry-scoped messaging with conversation summaries, and a response-time endpoint that turns first-reply speed from a habit into a number on the dashboard.
The Dealership
- A dealer directory and detail page with slug, branding, bio, contacts, geography, specializations and languages. A CRM holding clients with email, phone, budget, status and private notes, curated listing shortlists attached per client, and dealer-association middleware gating every dealer route so leads reach the right desk.
The Service Desk
- Eight adjacent marine modules with their own intake forms, reference codes and operator queues: sell leads, charter, insurance, transport, finance, surveyors, valuations and boat shows. Each captures structured intent and carries a status workflow rather than landing in a shared mailbox.
The Operator
- User and dealer administration, listing moderation, plan CRUD with an activate toggle and subscriber counts, taxonomy control over boat types, categories, conditions and features, platform settings, articles and FAQs, support tickets and disputes with assignment and resolution, and all eight service queues in one console.
How It Works, End to End
One buyer, one vessel, from first search to under offer.
Search and shortlist
- The buyer filters on the criteria that actually matter for a vessel, saves a search with named JSON criteria, and sets an alert to daily or weekly. Distinct facet APIs for make, type and location serve the filter UI, so refining a filter does not force a full result recount.
- Favourites and a side-by-side compare view on web and mobile, and on each listing an append-only price-history trail with price-drop badges. A price-drop-only toggle in search exists because on a seven-figure asset a reduction is the single strongest buying signal there is.
Inquire, and get qualified
- The inquiry is rate-limited, captures guest contact context, and carries a subject, message, source and intent. The buyer then answers the LeadSmart questionnaire, which is scored against a dealer-configurable intent threshold, so what arrives at the desk is a qualified lead rather than a name.
Stage it and answer it
- The lead lands on the broker kanban with status, stage and private notes. Replies happen in inquiry-scoped threads with sender identity, role, name and timestamp on every message, and a per-user server-sent event stream delivers it with a thirty-second heartbeat.
Curate the alternatives
- The broker attaches listings to the client record with their own notes, which is how a good broker actually works: the vessel the buyer asked about is rarely the one they buy. The client record holds budget and status, so the shortlist is built against a number rather than a guess.
Under offer, then sold
- Listing status moves through active, under offer and sold, with a sold price and date recorded. Those become the comparables behind market evaluation and the public market reports, which is what makes the next valuation conversation evidence-based rather than anecdotal.
The services that follow
- A vessel sale drags insurance, transport, finance and survey demand behind it whether or not you capture it. Each has its own intake form, reference code and operator queue, which turns adjacent demand into a recorded lead rather than a referral you never see again.
Every Feature Earns Its Place
Each row is here because a brokerage stops working without it, not because a competitor lists it.
Everything above is white-label and can be enabled, disabled or re-labelled per deployment through plans, settings and taxonomy.
The Technology Behind the Features
What the platform is built on, and what that means for the team who inherits it.
Thirty-five route modules each own their handlers and schema, and every integration point - payments, SMTP, VAPID, exchange rates, object storage - is a documented seam rather than a hard-coded provider.
Boundaries we state in writing for your build
Named here rather than discovered after the invoice.
Live card processing
- Plan selection, billing-cycle records, checkout and cancellation are implemented, and the invoice history is a generated six-entry mock. Connecting Stripe, Adyen or another provider is a standard configuration step that we quote with your deployment, not a platform gap - but it is not live in an initial scope.
Some admin surfaces are presentation only
- Only platform-settings round-trips are confirmed persistent. A small number of decorative admin controls are presentation only, and the six-month subscription amount trend is a modelled monthly-equivalent series rather than settled cash. The security handbook names each one individually.
Realtime is process-local
- Server-sent events deliver typed inquiry and message events with a thirty-second heartbeat and disconnect cleanup. Delivery is process-local rather than a durable queue, so a second instance needs shared pub/sub before every user sees every event. Rate limiting is in-process at launch for the same reason.
The service modules facilitate only
- Insurance, transport, finance, survey and valuation intake capture structured demand and route it to a queue. They do not bind insurance, approve credit, guarantee transport or certify surveys, and the platform never claims otherwise. Partner fulfilment workflows are scoped work.
What is built is real
- The developer and security handbook maps every control to the file that implements it and marks each as implemented or as a pre-launch hardening item. The named release gates are listed on the Development Company page.
More pages on this build
Five pages describing this proposed build. You are on Features.
A brokerage platform, not a listing grid
Specification-rich listings, technical and geographic search, a lead object that survives being handed between people, a broker CRM and eight marine service queues, with the full source on infrastructure you own.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by YachtWorld .
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com