How to Hire a Demurrage and Detention Software Development Company
Hire a partner who buys container event data and spends your budget on the obligation model instead.
On this page
Hire a partner who buys container event data and spends your budget on the obligation model instead. Expect $60,000 to $130,000 for free time clocks, last free day alerting and an evidence log, rising to $150,000 to $350,000 for per-carrier tariff modelling, dispute packet generation and daily accruals. The deciding question is simple: where does their clock start, discharge or availability.
Buying demurrage software is like buying a stopwatch for a race that started before anyone told you it was running. The terminal starts your clock on its data and stops it on its data, you receive both late, and the invoice that lands six weeks later is the first time most of the numbers become visible. By then the only thing left to argue about is evidence you did not know to collect.
This category is hard to buy because the thing you need is not a tracking product, and almost everything on the market is a tracking product. Container visibility tells you the state of the box. It cannot tell you the state of your obligation, because free time is a term of your service contract rather than a fact about the port: how many free days that carrier owes you on that trade, whether weekends and holidays count, whether demurrage and detention run concurrently, sequentially or merged, and what the accrued liability is in dollars this morning. That information lives in PDFs in a procurement folder. Meanwhile the charges are a few hundred dollars per container per day, so one congested week across a few hundred boxes becomes a number your finance director asks about by name.
What a demurrage and detention software development company actually does
The dashboard is the easy half. The work that decides whether the system recovers money looks different.
A capable partner creates the container record at booking or bill of lading issue rather than at arrival notice, so the clock is computed from events instead of typed in after a day of free time has already gone. They model free time as a versioned rule per carrier, per contract and per trade lane with effective dates, so a charge from March is evaluated against the terms that applied in March. They build evidence capture that records what the system saw at the time it saw it: every appointment search, every failed booking, every empty return restriction, timestamped and attached to the container, because a screenshot taken today proves nothing about a terminal state from last month. They make ingestion idempotent, since a terminal feed that goes quiet for six hours and then delivers its backlog is the normal condition here rather than an edge case. And they post a daily accrual into the dimensions your finance team already uses, so the invoice becomes a reconciliation rather than a surprise.
What it really costs in 2026
These are Digital Heroes delivery bands, and they assume you are buying container event data from a visibility provider rather than building terminal scrapers.
| Project tier | Cost | Timeline |
|---|---|---|
| Container records at booking, event ingestion, computed free time clocks, last free day alerting, evidence log | $60,000 to $130,000 | 10 to 14 weeks |
| Adds per-carrier tariff and contract modelling with effective dates, plus invoice checking | $110,000 to $220,000 | 4 to 7 months |
| Full platform with appointment attempt capture, dispute packet generation, daily accruals and cause analytics | $150,000 to $350,000 | 6 to 10 months |
| Maintenance, new carriers and new lanes | 15 to 20 percent of build per year | Retainer |
Two line items are missing from nearly every quote. The first is assembling your own service contracts. Free time terms cannot be modelled until somebody produces the current set with every amendment, and in most importers those documents are scattered across procurement, logistics and legal with nobody certain which version is live. That is two to four weeks of your team's time before engineering can start, and it is the most common reason these projects slip. The second is drayage partner integration, which is a project per partner and a commercial negotiation before it is an engineering task. Your carrier's dispatch system holds better records of failed appointments than you do, and whether you get a structured feed or an emailed narrative is decided by your commercial relationship, not by your developer.
Signals of a strong partner
- They tell you not to build container tracking. Terminal integrations break constantly and maintaining them has no competitive value. Buying the event feed and building the obligation model on top is almost always the right split.
- They distinguish demurrage from detention in the data model. One relates to the box sitting at the terminal, the other to your holding of the equipment, and they are separate meters against the same container.
- They ask which ports and terminals you touch. Every terminal exposes data differently and some expose almost nothing, so the answer changes both scope and honesty of the estimate.
- They design for late and duplicate events. Idempotent ingestion is not a nicety here. Without it your accrual drifts and nobody notices until a claim is adjusted.
- They treat the dispute as a generated packet. Container, tariff applied, contract terms, event timeline, attempt log and the specific days contested with a reason for each, produced in week one rather than assembled by hand in week four.
- They ask about your finance dimensions. Accrual by site, supplier, carrier and cause is what changes behaviour, and it only works if it lands in the structure your controllers already report on.
Red flags
- They propose scraping terminal websites. That is a permanent maintenance cost with no upside, and it will be broken during your first peak season.
- Free time is a number in a settings page. Terms vary by carrier and change mid-year, so a single configurable value guarantees you evaluate historic charges against the wrong rules.
- Evidence is captured on request. Storing a screenshot when someone remembers is not evidence. The system has to record automatically at the moment of observation.
- The clock starts at arrival notice. That is when your team learned about the box, not when the tariff started counting, and the gap is exactly the free time you are trying to protect.
- They quote before asking about your carrier mix. Every contract structure is its own rule set, so a number produced without that count is a placeholder.
Questions to ask on the first call
- Where does the clock start in your model, discharge or availability, and how does that vary by tariff?
- Show me how you would represent a carrier changing free time terms mid-year without corrupting last quarter's charges.
- A terminal feed is silent for six hours then uploads a backlog. What stops the accrual double counting?
- How does the system capture a failed appointment search so it is still usable as evidence in four months?
- Which visibility provider would you integrate, and what would you refuse to build yourself?
- How do you model merged demurrage and detention against a container that also has separate storage charges?
- Walk me through the dispute packet you would generate, field by field.
- What dimensions do you post the daily accrual against, and who signs off that mapping?
- Who owns the evidence archive, and can we export it in full if we change developer?
A simple way to decide
Rather than comparing three proposals written against three different assumptions, buy a paid discovery phase of two to three weeks and insist that the output is a written specification you own: the obligation model with free time expressed as versioned rules, an inventory of your carriers and terminals with what each will actually give you, the evidence events to be captured and where they come from, the dispute packet layout, the accrual mapping agreed with finance, and a fixed quote against that scope. Take it to every firm on your shortlist. If a vendor will not sell you the thinking separately from the build, that tells you what the build will be like.
Digital Heroes works PRD-first for that reason, and contracts through India LLP, US LLC and UK LTD entities so intellectual property assigns under your own jurisdiction's law. In this category insist on owning the evidence archive outright as well as the code, because it is the asset that wins disputes two years from now.
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.
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
Frequently asked questions
How much does it cost to hire a demurrage and detention software developer?
A focused first release with container records created at booking, event ingestion from a visibility provider, computed free time clocks with last free day alerting and an evidence log runs $60,000 to $130,000 over 10 to 14 weeks. A full platform adding per-carrier tariff modelling, appointment attempt capture, dispute packet generation and daily accrual posting runs $150,000 to $350,000 across 6 to 10 months.
Should the developer build container tracking or buy it?
Buy it. Terminal and carrier integrations break constantly, maintaining scrapers across dozens of terminals is a permanent cost with no competitive value, and providers already sell the event feed cheaply. Spend the engineering budget on the obligation model, evidence capture and the dispute engine, which nobody sells and which are the parts that recover money. A vendor who proposes building tracking is quoting you a maintenance liability.
What preparation does the buyer have to do before the build starts?
Assemble your current service contracts with every amendment, and confirm which version is live for each carrier. Free time terms cannot be modelled until that exists, and in most importers the documents are spread across procurement, logistics and legal. Budget two to four weeks of internal effort before engineering can begin. This is the single most common reason a demurrage project misses its first milestone.
How do we know a vendor understands demurrage rather than logistics generally?
Ask where their clock starts. If they cannot immediately discuss discharge versus availability and why the distinction changes per tariff, they will count from the wrong event and every figure the system produces will be right only by accident. Follow up by asking how free time is modelled. You want a versioned rule per carrier and contract with effective dates, not a configurable number.
Who should own the evidence archive when an agency builds this?
You should, alongside the repository, the cloud accounts and the right to hire another firm, settled in writing before kickoff. At Digital Heroes the client owns the code from the first commit. Evidence matters as much as code in this category, because a dispute filed today may rely on a terminal state observed two years ago, and an arrangement where a vendor holds those records is a dependency you cannot afford.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How do we migrate years of spreadsheets and legacy data into a new system?
Migration runs as its own workstream: extract and profile the data, clean duplicates and dead SKUs, map fields to the new schema, then do trial loads and a final cutover during a weekend or slow period. Expect 2 to 6 weeks depending on how many sources you have and how dirty they are. Digital Heroes runs old and new systems in parallel for 2 to 4 weeks on most supply chain cutovers so inventory counts and open orders can be reconciled before the legacy system is retired.
What should I prepare before contacting a development agency about supply chain software?
Bring a written list of your workflows from purchase order to delivery, the systems each step touches, and the 3 to 5 pain points costing you the most hours or errors. Export a sample of your real data, SKUs, orders, and locations, because data shape drives half the design decisions. You do not need a formal spec; Digital Heroes scopes most supply chain projects from a two-page problem description plus screen-share walkthroughs of the current process.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Why do companies replace generic SCM software with custom systems?
The usual trigger is workflow mismatch: generic SCM tools model a standard distributor, so anything unusual, like mixed lot and serial tracking, consignment inventory, or customer-specific routing rules, ends up managed in spreadsheets beside the system. Companies also leave when per-user pricing punishes growth or the vendor's API cannot support needed integrations. In Digital Heroes projects, the number of spreadsheets living around the official system is the most reliable signal a team has outgrown its off-the-shelf tool.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Should we start with an MVP or build the full supply chain platform at once?
Start with an MVP that fixes your single most expensive workflow, prove it in daily operations, then expand module by module. That gets working software onto the warehouse floor in about 12 weeks instead of debating a year-long spec, and real usage always reorders the roadmap; features that felt critical in planning routinely get cut after go-live. Digital Heroes typically scopes phase one at 30 to 40 percent of the total vision and lets measured results justify each next phase.
Who owns the code when an agency builds my supply chain software?
You should own it outright, with full IP assignment on payment written into the contract, and you should walk away from any agency that only licenses the software to you. Insist on the code living in a repository under your own GitHub or GitLab account from day one, not handed over at the end. Digital Heroes contracts assign all custom code, database schemas, and documentation to the client; the only carve-outs should be clearly listed open source libraries.
What tech stack is best for custom supply chain software?
Boring and mainstream wins: a typed backend such as Node with TypeScript, Python, or C#, PostgreSQL for transactional inventory data, a React web frontend, and hosting on AWS, Azure, or GCP. Real-time needs like scanner feeds or live shipment tracking add a message queue such as Redis or RabbitMQ. Be wary of any agency pitching an exotic stack; in Digital Heroes handover work, systems built on niche frameworks are consistently the hardest and most expensive for a new team to take over.
What does it cost to maintain custom supply chain software each year?
Budget 15 to 20 percent of the original build cost per year, so roughly $9,000 to $12,000 annually on a $60,000 system, covering hosting management, dependency updates, bug fixes, and small enhancements. Across its maintenance contracts, Digital Heroes sees supply chain systems need more upkeep than typical web apps because carrier APIs, EDI specs, and ERP versions keep changing underneath them. Hosting itself is usually minor, often $100 to $500 per month for a mid-size operation.
Who can build a custom supply chain software system?
Digital Heroes builds custom supply chain 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 supply chain 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 .
