How Much Does Ship Agency and Port Call Software Cost in 2026?
$70,000 to $500,000 covers the realistic range for a custom port call and disbursement platform, and the decision that moves your number most is how many port tariffs you model.
On this page
$70,000 to $500,000 covers the realistic range for a custom port call and disbursement platform, and the decision that moves your number most is how many port tariffs you model. Each tariff is its own exercise in versioned calculation rules, and a complex port takes days rather than hours, so an agency starting with its top three ports by call volume usually covers most of its traffic at the bottom of the band, while a network build across twenty ports pushes you toward the top before a single workflow feature is discussed. Model fewer ports properly and you spend less and finish sooner.
The bands a port call software build falls into
A focused first release covering appointment through to a tariff driven proforma disbursement account, supplier invoice capture with matching, and final account reconciliation with line level variance runs $70,000 to $160,000 and ships in 12 to 18 weeks in Digital Heroes delivery experience. That build addresses the thing agencies actually lose money on, which is unrecovered variance between the proforma and the final account, and it does it by making the disbursement one object rather than two documents.
The full platform adds funds in advance ledgers held per principal per call, principal approval workflows with configurable thresholds, multi currency settlement with exchange difference handling, statutory filing integration into single window systems, and a principal facing portal. That runs $200,000 to $500,000 phased over 6 to 12 months. Most agencies that reach the upper band got there over two or three funded phases, and the ones that tried to buy it all at once usually stalled somewhere in tariff modelling, because that work cannot be compressed by adding people.
What drives a port call build up
Port count is the dominant driver. Tonnage dues on a scale, pilotage by length overall and draught with night and weekend factors, towage by bollard pull with minimum charges, berth dues per metre per period and waste reception on a fixed and variable basis are all formulas, and each port publishes its own, revises them on its own schedule and expresses them in its own structure. Modelling one port properly is a discrete piece of work with a discrete cost.
Statutory filing is the second driver. Reporting has moved substantially towards electronic single window systems, including the European maritime single window environment which consolidates reporting formalities for calls at member state ports, and each implementation has its own interface and its own validation rules. Integrating two of them is not twice the cost of one, it is two separate specifications.
Then accounting integration, which is unavoidable because funds in advance are client money and must reconcile exactly, and principal count, since every principal with genuinely bespoke cost coding and approval rules adds configuration work. The least visible driver is supplier invoice capture. Invoices arrive as PDFs in dozens of layouts from launch boat operators, chandlers and port authorities, and getting extraction to propose a usable match against commitments is where the operational hours actually go.
What keeps the number down
Start with your top three ports by call volume. For most agencies that covers the majority of traffic, proves the tariff model, and means the fourth port costs a fraction of the first because the calculation framework already exists.
Build the tariff and disbursement layer only, if variance is your real problem rather than coordination. A great many agencies find that modelling tariffs as versioned rules and making the disbursement a single object with line level variance and reason codes resolves most of the pain, at the lower end of the first release band, without touching port call task management at all.
Keep statutory filing out of phase one unless a specific jurisdiction is already causing you delays. The data model that feeds a filing is the same vessel and voyage record you are building anyway, so adding the interface later costs no more than adding it now and it does not sit on the critical path to your first live call.
And bring your most experienced agent to the design sessions. The tariff knowledge that makes your agency worth appointing lives in that person's head, and extracting it is the single highest value activity in the project.
A worked example that adds up
A regional agency handling roughly 900 calls a year across four ports, with 14 principals and funds in advance held for most of them. Costed as a first release from our delivery experience:
- Discovery, tariff interrogation and rule capture across four ports: $16,000
- Tariff engine with versioned calculation rules and effective dating: $32,000
- Disbursement as one object moving through estimate, commitment and actual, with variance and reason codes: $30,000
- Appointment intake, vessel and voyage record, and generated port call task sets: $22,000
- Supplier invoice capture with document extraction, matching against commitments and an exception queue: $24,000
- Accounting integration, final account output and four weeks of hypercare: $18,000
That totals $142,000, delivered across 16 calendar weeks. It sits in the upper half of the first release band because four ports included one with an unusually layered extended stay tariff and because the accounting package involved a file based interface rather than an application programming interface. Reduce to two ports and defer task generation and the same core comes in nearer $95,000.
How the spend phases
Roughly a tenth of the first release goes on discovery, and in this category that means sitting with an agent and a stack of published tariffs until every scale, factor and minimum is written down. Resist the temptation to shorten it. A tariff modelled from a summary rather than the source is a reconciliation error that will surface a year later on every historical call.
The build then runs in two or three week increments, each ending with something an agent can open. Tariff engine first, because everything downstream depends on it, then the disbursement lifecycle, then invoice capture. Insist on producing a real proforma for a real upcoming call by week eight; that is the point at which your team stops describing the system and starts arguing with it, which is when the requirements get accurate.
Hold ten to fifteen per cent for hypercare. The first month live generates a queue of tariff corrections, because a published tariff and a port's actual invoicing behaviour are not always the same document, and you want budget available to fix those without a change request conversation. Additional ports, funds ledgers, statutory filing and the principal portal then become separately funded phases.
The ongoing costs nobody quotes
Plan on 15 to 20 per cent of the build cost each year, based on what our clients spend. Hosting is inexpensive here because volumes are low and the workload is bursty rather than sustained. The bulk is patching, dependency upgrades and a support arrangement.
The category specific running costs are tariff maintenance and interface drift. Ports revise tariffs, and someone has to update the rule version with the correct effective date so that historical reconciliations stay stable. That is a small recurring task and it is also the one that silently degrades the system if nobody owns it, so name a person rather than assuming it happens.
Single window implementations change their schemas. Accounting packages get upgraded. Document extraction quality drifts as suppliers redesign their invoice layouts, and the exception queue is your early warning that it has. None of these is expensive to handle in the month it appears. All of them are expensive to handle three years later at once.
Comparing a build against your current renewal
Add up what the current arrangement actually costs, not just the licence line. Your agency system subscription, the modules you pay for but do not use, the annual support fee, the internal hours your controller spends reconstructing funds positions per principal per call, and the variance you write off each year because you could not evidence it to a principal's cost controller.
That last figure is the one worth measuring before you decide anything. Take a quarter of final accounts, compare each against a recomputed expectation from the published tariff, and count the lines you could not defend. In our experience agencies are consistently surprised by it, and it is a far better basis for a build decision than a feature comparison.
Then look at where your current system's ceiling actually is. If your tariffs live in a flat rate table with one amount per service, every tariff revision quietly rewrites your history and variance analysis is unreliable by design. If you cannot produce a funds in advance position per principal per call without a spreadsheet, that is a data model limit rather than a configuration setting, and no amount of support tickets will move it.
When buying beats building
Do not build if you are a single port agency handling a couple of hundred calls a year with a handful of principals. A disciplined proforma template, a good accounting package and one experienced agent will beat anything you could afford at that scale, and we would tell you to put the money into staff. This is a genuinely small business and software will not change its economics.
Buy ShipNet or Softship if you need broad agency or liner functionality quickly across a network and your processes are close enough to their model that you can adopt rather than adapt. Both have real depth and rebuilding general agency and liner administration would be a poor use of your capital. If you are a shipping line rather than an agent and your problem is auditing incoming disbursement accounts at scale, Marcura DA-Desk is aimed precisely at that and is the sensible purchase; it does not run an agent's operation, and it is not trying to.
Build when you operate across several ports with different tariff regimes, when you serve enough principals that re-keying into their formats is a measurable cost, or when client money is large enough that your funds position needs to be knowable rather than reconstructable. The trigger is always the same: the difference between what should have been charged and what was charged is currently invisible.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
What is the total cost of custom port call and disbursement software?
A first release covering appointment through to a tariff driven proforma, supplier invoice capture with matching, and final account reconciliation with line level variance runs $70,000 to $160,000 over 12 to 18 weeks in Digital Heroes delivery experience. Adding funds in advance ledgers, principal approval workflows, multi currency settlement, statutory filing integration and a principal portal takes the total to $200,000 to $500,000 across 6 to 12 months.
The number of ports you model drives the figure more than call volume does. An agency handling 2,000 calls through three ports is a cheaper build than one handling 700 calls through twelve.
How much does a port call platform cost to run annually?
Budget 15 to 20 per cent of the build cost each year. Hosting is a small part of that because port call volumes are low and the workload is bursty; most of it is patching, dependency upgrades and support.
The costs specific to this category are tariff maintenance, which needs a named owner who updates rule versions with correct effective dates whenever a port revises its charges, and interface drift as single window schemas change and suppliers redesign their invoice layouts. Handled monthly these are trivial. Left for three years they become a rebuild.
How long before we can issue a proforma from the new system?
Twelve to eighteen weeks to a production first release, but you should be producing a real proforma for a real upcoming call by around week eight. That is a deliberate milestone rather than an optimistic one, because it is the point where your agents stop describing the process and start correcting the system, which is when requirements become accurate.
The schedule risk sits almost entirely in tariff modelling and supplier invoice capture. Agencies that start with their top three ports by call volume move considerably faster than those attempting the whole network at once.
Is DA-Desk cheaper than building our own agency system?
They solve different sides of the same problem, so a direct price comparison misleads. Marcura DA-Desk works on the principal's behalf auditing disbursement accounts at scale, which is genuinely useful if you are a shipping line with an internal port cost function.
It does not run an agent's operation. The agent still has to coordinate the call, order services, hold client funds, produce accurate proformas from local tariffs and file statutory declarations. If you are the agency, the comparison you want is against ShipNet or Softship, and the question that decides it is whether their tariff model supports versioned calculation rules with effective dates or a flat rate table.
Why is tariff modelling such a large share of the cost?
Because a port tariff is a set of formulas, not a price list. Tonnage dues on a scale, pilotage by length overall and draught with night factors, towage with minimum charges and berth dues per period all need modelling as versioned calculation rules with effective dates, so that a proforma for a call in three weeks uses the tariff that will be in force and a reconciliation uses the one that applied at the time.
Get that wrong and every tariff revision silently rewrites your history, which makes variance analysis meaningless. It is the single most valuable thing in the system and the reason the first port costs more than the fourth.
What is the cheapest useful version of this?
The tariff engine plus the disbursement lifecycle, at the bottom of the first release band. Model your busiest two or three ports as versioned rules, make the disbursement one object whose lines move from estimate to commitment to actual with a variance and a reason code, and attach the supporting supplier invoice to each line.
That alone converts principal disputes from a negotiation about trust into an argument about a specific line, and in our experience most of the disputes do not survive that treatment. Port call task management, funds ledgers and the principal portal can all wait for a second phase.
Should statutory single window filing be in phase one?
Usually not, unless a specific jurisdiction is already causing you delays or penalties. The vessel and voyage record that feeds a filing is the same record you are building for the disbursement, so adding the interface later costs no more than adding it now and it keeps a fixed external dependency off your critical path.
When you do add it, budget each jurisdiction separately. Each single window implementation has its own interface and validation rules, so two of them is two specifications rather than one and a half.
How do we cost the funds in advance module?
Treat it as its own phase with its own justification, because it is a ledger rather than a feature. It needs receipts, disbursements, exchange differences and returns recorded per principal per call, with the aggregate agency position available at any moment and underfunded calls flagged before the vessel arrives rather than after.
The value is operational rather than financial reporting. A supplier who is not paid does not attend, and a vessel delayed for that reason is a failure that has nothing to do with shipping. If that has happened to you even once, the module has a clear business case.
Who owns the tariff library if an agency builds our system?
You should own the repository, the cloud accounts and the tariff models, agreed in writing before kickoff. At Digital Heroes the client owns the code and the data from the first commit.
This is more consequential here than in most categories. The tariff models encode your accumulated local port knowledge and are more valuable than the code around them. A developer who wants to retain your tariff library as their own platform content is taking the asset that makes your agency worth appointing, so settle ownership and the export format before any modelling work starts.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
Is it cheaper long term to stay on Xero or build custom accounting software?
Xero stays cheaper as long as its workflows fit your business, since even its top plan costs around $1,000 a year and custom development starts around $25,000. The math flips once you stack add-ons: companies Digital Heroes scopes after they have bolted inventory, job costing, and approval apps onto Xero are usually paying more for the app stack and the labor of keeping five tools in sync than for Xero itself. Custom wins when the real cost is that labor and its errors, not the license fee.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
What are the biggest mistakes companies make when building accounting software?
The three we see most across Digital Heroes rescue projects: replacing everything at once instead of automating the most painful workflow first, skipping the parallel run so errors surface in live books, and letting developers design the ledger without an accountant reviewing the data model. A fourth is quietly expensive: no assigned owner for tax rate and compliance updates after launch. Every one of these is cheap to prevent and costly to unwind.
Should I hire a freelancer or an agency to build my accounting software?
A strong freelancer is fine for a reporting dashboard or one integration; anything that holds your books needs a team. Ledger software requires backend, frontend, QA, and accounting domain knowledge, and one person rarely covers all four while staying available for the 5 to 10 year life of the system. The most common rescue job Digital Heroes takes on is a solo-built ledger with no tests and no documentation after the freelancer moved on.
How much does custom accounting software cost for a small business?
Most small business accounting builds land between $25,000 and $75,000 for a working first version, while a full double-entry platform with invoicing, payroll, and reporting runs $100,000 to $250,000. Across 2,000+ projects at Digital Heroes, the biggest cost driver is how many external systems the software must connect to, not the accounting logic itself. A tool that automates a single painful workflow, like reconciliation or job costing, can come in under $20,000.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting 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 accounting 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 .
