What exactly does a transport software partner do?
A transport software partner takes over the role of an in-house software team for transport companies that don't have one. In practice: a strategic roadmap for your software portfolio, building and maintaining custom TMS components, customer portals and driver apps, integrations with telematics, accounting and customs systems, and advice on vendor choices. The aim is for you to have one permanent point of contact for everything software-related, instead of a new supplier for every topic. A partnership also covers things that aren't projects: thinking along on a security incident, carrying out a technical due diligence on an acquisition, evaluating a telematics supplier, or advising a management team on an AI experiment. The difference from hiring an agency lies in continuity and context: after a year, we know how your planners think and which compromises have been made over time.
Do you replace Transwide, Pionira or Centric Distributievloer?
No, not if those packages work well for what you use them for. Standard TMS packages are usually the right choice for commodity functionality such as administration, trip registration and standard planning. We build on top of them, integrate with them and extend them: customer portals, mobile apps, custom planning, integrations with your other systems. We only replace a package when it structurally no longer fits your operation, when the supplier ceases to exist, or when annual licence costs and integration restrictions outweigh the cost of building your own. In most cases, the honest conclusion is that a healthy mix works best: a standard TMS for the accounting core, and your own software for what sets your business apart.
What is the difference from a staffing agency?
A staffing agency sells people's hours. We deliver an accountable team with a tech lead who stays with you for years. The concrete differences: senior instead of junior, retention instead of rotation, code review and knowledge transfer built in as standard, and we remain responsible for what we build, even if an individual engineer changes. The hourly rate is therefore usually higher, but the total cost over a multi-year engagement is lower because there is less rework and onboarding.
What is included in a managed services contract?
With managed services, we take on the continuity of your software. In practice this includes: monitoring and alerting, regular maintenance (security patches, dependency updates), a small monthly development budget for minor changes, incident response during your agreed working hours, a dedicated tech lead as your point of contact, and a quarterly report on what has happened. Larger build assignments come on top as a separate project.
How do you handle GDPR, NIS2 and CSRD?
Transport increasingly falls under NIS2 as critical infrastructure, particularly for road transport of dangerous goods, customs processing and large-scale logistics. We help build towards a NIS2-compliant security level (access management, log monitoring, incident procedure, supply chain checks) and support directors with the governance side: who is responsible, how reporting works, and which suppliers fall within scope. GDPR is built into everything we develop as standard: data minimisation, retention rules, audit trail, and pseudonymisation where possible. For CSRD scope 3 emissions, we help collect fuel and route data from telematics into a reporting layer, so you can substantiate your scope 3 figures and make them auditable. We are not compliance lawyers — we work with your legal or compliance partner if you have one, and focus mainly on getting the technical implementation right.
What does a partnership cost?
That depends heavily on the service model and the scope. A discovery and roadmap is a well-defined first engagement with a fixed sprint budget — deliberately limited in size so you come out of it with a well-founded plan without a major investment. Managed services are a fixed monthly fee based on the complexity of your landscape and the agreed response level (office hours versus 24/7, same-day response versus within an hour). An embedded team is priced on the number of engineers and the duration, with on-demand flexibility within reasonable limits. CTO-as-a-service is typically half a day or a day per week, with variable activation for bigger decisions. After an introductory call and a short intake, we give you a concrete quote — no web calculator, because the spread between scenarios is too large to show fairly up front. What we do guarantee is that rates and pricing bases are clear before you start, and that there are no hidden margins in licence pass-through.
How does an engagement start?
With an introductory call of about half an hour, where we go through what you have now and what you are running into. This is usually followed by a short discovery phase: a few days to a couple of sprints in which we map your existing applications, integrations and pain points, talk to planning and operations, and put together a proposal. Only then do you choose a format — project, managed services, embedded team — and we get started. No multi-year contract on day one: the partnership grows organically out of the first well-defined assignment. We are also perfectly happy to deliver just an audit or second opinion first, and part ways if it turns out you are better off with another provider. A forced partnership is not a partnership.
Can you also do AI integration?
Yes, and we prefer to keep it pragmatic and focused. Route optimisation, document AI for CMRs and invoices, a planning assistant that supports the planner rather than replacing them, AI search across your trip history. We have a separate page on this:
AI in transport. Importantly, we don't build AI because it's trendy, only where it measurably saves work or improves decisions.
Which other transport segments do you cover?
Besides road transport, we also work in adjacent logistics domains. See, for example, our page on
maritime software for ship cargo handling and port operations, and
enterprise software for larger organisations with multiple business units. We take the same approach to specialty transport such as vehicle transport, refrigerated transport and hazmat: custom workflows, not forced into a standard TMS.