308 Research looks for needs in critical sectors that nobody is selling an answer to, then forms a new company with partners to build one. Each product spins out as a company of its own, and 308 and the partners hold equity in it alongside each other. Salus, built with Vox Novus, was the first.
We look for founders and small companies with real potential, the capability to build, and the care that zero trust environments demand. Bring your own idea or build on one of ours. Either way it goes through the same five gates.
It’s the framework we wrote so partners can trust each other with IP before anything is proven. What you bring in stays yours, anything built in the project is held for the company it becomes, and equity follows the risk you took and what you delivered. Every project gets a secured environment and an independent audit. It’s how Vox Novus built Salus with us, and it’s how you would too.
The same need keeps surfacing, and the workaround is costing someone. One observation is an anecdote. The gate opens on a pattern with a cost we can measure.
The problem is written down precisely, before anyone is allowed to fall for an answer. It covers who it hurts, what success looks like, and what conditions it must survive. How it will be built is deliberately left out.
A formal review with the accountable people in the room, and many ideas stop here. The decision is recorded against their names, including a decision to stop.
Many ideas stop hereBuilt from a hardened baseline, with who can see what settled before the first feature. Partners bring in capability where the product needs it.
Judged against the need as it was first written down, by people who didn’t build it. Passing this gate opens the conversation about forming the company under PartnershipDNA.
Company formed under PartnershipDNA
Every build follows a DevSecOps method. The threat model is written before the architecture, each product starts from a hardened baseline we maintain, and we attack it ourselves before anyone else can.
We classify the data before we model it and decide who can see what before the schema is drawn. How long data is kept and how it’s destroyed are decided on day one.
Automated evaluation runs for the whole build, covering the cases that matter and everything that has failed before. The evidence is kept so it can be produced when someone asks for it.
Hardware gets the same controls as software, from the parts list to the last unit shipped. Components are sourced as a supply chain and board revisions are versioned like code.
Each product is funded for what it needs to reach the market. That can be 308, the partners, grants or outside investors, venture capital included. The mix is set by the product’s timeline and what it costs to build. 308 itself stays with its founders.
Salus drafts care plans for Australian home care and Support at Home providers. It reads the assessments, notes and records a provider already holds, pulls them into one picture of the client, and produces a draft plan that a care manager reviews, edits and approves.
No. Research builds products from needs we’ve found ourselves or that a partner brings to us. Nothing we see inside a Continuity client becomes a Research product.
Yes. If a large firm has a problem its own setup can’t carry, we’ll build the answer with them under PartnershipDNA.
We’ll look at what you’ve built. If we don’t have the capacity or aren’t the right fit, we’ll introduce you to people who might be, once we’ve done our own checks.
The company it spins out into does. Each product becomes its own company, with 308 and the partners holding equity alongside each other. Background IP stays with whoever brought it, and that’s agreed in writing before any work starts.
If you’re responsible for something that can’t be allowed to fail, start here.