Build It Into the PMS or Buy a Dock System: The Arithmetic a GM Should Run First

For most properties the arithmetic favours buying, and what decides it is rarely the build cost. The difference shows up in years two and three, when the extension has to be maintained, retested at every PMS upgrade, and extended again the first time the dock changes. Before you ask anyone for a quote, run the same four-line calculation on both options: what it costs to get live, what it costs to keep running, what it costs in your own team's time, and what the dock is losing while you decide. This guide sets out how to build that comparison honestly, including the numbers that only appear later.

Key Takeaways

• Compare four lines on both options: cost to go live, cost to keep running, internal time, and the cost of delay.

• A build quote covers the build, rarely the maintenance that follows it.

• Every PMS upgrade means retesting whatever was bolted on, indefinitely.

• The dock changes more often than a property expects, and each change reopens the build.

• Your own team's hours are a real cost even when no invoice is raised for them.

• Configuring the PMS without custom development is a legitimate third option for a small dock.

• The revenue currently uncaptured at the dock belongs in the comparison as the cost of waiting.

• Rebuild the model with your own figures rather than trusting anyone's benchmark.

Line 1: What it costs to get live

For a bought system this line is straightforward, because it is quoted: a subscription, a one-time onboarding and migration fee, and any integration setup. You can put it in a table before you talk to anyone.

For a build it is harder, and the quote you receive is usually only part of it. Specification takes time from whoever knows how the dock actually runs, which is normally the person least able to spare it. Then there is the build itself, testing against real berth and vessel data rather than a sample, and a pilot season during which somebody has to watch it closely. Ask for the build quote, then ask separately what the property is expected to contribute in hours, because that second number rarely appears in the proposal.

Line 2: What it costs to keep running, which is where the two diverge

This is the line that decides most build-versus-buy questions, and it is the one most comparisons leave out. A bought system carries its own maintenance inside the subscription, so upgrades, fixes and new capability arrive without a project. A build is an asset the property now owns, with everything that implies.

Three costs recur. The PMS is upgraded on the vendor's schedule, and anything bolted onto it has to be retested each time, indefinitely. The dock changes, because a pontoon is reconfigured, a berth is re-sized, a tariff structure changes or metered power is added, and each change reopens the build. And the knowledge of how the extension works sits with whoever built it, so a developer leaving the agency or the group is a risk with no obvious owner. None of these appear in year one, which is exactly why a year-one comparison flatters the build.

Line 3: What it costs in your own team's hours

Internal time is real money that never reaches an invoice, so it tends to be excluded from the comparison entirely. It belongs in both columns. For a bought system it is the hours spent on data preparation, configuration decisions and training. For a build it is all of that plus specification, acceptance testing, and the ongoing role of being the person who explains to a developer why a berth is not a room.

Price those hours at whatever your property uses internally and put the figure in the table. A build that looks cheaper on the quote frequently stops looking cheaper once the GM's and the finance team's time is counted at a realistic rate.

Line 4: What the dock is losing while the decision is open

The fourth line is the one nobody asks for, and it is often the largest. While the question is open, the dock continues to run as it does now, which for most properties means berth nights that are never invoiced, power estimated at departure rather than metered, and charges that were never written down. A build that takes two seasons to deliver carries two seasons of that.

Measure it rather than assume it. Take one busy week, count the moorings, day berths and power actually delivered, and compare that with what reached an invoice. The gap, multiplied across your season, is the cost of delay, and it belongs in the comparison against both options. The detail of the power side is in the guide to metering and billing dock electricity.

A worked comparison you can rebuild with your own figures

Here is the shape of the calculation, using illustrative figures for a property with around forty moorings and metered power. On the buy side, a configured dock system carries a subscription plus a one-time onboarding fee in year one and a lower recurring figure after that, with maintenance included. Resort deployments are quoted per property rather than from a marina list price, so use the figure you are actually given rather than a published band. On the build side, a modest extension quoted at, say, twenty thousand euros arrives with an annual maintenance and regression-testing commitment that commonly runs at a meaningful fraction of the original build each year, plus the internal hours in lines one and three.

Run both across three years rather than one. In most versions of this arithmetic the build is behind by the end of year two, and the gap widens in year three because the maintenance line keeps running while the bought system's price does not change in the same way. These are illustrative figures rather than a published result, and the point is the shape rather than the amounts. Put your own build quote, your own hourly rates and your own uncaptured revenue into the same four lines, and the answer for your property will be visible.

Configuring the PMS without custom development is a legitimate third option

There is a middle route that often gets skipped. Using existing rate codes, item types and profile fields to handle a small number of day berths costs nothing and works, provided the dock is genuinely simple: no resident berth holders, no metered power, and boats of broadly similar size. For a property in that position, adding a system would be overkill and the honest recommendation is to configure what you have.

The threshold is worth naming. Once there are seasonal berth holders on contracts, metered electricity, vessels of varying length and beam, or visiting boats who are not hotel guests, the configuration starts breaking in ways that show up in front of guests. What a property management system does and does not cover at the dock is set out in the guide to what Opera, Mews and Cloudbeds cover.

Six questions to put to whoever proposes the build

1. What is quoted, and what is excluded from the quote?

2. Who maintains it, and what does that cost each year?

3. What happens at the next PMS upgrade, and who pays for the retesting?

4. What does it cost to change when the dock changes, such as a new tariff or metered power?

5. Who holds the knowledge if the person who built it leaves?

6. How many hours do you need from our team, in specification, testing and training?

The answers to questions two, three and four are what move the arithmetic. If they come back vague, that vagueness is itself the finding, and it belongs in the comparison as risk rather than as a blank.

Run the four lines before you take a single meeting

Build the table first, with both options in it and all four lines filled, including the cost of delay. Then take the meetings, because you will be able to test what each side tells you against a model you already trust. Most properties find the decision is clearer than expected once maintenance and internal hours are in the same table as the build quote.

To put real figures against the buy side, book a demo and bring your mooring count, your tariffs and the PMS you run. The operational case for running the dock without touching the system that runs your rooms is on the page about marine operations alongside your PMS.

Frequently Asked Questions

1. Is it cheaper to extend our PMS or buy a dock system?

Over a single year a build can look cheaper, and over three years it usually is not, because maintenance, retesting at each PMS upgrade and rework when the dock changes all recur while the build quote does not. Run both options across three years with four lines each: cost to go live, cost to keep running, internal hours, and the revenue the dock is losing while the decision is open.

2. What does a PMS extension actually cost to maintain?

Ask the party proposing it for an annual figure in writing, covering maintenance, retesting after each PMS upgrade, and changes when the dock itself changes. If that figure is not offered, treat the omission as the answer and put a placeholder in your model, because the work happens whether or not it was quoted.

3. Can we just configure our existing PMS instead of building anything?

For a small dock, yes, and it is worth trying first because it costs nothing. Rate codes, item types and profile fields can carry a handful of day berths for boats of similar size. The approach starts failing once you have seasonal berth holders on contracts, metered power, mixed vessel dimensions, or visiting boats who are not staying at the property.

4. How do we put a number on what the dock is losing today?

Take one busy week in season and compare what was delivered with what was invoiced: moorings and day berths used, power consumed, services provided. The difference, scaled across your season, is the cost of leaving the situation as it is, and it belongs in the comparison against both the build and the purchase.

5. Who should own the build-versus-buy decision at a hotel?

The GM or Director of Operations, with finance in the room, because the decision turns on recurring cost and internal time rather than on technical preference. Involve whoever runs the dock day to day for the specification questions, since they are the only people who can say what the operation actually requires.

6. What if the group has already built something at another property?

Ask that property three questions: what it cost to maintain last year, how many times it broke after a PMS upgrade, and whether they would build it again. An existing build is worth reusing when the answers are reassuring, and it is worth treating carefully when the honest answer is that one person keeps it alive.