Most companies tell you what they do. We have already done that. This story is the opposite. It is the list of things we will not do – the requests we have turned down, the contracts we have walked away from, and the categories of work that we have decided, deliberately, are not Verne’s job.
We publish this list because the shipyards that are right for us will read it and recognise themselves in our refusals. The shipyards that are wrong for us will read it and know early. Both outcomes are good for everyone involved.
Verne builds the brain of the yacht and the experience the owner touches. We do not manufacture lights. We do not manufacture sensors. We do not manufacture speakers, screens, hatches, locks, or thermostats. The market is full of excellent partners who do this work better than we ever will, and we have spent years curating relationships with them.
The temptation to vertically integrate downward – to put our logo on a light fixture and earn a margin on every fitting – is real. We refuse it. The moment we become a hardware vendor selling components, we stop being an honest broker about which components belong on your boat. Our value is that we will tell you to use someone else’s lighting when someone else’s lighting is the right answer. That value disappears the day we start selling our own.
We are the brain. Everything below the brain, we integrate. That is the discipline.
There is real money in crew-facing operational software. Captains, engineers, fleet managers, charter operators – there is an entire category of yachting software built for them, and it is largely good software. We will not build it.
Verne is for the owner. Every product decision we make is filtered through that one constraint. The captain and the engineer get the interfaces they need to do their jobs – we are not careless about that – but the centre of gravity of our product is the human who paid for the boat. The moment we start designing for crew operations as a primary use case, we become a different company. We have watched too many platforms try to serve both audiences and end up serving neither well.
If you are a shipyard whose primary problem is fleet operations, you should not work with us. There are better companies for that problem. We will introduce you.
Every platform in this category eventually gets the same question: what happens if we want to leave?
Most platforms answer that question with friction. Proprietary protocols. Encrypted firmware. Source code held in escrow with conditions designed to never be triggered. Support contracts that auto-renew until the heat death of the universe.
We refuse all of it. At handover, the shipyard receives the full source code, the full schematics, the full operational documentation, and a license to operate, maintain, and extend the platform independently. Your in-house team can fork it. Another vendor can service it. You can leave us tomorrow and the system will keep running.
We do this because we have been on the other side of vendor lock-in, in other industries, and we know what it does to the operators who are trapped by it. It corrodes the relationship. It makes every renewal conversation adversarial. It rewards the platform for being mediocre because the cost of leaving is higher than the cost of staying.
Our model is the opposite. Staying with Verne should be a choice you re-make every year because we are good – not because leaving us would cost you eighteen months and a class-society re-certification.
This is the most counterintuitive refusal on the list, so it deserves an explanation.
Verne is brand-invisible to the owner. The app on the owner’s phone carries the shipyard’s name and design language, not ours, and we are proud of that. But Verne is not anonymous to the shipyard. Every shipyard we work with knows exactly who we are, what we do, who is on our team, and what is in the system they are deploying. We will not enter relationships where Verne is reduced to a sub-supplier hidden three layers down a contract chain, with no direct line to the shipyard founder and no engagement with the actual product decisions.
We have turned this work down. It pays well. It also produces bad work. Brand-invisibility to the owner is a design principle. Brand-invisibility to the shipyard is a route to mediocrity.
If we are building your platform, we want to be in the room when the decisions get made.
This is the deepest refusal, and the one that filters the most aggressively.
Some shipyards see the digital experience as something to be tolerated – a checkbox forced by the market, a cost line to be minimised, a problem for the IT subcontractor to handle two months before launch. We do not work with those shipyards. Not because they are bad shipyards. Often they are excellent at the parts of the work they believe in. But the kind of work Verne does requires a partner who understands that in 2026, the digital experience layer is part of the yacht, not a feature attached to it.
The shipyards who are right for us are the ones whose founders read the manifesto and felt it. The ones who already suspected the industry had got the order wrong. The ones who want to build hulls that, twenty years from now, are remembered as the first generation to fix this.
That self-selection is not a marketing convenience. It is the entire basis of how we choose who to work with.
Everything we refuse exists to protect what we do.
We build mission-critical control architecture and owner experience platforms for shipyards who want to ship the best digital experience the yachting industry has ever produced. We do that work seriously, embedded, with full IP transfer, brand-invisible to the owner, for partners who believe – as we do – that the owner experience is part of the yacht.
That is the only work we want to do.
That is the only work we are going to do.
If you refuse to sell hardware below the controller, how do you make money on a project?
The refusal to white-label feels restrictive. What if our procurement structure requires it?
How often do you actually turn shipyards down?
