Ferry Operations Software: Build or Buy, and Whether the Packaged Capacity Model Fits Your Deck
The test is what happens when your longest serving superintendent takes leave. If deck utilisation drops that week, the capacity model lives in a person rather than in software.
On this page
The test is what happens when your longest serving superintendent takes leave. If deck utilisation drops that week, the capacity model lives in a person rather than in software. One or two vessels on a short route with simple vehicle categories, no significant freight contracts and no dangerous goods: buy, and Hogia Ferry Systems or Carus will serve you well with a check in tablet alongside. Once you are running mixed passenger, vehicle and freight traffic across more than a couple of vessels, lane metres against a certificate limit and a cabin inventory is three constraints on one sailing, and a first release modelling that properly runs $90,000 to $185,000 over 14 to 20 weeks.
When is off the shelf genuinely the right call here?
Buy if you run one or two vessels on a short route with simple vehicle categories, no significant freight contracts and no dangerous goods. Hogia Ferry Systems and Carus are genuine ferry products and neither deserves the criticism aimed at general booking tools. They understand ro-ro capacity, freight and passenger traffic properly, and an operator moving off a legacy system will get real value from either.
Buy also if your immediate problem is channel distribution and online booking presentation rather than deck utilisation. That is commodity plumbing, and building it changes nothing about how full the deck is.
Be clear about what a packaged product does and does not carry, because it is fit rather than quality. What stays outside is the physical reality of your vessels and terminals: deck configurations, hoistable deck rules, which lane takes which height, and how your crew loads. So does a pricing structure where freight sits on contracts and retail on yield managed fares against the same deck, and so does disruption handling, which on a weather affected route is a regular Tuesday rather than an edge case.
The signal that buying is still right is that the system's answer is the answer. If your operations manager rarely overrides availability, and check in rarely produces a vehicle that does not match its booking, the packaged capacity model expresses your operation. What ends the buy case is a superintendent quietly fixing Friday evenings every week, so the commercial team never learns the route systematically oversells lane metres.
When does a custom build actually pay off?
The build case is one modelling problem. Every general reservation system counts units of the same thing, and a ferry sells at least three constrained resources on one sailing: lane metres of deck with height and weight limits, passenger places against the vessel certificate, and cabins by type. A motorhome and four foot passengers consume the same certificate places and completely different amounts of deck. An unaccompanied trailer takes deck and no passengers at all.
Build when two or more of these are true.
- Deck utilisation is managed by a person with local knowledge rather than by the system, and their judgement is good, which is why nobody has noticed the dependency.
- Check in regularly discovers vehicles that do not match their booking and nobody measures how often. A car with a trailer booked as a car, a van booked as a car because it was cheaper, a motorhome whose height matters because the mezzanine is down.
- Freight and retail compete for the same deck with no explicit allocation rule, so the split is an accident of who booked first rather than a management decision.
- A cancelled sailing means a day of phone calls, rebooking an entire departure across later ones while respecting every capacity constraint again.
- Your vessels have configurations your current system expresses as a note, such as a hoistable deck with height dependent lane rules.
Underneath all of it sits the manifest. Before the ramp closes you must know how many persons are on board and be able to produce that record, with dangerous goods declarations matching what is physically loaded and where. A manifest assembled from three systems and a handwritten list is the thing you would be judged on afterwards.
How do they compare on the things that matter in this industry?
On channel distribution, payments and booking presentation, buying wins outright.
On capacity, a build wins because availability has to be a fit question rather than a counter. A booking consumes a vector across lane metres, certificate places and cabin inventory, and availability is whether that vector fits. This is a data model decision, expensive to retrofit, so it belongs in the first release or not at all.
On check in, a build wins on what it records rather than what it displays. Vehicle categories should carry real dimensions instead of price bands, with a declared value at booking and an actual value at the ramp, and the difference retained. That retained difference is what turns overbooking policy from instinct into a calibrated decision per route and per day of the week.
On load planning, a build wins if the deck crew will actually use it. Vehicles assigned to lanes and decks with the constraints applied, produced before check in and adjustable at the ramp on a tablet that keeps working when the terminal network does not. A plan that lives only in the office means the crew keep their own and yours becomes fiction.
On dangerous goods, a build wins on the block rather than the flag. Declaration at booking, class and quantity limits per sailing, segregation rules constraining placement, and a hard refusal rather than a warning someone can click past.
On integration burden, buying wins. Terminal hardware in a salt air environment, agent channels and payment providers are all yours to maintain once you own them.
On portability, building wins, because the system holds passenger registration records you may need to produce to an authority years later.
What does total cost of ownership look like at your scale?
A first release runs $90,000 to $185,000 over 14 to 20 weeks: the multi dimensional capacity model, booking and availability against it, offline check in capturing actual measured dimensions, and controlled manifest closure. A full platform adding load planning, dangerous goods acceptance, freight contracts and invoicing, yield managed retail fares, disruption rebooking, terminal hardware and agent channels runs $250,000 to $600,000 across 8 to 14 months.
A worked shape. Two vessels on one mainland to island route plus a summer route, mixed passenger, car, motorhome and accompanied freight, two terminals: discovery including two days at the ramp $15,000, capacity model with lane metres by deck, height limits, certificate places and cabins $31,000, vehicle categories with declared and actual dimensions $12,000, booking and availability as a fit question $24,000, offline check in with discrepancy retention $29,000, manifest closure as a non editable step $18,000, second vessel and summer route $14,000, and terminal testing with training $13,000. That is $156,000. A single small vessel on a short route lands nearer $92,000.
Vessel configurations drive the number more than passenger volume does. Two identical sisters cost barely more than one. A genuinely different configuration adds $18,000 to $35,000 after the first, and a refit that changes lane configuration is a software change with a shipyard deadline rather than one you set.
Running costs are 12 to 18 percent of build a year plus hosting at roughly $300 to $800 a month, where the peak profile matters more than the average. Then two physical lines software people forget: spares for scanners and lane displays at every port, and a redundant or cellular link at the ramp, which most operators end up buying once check in exposes how often the primary fails.
What does the hybrid look like, and when is it the honest answer?
There are two hybrids here and most operators should run both.
The first is between products. Keep your payment provider, agent channels and online distribution if they work, and keep the packaged product for anything it genuinely handles. Then build the capacity model, check in and manifest closure, because those are specific to your steel. Rebuilding distribution spends on a solved problem while the deck stays half empty.
The second hybrid is inside the build, and it is the more important one. Model one vessel and one route completely before generalising. That narrow release, meaning the capacity model, booking against it, offline check in and manifest closure, runs $55,000 to $85,000 over nine to eleven weeks with freight still handled the way you handle it today. It proves the model against a real ramp before you commit to abstraction, and it is the cheapest insurance available in this category. Operators who start by building a configuration engine for the whole fleet spend the budget on abstraction written before anyone watched a real marshalling area.
Defer terminal hardware to phase two. A tablet with a camera and a printed boarding list runs a check in perfectly well while the capacity model proves itself. Start disruption rebooking as a rules assisted workflow putting a proposal in front of a duty officer, which captures most of the value at the lower end of a $25,000 to $55,000 range.
Then run one full season week in parallel before switching over, and choose the busiest week rather than the quietest.
Which should you choose, by operator size and stage?
One vessel, short route, foot passengers and a handful of cars: buy Hogia or Carus, add a check in tablet, and stop. Revisit when freight contracts appear or when a second vessel with a different deck joins.
Two similar vessels, standard categories, modest freight: still buy, and spend the effort on one free discipline instead. Start recording the measured length of every vehicle that does not match its booking, in a notebook if necessary. Six months of that data is the most valuable input to any future build, and it may show that your system is fine and your declaration process is the problem.
Two or more vessels with mixed traffic, or any vessel with a hoistable deck: build the narrow release at $55,000 to $85,000 first. One vessel, one route, capacity model and check in. Prove it, then extend to the fleet.
Multi vessel operators with freight contracts, dangerous goods, several terminals or a weather exposed route: the full platform at $250,000 to $600,000 across three to four quarters. Decide multi leg island hopping at the start rather than later, because holding capacity per leg rather than per sailing is expensive to retrofit.
Whoever you hire, ask how availability is calculated for a motorhome towing a car on a night sailing. The answer must involve lane metres, height, certificate passenger places and cabin inventory in one check. If it involves a single count, you are buying an airline seat map with a boat on the login screen. Ask what happens at check in when a vehicle is two metres longer than booked, and expect capture, an immediate effect on the load plan and retention of the discrepancy. Ask how the application behaves with no network. Settle ownership of the code, the repository and the cloud accounts before kickoff.
If you want a second opinion before signing anything, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In a practice using direct self-booking with easy rescheduling, online-booked appointments had a far lower no-show rate (1.8% median) than offline bookings (5.9%), though a hospital's request/triage system showed the opposite pattern - indicating booking-system design, not online booking per se, drives no-show outcomes. Source: GMS / PubMed Central (German medical practice & university hospital study) (2025) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- An EY survey found one in five U.S. payrolls contains errors, each costing an average of $291 to remediate, with a typical 1,000-employee organization spending roughly 29 workweeks per year fixing common payroll errors. Source: EY (Ernst & Young) (2022) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
Frequently asked questions
What does it cost to migrate off Hogia or Carus, or off a legacy system?
The bookings and customer records are the easy part. The expensive part is that your historical sailing data, which is what calibrates a capacity model, often exists only as totals rather than as the vehicle level detail you need.
Plan to run the new capacity model against historical sailings where you know what fitted and what did not, and accept that the first season generates better calibration data than anything you can migrate. Keep the old system readable through one full audit cycle for manifest records.
What if our reservation vendor raises prices or changes its model?
Your exposure depends on whether the capacity model is yours. If it is, a price change affects distribution and support, both of which have alternatives, rather than your ability to sell the deck correctly.
The recurring cost you take on instead is physical and predictable: terminal hardware maintenance, spares at each port, and a redundant link at the ramp. Those sit inside the 12 to 18 percent annual figure and they do not go away when a vendor relationship does.
How long does a ferry operations build take?
Fourteen to twenty weeks for a first release covering one vessel and one route completely, or nine to eleven weeks for the narrow capacity model and check in release. The full platform reaches 8 to 14 months.
Discovery is three to four weeks and has to happen at the ramp rather than in a meeting room. A developer pricing this from a specification document has not seen a marshalling area on a Friday evening, and will model availability as a counter.
Is Hogia Ferry Systems enough for a two vessel ro-ro operator?
Often yes, and that is the honest answer for a conventional route structure with standard vehicle categories and modest freight. It understands ro-ro capacity properly, which general reservation products do not.
The gap appears where your vessels are unusual, where freight contracts and retail fares compete for the same deck without an explicit allocation rule, or where disruption is frequent. Test it by asking your operations manager how often they override availability, and by asking what happens when the superintendent takes leave.
Can we build just the capacity model and check in first?
Yes, and it is the correct opening move for most operators. One vessel, one route, the capacity model, booking against it, offline check in with actual measurement capture and manifest closure runs $55,000 to $85,000 over nine to eleven weeks, with freight still handled the way you handle it now.
It proves the model against a real ramp before you generalise across the fleet, and it starts producing declared against actual dimension data, which is what turns overbooking policy into a calibrated decision.
Why does each additional vessel configuration cost so much?
Because a deck layout is a constraint set rather than a setting. Lane metres by deck, height limits per lane, weight limits, hoistable deck rules, which lanes take a refrigerated unit needing power, and dangerous goods segregation all differ, and load planning behaviour differs with them.
Two identical sisters cost barely more than one. A genuinely different configuration adds $18,000 to $35,000. Budget for refits too, because a vessel that gains a mezzanine deck changes the constraint set on the shipyard's timetable.
Does check in really have to work offline?
Yes, and it adds roughly $20,000 to $38,000. Ramps and marshalling areas are steel structures at the edge of ports, and terminal connectivity fails often enough that any design assuming a network will be abandoned by staff within a month.
Offline capture with reconciliation has to include manifest counting, because ramp closure cannot wait for a router. Test it on the devices your staff will actually hold, in the actual location, with the network switched off deliberately.
Who owns the code and the manifest records if an agency builds this?
You should own the repository, the cloud accounts and the unrestricted right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more than in most categories because the system holds passenger registration records and dangerous goods documentation you may need to produce to an authority long after any vendor relationship has ended, and in a form that cannot have been edited after ramp closure.
What should the first version of a booking app include?
Ship four things: a public booking page, staff calendars with availability rules, card payments or deposits, and automated email and SMS reminders. Leave memberships, packages, gift cards, and reporting dashboards for phase two; they roughly double the build cost and get redesigned after real usage anyway. In Digital Heroes MVP scopes, that four-feature core covers about 80 percent of daily front-desk work from day one.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Will a custom booking system scale if we open more locations?
Yes, provided multi-location support is designed in from day one: location-scoped staff, services, pricing, and reporting with a shared client record underneath. Retrofitting locations onto a single-site build is one of the costlier changes we handle at Digital Heroes, often 30 to 40 percent of the original build price. If expansion is even a maybe, say so during scoping; the data-model decision costs almost nothing upfront and prevents a rebuild later.
How quickly does a custom booking system pay for itself?
Payback comes from three lines: cancelled subscriptions, which run $100 to $600 a month for tools like Mindbody, recovered no-show revenue from deposits and reminders, and admin hours saved on manual scheduling. For businesses handling 300+ bookings a month, Digital Heroes typically sees a $20,000 to $30,000 build recover its cost within 18 to 30 months. Under about 100 bookings a month the math rarely works, and an off-the-shelf tool remains the right call.
How long does it take to build custom booking software?
Plan on 6 to 10 weeks for a working MVP and 3 to 5 months for a full platform with memberships, reporting, and integrations. Across Digital Heroes booking projects, the calendar engine takes about a third of the timeline because recurring availability, time zones, and double-booking prevention need heavy testing. Migrating data from your old tool usually adds 1 to 2 weeks at the end.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Who can build a custom booking & scheduling software system?
Digital Heroes builds custom booking & scheduling software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other booking & scheduling software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
