ABOUT PILOTLINK
You probably shouldn’t read this page.
If you run a pilotage operation you do not have time for a company’s story. Go and use the software instead — ten minutes inside it will tell you more than anything written here.
This page is for the people who want to know who they would be dealing with before they spend the ten minutes. That is a fair thing to want.
WHY IT EXISTS
We know what the desk actually feels like.
The waiting. The board redraws and you wait. The rotation recalculates and you wait. You change one time on one job and you wait again. Dispatchers are fast — faster than the people who buy the software ever realise. When they change something it needs to be there, immediately, or the tool is fighting them.
The keyboard. A working dispatcher does not reach for the mouse. They tab through fields, eyes on the board, hands never leaving the keys. A system that breaks tab order breaks the job — which is why keyboard-first entry is a standard we hold ourselves to rather than a feature we got around to.
The phone. Agents, pilots, tug operators, the terminal — all at once, all wanting an answer now. Whatever you need has to be one action away from wherever you already are. That is the real reason Mira exists, and the reason the board answers a right-click instead of sending you to another screen.
None of that comes out of a requirements document. It comes from sitting in the chair, on nights, for twenty years.
WHO BUILDS IT
Twenty years, thirty-odd systems.
30+
SYSTEMS DELIVERED
20
YEARS IN PILOTAGE
I’m Alex G. I started at Klein Systems in 2000, stayed through its sale to HITT and then to Saab, and spent twenty years building pilotage software — more than thirty enterprise systems for authorities and associations across several continents. Dispatch boards, billing engines, rotation schedulers, tariff calculators.
You will not find a logo wall on this page. Those systems belonged to my employers and their clients were theirs, not mine. Naming them to sell you something would say more about how I’d treat your data than it would about my experience.
I left in June 2020, twenty years and thirty-odd systems after I started. The short version is that I reached a point where I could no longer decide what the software should be — and building pilotage software you do not get to shape is not a job worth keeping. Then I sat out a two-year non-compete, which is a long time to think about what you would do differently.
The problem I had spent twenty years on did not go away while I waited. So I started again from scratch, with the things that were not possible in 2005: a modern stack, a database that can carry the rules instead of hiding them, and an assistant that can actually read an order.
The people who keep ships safe deserve tools built with the same seriousness they bring to the job.
THE SECOND QUESTION
“Will you still be here in three years?”
Everybody asks what it costs first. This is what they ask second, usually more carefully, and it is the better question — because the last two times you changed systems, somebody promised you something.
The honest answer has two halves. The first is that PilotLink is not a one-man hobby: new times need younger minds and there are plenty of them here, building alongside the twenty years.
The second half matters more, because it does not require you to believe us at all. Your instance is yours. Your data is yours. You can export all of it, in full, whenever you ask — not as a favour, not as an exit negotiation, and not for a fee. Nothing is held hostage and nothing about leaving is difficult.
We would rather be the vendor you stay with because the software works than the one you cannot get away from. Those are genuinely different businesses, and only one of them is worth building.
No sales team. No lock-in. If you call, we answer.
Still here?
Then you have already spent longer on this page than we asked you to. Go and use the thing — that is the only argument that counts.