OUR STORY

Difficult problems deserve
determined solutions.

Fallon Apus Orbital Systems didn’t begin with a business plan.
It began with a way of facing obstacles.

A clear view of Earth from orbit
THE JOURNEY

A soldier, a Red Coat, a flying chef, a student.

Paul Fallon’s route into software engineering was not, by any measure, the conventional one. At Wymondham College, a boarding school in Norfolk, his London accent made him stand out — the first of many rooms he didn’t quite fit. Only much later did he recognise that undiagnosed ADHD had shaped many of those early experiences and challenges. Not fitting in turned out to be excellent training.

First stop: the British Army, as a Pioneer Soldier — the army’s builders and breakers. Obstacles, bridging, earthworks, demolitions: the unglamorous work that lets everyone else move forward. He passed D and P Company and completed two operational tours, learning how to stay steady under pressure, adapt when the plan falls apart, and keep going when stopping would be considerably more comfortable.

Out of uniform, the natural next step was obviously… a Red Coat at Butlin’s. From operational tours to holiday-camp entertainment is not a career move they teach at Sandhurst, but it is a different kind of service: hold a room of strangers, keep the day running, and do it all with a smile whether or not the audience is cooperating.

Then the kitchen. He qualified as a chef and ended up flying with the best of them, cooking in the air for A-list guests — a trade where the standard is fixed, the timing is unforgiving, and nobody asks how you feel about it. The army taught him to improvise under pressure; a galley at altitude simply added turbulence.

And then, having collected what he cheerfully admits is one of the stranger CVs in engineering, he went back to school. A Humanities degree through the Open University, then coding and intelligence-related disciplines at Westminster in London.

Alongside all of it, he spent years independently researching software, artificial intelligence and systems engineering — and how technology can be used to solve genuinely difficult problems.

  1. BRITISH ARMYPioneer Soldier · passed D and P Company · two operational tours
  2. BUTLIN'SRed Coat
  3. THE KITCHENQualified chef · flew and cooked for A-list guests
  4. OPEN UNIVERSITYHumanities degree
  5. WESTMINSTER, LONDONCoding & intelligence-related disciplines
LESSONS LEARNED
01 / RESILIENCE

Obstacles are information.

Every setback shows you something about the problem — and about yourself — that you couldn’t have seen otherwise.

02 / CURIOSITY

Keep learning, always.

From the parade ground to the galley to the lecture hall to code, every new discipline offered a different way to think about how things work.

03 / SERVICE

Work for something bigger.

Uniform, kitchen, camp: in every one of them, somebody was relying on the job being done well.

WHY FALLON APUS ORBITAL SYSTEMS EXISTS

Not another technology company.

Fallon Apus Orbital Systems wasn’t founded out of a desire to start a tech company — few tech companies begin with a Pioneer’s shovel, a Red Coat and a set of chef’s knives. It was founded on a belief: that difficult problems deserve determined solutions, and that the most useful work often lies exactly where others see obstacles.

The company is still evolving, but its purpose is becoming clear — helping organisations understand and solve complex technical, software, automation and systems challenges, with patience, honesty and care.

LOOKING FORWARD

Learning, adapting, persevering.

Fallon Apus Orbital Systems is built on a simple conviction: progress comes from learning, adapting, persevering and continuing forward regardless of obstacles.

That’s how Paul got here. It’s how the company intends to approach every problem it takes on. If you’re facing a challenge that others have called too hard, we’d like to hear about it.

WORK WITH FALLON APUS

Working on a difficult
engineering problem?

We are interested in conversations with engineering organisations working on autonomy, assurance, resilience and complex software systems.

Discuss an Engineering Problem