Workflow review
We start with the captain, chief engineer, or manager to understand current maintenance routines, recurring failures, reporting needs, and who actually owns each part of the process.
Deployment guide
MYS is sold as a vessel deployment, not as an off-the-shelf subscription. Each app is configured around one yacht's systems, crew structure, and management preferences, then refined in live use.
Process
We start with the captain, chief engineer, or manager to understand current maintenance routines, recurring failures, reporting needs, and who actually owns each part of the process.
The app is structured around the yacht's systems, departments, user roles, terminology, sign-off requirements, and management preferences rather than a fixed software template.
Existing manuals, service records, parts lists, and maintenance notes are used to seed jobs, planned maintenance, inventories, and technical references with far less manual setup.
We launch with the onboard team, validate how the app is used during daily work, and adjust the workflow where crew friction appears.
After launch, MYS continues refining reports, permissions, forms, and module detail so the deployment keeps matching how the vessel is run.
Good fit
Rollout inputs
Commercial model
Typical commercial structure is an initial vessel setup and rollout, followed by optional ongoing support and iteration as the workflow matures onboard.