Chassis Pool Management Software: Build or Buy at Your Unit Count
The line is your interchange agreements, not your unit count.
On this page
The line is your interchange agreements, not your unit count. If you run one pool under a single agreement with a few hundred units and your disputes are occasional rather than structural, buy: Blume Global plus your pool operator's portal plus a competent billing analyst is proportionate, and a build would be a hobby with a budget. Once you carry two or more agreements with materially different free time, suspension and chargeback terms, no visibility product settles the argument, because the argument is about your contracts rather than about where a unit is. A per diem engine alone starts at $45,000 to $85,000, and a full platform reaches $450,000.
When is off the shelf genuinely the right call here?
More often than an operator with a budget wants to hear. Blume Global is real infrastructure and it is strong at network level visibility across the intermodal ecosystem. If your question is where a unit is, it answers it, and it answers it across parties you have no other line of sight into. Your pool operator's portal covers the pool side. A billing analyst who knows your agreements covers the rest.
Buy, and commission nothing, if this describes you. A few hundred units. One pool. One interchange agreement, so free time, suspension days and repair chargebacks follow a single set of rules everybody already knows. Disputes that arrive occasionally rather than as a weekly workload. And an event picture that comes from one or two terminals whose data you already trust.
At that size the money is better spent on units. We tell operators this regularly and mean it, because a chassis pool build is priced on the number of parties whose data you have to accept rather than on the number of units you own, and a small operator with two feeds is buying a system that solves a problem they do not yet have.
There is a second and larger group who should keep buying part of the stack permanently. Network position data is genuinely hard to assemble and Blume has already assembled it. Rebuilding that layer is spending money to arrive where you already are. Operators who eventually build keep the visibility subscription, and that is a defensible architecture rather than a compromise.
When does a custom build actually pay off?
When two or more of these hold.
- You are the equipment provider or pool operator. That means you carry the maintenance and inspection obligation, so roadability is your liability rather than somebody else's status field, and the record has to be yours.
- You hold more than one interchange agreement with materially different per diem terms. Three free days measured in business days under one agreement and two measured in calendar days under another is not a setting. It is conditional logic that currently lives in an analyst's spreadsheet, unaudited and unversioned.
- Damage chargebacks are written off at a rate you would not comfortably quote to a board. Liability defaults to whoever keeps the worst records, and without a condition record attached to each handoff that party is you.
- Your event data arrives from more than three source systems that disagree. Terminal gate transactions, depot receipts, driver photographs and paper interchange receipts rarely agree on time and sometimes disagree on which unit.
- You are a drayage carrier large enough that per diem is a line item your finance director asks about by name. You are then building the defensive mirror image of the same system, for exactly the same reason.
Wanting better dashboards is not on that list. Ask whether the gap is a data model the product does not have, or a report it has not built.
How do they compare on the things that matter in this industry?
Five comparisons, and none of them are about maps.
What the system treats as the primary object. Visibility products and asset registers hold a chassis with a current location. A build holds the interchange event: unit, timestamp, location, counterparty, direction, source system and confidence. Conflicting events are stored side by side and resolved by a rule you set rather than overwritten. That distinction decides whether you flag a unit as contested before the invoice arrives or reconstruct its history six weeks after.
Per diem as rules or as a rate. Packaged tools model per diem as a daily rate multiplied by days. Real per diem carries conditional free time, suspension for terminal closures and congestion declarations, flip charges, street turn credits and thresholds. A build expresses each agreement as versioned executable rules with effective dates and computes from the event ledger, so every charge line carries its own derivation. When a carrier disputes, you send the derivation rather than a spreadsheet.
Where the condition record lives. Damage found at gate in is billed to the last recorded custodian. A build attaches condition to the interchange event itself, captured at the handoff, with fixed photo angles, timestamps, geotags and an append only store. The moment anyone can replace an image, every image becomes arguable.
Roadable against available. Most inventory systems conflate present, legally roadable and available to dispatch. A unit with an expired inspection or an open repair order is present and unavailable, and sending a driver for it costs a wasted turn plus a detention claim.
Position derived or position reported. Balancing a pool from reported inventory is planning from feel. Derived position, split by roadable and non roadable, is a different instrument.
What does total cost of ownership look like at your scale?
Three project shapes, and they separate on how much of the physical operation you pull into the record.
The narrow build is a per diem engine on top of event data you already receive: versioned agreement rules, a derivation on every charge line, and comparison against the invoices you are billed. That is $45,000 to $85,000 in 8 to 12 weeks in Digital Heroes delivery experience, and it is the right size when your disputes are about calculation rather than custody. The focused first release adds the interchange event ledger with multi source ingestion and conflict handling, plus the damage evidence trail with a driver capture application, at $80,000 to $160,000 over 12 to 18 weeks. The full platform adds depot and repair order workflow, roadability status resolving into one availability answer, pool balancing, carrier self service and billing integration, at $200,000 to $450,000 phased over 7 to 12 months.
An equipment provider running roughly 6,200 units across two port complexes, with four agreements and five data feeds, landed at $152,000 over sixteen weeks for the first release. Hold on to one number from that build: ingestion was $24,000 for five feeds, and additional feeds run $4,000 to $9,000 each. It scales close to linearly, which is how a $152,000 project becomes a $230,000 project when someone adds four terminals in week nine.
Running cost is 15 to 20 percent of build annually, plus lines nobody quotes. Photo storage grows rather than sits flat, and a fleet of that size turning three times a week produces close to a million interchanges a year. Electronic data interchange mailbox fees accumulate quietly per trading partner. Hosting is $600 to $2,000 a month before images. Agreements change mid year and each change is a new rule version while old periods must still compute as they did then.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In this category the hybrid is not a compromise, it is the architecture most operators should end on.
Keep Blume Global for network position data. It answers where equipment is across parties you cannot see into, and that capability is expensive to reproduce. Then build only what the agreements require: the interchange event ledger with conflict retention, the per diem rules engine with a derivation on every line, and the condition record captured at handoff. The packaged product tells you where the unit is. Your layer tells you who owes whom and why, which is the part your invoices depend on.
A smaller hybrid exists for operators not ready to fund the ledger. Build the per diem engine alone against the event data you already receive, at $45,000 to $85,000. The catch is worth stating plainly: an engine computing from contested events produces confident wrong answers faster. If two sources routinely disagree about which carrier had a unit, the ledger has to come first and the narrow build is the wrong purchase.
The hybrid also stops being honest when a terminal will only give you a portal. Screen scraping a terminal portal is a maintenance liability with no owner. Negotiate a file before you build a parser, and treat that as a commercial conversation you start before signing a build contract.
Which should you choose, by operator size and stage?
- Under roughly 500 units, one pool, one agreement. Buy. Blume Global, your pool operator's portal and one competent analyst. Spend the difference on units.
- A few thousand units, one pool, one agreement, disputes rising. Buy the visibility layer and build the per diem engine only, at $45,000 to $85,000, but confirm first that your event data is reliable enough to compute from.
- Equipment provider or pool operator with two or more agreements. Build the focused first release. Ledger, per diem rules and the driver capture application. This is the highest value project in the category and it is where the leakage actually sits.
- Multiple port complexes, nine or more depots, telematics on units. Build the full platform, phased, and start with one port complex, one pool and your five counterparties by dispute volume. That covers most of the money and all of the arguments before you widen.
- Large drayage carrier paying per diem rather than billing it. Build the defensive version. Your evidence requirement is identical and your write offs are somebody else's revenue.
One discipline regardless of size. Before anyone quotes you, agree in writing which terminals and depots will send you data, in what format and under whose authority. That is the schedule risk in this category, it is commercial rather than technical, and every feed added after kickoff is a change request with a price attached.
If you would rather someone argued with your brief than agreed with it, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- Independent reporting of Gartner's 2025 survey confirms 59% of finance leaders use AI, up from 37% in 2023, with error and anomaly detection (34%) and accounts payable automation (37%) among the leading use cases. Source: CPA Practice Advisor (reporting Gartner) (2025) →
Frequently asked questions
What does it cost to switch off Blume Global or a pool operator portal?
In most cases you should not switch off the visibility layer at all. The hybrid keeps it for network position data and builds the agreement and liability layer alongside, so there is no migration to fund.
Where switching cost genuinely bites is your own accumulated record. Before signing anything, confirm what a full export contains and whether historical events leave with their source and timestamp intact. Value in intermodal accrues in years of event history and rule versions, and a dispute about a period you cannot reconstruct is a dispute you lose.
What happens if our pool operator or visibility vendor changes its pricing?
Model it on your unit growth rather than today's fleet, because per unit or per trading partner components rise exactly when your operation is expanding and capital is committed elsewhere.
The practical defence is portability. Secure written confirmation that you can export gate and interchange records in a documented structured form on demand. An operator whose own ledger already holds every event in a defensible form is negotiating from a different position at renewal, and that is a benefit of the build that rarely reaches the business case.
How long does a chassis interchange and per diem system take to build?
Twelve to eighteen weeks for a focused first release: three to four weeks of discovery, nine or ten weeks of build, and three to five weeks of reconciliation and acceptance. A per diem engine alone is 8 to 12 weeks.
The schedule risk is almost never engineering. It is agreeing data access with terminals and depots, which is a commercial conversation with several parties. An operation already receiving electronic gate activity messages moves months faster than one starting from emailed interchange receipts, so start those conversations before you sign a build contract.
Is Blume Global enough, and where exactly does it stop?
It is strong at network level visibility across intermodal and worth keeping regardless of what else you do. It answers where a unit is, across parties you have no other way to observe.
What it does not hold is your specific pool agreements: conditional free time measured in business or calendar days, suspension for terminal closures, flip and street turn credits, and repair chargeback matrices negotiated per counterparty. If your disputes are about those terms rather than about location, no visibility product will settle them, because the disagreement is contractual.
Do we need the driver capture application, or can depots record everything?
You need it if you want to win damage disputes. Depots and terminals only observe the unit at their own gate, which leaves every yard move, street turn and shipper drop unrecorded, and those gaps are exactly where liability is argued.
Budget $22,000 to $35,000 inside a first release. The cost is offline behaviour rather than screens, because marine terminal lanes routinely have no signal and capture must queue locally, survive a reboot and sync without duplicating. Keep the interaction to a fixed photo sequence and a two tap confirmation, since a skipped capture is worse than no application at all.
How much does adding another terminal or depot cost?
Roughly $4,000 to $9,000 per feed once the ledger exists, depending on whether the counterparty sends a structured electronic gate activity message or a file whose columns change without notice.
Keep that number in front of you during scoping, because it scales close to linearly. A project sized around five feeds becomes a materially different project when four more terminals are added mid build, so agree the feed list in writing and treat additions as change requests rather than absorbing them.
Will a build recover money, or only organise information?
It stops future leakage rather than reclaiming past leakage, and the payback should be modelled on forward volume only. The recoverable amounts sit in per diem charged on days that should have been suspended, damage chargebacks written off for want of a condition record at handoff, and units billed to a carrier that never took custody because a gate read a plate wrong.
None of those are recoverable retroactively without evidence you did not capture. Anyone promising retrospective recovery is selling you something the records cannot support.
Who owns the code and the event history if we build?
You should own the repository, the cloud accounts, the photo store and the unrestricted right to hire another firm, agreed in writing before kickoff rather than at handover. At Digital Heroes the client owns the code from the first commit.
This matters more than usual in intermodal because the asset is the history. If you cannot export the event ledger and the versioned agreement rules in a usable form, you cannot defend a dispute about a period that predates whatever you move to next, and that exposure outlives any commercial relationship.
When is SAP actually a better choice than building custom supply chain software?
Choose SAP when you need a full ERP, operate in a heavily audited industry that expects standard systems, or run global operations where localization, tax, and compliance content matter more than workflow fit. SAP's strength is breadth: finance, manufacturing, and supply chain in one validated suite. Custom wins when your edge lives in a specific workflow, like how you allocate inventory or route orders, that SAP would force you to bend to its standard process. Many Digital Heroes clients keep SAP as the system of record and build custom operational tools around it.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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 are the biggest mistakes companies make on supply chain software projects?
The top three: replacing every system at once instead of one workflow at a time, skipping data cleanup so the new system inherits years of bad SKUs and phantom stock, and designing screens without the warehouse staff who will use them daily. A fourth is underscoping integrations and discovering mid-project that the ERP connection is half the work. Digital Heroes sees more supply chain projects fail from scope and data problems than from any technical cause.
How much does custom supply chain software cost for a small business?
For a small business, a focused custom supply chain tool usually lands between $15,000 and $45,000, covering one core workflow like inventory tracking, purchase orders, or shipment visibility. Across 2,000+ delivered projects, Digital Heroes sees most small distributors and light manufacturers start in the $20,000 to $35,000 range for a first working version. Adding barcode scanning, multi-warehouse support, or carrier integrations pushes budgets toward $50,000 and up.
Is custom supply chain software cheaper than SAP over five years?
For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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
More from Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
