Two Nights, One System, and Three Nephews Who Accidentally Became Software Engineers

There is a particular kind of chaos that arrives in your life after an ACL rupture.
You start rebuilding your leg… and then, apparently, your entire business infrastructure. Because… well why not. I couldn’t possibly sit on my arse and do nothing.

This story is about the latter.

It begins innocently:
I was fed up with chasing and reconciling invoices like a Victorian clerk. I just moved to Xero accounting for my property company and it was like being liberated. We found a saas software company called TailRide and for £400 a year they would auto fetch all my invoices. It didn’t. At the same time, Amazon Business had decided it was far too important to email invoices like a normal company.

So, naturally, the solution was obvious:
build my own multi-entity invoice ingestion engine from scratch.

In two nights.
From 4pm to 11pm.
With discussions, planning, modding, coding, implementing, testing.

But the surprising part wasn’t the speed.
It was that it was… fun.

And that’s because somewhere along the way, I started naming the components after my nephews.


Meet Ethan, Alfie, and Leo — the accidental software team

Most people name systems after Greek gods or animals.
I name mine after my nephews with concerningly accurate software personalities.

Ethan

Calm. Observant. Forensic.
The kind of kid who will one day dismantle an engine just to understand the noise it makes.

Perfect for the orchestrator that monitors everything.
Hence: EthansEye — the watcher.

Alfie

A hooligan. Like a massive one!
If Ethan watches the world, Alfie grabs it. Hard.

Ideal for the Amazon Business spider that crashes through the DOM and seizes invoices from deep inside the UI.
Hence: AlfiesArm — the grabber.

Leo

Explorer. Collector. Takes things and stores them in mysterious locations “for later”.
If you leave a wallet, spoon, or remote unattended, he will migrate it to a new ecosystem.

Perfect match for the Google Drive collector that quietly hoovers up stray files from the cloud.
Hence: LeosLair — the cave where things accumulate.

Together, the three of them form a very strange but very accurate software stack:

  • Ethan watches.
  • Alfie grabs.
  • Leo hoards things in a digital cave.

And I cannot overstate how much more enjoyable debugging becomes when the log reads like childcare reports:

  • “Alfie’s Arm smashed into a selector again.”
  • “Leo’s Lair has collected 17 files no one recalls creating.”
  • “EthansEye is patiently cleaning up behind them.”

This naming decision made the entire build entertaining in a way no corporate developer will ever understand.


Two Nights. A Bit of AI. And a Lot of Clarity.

People assume the magic was the AI.
It wasn’t.

AI is not a wizard locked in my PC writing sonnets in Python.

AI is multiplication.
If you multiply clarity, you get speed.
If you multiply chaos, you get garbage.

What happened over those two nights was simple:

  • I knew exactly what I wanted the system to do.
  • I forced myself to articulate it precisely.
  • Claude wrote the code as fast as I refined the design.
  • I tested, corrected, and shaped the architecture.
  • I then handed md docs to chatgpt for a celebratory high 5!

AI handled the typing; I handled the thinking.

That combination is lethal.

It wasn’t “AI built EthansEye”.
It was:

I built EthansEye in my head, and AI removed the friction.


KISS, but honour it properly

For those who dont know KISS = KEEP IT SIMPLE STUPID!

Somewhere around midnight on day one, the original dream of dashboards, interfaces, views, and filters collapsed under the weight of its own pointlessness.

I scrapped all of it.

Why?

  • Dropbox folders already exist.
  • Xero inboxes already exist.
  • Logs already exist.
  • File movement is the real truth.
  • UIs are maintenance debt.

So I rewrote the architecture to the simplest version that could live for ten years with zero attention:

  • Three collectors → Dropbox
  • Entity detection → ACP / BLS / BOS / UNKNOWN
  • One sender → Xero
  • One archive → history
  • WhatsApp notification → me
  • Done.

This is KISS, not as a slogan but as a survival strategy.

If you want the extended-cut director’s commentary with diagrams, selectors, and JSON state files, the technical MD documents cover it in forensic detail.

But the soul of the system is exactly one sentence:

Invoices flow in. EthansEye routes them. Xero receives them. I do nothing.


The moment I realised it was done

It was about 22:40 on night two.

The scheduler ran manually:

  • Amazon invoices: collected.
  • Gmail attachments: collected.
  • Google Drive strays: collected.
  • Everything sorted cleanly into ACP, BLS, BOS.
  • Everything delivered to Xero inboxes.
  • Everything archived.
  • WhatsApp message:

    “EthansEye Xero Sender Complete – Sent 12 invoices.”

That was it.

The admin shadow that followed me for years evaporated.
The multi-company complexity collapsed into a single elegant pipeline.
The entire system was now self-maintaining.

And somewhere, metaphorically speaking:

  • Ethan approved quietly,
  • Alfie pressed send repeatedly,(why not right!?)
  • And Leo kept the backups in a cave.

Conclusion: We don’t just recover knees. We recover time.

This all started because I wanted to stop wasting energy on admin; but underneath that was something bigger:

Rebuilding capability.
Rebuilding agency.
Rebuilding the parts of life that drain you without permission.

ACL rehab teaches you quickly that your time isn’t infinite, your attention isn’t free, and your systems need to work for you, not against you.

Automation isn’t laziness.
It is liberation.

Ghost OS is no longer just a folder of scripts; it is becoming the platform that gives me my hours back. My clarity back. My evenings back.

And the funniest part?

I owe a surprising amount of that momentum to the mythology I built around three small nephews who have no idea they’re now department heads inside an automation system.

  • Ethan: Head of Observability
  • Alfie: Head of Retrieval
  • Leo: Head of Storage

Ghost OS has its founding team.

And the invoices can look after themselves now.

What the System Actually Does

For anyone who wants the practical version, here’s the entire pipeline in plain English:

  • AlfiesArm – Logs into Amazon Business, grabs all the invoices, and drops them into the correct Dropbox folders.
  • Gmail Poller – Scans email for PDF invoices and sends them to Dropbox too.
  • Leo’s Lair – Collects any invoices sitting in a Google Drive dump folder and moves them into Dropbox.
  • Entity Detection – Reads each PDF, figures out if it’s ACP, BLS, BOS (or UNKNOWN), and sorts it automatically.
  • Xero Sender – Emails the sorted invoices to the correct Xero inbox and archives them.
  • Scheduler – Runs the whole thing daily while I’m asleep.

Result: The invoices process themselves, and I get a WhatsApp message telling me it’s done. A process which would take 1 to 2 hours now takes less than 2minutes!

For full technical details, here’s the specs:
EthansEye Documentation (Technical)
AlfiesArm Documentation (Technical)

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top