The buyer writes in Italian,the seller in Spanish.
Yacht negotiations run over weeks, and every conversation moves in a different language on a different channel. What we built is not a translation tool: it is a visibility layer that gathers which buyer is moving on which yacht, at which price, in one place.
Sector
Yacht brokerage
Built
Multilingual listing and negotiation pipeline
Scope
Valencia and Rome
Status
Live
What the situation wasbefore the build.
The broker was moving between WhatsApp and email, noting the state of each negotiation in spreadsheets. A translation tool on its own does not remove that spreadsheet.
- Conversations about the same yacht were running in three separate languages.
- Which offer was at which stage lived in personal spreadsheets.
- Understanding the message was not the problem; visibility was.
The pieces builtfor Newsail.
- 01
The tasks were separated
Instead of one bot, the work was split: one step translates the incoming message into a shared language, one pulls the current state of the yacht being discussed, one summarises the history of the price negotiation.
- 02
Channels on one spine
WhatsApp and email joined the same flow. Whichever channel it arrives on, every message lands in the same record.
- 03
One line for the broker
The board runs in the background and gives the broker a one-line summary: which buyer, which yacht, the last offer and the next step.
- 04
Multilingual listing infrastructure
The site and listing structure were built to publish in more than one language; the same yacht record feeds every language from one source.
Negotiations moved out of scattered spreadsheetsand onto one board.
No before and after measurement was taken on this build, so we do not publish a number. What changed is qualitative and plain to see: the broker no longer moves between spreadsheets mid-negotiation.
No before and after measurement was taken on this build. The items below are not a measured result; they are the way of working that changed with it.
- Conversations running in three languages were gathered into one view.
- The stage of an offer lives in the system rather than a personal spreadsheet.
- Adding a new language does not mean rebuilding the flow.
The products usedin this build.
Request handling
Every message from WhatsApp and email joins one spine.
Agent deployment
Instead of one bot, steps with divided jobs were built: translation, status, summary.
Web and mobile development
The multilingual listing infrastructure feeds from the same yacht record.
CRM and customer management
Which buyer is moving forward with which yacht is read from one record.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
