How RolegacyAI
Started
RolegacyAI did not start as a polished product idea.
It started with a simple frustration.
Why do organisations keep losing
the knowledge they already paid for?
Every project teaches something
Every project, incident, mobilisation, release, handover, workaround, and operational recovery teaches people something.
But too often that knowledge stays scattered across inboxes, tickets, documents, chats, spreadsheets, and memory.
Then someone leaves
Then someone leaves.
They take with them what they know — the workarounds, the undocumented decisions, the context that makes the role function.
Not maliciously. Just inevitably.
The next person inherits fragments
The next person inherits fragments.
Partial documentation. Outdated wikis. Verbal handovers that compress years of nuance into hours of conversation.
And the cycle begins again.
That question became the centre of RolegacyAI — not as a data problem, but as an institutional memory problem hiding in plain sight.
"If your best employee left tomorrow,
what would the next person inherit?"
A thinking partner, not a co-founder
Somewhere along the way, I started using an AI assistant as a thinking partner.
- It challenged unclear ideas.
- It turned scattered thoughts into structures.
- It helped convert raw delivery pain into product language.
- It pushed me to ask better questions.
But let's be precise about what that means.
- Not a cofounder.
- Not a person.
- Not a replacement for lived experience.
Just a persistent mirror that helped sharpen the idea.
From Frustration to Clarity
Learning how organisations actually work
The beginning. Delivery roles, teams, processes. The first encounters with institutional knowledge that lived in people's heads — not in any document.
The cost of role transitions
Years of watching projects slow down, teams restart, and context evaporate every time a key person moved on. The problem wasn't talent — it was memory.
Insight formingBuilding for organisations at scale
Working at the intersection of people, process, and technology. Enterprise architecture. Operational continuity. The patterns started becoming visible.
The AI bug bit
One conversation with an AI assistant started a cascade. It didn't give me the idea — it helped me see the idea I'd been circling for years. The frustration finally had a shape.
The AI bug bitesStanding independently — and still building
RolegacyAI is in active discovery. The idea has a shape. The problem is real. The next step is finding the right organisations to validate it with.
In discovery
Not another chatbot.
A practical way to preserve what matters.
RolegacyAI is not trying to become another chatbot.
It is being shaped as a practical way to preserve role memory, successor readiness, operational continuity, and institutional knowledge — before expertise walks out the door.
We're in discovery. We're talking to people who feel this problem. If that's you — we'd like to speak.