This is 308 Research as published. Defence and government work is held separately and shared on request.
ResearchSmall teams, quiet builds, serious problems. The difference from the classic version is the door. Since day one we have gone out scouting for capability, because the scale of what we are building demands it. If you are a builder who feels stuck, or a small company that cannot see the path, walk in. You will find straight talk and people who will problem-solve with you.
308 funds Research from its own delivery work, so nothing ships before it is ready and a weak idea costs nothing to kill. Venture capital has its place here too. When a build spins out and needs to grow fast or reach new markets, we deploy it deliberately. The mission sets the pace.
Our method is a hybrid. It balances speed with tested practice, and part of it exists to undermine our own work. We try to break what we built, then fix what breaks, before we deliver. Some people put the plane in the sky and work on the engines later. We are the opposite, and our workflow and tooling keep the gap between those two approaches far smaller than you would expect.
Signal
A real need keeps surfacing, and the workaround is costing someone.
One observation is an anecdote. The gate opens on a pattern with a measurable cost.
Definition
The problem gets written down hard, before anyone is allowed to love an answer.
Who it hurts, what success looks like, what conditions it must survive. Implementation is deliberately excluded.
Review
A formal review with accountable people in the room. Plenty stops here.
That is the system working. Names attach to the decision, including the decision to stop.
Build
Development under security discipline from the first commit.
Hardened baseline, tenancy settled before the first feature, partner capability where it sharpens the result.
Validation
Judged against the original need, by people who did not build it.
It advances when it holds. The date follows the evidence, every time.
Hardware & software, one discipline
The bench gets the same rigour as the repository.
Research builds physical things as well as code. Component sourcing is treated as supply chain, firmware ships under the same pipeline controls as software, and test rigs produce evidence you can put in front of someone.
Data architecture & governance for regulated environments
In a regulated environment, the data model is the compliance position.
Classify the data before modelling it. Decide tenancy before the schema. Treat every boundary the data crosses as a control that has to be justified.
Assurance & evaluation
Shipping is a conclusion the evidence reaches.
Evaluation harnesses run through the whole build. Performance on the cases that matter, behaviour on the edge cases that hurt, regression against everything that has failed before.
Research
Salus
PartnershipDNAThe drafting layer between what a provider already knows and the care plan it owes.
Australian home care providers already hold everything a care plan needs. Salus structures it into a single client picture and an auditable draft in under 30 minutes, against three to five hours by hand with detail still going missing. A care manager reviews, edits and approves.
Visit Salus website