Founding Product Builder, Operations
Job Description & Overview
Odin is building the investment infrastructure for the future of private markets.
We believe capital is one of the most powerful tools for shaping the world - and more people should know how to put it to work. Our mission is to make it radically easier to raise and deploy capital, so that anyone, anywhere, can back the companies and ideas they believe in.
Our first product is a full-stack platform for launching and running private investment firms, allowing you to run everything from your phone - think Shopify for VC and PE. We handle all the infrastructure: from legal structuring and investor onboarding to KYC/AML, payments, tax, reporting, and exits.
We're already trusted by over 10,000 angels, VCs, and founders. We administer over $750m in assets, covering investments from pre-seed to series E. This includes household names like ElevenLabs, OpenAI, SpaceX, xAI, Anduril, etc. but also new companies creating everything from synthetic brains to small nuclear reactors.
Why we're hiring
We are automating a decades old part of the financial services industry. AI pilled builders like you are the beating heart of this plan, because LLMs & agents allow us to turn this services business entirely into software.
This is a product role, and your product is how Odin operates. Think of it as our ghostbuster: every operational problem lands with you, you decide what gets fixed, and you ship most of the fixes yourself rather than writing tickets for someone else.
We're post-PMF, fast-growing, and rolling out new products (fund admin) & geographies (USA). Customer & deal volume is climbing fast.
Today we're on track for roughly 700 deals a year, with a team of ~20, and we'll process $500m-$750m of investment in 2026 alone.
The next goal is 7,000 deals a year and billions in annual investment flows.
We believe this can be achieved with a team of around 50 people. But it will only be possible if we turn human-driven services workflows into software.
Odin's operations run on around 50 processes, some code and some people, and plenty still held together by spreadsheets. Your job is to take each one apart, question why it exists, then rebuild it or kill it.
The simplest way to think about it: the numerator is how many deals we close, the denominator is what each deal costs us to run. You'll focus on the denominator, and the right person won't be able to stop themselves thinking about the numerator too.
We expect the right hire to be spending more time in Claude Code than in Excel, email or anything else.
What you'll own
Triage: Every operational problem comes to you before it reaches product and engineering. For each one you decide: scope it so precisely that engineering knows exactly what to build, or build it yourself.
Cost per deal: There will be big early wins where a whole process can be ripped out and replaced. After that, doubling ops efficiency comes from 150 small changes, and you'll be the one making them.
Automation: You'll sit with the deal operations team, learn each workflow end to end, then build what replaces it. Most of what you ship you'll build without engineering. What does go to them arrives simple, scoped and usually with a working prototype attached.
Deleting things and saying no: You decide what belongs in our processes and what doesn't. If a request from sales doesn't scale and isn't highly profitable we don't do it. If a way of working exists for no good reason, you kill it.
The ops team: You'll lead the core deal operations team, deciding where their time goes while you rebuild the work around them.
What we're looking for
You build, not buy: Clear evidence, at work or in your own time, that you've built real solutions with AI with no budget and no engineers. Buying a tool or setting up workflows in Sheets doesn't count. We want to see what you've shipped in Claude Code or similar.
Founder or product DNA: You've founded something, been early on a founding team, or worked as a product manager. That usually means four or more years of experience and a track record of finishing what you start.
Systems thinker: You look at any process the way a good product manager looks at a product: What's the job? Why are we doing this at all? What's the smallest, simplest system that achieves the goal? You think about the whole business, not just your corner of it.
A lot of what happens in fund admin is inherited convention, an industry "given", or a constraint of some third party. You should