Your IP
Background IP stays yours, ringfenced in writing before any work starts.
On exit you leave with what you need to keep running on your own. Nothing you brought in can be held hostage.
Everything agreed before anything is built.
308’s legal and operational framework for building with others. IP, confidentiality and decision rights settled up front, so capable companies can combine without being diluted, locked in or absorbed.
What you’ve built is half of something bigger.
We watch capable small companies burn margin competing for the same thin slice of the same vertical. Two of them joined early would have a stronger, more defensible product than either will reach alone. Nobody joins, because nobody trusts the paperwork. PartnershipDNA is the paperwork, done properly, before anyone is invested enough to argue.
It works as a hedge too. A vertical startup can move horizontally by combining with performers in adjacent verticals, extend an existing capability into a bigger product, and draw on 308’s delivery record and solutioning along the way. The framework exists for combining what already works and building on top of it.
PartnershipDNA is already running. Salus is our flagship collaboration, built together with Vox Novus under this framework and governed by it from the first day.
Two phases. Nothing improvised.
- Collaboration
- You work as independent companies. Licences are mutual and bounded to the project’s defined field.
- Background IP
- What you bring in stays yours. Identified and ringfenced in writing before any work starts, and it leaves with you on exit.
- Foreground IP
- What gets created inside the project is held in trust for the future venture from the moment it is made. At conversion it moves into the venture. It never quietly becomes anyone’s alone.
- Conversion
- At an agreed trigger, a commercialisation vehicle is formed, the foreground IP moves in, and equity is issued against recorded risk and contribution.
- Decision rights
- Who decides what, written down at the outset. One partner stays accountable for the whole.
What you keep.
Your credit
Contribution is recognised and tied to what you actually deliver.
Recorded as the project runs, so the equity conversation starts from evidence.
Clear lines
One partner stays accountable for the whole, so responsibility never scatters.
One name stays on it from the first workshop to the last release, and it doesn’t move when things get hard or when somebody would rather it did.
Your time
Involvement is scoped to the work in front of you.
Scope changes by agreement and in writing, so a month of your time cannot quietly become a year of it.
A rising tide lifts all boats.
John F. Kennedy
You’re not asked to take us on faith.
- The environment
- 308 stands up and runs a high-assurance environment for each project. Development, source control, identity, secrets, runbooks. Open to inspection by every partner, on reasonable notice, without charge.
- Independent audit
- Every project includes an independent risk and compliance party. It audits the environment and verifies security and regulatory compliance for all partners, and its findings go to every partner at the same time.
- Equity
- Follows risk and contribution. Shares are set per project and worked out in the room.
- Pace
- Cadence over speed. Projects move at the pace each partner can sustain. Slow is fine. Absent is not.
Capability that actually deploys.
A real track record
Deployed and running in regulated or high-consequence environments.
Tell us what you built, where it ran, and what happened the first time it was stressed. We are more interested in the failure you fixed than the demo you polished.
A security posture that holds
Practices that stand up to scrutiny from the first conversation.
How you handle secrets, access and disclosure, as you actually do it day to day. We ask early, because retrofitting this into a shared build is far harder than starting with it.
A clean supply chain
Sourcing that is secure and transparent end to end.
An unexamined supply chain is a risk every partner in the project inherits, whether or not they knew it was there. You should be able to say where your components, dependencies and subcontracted effort come from.