What Should the Broker See First on a Phone?
27 June 2026Keep Your Marketplace and Your Own Website in Step
8 July 2026
No. A yacht business can have specialised work and still use an existing CRM effectively. The decision depends on the relationships and tasks that the system must support, the tools already in place and the team’s ability to maintain the result.
At Bilişim Atölyesi we build custom software. That makes it especially useful to be clear about where custom work earns its place. Recreating a contact list is a different proposition from connecting yacht inventory, buyer shortlists and approved client documents.
Three routes worth discussing
| Route | When it deserves investigation | What still needs checking |
|---|---|---|
| Configure an existing CRM | The main work is contact management, tasks and a conventional pipeline. | Can it represent multiple yacht enquiries per buyer and the required access rules? |
| Add a focused custom component | One recurring gap concerns PDFs, listing outputs or a specific handover. | Can it use approved records without creating another conflicting data source? |
| Build a broader custom system | The core relationships and workflows do not fit the available configuration. | Is there a clear owner, migration plan and maintenance arrangement? |
This is a project decision framework, not a product ranking. A team may combine the routes. For example, an existing CRM could remain the relationship system while a custom document component uses approved listing data. Whether that connection is practical depends on the actual systems and access available.
Demonstrate the difficult conversation
Choose a buyer who discusses several yachts, changes the shortlist and requests a tailored selection. Use an invented record or a suitably handled example. Ask the software supplier to demonstrate the entire sequence, including the handover to another broker. A contact screen and an impressive dashboard are not enough to show how those relationships behave.
Next, correct a specification. Show what happens to the website and to the next generated PDF. Finally, mark one yacht unavailable. The buyer relationship should remain understandable even though that particular opportunity has changed.
These exercises reveal whether the problem is missing functionality, a configuration choice or an unclear working rule. Custom code cannot resolve a disagreement about who approves a listing unless the business first defines the responsibility.
Include the work after launch
Compare more than the initial build. Somebody needs to manage access, review changes, support the team and keep connections working when another provider changes its service. Existing products and custom systems both have operational dependencies, although the responsibilities differ.
Ask who can export the relevant records and how the business would move to another arrangement later. Review the practical handover: data definitions, document templates, access administration and the process for reporting a problem. Do not leave these questions until the first person who knows the system departs.
A small brief can be the right brief
If the recurring problem is an inconsistent buyer PDF, describe that problem directly. The first project might be a controlled document workflow rather than a replacement CRM. If the team cannot follow buyer relationships across its tools, a broader review may be justified.
Bring the difficult examples to a software discussion. The useful outcome is a scope that solves the demonstrated problem and can be operated by the business afterward. It does not have to be the largest system we could build.