Engagement scope - proposed scope
YachtWorld Clone Development Company: What to Check Before You Hire
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
What happens to an inquiry after it arrives?
- If the answer is a notification email, there is no lead lifecycle. Ask to see status, stage, private notes, a reply field and a response timestamp on the same record.
How many specification fields does a listing carry?
- Draft, beam, displacement, engine hours, hull material, keel and rig are not optional extras on a vessel. A schema that treats them as custom fields will not filter on them properly.
Can search combine a numeric range with a radius?
- Ask them to filter length and engine hours while also limiting to 200 miles of a port. That single query shape is what decides whether the marketplace feels fast at two hundred thousand listings.
Is response time measured?
- When the same vessel sits on four portals, replying first with context is the whole differentiator. Ask whether it is a number on a dashboard or something a manager has to guess at.
How are dealer routes enforced?
- In a multi-office group, one dealer must not read another's clients. Ask whether that is middleware on the server or a filter in the interface, because only one of those is a control.
Which admin controls actually persist?
- Half-built consoles are the norm in this category. Ask them to change a setting, reload, and show you it stuck. Ours is honest about this and the answer is below.
Is payment processing live or mocked?
- Plans and checkout flows can exist without a provider behind them. Ask directly which part is implemented and which part is configuration, and get it in writing.
What is the realtime guarantee?
- "Realtime messaging" covers everything from a durable queue to an in-process event map. Ask what happens to delivery when you run a second instance.
What is on the pre-launch hardening list?
- Any provider whose list is empty either has not looked or is not telling you. Ours runs to six named gates and sits further down this page.
A proposed launch process, without time promises
Define the first service area
- Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.
Apply your branding
- Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.
Set the commercial rules
- Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.
Connect your own accounts
- Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
Red Flags That Mean Walk Away
Five answers that should end the conversation
- "Inquiries go straight to the broker's email." Then there is no pipeline, no response measurement and no record of what was offered instead. On a handful of high-value leads a month, that is the entire commercial risk of the platform.
- "We can add the extra vessel fields later." Specification fields drive the range filters. Retrofitting them means re-indexing, re-entering inventory and rebuilding search, which costs more than designing them in did.
- "Realtime messaging is fully scalable." Ask what happens on a second instance. If the answer is vague, delivery is in-process and they have not thought about it. Ours is in-process too, and we say so.
- "The admin panel is complete." Almost none are. Ask them to change a setting and reload. A provider who has audited their own console will tell you which controls persist without being asked twice.
What a Marine Marketplace Has to Get Right
The parts that are unglamorous, mandatory and slow to build properly.
What We Have Not Done Yet
Six items, stated before a purchase rather than after one.
Six named release gates
- The handbook publishes them rather than waiting for a tester: eliminating the fallback JWT secret, completing object-level ownership checks on every identifier-bearing route, encrypting TOTP secrets, hashing reset tokens, private scanned uploads, and a full privacy review across all forty tables. We would rather hand you that list.
Live card processing is configuration
- Plan selection, billing-cycle records, checkout and cancellation are implemented, and invoice history is a generated six-entry mock. Connecting Stripe, Adyen or a regional provider is a standard configuration step quoted with your deployment, but it is not live in an initial scope and we will not imply that it is.
Parts of the console 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 handbook names each one individually.
What is built is real
- The service modules facilitate leads. They do not bind insurance, approve credit, guarantee transport or certify surveys, and no certification or vulnerability-free claim is made anywhere in the documentation.
Modelled Reference Deployment
Brokerage Marketplace and Dealer Network
- How this platform is configured for a brokerage group whose leads currently arrive by email and WhatsApp, and where inventory, inquiry pipeline, broker CRM and adjacent marine services need to sit in one system rather than five.
- What the situation makes hard: leads arriving by email and WhatsApp, then getting lost, duplicated or left unanswered; no single view of inventory, clients or broker performance across offices; and adjacent services like insurance, transport and finance captured on paper with no queue behind them.
- What the configuration addresses: one system holding listings, inquiry pipeline, messaging and broker CRM together; response-time measurement that makes broker accountability visible rather than assumed; and eight marine service modules turning adjacent demand into a second revenue line.
- Named client deployments are published separately. See the Omnistu portfolio for real engagements with their own reported figures, and hold this page to what it says it is.
More pages on this build
Five pages describing this proposed build. You are on Development Company.
Hire on the answers, not the deck
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by YachtWorld .
YachtWorld Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to YachtWorld, and how clients search for it.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com