Operational & field systemsWe build systems that don’t need us to keep working.
Software, connected hardware, and automation for operations that have outgrown spreadsheets and off-the-shelf tools — built to be owned by the people who run them.
Your operation works. It isn’t built for where you’re going.
What keeps it running lives with specific people, not on paper. That has a name — operational decay — and an honest read on whether to act is where we start.
See what we help you solveEnvironmental & government
Your workflow produces the right outputs because the right people do the right manual steps. You can see it won't scale — and you need an honest read on whether technology is the answer, and what it would take.
Industrial & utilities
You inherited a system the team runs but nobody fully designed. It works — until it doesn't, and then you find out how much of it lived in one person's head.
IoT & scale-ups
Something that works, built and held by one engineer. Growth is the trigger — the real question is whether the systems and the knowledge can keep up.
Custom software, IoT, and automation for operations teams in Australia.
Operational decay shows up differently depending on the medium. The deterioration is the same — the fix requires understanding all three.
Installed, not integrated
Field devices deployed by the build team — calibrated once, documented loosely, left with an operations team who didn't design the system. We build for the engineer who maintains it.
Read on hardware
Shipped, not sustained
A platform built to spec and handed over. The original developers move on, updates stack up, one dependency breaks and nobody knows where to start. We build so your team can change it without calling us.
Read on software
Triggered, not trusted
Automated workflows built around one person's understanding of the operation. When something behaves unexpectedly there's no runbook — just the person who built it, if they're still there.
Read on automationNot the biggest team. The one that hands the system back.
Plenty of firms can build you something. Fewer build it so you own it, fewer still for the real environment it runs in — and fewer again will tell you when not to build at all.
Built to be owned
Source, documentation, runbooks, and training — handed over so your team can run, change, and recover the system without us. We're not done until they can.
02Field-first, real environments
We visit the site before we design. Systems are built for dust, vibration, connectivity loss, and remote access — not for a demo that only works in the office.
03Honest discovery before build
A fixed-fee Discovery Sprint that maps the operation and gives a straight verdict — including “don't build” when that's the honest answer. You pay for a decision, not a sales pitch.
Start where you are.
Most clients come to us with a problem, not a brief. These are the three stages of every engagement — you can start at any one of them.
Discovery Sprint
Map the problem, the constraints, and the right path forward — before spending anything on a build.
Field Prototype Production Platform
Build something that works in your actual environment — and can be owned by the people who run it.
Operations Retainer
Keep the system running, evolving, and genuinely owned — long after handover.
Deployed systems and field notes.
ActiveAir Dispersion Modelling Platform
Air Environment
Workflow automation, interface improvements, and hardware experimentation to accelerate air dispersion modelling for environmental consulting teams.
Handed over / June 2025
Flood Intelligence Network
End-to-end telemetry system for a multi-agency flood monitoring network. On-site commissioning, sensor calibration, and a unified data broker normalising inputs from LoRaWAN, cellular, and legacy serial sensors.
Field note / 6 min read
Shipped in weeks, inherited for years
You have seen the pitch — polished site, thirty-minute audit, deployment in weeks, an ROI that compounds. What it does not tell you is what you are inheriting. Three failure modes show up in this category of build, and they are structural, not accidental.
A small, senior team — and we don’t hide it.
Slash Tech is founder-led and still small — growing deliberately. You work directly with the founders on every engagement, and as the team grows we hold everyone to the same standard: everything we build is documented and handed over so it keeps running whoever is in the room.
Direct founder access
The people who scope your work are the people who build it — no account managers, no hand-offs to someone who was never in the room.
Documented, not tribal
You own the source, the docs, and the runbooks as we go — so the operation never depends on any one person, including us.
Visible operations
A Client Hub for your project, documents, and runbooks, and a public status page for live system health.
We’re a good fit for some work, and honest about the rest.
A good fit if
Probably not the right fit if
Not sure if technology is the answer? Find out — honestly.
Book a 25-minute Fit Call. Tell us about one part of your operation and we’ll give you an honest read on whether a Discovery Sprint makes sense — and if it doesn’t, we’ll tell you that too.
No deck, no pitch — we tell you if it’s not a fit.
Take the operational decay assessment
Six quick questions. A clear read on where your operating layer stands — what’s owned, what’s drifting, and whether technology can help.