Voyage and Chartering Management Software: Custom Build vs Veson IMOS
Buy. A dry bulk operator running under about six vessels on standard voyage charters should licence Veson IMOS or Dataloy, because the vendor model matches how you actually work.
On this page
Buy. A dry bulk operator running under about six vessels on standard voyage charters should licence Veson IMOS or Dataloy, because the vendor model matches how you actually work. The line moves near thirteen vessels, and it moves sooner for parcel tankers, contract of affreightment businesses and pool managers whose commercial logic lives in a spreadsheet.
What Veson IMOS, Dataloy and Q88 already do well
Start with the concession, because it is real. Veson Nautical IMOS is the market standard and it is the market standard for good reasons. It is deep, it has been hardened against every conventional trade, and its estimate, fixture and post-fixture modules encode decades of practice that you would otherwise learn slowly and expensively. Dataloy serves real segments well and is a genuine alternative rather than a compromise. Q88 knows tanker vessel data better than anyone and its questionnaire ecosystem is embedded in how the market actually operates.
The honest criticism is not that they lack capability. It is that they encode an opinionated model of how a voyage works, priced for scale, and operators with unusual trades find themselves working around the model. That is a fair trade for most operators, because the opinion is a good one.
Buy if you run a conventional trade at moderate scale. Under about six vessels on standard voyage charters, a licensed system will fit your business closely and a build would recreate their functionality less well, later, for more money. We say this plainly to operators who arrive expecting a proposal.
There is also a middle path worth naming before the arithmetic. Buy the platform and build the edge. If the core suits you but one commercially critical thing does not, such as a bespoke pool distribution or an in-house cargo position view, building that alongside a licensed system and reading its data is usually the right economics and a fraction of the cost.
Where they stop: the statement of facts and the demurrage time bar
A clean products tanker discharges at two ports. The statement of facts from the second port arrives from the agent as a scanned document with handwritten times in the margin. Notice of readiness was tendered at 04:10, but the berth was occupied until 19:30 and the charter party makes the notice valid whether in berth or not. Laytime ran during shifting at one port and not the other. There was a four hour stoppage the master recorded as awaiting shore tanks and the terminal recorded as a vessel pumping issue, which is the difference between demurrage and an owner's cost. The operator who understood this voyage left in March. The claim is assembled in August, and the time bar written into the charter party has already passed.
That is where voyage results actually diverge from the estimate. The fixture was negotiated by capable people. What erodes the result is post-fixture detail: laytime computed loosely, demurrage claimed late or not at all, bunker consumption never reconciled against the warranty, and a profit and loss actualised so long after completion that nobody can act on it.
Two specific things no licensed platform closes for you. First, transcription. Laytime cannot be calculated until agent documents become structured events, and that transcription is the slowest step in the claim process and the one that pushes claims past the bar, after which the merits stop mattering. Second, the clause set. Laytime depends on how notice of readiness may be tendered and when it becomes valid, turn time, whether time counts in berth or not, weather working days, exclusions, reversibility across ports, shifting and any pumping warranty. Those terms come from a negotiated recap amending a standard form such as GENCON or ASBATANKVOY, and the amendments are exactly where the disputes live. A summary field does not defend a claim. A calculation citing the clause does.
The arithmetic: per vessel licensing versus the cost to build
Do this against your own contract rather than a published figure, because licence, modules, services and hosting rarely appear on one line.
Add licence, annual support, the implementation services amortised over the term, and the internal cost of the person who maintains the spreadsheet sitting beside the system. Divide by vessels under commercial management. If that lands near $900 per vessel per month, a fleet of eight is $86,400 a year and a fleet of twenty is $216,000.
Against that, a first release covering the estimator with your own performance and cost model, structured fixture capture with the clause set, and laytime calculation with statement of facts extraction runs $120,000 to $280,000. Take the middle at $200,000, add migration, add year two support, and the two-year figure is roughly $275,000.
The crossover therefore sits near thirteen vessels under commercial management at that rate. Below it, licence. Above it, ownership pays back inside three years and keeps paying, because the licence scales with fleet count and the build does not.
One caveat that matters more than the vessel count. If your trade is parcel tankers, or a contract of affreightment business with liftings split across vessels and periods, or a pool with its own distribution rules, the crossover arrives far earlier, because the workaround spreadsheet is not an inefficiency. It is where your commercial thinking lives.
What a custom build actually costs
- First release: $120,000 to $280,000 in 16 to 24 weeks. Estimator with performance curves derived from your own noon reports and port costs seeded from your own disbursement history, structured fixture and clause capture, and laytime calculation with document extraction into a draft event sequence.
- Full platform: $350,000 to $800,000 across 9 to 18 months. Adds post-fixture operations, bunker inventory and claims, disbursement control, live voyage profit and loss with estimated, accrued and final lines, and emissions cost modelling.
Migration runs 10 to 25 percent of the build. Migrate historical voyages only for the estimate calibration data, which is genuinely valuable, and rarely for anything else. Year two runs 15 to 20 percent of the build annually.
What drives the number up in shipping specifically: the number of trades, because tanker, dry bulk and gas carry different freight conventions and a parcel trade is harder than all of them. Contracts of affreightment and pool arrangements, since allocation and distribution rules are bespoke commercial agreements rather than features. Accounting integration, because voyage accounting has to reconcile to a general ledger never designed for it. And market data, if you need rate feeds or distance and weather routing services.
The four situations where building wins
- Regulatory fit. Carbon cost now belongs inside the estimate rather than in a compliance spreadsheet. The extension of the European Union Emissions Trading System to maritime transport and the fuel intensity requirements under FuelEU Maritime mean an estimate without a carbon line is quoting the wrong number on European trades, and the Carbon Intensity Indicator and the IMO Data Collection System add reporting obligations against the same voyage record.
- Scale economics. Past roughly thirteen vessels under commercial management, where the licence line grows with the fleet and an owned system does not.
- A workflow that is your competitive advantage. Your estimate model and your allocation logic. If the spreadsheet your commercial team would refuse to give up holds either of those, that spreadsheet is your requirement document and it is describing a build.
- Integration sprawl across three or more systems. A licensed platform, an accounting ledger, a bunker procurement tool, a noon report feed and a weather routing service. When under-performance claims are not pursued because assembling the evidence costs more than the average claim, the join is the missing product.
How to decide in a week
Take your three most recent completed voyages and run a timed exercise on Monday.
For each one, ask your operations desk two questions. First, produce the laytime calculation and, beside every decision it contains, the clause that produced it. Second, state the date the demurrage time bar falls and how many days remain. Give them one day. If both come back cleanly, you have a system that fits and you should keep paying for it.
Then the money question, which is harder and more useful. Take those same three voyages and decompose estimate against actual by assumption: speed, port time, bunker price, port cost, cargo quantity. If nobody can tell you which assumption was wrong, you are not learning from your own voyages, and correcting a systematic bias in speed or port time assumptions is worth more over a year than any single negotiation.
Move the shortlist into a paid discovery phase. Ours runs three to four weeks for this category, because the clause modelling deserves the time, and it ends with a signed product requirements document covering the voyage and fixture model, the laytime engine's explanation rules, the document extraction path with human confirmation, the accounting interface, and acceptance criteria measured against a real historical claim. That document keeps a fixed price fixed and you own it either way.
Digital Heroes is wrong for you if you want a hosted platform on a monthly fee, or a supplier holding your estimate model and voyage history in their environment. We build systems you own. Our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under your own law. More than fifty specialists, in-house products including ShopScore and Section Vault, a named team you meet before signing, and a record checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
How much does custom voyage management software cost?
A first release covering the estimator with your own performance and cost model, structured fixture capture and laytime calculation with document extraction runs $120,000 to $280,000 over 16 to 24 weeks. Adding post-fixture operations, bunker inventory and claims, disbursement control, live voyage profit and loss and emissions cost takes it to $350,000 to $800,000 across 9 to 18 months, plus migration and annual support.
Can we keep Veson IMOS and build only the part it does not cover?
Yes, and for many operators that is the right economics. If the core suits you but one commercially critical thing does not, such as a pool distribution rule or an in-house cargo position view, build that alongside the licensed system and read its data. You keep the hardened core, you own the part that is actually your edge, and the project is a fraction of a full platform.
What is the difference between voyage management and freight forwarding software?
They share almost nothing. Freight forwarding software moves shipments and raises invoices. Voyage management models an estimate, a fixture with its negotiated clause set, an itinerary with port calls, bunker inventory per grade, laytime against those clauses, and a result with estimated, accrued and final lines. A developer who draws shipments and invoices for a chartering business will not survive the first laytime dispute.
How long does a chartering system take to build?
Sixteen to twenty-four weeks for a first release, and nine to eighteen months for a full platform. The schedule risk is clause modelling rather than screens. Every amendment your recaps make to a standard form is a decision about how the engine behaves, and those decisions need a commercial person available weekly. Operators who assign that role properly finish on time and the others do not.
Who owns the estimate model and the voyage history?
You should, in writing, before kickoff, covering the repository, the cloud accounts and the data. Your performance curves and your historical voyage results are genuine competitive assets, and they should not sit in a supplier environment where moving firms means leaving them behind. Digital Heroes assigns from the first commit through its India, United States and United Kingdom entities.
Can artificial intelligence read a handwritten statement of facts?
It can produce a draft event sequence with times, ports and remarks mapped to your event taxonomy, which an operator confirms rather than types. That is the right use and it collapses transcription from hours to minutes. Anything promising fully automated interpretation without review has not seen the documents agents actually send. The value is claims assembled while facts are fresh, not the keystrokes saved.
What happens if a demurrage claim passes its time bar?
The merits stop mattering, which is why the clock deserves to be a system feature rather than a diary note. Every voyage should carry its bar computed from the charter party terms, with escalation as it approaches and a visible queue of claims running out of time. A claim lost to a time bar is a pure avoidable loss and the most infuriating line in any post-voyage review.
Should a small operator build just a laytime calculator?
It is a reasonable first move if demurrage is where your money leaks. A standalone engine captures the clause set from the recap, produces a calculation that cites the term behind every decision, and forces a recorded human decision where a term cannot be modelled. It touches nothing in accounting and it gives you something you can put in front of a counterparty.
Does carbon cost belong in the voyage estimate?
On European trades it does, and operators still estimating without it are quoting the wrong number. The extension of the European Union Emissions Trading System to maritime transport and the fuel intensity requirements under FuelEU Maritime attach a cost to the same voyage the freight is priced against. Keeping that in a separate compliance spreadsheet means your commercial team never sees it during negotiation.
What happens if the fixed quote turns out to be wrong?
That is what a paid discovery phase prevents, and in this category we run three to four weeks rather than two. It produces a signed specification covering the voyage and fixture model, the laytime engine's explanation rules, the extraction path, the accounting interface and acceptance criteria measured against a real historical claim. The fixed price is fixed against that document, and changes are priced in writing beforehand.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 .
