PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Engagement scope - proposed scope

Choosing a White Label Yacht Marketplace Provider: Four Routes

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

Typical scoping questions

Who owns the source and the database?

  • Ask for the repository and the buyer records by name. A right to use software is not ownership, and the difference shows up the first time you want to change how a lead is qualified.

What happens the day payments stop?

  • With a rental, the site and often the client list can go dark with the invoice. With a platform you own, you carry on with a hosting bill and little else. Get the answer in writing.

What does an enquiry turn into?

  • If the answer is a notification email, there is no lead lifecycle. Ask to see a status, a stage, private notes, a reply and a first-response timestamp on one record.

Can search join a range to a radius?

  • Ask them to filter by length and engine hours while limiting results to a stretch of coast. That one query shape decides whether the marketplace stays quick as stock grows.

What do the service modules really do?

  • Ours capture an insurance, transport, finance or survey request and queue it. They do not bind cover, approve credit, guarantee transport or certify a survey. Be wary of anyone who says theirs do.

Who answers for broker licensing and listing accuracy?

  • You do, and so does every operator. No platform supplies vessels, brokers or service partners, or checks titles. A provider that implies otherwise is selling you a liability.

Is payment processing live or mocked?

  • Plans and checkout can exist without a provider behind them. Ask which part is implemented and which is configuration, and get it in writing. Ours: built flows, a mock invoice history, and a provider hookup we quote.

What is on the pre-launch hardening list?

  • A provider whose list is empty has either not looked or is not telling you. Ours names six gates, and it sits lower on this page.

The Six-Step Delivery Process

What follows a yes, in the order it happens.

Stock, brokerages and qualification

  • The first listings go up with specifications and media, brokerage records are created, and each brokerage's LeadSmart intent threshold is set. Plan limits and taxonomy chosen carelessly are the two things you cannot quietly change once brokers sign up against them.

Run a lead end to end, then hand over

  • In front of your team, a buyer searches and enquires, the lead is staged and answered, a shortlist joins the client file, and the response-time view and service desks are opened. The repository, schema, contract and documents then transfer.

Support with a calendar

  • Day zero deserves the most attention. A finished platform with no payment account or developer identity behind it is still one that cannot take a real plan payment or reach an app store.

Red Flags That Mean Walk Away

Five claims that should end a sales call

  • "Enquiries go straight to the broker's inbox." Then no pipeline exists, nothing measures how fast anyone replies, and nothing records what was offered instead. With a handful of high-value leads a month, that is the platform's whole commercial risk.
  • "You get a licence, the code stays with us." Every change you want then becomes a favor you ask for. A marketplace you cannot alter is a rented storefront with your logo on it.
  • "Your buyer data lives on our servers." Saved searches, budgets and conversations are the asset you are building. Confirm where they sit and how you would export them before the first broker signs up.
  • "Our insurance and finance modules handle it all." A software module that captures a request cannot bind cover or approve credit, and one that claims to has crossed into regulated work that no platform vendor performs for you.

What a Yacht Marketplace Has to Get Right

The unglamorous parts that no screenshot shows, and that decide whether brokers keep using it.

What We Have Not Done Yet

Six limits, given to you before the purchase and not after it.

Six named release gates

  • The handbook lists them so a tester does not have to: removing the fallback JWT secret, finishing object-level ownership checks on every route that takes an identifier, encrypting TOTP secrets, hashing reset tokens, making scanned uploads private, and a full privacy review across all forty tables.

Live payments are a configuration step

  • Plan selection, billing-cycle records, checkout and cancellation are built, and invoice history is a generated six-row mock. Wiring in a provider such as Stripe or Adyen is a standard step we quote with your deployment. It is not live in an initial scope.

Some controls are decorative, updates run on one node

  • 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 series. Live updates and rate limits are process-local, and a second instance needs shared pub/sub and a shared store first.

The desks route enquiries and nothing more

  • The eight service modules do not bind cover, approve credit, guarantee transport or certify surveys. No vessels, brokers or service partners come with the platform, and broker licensing, listing accuracy and title checks are yours, along with the regulated work your partners do.

What exists is real

  • No certification or vulnerability-free claim is made anywhere. This is an original implementation, and no marine listing service is a supplier, partner or reference customer of it.

Modelled Reference Deployment

An illustration, not a client story. It shows how the platform would be configured for an operator that starts from marine services. Every figure describes the build and none reports a result.

A Marine Services Operator Adding a Listings Marketplace

  • An independent business that takes insurance, transport and finance requests from vessel owners by phone and email today, holds no stock of its own, and wants brokers and private sellers to pay to list beside those services.
  • The situation: requests scattered across inboxes with no reference code or queue, no way for brokers to list, and no record of how much service demand goes to partners unrecorded.
  • The configuration: the service desks switched on first, broker plans with listing and featured limits offered beside them, and listing upgrades sold per vessel. Referral or per-lead terms with partners are set by the operator, and the modules only route the enquiry.
  • No named marine client is quoted on this page and none is implied. We would rather label an illustration honestly than borrow credibility from a different kind of project.

Choose on the answers, not the pitch

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.

White label yacht marketplace describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com