Regulation does not scale with fleet size, and that single fact defines what it is like to run two to ten ships. A three-vessel owner faces the same ISM Code, the same SOLAS chapters, the same MLC obligations, the same Port State Control regime and the same set of 2026 amendments as an operator with three hundred. The obligations are written per vessel and per company; they do not discount for scale. What does scale is the capacity to absorb them. Published analysis puts an average ten-vessel fleet at two to four shore compliance staff covering safety, environmental, crew, vetting and regulatory reporting — roughly one person for every three to five ships. Run that ratio down to four vessels and you have one person. Run it to two and you have a fraction of a person, which in practice means somebody who also does chartering, insurance, banking and probably crewing. Meanwhile new regulatory requirements are estimated to add fifteen to twenty hours of monthly workload per vessel, and hiring a dedicated compliance position costs a hundred and twenty to a hundred and eighty thousand dollars a year — an expense many operators simply cannot justify. That gap is the small fleet problem, and it is not a budget problem. Start a free trial of Marine Inspection and close it without adding a salary.
2-3 vessels
Shore compliance capacity
Part of one person
Somebody who also handles chartering, insurance and crewing. The compliance obligation is identical to a large fleet's and there is no one else who understands it.
4-6 vessels
Shore compliance capacity
Roughly one person
Enough to be a genuine role and not enough to be two. Holiday, illness or a resignation removes the entire function, and nothing about the regulatory calendar pauses while you recruit.
10 vessels
Shore compliance capacity
Two to four people
The point at which specialisation becomes possible and one person's absence stops being a crisis. Published analysis puts an average ten-vessel fleet at this staffing level.
Note what stays constant across all three columns: the ISM Code, the certificate set, the survey cycles, the vetting expectations, the reporting obligations and the amendments landing each January. A small fleet is not a scaled-down version of a large one. It is the same regulatory burden carried by fewer people, which makes it structurally harder rather than structurally simpler.
The Real Constraint Is Not Money
Small operators are usually sold on cost, and cost is rarely the binding problem. The binding problem is that the knowledge lives in one head. Book a Marine Inspection demo and think about what happens to your operation if that person is unreachable for a fortnight.
In a small operation, one person is
The certificate calendar
The class survey position
The memory of what the last surveyor said
The knowledge of which vessel has the awkward generator
The relationship with the flag administration
The person who knows what was deferred and why
Why this is the actual risk
A large fleet losing a superintendent loses one of several. A three-vessel operator losing theirs loses the compliance function entirely, along with the undocumented context that made it work — and the certificate expiries, survey windows and inspection cycles carry on regardless.
What software is actually for here
Not efficiency, which is what it is sold as. Externalising the knowledge that currently exists only in one person's head and one person's inbox, so the operation continues functioning when they are on leave, unwell, or gone. That is a different value proposition from the one a large fleet buys.
And it changes what to prioritise
Certificate and survey visibility before anything else, because that is the knowledge with the hardest deadlines and the worst consequences. Defect history second, because it is what a new person needs to understand a vessel they have never seen. Everything else can wait.
What Enterprise Buying Assumes That You Do Not Have
Most maritime software procurement is designed around a buyer who does not exist at this scale, which is why evaluating it feels disproportionately hard. Sign up for Marine Inspection and skip most of the process below.
A project team
Enterprise implementations assume a named project manager, an IT function and departmental representatives with time allocated. A four-vessel operator has one person who is also doing everything else, evaluating software in evenings and between port calls.
A discovery process
Custom quotation, scoping calls, a proposal cycle measured in weeks. That process costs a small operator more in time than the software costs in money, and it exists largely so a vendor can work out what to charge.
Months of configuration
Published comparisons put mid-market modular platforms at three to six months to implement and enterprise suites at six to fifteen. On three vessels that is a rollout longer than the useful life of most of the reasons you started.
Consultant-led setup
Professional services priced on the assumption that configuration is complex because the buyer is complex. A small fleet's configuration is genuinely simple, and paying enterprise implementation fees for it is paying for somebody else's complexity.
A multi-year commitment
Three-year terms are normal at the enterprise tier because they protect the vendor against non-adoption. For an operator who cannot absorb a failed implementation, the option to leave has more value than the discount for surrendering it — so price that option rather than trading it away.
The evaluation a small fleet should actually run
Sign up without talking to anybody. Load one vessel's equipment and certificates in an afternoon. Put it on a phone and have somebody walk a real round with it. Check that it works with no signal. See whether a certificate expiry alerts you before it matters. If it does those four things and the published price fits your budget, you have completed an evaluation that would take an enterprise buyer three months — and you have done it without a single scoping call.
Three Honest Options, Not One
Software is one answer to the small fleet problem and it is not always the right one. Being clear about the alternatives makes the choice better whichever way it goes. Schedule a walkthrough once you know which of these three you are actually choosing between.
Carry on as you are
Spreadsheets, a certificate folder, email and one person's memory. It works, frequently for years, and it is not a foolish choice for two well-run vessels with a stable and experienced manager.
Breaks when: that person leaves, or the fleet grows past what one memory holds, or a new requirement adds fifteen to twenty hours a month per vessel that nobody has
Outsource technical management
A third-party manager brings specialised expertise and established systems without the fixed cost of building your own shore infrastructure. In-house management offers direct control but requires real investment in staff, systems and compliance capability.
Right when: you want the asset managed and do not want to build a technical department. Costs control and a monthly fee, and you should still ask who owns the maintenance record
Keep control, add a system
Retain direct control of your vessels and replace the parts of the burden that are genuinely mechanical — certificate tracking, survey windows, defect history, inspection records — so that one person can carry a fleet that would otherwise need two.
Right when: you want to stay in-house, the fleet is growing, or the concentration of knowledge in one person has started to worry you
Worth saying plainly, since this page is published by a software vendor: the second option is genuinely right for some owners, and a manager who runs an established system across many vessels will do certain things better than a small in-house team with a new platform. The question that distinguishes it is whether you want operational control. If you do, a system is how you keep it affordably. If you do not, a manager is a reasonable answer and the software conversation can wait — though you should still establish, contractually, that the maintenance and inspection record belongs to the vessel rather than to the manager's platform.
What a Small Fleet Actually Needs
Feature lists are written for the largest buyer in the market. Most of what is on them does not apply below ten vessels, and paying for it is the most common way small operators overspend. Start a free trial and check your requirement against the first column only.
Needed from day one
Certificate and survey windows with alerting well before expiry
An equipment register at component level, per vessel
Inspection and round records captured on a phone, offline
Defects that become tracked work with an owner and a date
Closure with evidence — a measured value, a photograph, a name
History retrievable at the machine by whoever is standing there
Full export of your own data, at no charge, stated in writing
Can wait, genuinely
Integration with finance or procurement systems
Condition monitoring and sensor feeds
Advanced analytics and fleet benchmarking dashboards
Custom workflow engines and approval hierarchies
Multi-entity and multi-currency structures
Anything described as configurable rather than working
Modules for functions you currently perform in ten minutes a week
The test for the second column is straightforward: if you cannot name the person who would use it weekly and the decision it would change, it belongs there. Every feature carries configuration effort, training effort and a permanent maintenance obligation, and at this scale those costs are paid by the same one person who is already stretched. A smaller system that gets used beats a comprehensive one that gets worked around, and the gap between them is wider at three vessels than at thirty.
Seven things in the first column. If a platform does those well on a phone with no signal, it solves the small fleet problem.
Where the Crew Fit In
Small fleets have an advantage here that larger operators do not, and it is worth using deliberately. Book a walkthrough and involve a master before choosing anything.
The disadvantage first
Crews are already at the limit. Published analysis notes that crew working maximum regulatory hours under rest requirements cannot absorb additional documentation, that each new compliance requirement adds thirty to ninety minutes daily, and that poor implementation produces incomplete records which trigger deficiencies despite everybody working within their hour limits.
The advantage
You know your masters and chief engineers personally, and you can ask them before you buy rather than announcing afterwards. A four-vessel owner can have a genuine conversation with the people who will use the system — something a forty-vessel operator cannot do at all.
Use it
Send the trial to one master and one chief engineer, ask them to use it for a fortnight, and ask afterwards whether it was faster than what it replaced. Their answer is worth more than any evaluation matrix, and getting it costs you nothing.
And it changes the adoption problem
Large fleets need champion programmes and structured training because the shore team cannot reach everybody. At two to ten vessels the owner or manager can speak to every master directly, which removes most of the change management problem before it starts — provided the tool is genuinely faster than the paper.
Pricing Questions That Matter at This Scale
The commercial terms that are minor irritations for a large fleet are decisive here, because there is no procurement function to absorb them. Start a free trial and get straight answers on each before committing.
Table 1: Commercial Terms to Establish First
| Question | Why it matters more below ten vessels | A good answer | What should worry you |
|---|---|---|---|
| Is the price published? | You have no procurement function to run a negotiation | A per-vessel figure you can read without a call | Custom quotation, which is a discovery process you cannot afford in time |
| Is there a minimum? | Many platforms price from a floor that assumes a larger fleet | No minimum, or one below your vessel count | A minimum that makes you pay for capacity you will never use |
| Are users charged separately? | Capture at the work needs everyone aboard to have access | Not per seat, so crew access costs nothing extra | Per-user pricing, which pushes you to restrict exactly the wrong people |
| What is implementation? | You have no project team and no consulting budget | Included, or a small fixed fee, with go-live in weeks | Enterprise professional services for a three-vessel configuration |
| What is the term? | A failed implementation you cannot exit is existential at this size | Month to month available, with the annual price also quoted | Three years as the only option, which is where the risk sits |
| Adding a vessel? | Small fleets change composition proportionally more often | Pro-rated addition and a defined removal position | Easy additions and impossible removals, which is a ratchet |
| What is the uplift cap? | You have no leverage at renewal and no alternative supplier ready | A stated percentage cap in the agreement | Nothing stated, which becomes a problem in year two |
| What does export cost? | The record has to outlive the platform and the manager | Free, open format, stated contractually | Any charge to retrieve records you created |
| What support do we get? | There is no internal IT to absorb a problem | Stated response times at your tier, in your working hours | Community forums, or support priced as a separate tier |
A Realistic First Thirty Days
At this scale the rollout is short enough to describe honestly, and most of it is not software work. Schedule a demo and compare this against any timeline you are quoted.
Table 2: Thirty Days, Two to Ten Vessels
| When | What happens | Who does it | How long it really takes |
|---|---|---|---|
| Day 1 | Sign up, no call, and look at it properly | You | An hour, in the evening if that suits |
| Days 2-4 | Load one vessel: equipment, certificates, survey dates | You, or whoever holds the certificate folder | An afternoon per vessel if records are reasonable |
| Day 5 | Build the round and inspection checklists you actually use | You, with a master's input | Two hours, and cut anything that changes no decision |
| Week 2 | One master and one chief engineer use it for real, on a phone | Them, unsupervised | A fortnight, which is the actual test |
| Week 3 | Fix what they found — checklist length, wording, missing equipment | You | An hour or two, and it is the most valuable hour in the process |
| Week 4 | Load the remaining vessels using the corrected setup | You | Faster than the first, because the decisions are made |
| Ongoing | Certificate alerts arrive before expiry rather than after | The system | The point of the exercise |
| Deliberately absent | Integrations, analytics, custom workflows, consultants | Nobody | Later, if anybody asks twice |
SMALL FLEET REALITY
The staffing and workload figures cited here come from published industry analysis rather than from a survey of small operators specifically. The two to four shore compliance staff for an average ten-vessel fleet, the fifteen to twenty hours of additional monthly workload per vessel from new requirements, the thirty to ninety minutes daily added to crew workload, and the hundred and twenty to hundred and eighty thousand dollar annual cost of a compliance position are drawn from 2026 commentary and vary considerably by trade, flag, vessel type and how a company organises itself. Use them as a description of the shape of the problem rather than as your own numbers. Third-party management is a genuine alternative and is right for some owners; this page is published by a software vendor and says so in the relevant section rather than pretending otherwise. The regulatory obligations do not reduce with fleet size. Nothing in this page suggests a smaller operator faces a lighter compliance burden — the argument is the opposite. Confirm your own position with your flag, class and insurers rather than relying on any general summary.
Frequently Asked Questions
Why is compliance harder for a small fleet?
Because the obligation is constant and the capacity to absorb it is not. A three-vessel owner faces the same ISM Code, SOLAS chapters, MLC requirements, Port State Control regime and annual amendments as an operator with three hundred, since the rules are written per vessel and per company rather than scaled to fleet size. Published analysis puts an average ten-vessel fleet at two to four shore compliance staff — roughly one person for every three to five ships — so below that scale you are running the same regulatory function with a fraction of a person, frequently somebody who also handles chartering, insurance and crewing.
What is the actual risk in a small operation?
Concentration rather than cost. In a two to six vessel operation, one person is simultaneously the certificate calendar, the class survey position, the memory of what the last surveyor said, the knowledge of which vessel has the awkward generator, and the record of what was deferred and why. A large fleet losing a superintendent loses one of several; a small operator losing theirs loses the entire function along with the undocumented context that made it work — while the certificate expiries and survey windows carry on regardless. Software's real value at this scale is externalising that knowledge, not efficiency.
Can we not just hire somebody?
Frequently not, and the numbers explain why. Hiring an additional compliance position is estimated at a hundred and twenty to a hundred and eighty thousand dollars annually, described in industry commentary as an expense many operators cannot justify. Spread across three or four vessels that is a substantial addition to per-vessel operating cost for a function that a system can carry much of. The trigger for hiring is usually not workload alone but the point at which one person's absence becomes an unacceptable operational risk — and that trigger can also be addressed by making the knowledge institutional rather than personal.
What should a small fleet not pay for?
Integrations, condition monitoring, advanced analytics, custom workflow engines, multi-entity structures, and anything described as configurable rather than working. The test is simple: if you cannot name the person who would use it weekly and the decision it would change, you do not need it yet. Every additional feature carries configuration effort, training effort and a permanent maintenance obligation, and at this scale those are all paid by the same stretched person. A smaller system that gets used beats a comprehensive one that gets worked around, and that gap is considerably wider at three vessels than at thirty.
Should we outsource technical management instead?
It is a legitimate option and right for some owners, so it deserves a straight answer from a software vendor. In-house management offers direct control but requires real investment in shore staff, systems and compliance infrastructure; a third-party manager provides specialised expertise and established systems without those fixed costs. The distinguishing question is whether you want operational control of the vessels. If you do, a system is how you keep it affordably. If you do not, a manager is reasonable and the software question can wait — though you should establish contractually that the maintenance and inspection record belongs to the vessel rather than living inside the manager's platform, because you will want it if you change manager or sell.
How long does implementation actually take at this size?
Weeks rather than months, and most of the work is not software. Realistically: an hour to sign up and look at it properly, an afternoon per vessel to load equipment, certificates and survey dates if records are reasonable, two hours to build the checklists you actually use with a master's input, then a fortnight of one master and one chief engineer using it unsupervised — which is the real test. Fix what they find, load the remaining vessels using the corrected setup, and you are done. Published comparisons put mid-market platforms at three to six months and enterprise suites at six to fifteen; on three vessels that is a rollout longer than the problem you started with.
Two to ten vessels
The Same Rules, Carried by Fewer People
Nothing in the regulations gives a small operator a lighter load, and the capacity to carry it does not arrive until somewhere around ten ships. Until then the function rests on one person, along with everything they know that is written down nowhere. Start with the seven things that matter — certificate and survey windows with alerting, a component-level equipment register, offline capture on a phone, defects becoming tracked work, closure with evidence, history retrievable at the machine, and your data exportable at no charge. Skip everything else until somebody asks for it twice. And check the price is published, the users are not metered and the term is not three years, because at this scale those three terms matter more than any feature on the list.
