Aerial view of a superyacht cutting through dark open water, wake trailing behind

Guest intelligence for superyachts

Every guest.
Every detail.
Remembered.

Send the preference sheet you already have. Yotmind reads it, then remembers what actually happens aboard — and briefs every trip as if the same crew had been there for years. No new form. No guest account. Nothing for anyone to fill in.

From the team behind Yotspot — sixteen years, 180,000+ yachting professionals

Cited, never invented

Every line points at the note it came from — or it is not shown at all.

Stays with the yacht

Crew rotate; the memory does not go down the passerelle. And it is yours to export, always.

Access ends the same day

Off the yacht, off the data — on every device, that afternoon.

The problem

The sheet exists.
The memory doesn't.

01

Crew rotate

A chief stewardess leaves every six to ten weeks of rotation — and ten charters of guest knowledge walk off the passerelle inside her phone. The industry has a name for it: the passerelle leak.

02

Knowledge scatters

Preferences live in broker PDFs, group chats, notebooks and heads. The stew knows what the guest told the chef only if someone remembers to say.

03

Details slip

A missed allergy is a medical event. A forgotten anniversary is a lost rebooking. At £150,000 a week, "we forgot" is the most expensive sentence aboard.

Every trip starts with a preference sheet. Almost none of it survives to the next one.

How it thinks

Three kinds of knowing.

Most systems store a value. Yotmind keeps the difference between what a guest said, what the crew saw, and what follows from both — because that difference is the whole of the judgement.

Declared

What the guest tells you

“Cabin at 21°, please.”

Arrives on the preference sheet, from the broker, the owner’s office or the guest. Imported, never retyped. The source is recorded with it.

Observed

What the crew actually see

“Turned it down to 18° every night, three trips running.”

Captured by voice or note during service, attributed to the person who saw it and the trip it happened on. This is the part no preference sheet has ever held.

Inferred

What follows from both

“Recent evidence suggests 18° overnight.”

Always shown as a reading of the evidence, never as a fact, and never written over what was declared. Yotmind tells the crew what it has seen. The crew decide what to do.

Provenance

And how it knows

Who · when · which trip · how sure

Every line carries its source, its date and its confidence, and disagreements are kept rather than resolved away. Nothing is deleted to make the record tidy.

One fact, three trips · nobody retyped anything

Aug 2025 Declared

“Cabin at 21°, please.”

Arrived on the broker’s preference sheet. Imported, never retyped, and the source recorded with it.

Aug 2025 – Jun 2026 Observed

Turned down to 18°, every night.

Fifteen nights across two trips, each one signed — S. Dubois, 2nd stew. The declared 21° is left exactly as it was.

Jun 2026 Inferred

Evidence suggests 18° overnight.

Shown as a reading of the evidence, never as a fact — and never written over what the guest said. The crew decide what to do with it.

Jun 2027 Confirmed

The new sheet says 18°.

What the yacht had seen for two seasons, the guest has now written down themselves. Confidence becomes very high.

The yacht knew a year before the sheet did.

A declared preference and three contradicting observations is not an error. It is the most valuable thing in the file.

How it works

The sheet you already have
feeds the brain. The brain briefs the crew.

01 · Before the charter · crew

The Import

The sheet you were already sent — the broker's PDF, the owner's office email, a spreadsheet or a photograph of a page. Drop it in and Yotmind reads it, then proposes a baseline the chief stew confirms before any of it counts as declared. Nothing is retyped. Nobody is asked to fill in a form, least of all the guest. Safety records are never created from an import alone.

PDF · Word · spreadsheet · email · photograph
02 · During the charter · crew

The Brain

Crew capture moments by voice as they happen. Yotmind files each one — guest, category, confidence — and learns what actually happened: what was served, loved, left and reordered. A mis-heard note is caught at capture. A genuine collision between what was declared and what the crew saw is not — that one is shown to you, both sides intact, because it is usually the most useful thing in the file. Nothing enters memory without crew confirmation.

Surface · Midnight
03 · Every trip after · crew

The Brief

Before guests step aboard, the Pre-Arrival Brief assembles itself: critical flags, what changed since last time, key dates, the vendors that worked — and what was actually consumed last time, down to what ran short. What to order stays the chief stew’s call. The next crew inherits everything.

Regenerates live · reviewed by the chief stew

On the yacht

Two questions. One memory.

The whole product sits behind a pair of mirrored sentences. Capture asks “What would you like me to know?” Ask asks “What would you like to know?” Nothing lives more than two taps deep, and the mic never moves.

YotmindM/Y Aurora · 06:58

Good morning,
Chief Stew.

The Pantry Note · fresh edition 4 items for today — safety pinned first, anniversary tonight

What would you like me to know?

Say it · type it · snap it

What would you like to know?

Every answer has a source

Pantry Note

Brief me

Remember

Ask

M/Y Aurora

Hold to speak · never listening

01 · The front door

Two doors, one memory. The crew never choose a module — they either have something to tell the yacht, or something to ask it.

AskRetrieval only

What was Mrs C’s favourite anchorage here last year?

Answered in 1.4s · from 214 memories

Cala di Volpe, the north side — out of the swell. She asked to stay a second night.

Heard · Aug 2025 · S. Dubois, 2nd stew

Related — not the answer Ashore for dinner on the last night
Imported · 2024 sheet · may be stale

Pantry Note

Brief me

Remember

Ask

M/Y Aurora

Hold to speak · never listening

02 · The answer

The answer is the memory, quoted, with who heard it and when sitting underneath. Ask finds and orders; it never rewrites.

AskRetrieval only

What do the children eat for breakfast?

Searched 214 memories in 1.2s

Nothing captured on this yet.

Nothing in 214 memories mentions the children at breakfast — and the yacht won’t guess.

0 guesses · ever
Capture it tonight Ask at turndown, then hold the mic — say it once, and it is there every season after.

Pantry Note

Brief me

Remember

Ask

M/Y Aurora

Hold to speak · never listening

03 · The honest blank

“I don’t know” is a feature. One invented answer would cost the yacht everything; a hundred honest blanks build a memory worth having.

Every gap one crew fills is a gap the next crew never has.

Returning guests

The second time is the point.

Charter or private, it is the same pattern — the family that comes every August, the owner’s regular guests, the charter party on their fourth booking. A new preference sheet arrives, and most systems overwrite what they had. Yotmind treats it as new evidence, not a replacement record, and reconciles it against everything the yacht already knows.

Unchanged

The new sheet agrees with what the yacht held. Confidence rises; nobody’s attention is spent.

Changed

A preference has explicitly moved. Both values are kept, with their dates — vegetarian to pescatarian is itself worth knowing.

Confirmed

Something the crew noticed last time, now written down by the guest themselves. This is the product proving itself.

Conflicting

The sheet and the record disagree. Both are shown, intact. What was declared is never quietly overwritten by what was seen.

Omitted

Something important last time isn’t mentioned now. Absence is not cancellation — it is kept and raised, never deleted.

Stale

Old enough, or far enough from its context, that it is offered with less confidence rather than dropped.

Safety check

A safety record missing from the new sheet is never treated as resolved. It stands, and asks to be confirmed before provisioning or service.

Welcome back, the Wilsons

Last aboard August 2026 · new sheet arrived 14 June 2027
Reconciled against 3 trips and 61 crew notes

  • 42preferences unchanged
  • 7changed since last time
  • 3the crew had already noticed — now confirmed
  • 5important last time, not mentioned this time
  • 2worth a look before you provision
  • 1safety item to confirm — recorded 2026, absent now
None of that is on the new preference sheet. All of it is in the brief.

A preference sheet tells you about this trip. Yotmind remembers every one.

Why it's different

It remembers.
It stays out of sight.

Everything else in this industry is a form, a generator, or a chatbot. A form stores what you type. A generator drafts and forgets. A chatbot talks to guests who are paying for humans to know them. Yotmind is none of these — and three rules keep it that way.

Invisible to guests

Guests experience the result: crew who simply know. The technology never sits at the dinner table.

The crew stays in command

Every memory arrives signed — who heard it, their role, when. The chief stew signs off before anything safety-critical serves. She is the authority; the instrument is the servant.

Red is sacred

One colour exists in the system for life-safety alone. When something is red aboard, it is an allergy, a medical fact, a rule that cannot flex.

Critical conflict detected

This request clashes with a life-safety rule.

Standing rule · criticalShellfish — Mrs S., anaphylactic. Never on menu, never trace exposure.
"Mr S. loved the langoustines ashore — wants them aboard on Thursday"
Both sides, intact · from vendor memoryThe rule stands and the request stands. Yotmind puts them side by side and adds what it knows — the restaurant they loved last August does langoustines, ashore. What happens on Thursday is the chief stew’s call.

Trust, by architecture

Who holds what.

The first question every owner asks, answered before they ask it.

And about us. Yotmind staff have no routine access to guest content — that is enforced technically, not promised in a policy. Support access requires named, time-limited elevation with a reason, and it is written to an audit log the yacht can read. Your data is encrypted in transit and at rest inside a boundary of your own, and nothing is ever used to train anything.

The guest's · theirs to correct

What was declared

Preferences arrive the way they always have — on a sheet from the broker, the owner's office or the guest — and Yotmind records where each one came from. It belongs to the guest: viewable, correctable and erasable. We do not ask them to fill in anything of ours.

The vessel's · stays with the yacht

What the crew observed

Service memory is the vessel's own. It is never pooled with another yacht and never sold. Access is by role and every look is audited. Crew who leave lose access the same day — and the yacht keeps the knowledge. It is also yours to export, at any time, including the day you stop subscribing.

White label

The guest sees your yacht.
Never our software.

Guests see the yacht — or the management house — never the software. Each vessel mounts its own crest and colour on the guest-facing surfaces; the instrument beneath never changes. Yotmind signs only the privacy line, where a neutral trust mark matters.

AAurora

M/Y · 52M · Steel colours

SSerene

S/Y · 68M · Sage colours

HHalcyon

Management · Fleet colours

Built for

The people who carry the standard.

Chief stewardesses

Never start from zero

Walk onto a new programme and inherit years of guest knowledge on day one. Your own observations stay yours to confirm, refine and hand over properly.

Private yachts

Your own standard, kept

The owner’s family, the friends who come every August, the guests who matter most — remembered properly, whoever is aboard this season. No charter and no broker: often there is no preference sheet at all, because everyone is assumed to know.

Charter programmes

The standard survives turnover

Service stops depending on who happens to be aboard. Guests return to a yacht that remembers them — and rebook because of it.

Management companies

Fleet-wide, in your name

Every vessel in your fleet runs the same discipline under your own name. No preference lost when crew rotate between your yachts.

Owners’ offices

Asked once, not every season

The PA, house manager or family office holds what the family actually likes — and gets asked for it again every time the interior turns over. Send it once; the yacht keeps it.

Charter brokers

Your client, credited to you

Preference profiles are introduced through the broker, never around you. The client relationship stays yours — and the yacht remembers your client from one booking to the next, so the rebooking lands with you.

Questions, answered

What people ask us.

What is guest intelligence for superyachts?

Guest intelligence is the practice of combining what guests declare on preference sheets, what crews observe during service, and what actually happened on previous trips into one persistent memory — then using it to brief the crew before every arrival. It is how a yacht remembers a returning guest the way a great chief stewardess would, even after crew have rotated.

How is Yotmind different from a digital guest preference sheet?

A preference sheet records what guests say they like, once, before arrival. Yotmind treats the sheet as the starting point: crews add observations by voice during service, the system reconciles contradictions, learns from what was actually consumed, and generates role-aware pre-arrival briefs that show what happened rather than telling the crew what to do. The sheet is a form; Yotmind is a memory.

Who is Yotmind for?

Chief stewardesses and interior crews use it daily; captains, chefs and deck teams get role-specific briefs; owners and management companies buy it so the standard of service survives crew changes. It serves both private and charter programmes.

Does Yotmind work on a private yacht, or only on charter?

Both, and the private case is often the stronger one. A charter yacht gets a fresh preference sheet from a broker; a private yacht frequently gets nothing at all, because everybody aboard is assumed to already know. That assumption is exactly what breaks when the chief stewardess rotates off. On a private programme the owner’s office, PA or house manager sends whatever already exists — a document, an email, a spreadsheet — and the crew build from there. Owner trips are treated as trips like any other, so the family that comes aboard every August accumulates a memory in exactly the way a returning charter party does.

What happens to guest data?

Two kinds of memory, two owners. What guests declare belongs to the guest — viewable, correctable and erasable. What the crew observes is the vessel’s own service record: never pooled with another yacht, never sold, and never used to train anything. It runs in our cloud, inside an encrypted boundary of your own, with role-based and audited access and no routine access by Yotmind staff. It is also yours to export whenever you want it — including if you stop subscribing. Crew who leave lose access the same day; the yacht keeps the knowledge.

How does Yotmind handle safety-critical information like allergies?

With more care than anything else in the system. Allergy and medical records are never created from a voice note alone — a crew member always reviews and confirms them, they are flagged as always-enforced, they surface at the top of every brief, and they are never edited silently: every change is attributed, audited, and re-confirmed. The crew remains the authority; Yotmind is the discipline that makes sure nothing is missed.

What stops the memory being filled with wrong information?

Nothing enters anonymously. Every memory is signed — who recorded it, their role, when, and during whose stay — and the chief stewardess confirms new entries from a daily sign-off queue. Ordinary preferences serve straight away but are visibly marked unconfirmed until she signs them; anything safety-critical is held and never serves until confirmed. And because the ledger shows everything raw, a wrong note is corrected or forgotten in a tap — it dies in review, never in front of a guest.

Does it work at sea without connectivity?

Yes — the brief you need is on the device before you need it. Yotmind keeps an encrypted copy of the current trip on the crew’s phones and tablets, so pre-arrival briefs and guest detail stay readable with no signal at all, and observations captured offline queue up and sync the moment connectivity returns, keeping the time they were actually taken. The authoritative record lives in our cloud rather than on a box aboard — which is what lets a yacht be running the same afternoon it signs up, with no hardware, no installation and no engineer on the passerelle.

When does Yotmind launch?

Yotmind goes aboard its first yachts for the 2027 season — a small founding group working with us from day one. Join the waitlist below and you'll hear from us first.

Nothing is ever missed.

Yotmind goes aboard its first yachts for the 2027 season — a small founding group, working with us from day one. Join the waitlist and you'll hear from us first.

No spam, no sharing — just first word on Yotmind. Unsubscribe any time.

From the team behind Yotspot · Sixteen years · 180,000+ yachting professionals