A long-term partner for transport companies that don't have an 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 fixed point of contact rather than a one-off supplier per project.
A transport software partner is not a one-off supplier and not a standard TMS reseller. It is the partner that works with you over several years on your entire software portfolio: which packages you run, what you develop in-house, where the risks lie, and where there is room to modernise or integrate. This role exists because many mid-market transport companies have operational needs that a standard TMS doesn't fit, yet they 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. We become an extension of your organisation: senior engineers, a tech lead who helps shape the roadmap, and a fixed 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: with a serious partnership, you know who to call when the planning environment slows down on a Friday afternoon.
We don't replace a standard TMS where it works well. We complement it, integrate, modernise and build what makes your business unique: planning logic, customer portals, mobile apps, integrations and the compliance layer. Vendor-independent, with code ownership staying with you. We have no reseller deals with TMS vendors, no incentives to steer 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 will say so. If your existing system is actually fine and only lacks a good integration layer, we will build only that layer. A partnership is only worthwhile if we help you make better decisions over the years, not if we bill every month for work that is not really needed.
You have a planner, a controller and a management team, but no CTO and no development team. Software is nonetheless crucial to your operations.
A family business with its own Delphi, Visual Basic or early .NET application whose builder has retired or whose company has ceased trading.
Every new customer asks for their own white-label portal or EDI integration. That needs to be scalable, maintainable and securely built to a consistent standard.
You are building a new concept, such as last-mile, cold chain or vehicle transport, and need a scalable software foundation without hiring a dedicated team straight away.
Your operation does not fit a standard TMS. Safety, customs or compliance rules call for bespoke workflows.
Group-wide IT is far away or in another country. You want a local partner who can act independently within the group's standards.
The same engineers and the same tech lead, over several years. No loss of knowledge at each project handover. What we built last quarter, we still understand next quarter, and we can also explain it to a new member of your organisation. Documentation and code handover are an ongoing activity, not a separate final phase.
We help you choose between building, buying or integrating. Trimble, Webfleet or build your own? Standard TMS or custom software? Cloud or on-premises? We advise based on your context and economic reality, not on a reseller incentive or a SaaS licence we earn commission on. We have no reseller deals; that is a deliberate positioning.
Not pure consultancy with expensive reports that gather dust on a shelf, nor pure builders who only work through tickets. A technically thorough adviser who also builds hands-on, and builders who think along about direction. That dual approach is what makes a partnership both cheaper and smarter than two separate engagements.
The work we do during a multi-year partnership, from strategic roadmap to day-to-day maintenance.
Looking two to three years ahead: build, replace, integrate or consolidate.
Keeping your own package, or a fork of a standard TMS, in good health and continuing to develop it.
Moving Delphi, VB or early .NET applications step by step to a modern stack.
A mobile app for on the road: trips, scans, e-CMR, time registration, photo evidence.
Interim technical leadership, sounding board for the board, escalation role with vendors.
White-label portals for 3PL/4PL clients with EDI, track and trace and invoicing.
Independent advice on Trimble, Webfleet, Centric and other packages.
Route optimisation, planning assistant, document AI: pragmatic and focused.
NIS2 as critical infrastructure, CSRD Scope 3 emissions, customs and AEO integrations.
Accounting, banks, customs, Trimble Maps, telematics, EDI formats.
One central place for KPIs: margin per trip, fuel, hours, empty kilometres.
Periodic security reviews, backup testing, incident response procedures.
A partnership can start in several forms. They are not mutually exclusive and often grow into one another.
An initial, pragmatic engagement in which we map the existing software, hold conversations with planners, management and, where relevant, current suppliers, and deliver a well-founded roadmap.
A defined build assignment: a new portal, a driver mobile app, an EDI integration. Fixed scope, a dedicated tech lead, and code you own.
Ongoing maintenance, small-scale development, monitoring and incident resolution. A fixed monthly budget with transparent reporting.
One to three engineers become part of your team: they attend your stand-ups, know your planners by name, and are reachable as internal colleagues.
Interim technical leadership for management without an in-house CTO: roadmap, vendor choices, security questions, and support during due diligence or acquisitions.
A partnership rarely begins with a large, signed multi-year contract on day one. It almost always starts with a clearly bounded first piece of work: a discovery phase, an audit of the existing software, or an initial build project through which both parties get to know each other. Only once that first engagement goes well and mutual trust is established does it grow into managed services, an embedded team or a CTO role.
Operationally, a fixed structure surrounds it. A working meeting every two weeks with your point of contact and the tech lead, a shared backlog you can prioritise, and transparent reporting on budget spent and work delivered. No black-box time registration, 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 contact our engineers directly.
Strategically, we revisit the roadmap every quarter. What have we done, what has it delivered, what needs to happen in the next three months, and what should be put on hold? This keeps your software portfolio moving in step with your business instead of developing a life of its own. For boards without an in-house CTO, that quarterly review is often also the moment to put bigger strategic questions on the table: should 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 any one time. That is not a sales tactic but a choice: a tech lead can genuinely think along with two, at most three organisations. Beyond that, the work becomes role-playing and superficial rather than embedded. That self-imposed scarcity is precisely what makes the difference between a "supplier" and a "partner".
A transport software partner is not the only player on the field. We honestly outline where we are and are not the right party, and which other options may make sense depending on your situation. For a more thorough modernisation, we often also work together with an IT modernisation consultant, and for the broader context of AI applications, see our page AI in transport.
For pure commodity functionality such as administration and standard planning, a TMS package is often perfectly adequate. We don't replace those for commodity needs; we build what those packages don't do, and connect them to the rest of your landscape.
Staffing agencies rotate people and often send juniors. We bring senior engineers who stay with us, know your code over the years, and have a vested interest in keeping the solution maintainable.
One freelancer can do good work, but they fall away through illness or departure. We provide a team: back-up, code review, knowledge transfer and continuity are all included as standard.
Those firms are set up for concerns with turnover in the hundreds of millions of euros. For mid-market transport, they are often too heavy, too expensive and too far removed from operational reality. We are more pragmatic and closer to the practice.
A 30-minute introductory call in which we go through the software you currently run, where the pain points lie, and whether a partnership approach suits your organisation. No sales patter, just a conversation.
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.
We'll read through it and usually reply within one working day. Have anything to add? Send it to fabian.vandijk@appfront.nl.
Thank you for your interest! We'll get back to you as soon as possible, usually within 1 working day.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
