So what is Slash Group, actually?

It's the question we get asked most, and the honest starting point is that from the outside it looks like a holding company slide: one name over the top of a technology company, a people company, and a couple of things still being built. It isn't one. Slash Group is the operating home for companies built around real problems, useful systems, and people who are accountable for the outcome rather than the launch.

The difference is not in the wording. A holding company owns things. We run them — both operating ventures are Brisbane-based and founder-led by the two of us, both sell real work to real clients, and neither exists as a bet we're waiting to see pay off.

Operational decay

Most organisations don't fail at building things. They fail at keeping them.

A process gets designed once, works, and then slowly stops being a process. It becomes a habit, then a person, then a risk. Knowledge that should live in a system ends up living in someone's head. Nobody decides for this to happen — it accumulates, quietly, while everyone is busy. We call it operational decay, and most of what we build is aimed at reversing it.

Once you can see it, you see it in two places.

SlashTech deals with the version you can point at: the spreadsheet holding the business together, the off-the-shelf tool everyone has quietly built workarounds around, the export-and-reimport step that three people know about and nobody has written down. Slash Horizons deals with the version that's harder to see, because it usually gets diagnosed as a personality problem when it's a systems problem. If SlashTech asks whether your operation was designed or just tolerated, Horizons asks the same question about your team — are people developing on purpose, or getting by on whoever happened to be paying attention that quarter?

Same decay, different domain. That's not a positioning exercise. It's the reason two companies that look unrelated belong under one name.

Siblings, not departments

Technology operations and people operations are different disciplines with different failure modes. Bolting them into a single generalist offering would have made both weaker — you'd end up with a company that does software and also does training, which is a company that does neither properly.

So SlashTech and Slash Horizons are siblings under Slash Group, not departments of one company: separate teams, separate offers, separate customers, same standard.

It's also why we're not trying to make Slash Group a name people recognise for its own sake. It works best as the answer to "who's behind SlashTech?" — the thing that explains why two companies in different industries operate the same way.

What's actually operating

• SlashTech — operating. Custom software, connected hardware, and automation for operations teams who've outgrown spreadsheets and off-the-shelf tools. slashtech.com.au
• Slash Horizons — live. The same work on the people side: onboarding, capability, and progression built as systems rather than good intentions. slashhorizons.com
• Slash Flow — in development. Project management and business operations software for client work, deliverables, budgets, and team workload.
• Slash Labs — not a venture. It's the workshop: early experiments and internal tooling, including applied AI. Things get a name when they've earned one, and most of what's in there won't.

The standard

All of it is held to the same bar, and it's a short one. Don't launch something we can't stand behind. Say "this might not be a fit" when it's true — including about our own ventures, which is the only version of that sentence that costs anything. Build things that are meant to still be running in five years, run by the people who depend on them rather than by us.

That last part is the expensive one. Optimising for whether a company can operate without us propping it up means moving slower, turning down more work, and having less to announce. We've written before about why that trade is worth making: the goal isn't to launch more, it's to build better. This is what it looks like structurally.

Where you fit

Rough sorting, if you're trying to work out which door is yours:

• An operation running on spreadsheets, tribal knowledge, or a tool that stopped fitting a while ago → SlashTech.
• A team where development happens by accident rather than by design → Slash Horizons.
• Not sure, or honestly both → start with the problem rather than the venture. We'll tell you which one it is, or if it's neither.

Either way it's a conversation before it's anything else — start one here.