---
title: "What Custom Logistics Software Actually Costs in 2026: The Drivers Nobody Quotes You"
date: 2026-09-10
author: "Tobias Rast"
featured_image: "https://static.pegotec.net/uploads/2026/08/logistics-software-cost-drivers-2026.webp"
categories:
  - name: "Pegotec News"
    url: "/category/news.md"
---

# What Custom Logistics Software Actually Costs in 2026: The Drivers Nobody Quotes You

Ask what a transport management system costs and you will get a range with no arithmetic behind it. Your vendor is not necessarily avoiding the question. Neither SAP nor Oracle publishes license pricing for their logistics products, and contracts keep the actual numbers under non-disclosure. So this article takes a different approach. It uses published logistics software cost data from government contract awards and works backward to identify the cost drivers you can actually negotiate.

## The two ratios everyone quotes trace back to nothing

Two figures dominate every buying guide. First, “implementation runs one to three times the first-year license.” Second, “licensing is only 20–30% of total cost, implementation 50–70%.”

We went looking for the origin of both. Neither traces to a primary source. The percentages vary across retellings, and each citation points to another blog rather than to a study, a filing, or a contract. Consequently, treat them as folklore rather than benchmarks.

The same applies to per-user TMS prices circulating for vendors who publish none. If a figure has no disclosed sample and no named buyer, it is a guess wearing a decimal point.

## One real itemized quote, and what it exposes

Public bodies publish what private buyers cannot. In one fully itemized US municipal award, the vendor’s professional services line was 4.6 times the one-time license line: $378,000 in services against $81,681 in license fees.

The more useful detail is the discounting. That license was cut 75.5% from a $332,939 list price. Meanwhile, the $378,000 services line carried **no discount**.

Read that asymmetry carefully, because it tells you where the margin lives. Vendors discount the line you fixate on and hold firm on the line you under-scrutinize. Therefore, negotiate the services rate card and the hour count, not the headline license.

That services figure is decomposed into 1,632 billable hours at published rates — including project management at $200 per hour and onsite implementation at $225 per hour. Notably, an hours-and-rates breakdown is something you can actually challenge.

## What published awards say about scale.

Real contract values give you anchors that vendor ranges do not.

- **Small, genuinely off-the-shelf.** Gateshead Council awarded a £266,310 contract, excluding VAT, over four years for an explicitly “out-of-the-box” passenger transport system covering 774 passengers. That works out to roughly £86 per passenger per year, including implementation, because the project required no customization.
- **Mid-scale replacement.** Helsinki-region city transport awarded €3,556,000 for a transport management system in early 2026.
- **Integration-heavy.** Uppsala municipality awarded SEK 10,000,000 for warehouse and logistics flow support that had to integrate with two named incumbent systems.

The Gateshead number is the useful floor. Additionally, it came in 16.8% below the council’s own pre-tender estimate, based on seven bids. Anything far above that floor is buying customization, integration or scale — so make the vendor say which.

## Run cost dominates build cost.

Here is the driver most business cases understate. Across 24 major US Department of Defense business IT programs, operations and sustainment consumed **69%** of planned spend, compared with 31% for development and modernization — a run-to-build ratio of roughly **2.2 to 1,** on a portfolio averaging 16 years old.

One system in that portfolio makes the point vividly. The Defense Logistics Agency’s warehouse and distribution system, first invested in during 1992, was still consuming about $157 million a year while formally in sustainment — with officials reporting no new functionality in development.

Consequently, the model run cost is roughly twice the build cost over the asset’s life. If a five-year total-cost projection puts sustainment below half the total, ask which year of the curve it describes.

## Customization is the named overrun mechanism.

In that same portfolio, 12 of 24 programs reported cost increases since January 2023, ranging from $6.1 million to $815.5 million with a median of $173.5 million. Seven reported delays of three to 48 months, median 15 months.

Crucially, additional customizations drove the largest single increase — $815.5 million for a maintenance and overhaul program. Officials also extended the schedule by 15 months to accommodate those customizations.

That is a named mechanism, not a euphemism for poor management. Therefore, fix a customization budget and a change-control gate before signing. Furthermore, treat every “we can configure that” answer in a demo as a future change order until someone shows you the configuration screen.

## The integration surface is where estimates break.

Logistics software is rarely expensive because of logistics. It is expensive because of everything it must talk to.

The Helsinki requirement included transferring working-time events into payroll and interpreting them in accordance with the local collective agreement. No transport system comes with every country’s labor law already encoded. Similarly, Uppsala’s solution had to reconcile an e-procurement platform with a finance ERP, while a separate system handled warehouse picking.

Accordingly, count your integration endpoints before comparing license quotes. Each one carries build, test, and permanent maintenance costs.

## Your vendor sets your replacement clock

One detail from the Helsinki award deserves separate attention. The stated trigger for procurement was not a business case. It was the incumbent vendor announcing that support for the existing system would end.

That is the normal pattern. Consequently, price-forced-move risk into any long license commitment, and ask for the vendor’s published support-lifecycle policy before you sign, rather than after.

## What to ask before you compare quotes

1. **Show the services line as hours and rates.** A lump sum cannot be challenged; 1,632 hours at a published rate can.
2. **What is the discount on each line?** If the license is heavily discounted and services are not, you are negotiating the wrong number.
3. **How many integration endpoints are there, and who owns each?** Payroll, finance, carriers, customs, telematics.
4. **What is year-five run cost?** Assume roughly twice build across the life, then check their model against it.
5. **Which requirements are configuration and which are** customization**?** Ask for the demo, not the assurance.
6. **What is the published support-lifecycle policy?** That date, not your roadmap, sets your replacement clock.

## Where custom build changes the maths

Custom build removes the license line and the customization-versus-configuration argument. However, it does not remove the two costs that actually dominate: integration and run.

Therefore, build is usually right when your operational model genuinely differs from the packaged assumption, and wrong when you are paying to rebuild a commodity. Our [Build vs Buy](https://pegotec.net/build-vs-buy-when-custom-software-makes-sense/) framework works through that decision in general terms.

## A note on these numbers

Every figure above comes from a published contract award or government audit report, and we checked each one against its primary source. Notably, we excluded the widely quoted ratios precisely because we could not trace them back to a reliable source.

Public-sector awards tend to be larger and more procedural than commercial deals. Consequently, use them as structure and ratio, not as a price list for your own tender.

## How Pegotec helps

We build logistics and operations software for industry and government across Southeast Asia, so we scope the integration surface and the run cost before we quote a build. Furthermore, we will tell you when a packaged product is the better answer.

If you are comparing quotes and the numbers will not reconcile, [talk to us](https://pegotec.net/contact-us/).

## FAQ

**How much does a transport management system license cost in 2026?**Neither SAP nor Oracle publishes license pricing for their logistics products, and contracts keep the actual figures under non-disclosure. Therefore, any published range for those products relies on estimates without a disclosed sample. Published government awards provide better anchors. One government contract awarded £266,310 excluding VAT over four years for an off-the-shelf passenger transport system serving 774 passengers. That equals roughly £86 per passenger per year, including implementation. Mid-scale replacements can cost millions once they require integration.

 

**Is implementation really one to three times the license cost?**That ratio is repeated everywhere, but we could not trace it to any primary source — no study, filing, or contract, only other blogs citing one another. The same is true of the claim that licensing accounts for 20-30% of total costs. What is verifiable comes from itemized public awards: in one fully itemized municipal quote, the professional-services line was 4.6 times the one-time license line, $378,000 against $81,681. Use itemized awards rather than circulated ratios.

 

**Which line of a software quote should you actually negotiate?**The services line. In one itemized public award, the license was discounted 75.5% from a $332,939 list price down to $81,681, while the $378,000 professional-services line carried no discount at all. Vendors discount the line buyers fixate on and hold firm on the line buyers under-scrutinize. Ask for services as hours and rates rather than a lump sum — that award decomposed into 1,632 billable hours at published rates, which is something you can challenge line by line.

 

**What actually causes logistics software projects to overrun?**Customization, named explicitly. Across 24 major US Department of Defense business IT programs, 12 reported cost increases since January 2023, ranging from $6.1 million to $815.5 million (median $173.5 million), and 7 reported delays of 3 to 48 months (median 15 months). The largest single increase, $815.5 million for a maintenance and overhaul program, was attributed by officials to additional customizations, with the 15-month delay explicitly intended to accommodate them. Fix a customization budget and a change-control gate before signing.