A transport company with its own staff portal instead of five platforms

The situation

A mid-sized transport company ran on three systems that each did their job, but not together: Webfleet for GPS and vehicle tracking, Minox for accounting, EasyTrans as the TMS. Around them sat a layer of Excel, email, and miscellaneous online tools for hours, leave, contracts, and customer data.

Management saw the same data three times: drivers entered their hours in an app, planning turned it into Excel, administration retyped it into Minox. New hires got a contract by email, a password for the hours app, a login for planning. Clients lived in the owner's Outlook contacts, not in a shared CRM.

The question was not "which platform do we buy", but "can we make this one application that works our way".

What we did

We built a single-page application (web + mobile) that is their complete operating layer.

In the web app:

- Time tracking with clock-in/clock-out from phone, with location confirmation. - Leave management with approval through planning. - Contract management with digital signing and retention rules. - HRM for staff data, certificates (driver license, ADR), and periodic checks. - CRM with clients, contacts, and orders.

Glued underneath via APIs and webhooks:

- Webfleet: trip data and vehicle locations, surfaced in the driver view. - Minox: hours flow through automatically as costs; customer invoices are prepared from the CRM. - EasyTrans: orders and trips stay in sync across both systems, nobody retypes anything.

The data sits in a single Postgres at our end, with audit logging on sensitive actions. Staff log in once, see everything that matches their role, and never switch tabs.

What it delivered

In production:

- Hours admin from manual to automatic. What a driver clocks shows up in Minox the next morning. - One login per employee, instead of five accounts in five systems. - Customer data centralised. Sales, planning, and administration look at the same list. - Mobile access for drivers without exposing them to the TMS or the accounting package. - Three existing systems (Webfleet, Minox, EasyTrans) stayed in place; investment in those contracts was preserved.

Vectel hosts the application, runs maintenance and updates, and charges per active user per month. No platform seat license, no Premier Partner hours for every change. Field or workflow changes are a sprint, not a quote process.

What this wasn't

Not a Salesforce roll-out with custom objects where it eventually breaks. Not an all-in-one platform with seat pricing that scales exponentially. Not WordPress with thirty plugins. What it was: one application on a tailored stack (Next.js, TypeScript, Postgres) that we host and maintain, gluing the existing systems together without replacing them.