If you’d asked me when I started Vork what it was going to become, I’d probably have described it as an AI project.
Today, I don’t think that’s true.
Vork isn’t really about AI.
AI just happened to expose a problem I’d been living with for years.
Like most software engineers, my desktop had become a museum of applications.
CRM.
Ticketing.
Email.
Calendars.
Documentation.
Git.
Marketing.
Notes.
Each application solved one problem.
Each introduced another.
Every new tool meant another login.
Another subscription.
Another database.
Another place where knowledge disappeared.
Every application wanted to become the centre of my world.
None of them actually understood it.
At some point I realised something.
I didn’t need another application.
I needed an operating system.
For twenty-five years I’ve been building software.
SSH libraries.
Identity platforms.
VPNs.
Secure file transfer.
The products were different.
The goal rarely changed.
Reduce friction.
Build trust.
Help people get on with their work.
Yet somehow I’d ended up surrounded by software that spent more time managing itself than helping me.
Marketing software wanted me to build funnels.
Support software wanted me to manage tickets.
CRM software wanted me to manage contacts.
Every application had become another job.
As engineers we’re remarkably good at automating other people’s work.
We’re surprisingly bad at reducing our own.
Then AI arrived.
Most people asked:
“How do we add AI to our product?”
I found myself asking a different question.
Why does every application need its own AI?
Why does every product need another chatbot?
Why are we still building applications at all?
The problem wasn’t intelligence.
The problem was memory.
Every conversation started from scratch.
Every tool lived in isolation.
Every workflow was trapped inside a product boundary.
AI wasn’t exposing a lack of intelligence.
It was exposing a lack of organisational memory.
That’s where Vork began.
Not with agents.
Not with prompts.
With a much simpler idea.
What if software behaved more like a trusted colleague than another application?
A colleague remembers.
A colleague understands context.
A colleague knows which specialist to ask.
A colleague quietly gets on with the work.
That’s a very different model from another SaaS product asking you to create another account.
Everything in Vork follows that idea.
Records remember what matters.
Tools interact with the world.
Skills combine tools into useful behaviours.
Agents become specialists.
The Concierge understands intent and coordinates the work.
Humans remain responsible for judgement.
Nothing exists because AI made it possible.
Everything exists because organisations already work this way.
Vork simply mirrors that structure.
Perhaps that’s why I’ve stopped thinking of Vork as an AI framework.
I think it’s something else.
An operating system for work.
Not because it replaces every application overnight.
Because it slowly removes the need for them.
One behaviour at a time.
One skill at a time.
One organisation at a time.
I’ve only recently started writing these essays.
Not because I suddenly discovered these ideas.
Because I finally realised they were all connected.
Trust.
Memory.
Craft.
Simplicity.
Whether I was building SSH libraries, writing songs or designing Vork, I’d been solving the same problem all along.
I just hadn’t written it down until now.
Vork is simply where those ideas meet.