Why Protée OS exists
I'm Roy. I've been on every side of an event brief for 23 years — and I built Protée OS because the event management software I needed didn't exist.
Production mostly, over 23 years. Also venue operations, AV, event security, General Manager of an event hire company, and floristry school somewhere in there. On the tools and behind the keyboard the whole way through, constantly refining the process, always looking for the system I needed.
First it was the wall and the job sheet. The wall is a wall — A4 sheets, one per day. It still is. The job sheet started as the quote with a cover page, then became every email printed and attached, so that on site I had a source of truth in my hand. When a vendor or a venue or a planner told me to do something different, I had the client's own words to go back to. The client got what they asked for, not what was easiest for someone else on the day.
Then it was CRMs. Automations, workflows, pipelines — built for everyone, so built for no one. Good at sales and nurture sequences. Useless on the job itself. None of it touched the fragmented information that actually causes the damage.
Then event-specific software. I've tried a lot of it. Most of it has clearly never been carried through a load-in by the person who designed it.
Then a client portal on WordPress. Too much money, not enough time to build it myself, so it went to a developer. What came back was generic — because the nuance was in my head, not in the brief. That's not the developer's failure. There was no way to hand over two decades of knowing what breaks.
We ended up running all of it at once. The wall, the job sheet, the CRM, and a stack of other software besides.
By then I'd stopped believing the answer was another piece of software. I thought it was the industry.
Years of a fragmented industry. Brick walls, problems solved on the fly, fight-or-flight at 6am on a load-in — with 23 years behind me and a scope of work that was spot on every time. Being right on paper doesn't help when nobody else is reading the same page.
The measurement
Before Protée OS, I tried to fix this from the top down. An industry association. A standard everyone could work to.
To make the case, I ran a study on my own data. Six weeks of briefs, specs and requests coming into me as a vendor from event professionals across the industry.
The reason isn't incompetence. Agencies run on interns and new staff doing the grunt work, because that's what the margins allow. A brief passes through four hands before it reaches a vendor, and every hand is a chance for the truth to change shape. The person sending it has no way to know it's wrong. The person receiving it has no way to check.
An association was never going to fix that. A standard nobody can enforce is a suggestion.
The realisation
I was standing waist-deep in the water off Boracay when it landed.
The fix wasn't top-down. It was structural. Stop asking people to be more careful and remove the places where the truth can fork. One live record. Everyone reading from it. No re-typing, no re-sending, no version that only exists in someone's inbox.
I built this because nobody else could
First I built the thing I actually wanted, then a fix for every pain point I'd collected along the way — solved with simplicity and logic. That became the proprietary logic that powers Protée OS. Patent pending.
The logic isn't AI. Every rule in Protée OS came from someone who has stood in the rain at a load-in dock waiting on an answer. AI does what AI is good at — reading an image, comparing a quote to a brief. It doesn't decide how your event gets built.
What it means in practice
Your intern has 23 years of experience.
Not because they've learned anything — because the system holds what they'd otherwise have to know. Five inputs generate the full event build across over 100 functions. Everyone the intern contacts — vendor, venue, client, crew — receives the same one live source of truth, at the same time, in the form they need it.
The experience is in the pipeline. The person operating it doesn't have to supply it.
Why this works anywhere
Event production is the same everywhere. A run sheet is a run sheet. A load-in dock has a time on it and a truck that either makes it or doesn't. A vendor needs a spec, a venue needs a schedule, a client needs to know what's confirmed.
Las Vegas, Sydney, Auckland — the constraints don't change. The scale changes, the money changes, the language on the paperwork changes. The process underneath is identical.
That's why Protée OS launched with design partners in Melbourne, Brisbane and New Zealand rather than one market, and why nothing in the architecture is built around a single country's way of working.
What I build on
Across two decades of festivals, wine tastings and everything in between, I kept coming back to the same principles.
Every effort has to be repeatable.
A team running on adrenaline performs brilliantly once and badly after that. Performance climbs with pressure up to a point and then falls off a cliff — psychologists have measured that curve for a century. The job is to keep the crew in the productive band, and you do that with process, not heroics. If it only works when everyone is at full stretch, it doesn’t work.
Energy equals energy.
You get out what you put in. If you want energy from your crew, you show it first — at 5am on a wet load-in, not just in the pre-production meeting. Lead from the front or don’t expect the front to move.
If it’s not in writing, it’s not real.
A verbal confirmation is a memory, and memories diverge. This one turned out to be the whole product.
Where it stands
Protée OS is built and runs on my proprietary Logic Engine.
I'm a solo founder. Design partners are live and running real events on it. What I'm building next is decided by what those events expose — not by a roadmap I wrote before anyone had used it.
If you want to know what it does, the features pages are there. If you want help with onboarding directly, I'll answer.
Protée takes its name from Proteus — the shape-shifting figure who could not be pinned down, and who morphed into whatever was needed, like an event professional. Until now.
Want help with onboarding directly?
Book a time and I'll answer. No sales team, no handoff — you get the person who built it.