Feature scope - proposed scope
White Label Yacht Marketplace Features: Built Around the Lead
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
What Each Person Gets
Six working surfaces, all running on one API and one PostgreSQL database that you would hold.
The Buyer
- Search by keyword, then narrow with ranges for price, year, length, beam, draft and engine hours, or by country, state and a map radius. Favorites and side-by-side compare sit beside named saved searches that email new matches daily or weekly once your SMTP account is connected. Prices display in six currencies and the interface in five languages.
The Private Owner
- Owners describe the vessel, their contact details and the price they hope for in a structured sell form instead of a free-text message, and get a dashboard of their own. The listing that results carries ordered, captioned photos, a video tour link that plays inside the gallery, share links and a printable specification sheet.
The Broker
- A listing manager with photo and upgrade control, and a kanban board where each enquiry carries a status, a stage and private notes. Replies stay in a thread scoped to that enquiry, and the time to a broker's first answer is stored and reported, so a slow desk shows up on the dashboard.
The Brokerage
- A directory and profile page with branding, bio, contacts, regions served, specializations and languages, plus ratings, review counts and a verified badge. Behind it sit client records holding email, phone, budget, status and private notes, with vessels shortlisted against each client. Middleware ties every broker route to a brokerage.
The Service Desks
- Eight adjacent modules, each with a public intake form and an operator desk: sell leads, charter, insurance, transport, finance, surveyors, valuations and boat shows. Requests arrive as structured records with a status workflow. The modules route enquiries and do nothing more, a boundary spelled out further down this page.
The Operator
- Users and brokerages, listing moderation, plans with an activate switch and subscriber counts, taxonomy, platform settings, articles and FAQs, tickets and disputes, and the eight desks, all in one console that a non-engineer can run day to day.
One Lead, From First Search to Sold
A single buyer and a single vessel, followed through every screen they touch.
Narrow the stock, save the search
- The buyer sets length, draft, price and a map radius in a single query, then saves it under a name with a daily or weekly alert. Make, type and place counts come from separate facet endpoints, so changing one filter does not recount the whole result set.
- Favorites and a compare view work the same on web and mobile. Each listing keeps a price history that only ever appends, and a price-drop badge and search toggle bring reductions forward, because a cut on a high-value boat is what pushes a long decision along.
Send the enquiry, answer the questions
- Capture is rate limited and records the subject, message, source and intent, plus contact details for guests. The buyer can then complete a LeadSmart questionnaire, and each brokerage sets its own intent threshold for what counts as a hot lead.
Stage it and reply in the thread
- The lead lands on the broker's board. Every message in its thread shows sender, role, name and time, and a live server-sent stream pushes new activity with a thirty-second heartbeat. Web Push joins in once you supply VAPID keys.
Under offer, then sold
- A listing moves from active to under offer to sold, and a sold price and date are recorded. Those sales become the comparables behind market evaluation and the public market reports.
The requests that follow the sale
- A sale brings insurance, transport, finance, survey and valuation demand with it. Each of those requests goes through its own form, reference code where built, and desk, so the demand is recorded even though the work behind it belongs to your partners.
- Web and mobile talk to one API, so an enquiry typed on a phone shows up on the broker board with no second integration.
Why Each Module Is in the Base Build
Each row answers a problem a brokerage runs into within its first season, not a checklist item borrowed from a rival.
Each of these can be switched on, switched off or renamed for your deployment through plans, settings and taxonomy, which is what lets one build serve a single-brand portal or a multi-broker marketplace.
The Technology Under the Features
What the code is written in, and what that means for the engineers who take it over.
Every integration point, whether payments, SMTP, VAPID, exchange rates or object storage, is a documented seam and not a wired-in vendor, so your team can swap one without touching the rest.
Boundaries we state in writing for your build
Set out before a purchase, so nothing turns up on the invoice.
Live payment processing
- Plan selection, billing-cycle records, checkout and cancellation are built, but the invoice history is a generated six-row mock. Connecting a provider such as Stripe or Adyen is a standard configuration step that we quote with your deployment. It is not live in an initial scope.
Some console controls are for show
- Only the platform settings are confirmed to save and reload. A few admin controls are decorative, and the six-month subscription trend is a modelled monthly-equivalent series rather than settled cash. The security handbook lists each one.
Live updates run on one node
- Server-sent events are process-local, and rate limiting is in-process at launch. A second instance needs shared pub/sub and a shared rate-limit store first, and the written scale path says so.
What exists is real
- The developer and security handbook maps each control to the file that implements it and marks it as built or as pre-launch hardening. The named release gates are listed on the Provider page, and no certification is claimed anywhere.
Weighing a rental, a script, an agency and us?
- The Provider page sets the four routes side by side, lists the nine questions worth asking any seller, walks through the six-step delivery, and shows a modelled marine services deployment.
A brokerage platform, not a boat grid
Listings deep enough for the asset, search by range and radius, leads that keep their history as they change hands, broker client files and eight service desks, with the source on infrastructure you control.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by YachtWorld , or any other yacht, boat or marine listing service.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com