About
23 years on site.
Studied programming.
Built both.
The Rare Combination
Most custom software for operations industries is built by people who've never worked in them. Custom software developers have generally lived a life in front of the keyboard. And most people who've spent decades in operations industries have never built software. Those two groups rarely meet in the same person — which is what makes Thesis OS an unusual Sydney software development company. Roy has!
Thesis OS sits at that intersection. Twenty-three years in event production — not as a planner, but on the tools. Rigging, production crew, general management, venue operations, AV, safety. The kind of work where a wrong measurement at 6am costs a client their day. All the time building internal workflows and processes and manipulating off the shelf software tools, like you all have.
That experience produces a different kind of software. Not a cleaner interface on someone else's assumptions — a correct logic layer built by someone who lived the problem long enough to know where the real complexity sits.
Protée OS was the proof of concept. Nine months, patent pending, a new software category — built because no one had built it, not because there was a market gap on a spreadsheet.
What This Means For You
You don't have to teach us your industry
We've probably worked in something adjacent, or we'll learn it properly during discovery. Either way, we come in as someone who needs to understand operations — not someone who needs to be taught what a vendor brief is.
The logic map is the deliverable
Before we write code, we produce a structured document of how your business works. Most clients tell us it's the most useful thing they've ever had built — regardless of what comes next.
We work with a small number of clients
The quality of the thinking determines the quality of the software. That requires time and attention. We don't run a delivery factory. We run a logic-first studio.
You own everything
Code, documentation, data model. If we part ways, your next developer inherits a system they can read and extend. Lock-in is a failure mode, not a business model.
The Stack
Custom builds. No low-code shortcuts for client work. The stack is chosen for longevity, handover-readiness, and clean separation between logic and interface.
Sound like the right fit?
The first conversation is a logic session, not a sales call. Tell us what your business does.