Who can develop a TMS on demand for a transport company in the Netherlands?
There are roughly three types of parties that do this. First, domain-specific logistics software companies: they speak the language of the sector, but often deliver a configurable package that they 'tailor to your needs' rather than genuinely rebuilding from scratch. That is not necessarily bad, but it is a different thing from custom development. Second, generic custom developers: they build what you ask for, but sometimes lack the domain knowledge to translate your processes accurately into a system that still holds up three years from now. Third, software operating partners: parties that build the system entirely from scratch, with AI embedded at the core, and then remain responsible for running it in production. Bonsai falls into this last category. We build domain-specific core systems, including TMS, entirely from scratch for transport companies where off-the-shelf packages no longer fit. The client becomes the owner of the code, the data, and the system.
When is a configurable package better than fully custom development?
The honest outcome of a good conversation is sometimes: you do not need custom development. A configurable TMS package is a good fit when your processes are relatively standard, your fleet is under thirty vehicles, and you have no unusual integrations with client or government systems. If you also want to get started quickly and are willing to adapt your way of working to the package, custom development is over-engineering. Custom development becomes the smarter choice when you recognize one or more of the following: your operation has unique route structures, pricing agreements, or contract forms that no package handles well; you need multiple transport modalities or combinations of road transport, refrigerated transport, and hazardous goods in a single system; you want deep integration with client portals, on-board computers, customs software, or your own warehouse systems; or you are a mid-sized to large carrier where the licence costs of a standard package will eventually exceed the cost of a one-time build.
What does a custom TMS cost and how long does it take?
This is the question that other pages on this topic consistently avoid. Broad market indications for custom development in the Netherlands: a working MVP with the core functions (order management, planning, track-and-trace, invoicing integration) typically falls in the range of 50,000 to 150,000 euros with a lead time of three to six months. A fully featured enterprise TMS with multiple modalities, a client portal, proprietary on-board computer integration, and a reporting layer can quickly run to 200,000 to 500,000 euros with a lead time of twelve months or more. The range is wide because the complexity of integrations and the volume of exception logic in transport varies enormously from one company to the next. Ask every party for a detailed milestone plan with go/no-go moments, so you do not discover eight months in that the scope has expanded.
5 questions to ask a potential development partner
Before you sign, you want answers to these five questions. One: will I own the source code and the data, or will I be tied to your hosting after delivery? Red flag: a vague answer or 'we will sort that out later'. Two: have you previously built a TMS for a carrier with comparable modalities and client structure? Ask for a reference you can call yourself. Three: how are your milestones structured and what are the go/no-go criteria for each phase? Red flag: a single delivery at the end. Four: who manages the system after go-live and what are the costs? Red flag: the development partner has no operations team and refers you to third parties. Five: how do you capture and validate my domain logic, such as exception rates, specific client agreements, and regional regulations? Red flag: 'you fill that in yourself through the configuration'.
When does Bonsai fit and when does it not?
Bonsai fits when you are a mid-sized to large transport organisation where standard packages have become too rigid, your integration needs are complex, and you want to own what is being built. We build AI-native: not as a marketing claim, but because we embed order intake, document processing, and planning support at the core of the system. We work with milestones and go/no-go moments, and the client always owns the code and the data. Bonsai is not the right fit if you are looking for a standard planning solution quickly, your budget is below 50,000 euros, or you primarily want to configure an existing package. In those cases we would rather refer you elsewhere than start a project that is not the right match. For companies that do not want to replace their core system but do want to automate specific processes, such as order intake or document processing, we also offer AI Workers as a standalone layer on top of existing systems.