Buy when a packaged system fits most of how you work and its cost grows more slowly than your business. Build when your process is part of why customers choose you and packaged software can't represent it, or when workarounds and licence costs outweigh the cost of owning your own system. Buying the core and building around it is often the best option, and it keeps a full replacement open for later.
Who publishes build vs buy advice
Software vendors tend to argue for buying. One vendor's guide says that for most forwarders, buying purpose-built software delivers faster returns than custom development (GoFreight). Development firms tend to argue for building. Either answer can be right, depending on which of the signals below apply to your business.
The signals that matter
| Signal | Points to buying | Points to building |
|---|---|---|
| Process | Standard services handled in standard ways | Specialist services or customer-specific workflows that win business |
| Cost curve | Licence cost grows slower than margin | Per-job or per-user fees grow faster than margin |
| Workarounds | Few, and shrinking | Spreadsheets, rekeying, and side systems in every team |
| Customs footprint | Many countries, need coverage now | A defined set of countries you can connect directly or through partners |
| Data and AI | Vendor's built-in reporting and AI are enough | You want to own your data layer and choose your own AI |
| Roadmap | Vendor priorities line up with yours | The capability that sets you apart isn't coming |
| Ownership capacity | No appetite to own a system | Willing to own it, with a partner hosting and supporting it |
The third option: buy the core, build around it
Most forwarders don't need to choose all or nothing. Keep a packaged system for the core transactions and build your own layer for the pieces that differentiate you: quoting, customer experience, reporting, document automation, and AI. Those pieces connect to the core through its integration interfaces and carry over if you replace the core later. See building on top of CargoWise vs replacing it.
The costs people miss
When you buy
- Implementation, configuration, and consultants.
- Staff time spent on workarounds the system doesn't cover.
- Price changes you don't control. The CargoWise move to per-job Value Packs in December 2025 is a recent example (our guide).
- Upgrade disruption and retraining.
When you build
- Discovery: turning operators' knowledge into something developers can build from is the hard part (The Loadstar, reader commentary).
- Ongoing maintenance. One vendor puts it at 15 to 20 percent of the original build cost each year (GoFreight).
- Hosting, monitoring, security, and support.
- Migration, parallel running, and an archive for historical records.
A five-question check
- Would a customer notice if you ran your process the way the software expects? If yes, your process is an advantage worth protecting.
- What is your software cost per job today, and in three years at your growth plan?
- How many hours a week go into work outside the system?
- Who will own the system, and do you want a partner to host and support it?
- Can you start with one piece rather than the whole system? If yes, build around the core first.
How we approach it
We aren't tied to any one packaged system, so we have no reason to push one answer. Every engagement starts with a short diagnosis that puts costs and risks against each option: fix the process on the system you have, build around it, or replace it. We then deliver the option the diagnosis supports.
Common questions
Is building always more expensive than buying?
Upfront, usually yes. Over several years it depends on your volume, the pricing model of the system you would buy, and how much work currently happens outside it. Our cost guide includes a simple calculator for your current costs.
Do we need an in-house IT team to build?
No. We build, host, and support the system, and can keep supporting it for as long as you choose. If you would rather bring it in-house later, we hand it over and train your team.
What is the lowest-risk way to start?
Build one piece around your existing system, such as quoting or a customer portal. You get value quickly, learn how a build works, and the piece carries over if you later replace the core.