Partnership · Software for transport & logistics

Transport software partner.

A long-term partner for transport companies that have no in-house IT team but do have a growing software portfolio. We build, maintain and modernise TMS environments, planner portals, driver apps and integrations, acting as a single point of contact rather than a separate supplier for each project.

TypeSoftware partnership
Target groupMid-market transport
ScopeBuild + maintenance
ApproachEmbedded team
DurationMulti-year
LocationAmsterdam · NL remote

What is a transport software partner?

A transport software partner is not a one-off supplier and not a standard TMS reseller. It is the party that, over several years, looks after your entire software portfolio with you: which packages are running, what you develop further in-house, where the risks lie, and where there is room to modernise or integrate. The role exists because many mid-market transport companies have an operational reality that does not fit into a single standard TMS, but are too small to set up a full in-house IT team.

Unlike a one-off transport software project, the focus here is not on a single build assignment. We become an extension of your organisation: senior engineers, a tech lead who helps shape the roadmap, and a single point of contact for everything software-related — from a new portal for a 3PL client to taking over a Delphi package whose original builder left years ago. That point of contact is deliberately a person, not a ticketing system: in a serious partnership, you know who will pick up the phone when the planning environment slows down on a Friday afternoon.

We don't replace a standard TMS where it works well. We complement, integrate, modernise and build what makes your business unique: planning logic, client portals, mobile apps, integrations and a compliance layer. Vendor-independent, with code ownership on your side. We have no reseller deals with TMS vendors, no incentives to push you towards a specific package, and no "all-in cloud" lock-in. Whether you want to run on AWS, Azure, GCP or Hetzner is your choice, not ours.

The practical consequence of that positioning: our advice is sometimes unwelcome to vendors, and sometimes to ourselves. If the most honest route is "buy standard package X and build nothing yourself", we'll say so. If your existing system is actually fine and only lacks a good integration layer, we'll build only that layer. A partnership only makes sense if we help you make better choices over the years — not if we invoice every month for work that isn't actually needed.

1 partner
One dedicated point of contact for your entire software portfolio
Senior
Engineers with retention, not rotating juniors
100%
Code ownership with the client — no lock-in
Multi-cloud
AWS, Azure, GCP or Hetzner, whichever you prefer

When is a software partnership relevant?

01
No in-house IT

50-500 employees without an IT team

You have a planner, a controller and a management team — but no CTO and no development team. Software is nonetheless critical to your operations.

02
Legacy inheritance

The original builder is gone

A family business with its own Delphi, Visual Basic or early .NET application whose builder has retired or whose company has been dissolved.

03
Scale

3PL/4PL with multiple client portals

Every new client asks for their own white-label portal or EDI integration. That needs to be scalable, maintainable and consistently secure.

04
Growth

Logistics startup or scale-up

You're building a new concept — last-mile, cold chain, vehicle transport — and need a scalable software foundation without immediately hiring your own team.

05
Specialty

Car transport, refrigeration, hazmat, transshipment

Your operation doesn't fit a standard TMS. Safety, customs or compliance rules call for their own workflows.

06
International

Dutch branch of a foreign group

Group-wide IT is far away or in another country. You want a local partner who can act independently within group standards.

Three things a partnership approach does differently.

Core task 01

Continuity

The same engineers, the same tech lead, over several years. No loss of knowledge at every project handover. What we built last quarter, we still understand next quarter — and can explain to a new colleague in your organisation. Documentation and code handover are an ongoing activity, not a separate final phase.

Core task 02

Strategic advice

We help you choose between build, buy or integrate. Trimble or Webfleet or a custom build? Standard TMS or custom? Cloud or on-prem? Based on your context and your economic reality, not on a reseller incentive or a SaaS licence on which we earn commission. We have no reseller deals; that is a deliberate positioning.

Core task 03

Tech and build in one

Not pure consultancy with expensive reports that end up on a shelf, and not pure builders who simply work through tickets. A technically strong adviser who also builds hands-on — and builders who think along about the direction. That dual track is what makes a partnership approach cheaper and smarter than two separate engagements.

What a partnership covers in practice.

The work we do during a multi-year partnership, from strategic roadmap to operational maintenance.

Software roadmap

Looking two to three years ahead: build, replace, integrate or consolidate.

TMS & portal maintenance

Keeping a custom package or a fork of a standard TMS in good shape and developing it further.

Legacy modernisation

Moving Delphi, VB or early .NET applications to a modern stack step by step.

Driver app

Mobile app for drivers on the road: trips, scans, e-CMR, time registration, photo evidence.

CTO-as-a-service

Interim technical leadership, sparring with management, and an escalation role towards vendors.

Customer portals

White-label portals for 3PL/4PL customers with EDI, track & trace and invoicing.

Vendor management

Independent advice on Trimble, Webfleet, Centric and other packages.

AI integration

Route optimisation, planning assistant, document AI: pragmatic and focused.

Compliance programmes

NIS2 as critical infrastructure, CSRD scope 3 emissions, customs/AEO integrations.

Integrations

Accounting, banks, customs, Trimble Maps, telematics, EDI formats.

Data & reporting

One central place for KPIs: margin per trip, fuel, hours, empty kilometres.

Security & backups

Periodic security review, backup testing, incident response procedure.

Five service models.

A partnership can start in different forms. They are not mutually exclusive and often grow into one another.

Model 01

Discovery + roadmap

A first pragmatic engagement in which we map out your existing software, talk to planners, management and, where relevant, your current suppliers, and deliver a well-founded roadmap.

Model 02

Project work

A clearly scoped build assignment: a new portal, a mobile app for drivers, an EDI integration. Fixed scope, fixed tech lead, your own code.

Model 03

Managed services

Ongoing maintenance, small-scale further development, monitoring and incident resolution. Fixed monthly budget, transparent reporting.

Model 04

Embedded team

One to three engineers become part of your team: they join your stand-ups, know your planners by name, and are available as internal colleagues.

Model 05

CTO-as-a-service

Interim technical leadership for management teams without their own CTO: roadmap, vendor choices, security issues, and support with due diligence or acquisitions.

How a partnership works in practice.

A partnership rarely begins with a large, signed multi-year contract on day one. It almost always starts with a clearly defined first piece of work: a discovery, an audit of your existing software, or an initial build assignment through which both parties get to know each other. Only when that first engagement goes well and there is mutual trust does it grow into managed services, an embedded team or a CTO role.

Operationally, there is a fixed structure around it. A working session every two weeks with your point of contact and the tech lead, a shared backlog that you can prioritise, and transparent reporting on budget spent and work delivered. No black-box time tracking, no surprises at the end of the month. For incidents and operational questions there is an agreed channel, often a shared Slack or Teams channel, where your planners can liaise directly with our engineers.

Strategically, we revisit the roadmap every quarter. What have we done, what did it deliver, what takes priority over the next three months, and what gets pushed back? That way, the software portfolio keeps moving with your business instead of living a life of its own. For management teams without their own CTO, that quarterly review is often also the moment to put bigger strategic questions on the table: do we stay with this TMS or switch, how do we handle an acquisition, what do we do about AI?

We deliberately work with a small number of partnerships at a time. That is not a sales trick but a choice: a tech lead can only truly think along with two, at most three, organisations. On top of that, the role is kept at arm's length and not embedded. That self-imposed scarcity is exactly what makes the difference between a "supplier" and a "partner".

Our role alongside other options.

A transport software partner is not the only player in the field. We are honest about where we are and aren't the right choice, and which other options may make sense depending on your situation. For a more thorough modernisation, we often also work with an IT modernisation consultant, and for the broader context of AI applications, see our page on AI in transport.

vs standard TMS

Transwide, Centric Distributievloer, Pionira

For purely commodity functionality such as administration and standard planning, an off-the-shelf TMS package is often perfectly fine. We don't replace those for commodity features. We build what those packages don't do, and integrate them with the rest of your landscape.

vs staffing agency

Junior staff on a project basis

Staffing agencies rotate people and often send juniors. We bring senior engineers with high retention, who know your code over the years and have a stake in keeping the solution maintainable.

vs freelance developer

One senior on their own, no back-up

A single freelancer can deliver good work, but drops out through illness or departure. We provide a team, with back-up, code review, knowledge transfer and continuity included as standard.

vs enterprise consultancy

Accenture, Capgemini, large integrators

Those firms are set up for groups with revenues of many hundreds of millions of euros. For mid-market transport companies they are often too heavy, too expensive and too far removed from operational reality. We are more pragmatic and closer to the day-to-day practice.

Frequently asked questions.

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.

Talk to us about your transport software.

A half-hour introductory call where we go through which software you run now, where the pain points are, and whether a partnership approach suits your organisation. No sales pitch — a conversation.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam

Want to start a project?

We'd love to hear from you.

Long story, or would you otherwise have emailed it? Choose Detailed briefing: headings and bullet lists, images in the text and attached files.

Mies

Contact Mies

Business Developer

Contact Martijn

Founder of Appfront

Martijn

Your message has been sent

Thanks for your interest! We'll get back to you as soon as possible, usually within 1 working day.

Edit content