How ScyllaStar Transformed Yacht Management with Intuitive Software and Fleet ROI

My co-founder is a professional captain with 3,000 tonnage experience. He was spending hours every week on pure administration, chasing receipts, rebuilding financial reports from scratch every month, tracking crew documents manually, remembering security drills, instead of being on the water doing what he actually became a captain for. When he showed me the scale of the problem, I immediately recognized the product gap. Coming from financial software at Murex, I had spent years building complex tools for professionals who work under pressure. I knew exactly what a well-designed financial workflow looked like, and what we were seeing in yacht management was the opposite. Spreadsheets, WhatsApp threads, disconnected tools, and a permanent feeling that something was about to fall through the cracks. No existing software understood the operational reality of running a yacht. So we decided to build it ourselves, from scratch, with a captain at the table from day one.

Flopped hard, we initially targeted individual yacht captains directly. The product fit was there, but the sales cycle was painful. Captains loved the tool but rarely had budget authority, and onboarding one captain at a time was incredibly slow and resource-intensive. We were spending weeks onboarding a single user with limited revenue upside. What worked, pivoting to yacht management companies. One management company manages multiple vessels and multiple captains, so a single deal multiplied our impact immediately. The sales conversation was completely different too, management companies immediately understood the ROI of reducing captain admin time and getting real-time financial visibility across their fleet. We also made a deliberate decision to price at a fraction of what competitors charge, roughly four times cheaper, making the decision easy for management companies to say yes without lengthy procurement processes. Word of mouth within that community then did the rest.

Honestly, our biggest fear when we started was the learning curve for captains who are less comfortable with technology. We anticipated it would be our main challenge and a significant source of early churn. So we made intuitive UX our obsession from day one, we invested heavily in design to make Scyllastar genuinely easy to use, not just functional. The result is something we are genuinely proud of, even the least tech-savvy captains are fully autonomous after a single 30-minute onboarding session. No week-long training, no support tickets, no hand-holding required. That UX investment paid off in ways we didn't fully anticipate, it dramatically reduced our onboarding costs, accelerated client adoption across the entire fleet, and became one of our strongest selling points in every sales conversation. When prospects ask "will my captains actually use it?", we can now answer with complete confidence. The complaint we feared most never materialized because we solved it before it became a real problem.

The biggest misconception about the yacht management market is that captains resist technology. We heard this constantly when we started, "captains are old school, they won't use an app." It is completely wrong. Captains don't resist technology, they resist bad tools. Tools that were clearly designed by people who have never spent a night at sea, never chased a crew member for a missing receipt, never had to generate a passenger list for port authority in ten minutes flat. When you give a captain a tool that actually fits their workflow, that works intuitively, that takes three seconds to scan a receipt, that generates a crew list in one click, they adopt it immediately and enthusiastically. The resistance disappears the moment the tool genuinely saves them time. We proved this with a 30-minute onboarding. The market was never the problem. The tools previously available in the market were.

We are focused on three clear priorities. First, deeper integration with European accounting systems, many of our management company clients use accounting software that still requires manual data export, and we want to eliminate that last manual step entirely. Second, significant improvements to our charter module, APA management, broker API integrations, and post-charter reconciliation workflows are areas where we see strong demand from clients running high-volume charter seasons. Third, expanding our commercial presence beyond France, the UK and Spain are our immediate targets, both strong markets for professional yacht management companies. We are also continuing to invest in our AI capabilities, building on our existing receipt scanning feature to bring more automation to financial categorization and reporting. The goal is simple, every hour a captain or manager spends on admin today should eventually be handled automatically by Scyllastar.

Usually, the management company working with us grows their fleet 50% within the first year without hiring a single additional person. We have 78 units under management, and we aim for double-digit growth every year.

I spent several years as a Financial Product Manager at Murex, one of the world's leading capital markets software companies, used by major banks and financial institutions globally. That experience gave me a deep understanding of how to build complex financial workflows for professionals who operate under real pressure - where errors have serious consequences and usability is never optional. I learned how to translate domain expertise into product decisions, how to work with technically demanding users, and how enterprise-grade software gets built and maintained at scale. My co-founder brought maritime domain expertise - decades at sea, 3,000-tonnage certification, and firsthand experience of every operational frustration we are now solving. The combination of financial software product experience and deep maritime knowledge turned out to be exactly the right foundation for building Scyllastar. Neither of us could have built this alone. That complementarity is our biggest structural advantage.

Our biggest mistake was building too many features too early before fully validating the core with real clients. In the early days, we had a long product roadmap and tried to execute too much simultaneously, secondary modules, nice-to-have features, edge case workflows, before the fundamentals of financial management and crew compliance were truly solid. We spread ourselves too thin and delayed getting real feedback on what actually mattered most to clients in daily operations. The lesson was hard but clear, ship the core, get it in front of real users as fast as possible, and let their actual usage tell you what to build next. Every feature we built in isolation without client input took longer and delivered less value than features we co-developed with clients using the product every day. We now build nothing without a client conversation first.