Cruise ship refurbishment
A marine interiors manufacturer: the inspection nobody was selling
How a manufacturer that refurbishes cruise cabins turned an unpriced prerequisite into inspection tooling it owns and a capability it can name, scope and sell.
Before a cruise ship can be refurbished, somebody has to walk it. An inspector opens every cabin along every deck the refurbishment will touch, and writes down what is actually there. What is installed. What has failed. What is merely tired. That record decides the scope. The scope decides the price, and the price decides whether the job is worth winning at all. It is the most consequential hour of any refurbishment bid, and in much of this business it carries no name.
Our client refurbishes cruise cabins at scale. For years the inspection was simply part of winning the work, done well by people who had done it before. But it sat inside the bid, not beside it. Nobody quoted it. Nobody owned it. And because the work was commercially invisible, it was also the least instrumented part of a business that depends on it. Leadership already knew that most cost overruns traced back to its own planning and execution rather than to outside events. The company absorbed them.
A general tool proved the work and showed its ceiling
The first campaign ran on a general-purpose field-inspection product, bought off the shelf. That was the right call. It worked. Data came back reliable across cabin inspections, simulations, sea trials and the documentation that followed them. The client’s own team validated it alongside ours. The campaign finished under real schedule pressure, which is the only test that matters once a ship is out of service and waiting.
It also showed where a general tool stops. Licences are priced per device. Every extra person on board adds to the bill. The interface rate-limits its own data. Everyone downstream sees the campaign late rather than live, which is awkward when the schedule is the thing being managed. Its reporting answers the questions a field-inspection vendor imagined, which are not the questions a program owner asks. And the shipowner, who must choose what gets repaired within a fixed budget, could not make that choice from it at all. That gap is the commercial one.
A second lesson had nothing to do with software. Trained inspectors drifted into their own methods aboard, which made progress hard to read while the work was running. Problems surfaced late. Systematic execution matters more than individual speed, and that is a management finding rather than a technical one.
So the question changed. It was no longer which product to buy next, but which part of this the company should own.
The reporting layer grew into the product
Elexive built an analytics and reporting layer on top of the capture tool. It keeps its own database, pulling from the vendor on an interval, which is how you live with a rate limit instead of arguing with it. Out came the view the general product could never produce. Progress over time, defect rates as they moved, deck-level heatmaps, velocity, and which inspector had worked which cabin. Leadership saw the demonstration. The conclusion drew itself. A layer that reports on a tool can, given time, replace the tool.
This is the step most companies skip. A general product is bought precisely to avoid building anything, and the purchase is then treated as a settled question. Yet the layer above it is where a company’s own operating knowledge collects, cheap to build once data is moving. It is also the only part of the arrangement that can become theirs. Everything below it is rented.
The layer kept growing. It is now a backend and a progressive web app. Live operations dashboards run on it. So do per-deck and per-cabin views, an analytics surface, and inspection planning with route-optimized schedules measured against what actually happened. Supervisors get team views. Anyone with a question can ask the inspection data in plain language, rather than request a report and wait for it. One backend serves several campaigns, so each new vessel starts from the shape the last one left behind.
The pre-inspection became something you can sell
The commercial consequence is easy to lose inside the tooling, so it is worth stating plainly. Pre-inspection was not a product before this. It was a prerequisite. Absorbed into a refurbishment bid, defended internally as overhead, and never once named on anybody’s price list. It now has its own tooling, its own data and its own output, which is what a product needs. It can be scoped, quoted and sold. What is still missing is unit pricing behind each defect, so the shipowner can weigh cost against scope directly. Then the choice is theirs.
The licence dependency has a path to zero alongside it, and the route is drawn. Capture moves in-house next, onto a field app of the company’s own. The general-purpose product then stands down to a cold backup for one campaign, and retires. None of that has happened yet. It was never the point anyway. It is what follows when a company owns the layer where its knowledge sits. The saving is a by-product.
Refurbishment margin is settled long before any material is ordered, in the hour an inspector spends in a cabin. Nobody ever decided that hour was overhead; it simply became one, and that is how habits survive in a business. Own the data it produces, structure it, and make it readable by the customer paying for the outcome. The hour stops being a cost of bidding. It starts being something worth buying. That reframing is open to any company whose most valuable work sits buried inside somebody else’s purchase order.
Outcomes
An unpriced prerequisite reframed as a capability the company can name, scope and put in front of a customer
Inspection reporting the general-purpose tool could not produce: progress over time, defect rates, deck-level heatmaps and velocity
A cleaner basis for the shipowner to choose scope, in place of an interface built for inspectors
A path to zero on per-device licensing, with capture moving in-house and the third-party product stepping back to backup
Bring us your first problem
Each case here began the same way: someone brought us a concern worth taking seriously. Yours starts the same way.