Australian-owned, founder-held, small by design. Two co-founders and one job, which is protective and defensive technology for the organisations responsible for critical systems.
Origin
I came to this from disaster relief in global conflict zones. Places where the systems around you are broken by definition, and the only measure that matters is whether help actually arrives.
I spent years watching organisations with overlapping mandates duplicate effort, undermine each other for funding, and perform for stakeholders instead of delivering for the people they claimed to serve. What worked, when anything worked, was small teams, properly scoped risk, and no interest in credit. That carved the path for everything since, and it is why my co-founder came on board.
We named the company after an HTTP status code. 308. Permanent Redirect. The old path doesn’t work. We’re the new one.
BA · Co-founder
Product development and partnership in this country are fragmented and hard to see into. Work gets won by people who will not build it, resold by people who did not make it, and sold on certainty nobody has earned. Meanwhile the people who can actually build have nowhere to do it together. 308 exists to be that place, and it runs one way. A rigorous method, our own hands on the work, and no whitelabelling.
It is also built so it cannot drift into the thing we watched. There is no layer of people whose job is talking about the work, and no growth for its own sake. We are funded by delivery, accountable for what we ship, and small enough that everyone’s name is on something real. We grow at the pace the work sets, and we own the company outright.
BA
Co-founder · Leads 308 Research
The call on what 308 builds, and what it walks away from.
Field first, study after. International relations and security, then cyber and product capability built deliberately in the years since. Strategy, security and product development held together in one head, because deciding what 308 builds and why takes all three.
NM
Co-founder · Leads 308 Continuity
The call on when a thing is actually ready to ship.
A background in mechatronics, then a career in agentic systems and RPA across high-assurance sectors, finance and insurance among them. That experience runs through the pipelines, the baselines, and the definition of done that survives production.
Our people and partners work where a name on a website carries real exposure, so the absence of a team page is duty of care. Partners choose their own visibility, project by project. They are named on the work they have chosen and unnamed everywhere else, at no cost to how the upside is shared. Client names stay off for the same reason. Under NDA we will walk you through the work itself, deliberately de-identified, including the architecture, the method, what held and what we changed.
308 Impact
Protective work for the people and places that can’t pay.
Self-started projects and pro bono support for NGOs in disaster zones around the world. Coming soon.
Coming soon
Signal
A real need keeps surfacing, and the workaround is costing someone.
Definition
The problem is written down hard.
Review
Accountable people in the room. Plenty stops here. That is the system working.
Build
Security discipline from the first commit.
Validation
Judged by people who did not build it. It advances when it holds.
Ten years out we want a portfolio of companies that came out of Research, clients and partners who have been with us long enough to stop checking, and work supplying organisations large and small on terms nobody has to be nervous about. Somewhere a real builder can bring an idea without fear of it being taken, get support with no strings on it, and move on when their interests move on. People change, and so does what they are good at. A structure worth building is one that can hold that. Too much talent walks away because someone senior said no without thinking. Not here.
