Technology built, handed over, and then quietly breaking down. Nobody planned for what happens after launch. We built Slash Tech to do something about that.
That’s where we met — both there for the same reason. Once we’d worked together long enough, the alignment was obvious: we wanted to learn, to build, and to help organisations create systems they could rely on long after the technologists had left the room.
Slash Tech started as Jayben’s idea. With Javier, it became a company — and the foundation of something larger we’re building under The Slash Group. But the work starts here: the systems we build, and the operators who inherit them.
— Jayben & Javier
We work across the full picture — hardware, software, and the field — because real systems don’t fit neatly into one discipline. You work with the founders directly, on every project.
“It is only done when the work is fit for purpose.”
The same pattern kept showing up: organisations needed better technology than they were getting, and nobody was building it for the operators who would have to live with it. Slash Tech is his answer to that — and every output is held to his standard before it leaves the door.
“It is only done when the work is fit for purpose.”
The same pattern kept showing up: organisations needed better technology than they were getting, and nobody was building it for the operators who would have to live with it. Slash Tech is his answer to that — and every output is held to his standard before it leaves the door.
“The standard we hold for clients starts with how we run ourselves.”
He runs operations: keeping the business running, holding client relationships, and making sure Slash Tech itself functions as cleanly as the systems it ships. He still gets into the build work — but his job is to make sure there is a company underneath all of it.
Recognised as a 2025 Westpac Young Technologist Scholar.
Knowing we'll be responsible for something in three years makes us build it differently today. Better documentation. Clearer dependencies. No shortcuts that only the builder understands.
What we build has to work when the original team has moved on — because it always does. We design for the operator who inherits it, not just the engineer who commissions it.
We don't consider a project done until someone other than the builder can operate, change, and recover it. That's the bar we build to.
A dashboard that shows you a problem but cannot help you fix it is not useful. We build for the action, not just the visibility.
Tell us about one part of your operation. We’ll give you an honest read on whether technology is the answer — and who would own it afterwards.
