In development · preparing pilots

FOR OWNERS AND DISPATCHERS

Own and hired trips.One clear view.

Today it is your vehicle. Tomorrow it is a subcontracted carrier. We are developing Cargo Polis so you can understand what trip information you have and what needs a follow-up in either case.

Discuss a pilot How we start

The first workflow uses a supported Android phone with the driver.

Trip overviewILLUSTRATION

Recorded at 12:40

A gap in data

Trip A → BHired vehicle · Android

8 minposition age

Position age uses the recording time.

Interface illustration · sample data

A FAMILIAR WORKING SITUATION

A mixed fleet. Updates in different places.

Your own vehicles are in one system. Updates from hired drivers arrive in calls and messages. When the customer asks, the dispatcher has to piece the trip together again. We propose testing one shared workflow on selected trips.

Start with a practical question: which driver needs a follow-up right now?

WHAT WE PROPOSE TO TEST

A view you can work with

01 /

Location with its age

A recording time next to the last known position helps the dispatcher assess how fresh the information is.

02 /

The recorded route

Position history gives you a basis for reviewing a trip. Gaps in recording need to stay visible and be discussed separately.

03 /

A phone as the source

The first workflow uses the driver's Android phone. We check the device and recording behaviour before the pilot.

A supported Android phone
Agreed recipients
Clear sharing boundaries

DRIVER PARTICIPATION

The driver knows what is being shared

Before the pilot, we agree what the company needs and when work sharing ends. The driver takes part explicitly; personal history and unrelated trips should not automatically become available to the company.

It is worth talking if…

You manage several trips with your own or hired vehicles.
You need a recorded route and a clear indication of location freshness.
You can test one type of trip in a standalone web workspace.

A PILOT IN THREE STEPS

Start with one workflow

01
Understand your task
Discuss your fleet, hired vehicles and how the dispatcher gets updates today.
02
Agree on a workflow
Choose trips, participants, devices, available features and terms.
03
Test it in daily work
Review the trip view, recorded route, repeat onboarding and support needed.

BOUNDARIES OF THE FIRST WORKFLOW

Test the essentials. Develop what comes next.

A pilot starts with agreed features on selected devices. Future capabilities are not automatically part of it.

Pilot foundation

Android, map and history

Agree on the device, recording, position freshness and available view. Test your particular workflow.

In development

A view for the customer

A limited, revocable link-based view. Readiness is confirmed before including it in a pilot.

Planned for release

Journal and notifications

Operational trip notes, events and Telegram notifications. Each workflow is confirmed separately.

Later stages

Tracker, geofences and ETA

One selected tracker model after validation. Geofences and automatic arrival prediction need separate testing.

BEFORE WE TALK

Questions about the pilot

We already have tracking. Why discuss a pilot?

We start with an unmet need, such as updates from hired drivers. If your existing solution already works well, it is useful to establish that first.

Do we need to buy a GPS tracker?

The first workflow uses an Android phone. Support for one selected hardware tracker is a separate development path; its model and compatibility still need confirmation.

What happens when mobile data is unavailable?

The product is designed to record on the phone and upload after connectivity returns. The map needs to show the last known position and its age. Device reliability is tested in the agreed pilot.

What does participation cost?

Pricing has not been published. A single monthly subscription is the intended commercial model. Pilot scope, duration and terms are agreed before onboarding.

Explore the details