OS-Intelligence Get early access
V2 · the team operating system · in build

A team operating system for product management.

One repo for the whole product team. Meetings, decisions and research become shared context your AI reasons against, and every claim traces back to a source. Every PM does their work, saves sessions and runs research in the same place. Runs in Claude Code and Codex.

The workflow, end to end
Video coming soon
Why it exists

Your teams use AI every day. Where does all that work go?

The problem

Every PM starts from scratch

Every PM uses AI, each in their own way. One keeps a folder of prompts, another pastes notes into a chat, a third has built something impressive that only they can use. Company knowledge sits in dozens of places their AI can't reach, and the reasoning behind each decision is lost before the next cycle starts.

So plans reach review unchallenged, the same mistakes get made twice, and leaders see AI use going up but can't see what it has changed. The bill keeps growing.

The solution

One shared place for the team's knowledge

OS-Intelligence is a shared folder the whole product team works in, with AI built in. Meetings, documents and decisions go in. The AI turns them into one current picture of each project, and every point links back to where it came from.

Everyone works from that same picture, in the AI tools they already use.

What your teams get

Better answers, and plans that hold up

  • Answers built on what your company knows, with the source for each point.
  • An AI that challenges a plan with the evidence instead of telling you it looks great.
  • Research that's saved where the next person can find it.
  • Plans that stay in the PM's own words, so the PM still owns the decision.
For your PMs

What if every PM on your team could…

Spot the signal before it becomes a problem.

Three meetings, a research readout and a design review this week. You're back to back, so there's no time to work out how it all changes the plan. And you're the one on the hook for the direction.

The knowledge layer reads across all of it for you, and points out what's changed and what matters, with the source behind every point.

You see the problem while it's still cheap to fix.

Learn what your company already knows about your project.

Someone researched this last year. The findings are somewhere in a deck, a doc or a Slack thread, and nobody remembers where.

The research agent works through your company's knowledge for you, starting with your riskiest assumptions, and saves every finding with its source so the next person can find it too.

Research done once and saved for the team, not repeated three times.

Turn what you know into a plan that holds up.

The review is on Thursday. You asked your AI about the plan, and it said the plan looks great. It always does.

The sparring partner won't just agree with you. It raises the few issues worth discussing, challenges you with the evidence, and ends with a plan in your own words, with the biggest risks named.

You walk into the review with the hard questions already answered.

OS-Intelligence is a team operating system for product work. It gives your team one shared store of what it knows, from meetings, documents, decisions and research, and puts it to work: better answers, research nobody has to repeat, and plans that hold up. Every claim traces back to source.

Features

What it does.

V2 · in build · coming soon

Your whole team works from the same knowledge

  • Shared team knowledge. One place for the team's meetings, decisions and research, so what one PM learns, everyone can use, and nobody starts from scratch.
  • Knowledge layer. Meetings, documents and decisions synthesised into one current picture per project, with every claim traced to its source and stale context flagged.
  • Sparring partner. Raises the few issues worth discussing, challenges with the evidence, and ends each conversation with a plan in the PM's own words.
  • Autonomous research. Desk research on the riskiest assumptions, starting from "what if this is false", with a hard cap. Findings are logged as sources, never as facts.
  • Idea to prototype. One workflow from a one-line idea to an evidence-backed PRD and a working prototype, with design and engineering setting the quality bar.
V1 · open source · May 2026

Your AI remembers your product work

  • Picks up where you left off. Each session is saved, so the next one starts with what you already know instead of from a blank page.
  • One current picture per project. Meetings, documents, chats and notes become one up-to-date view: where things stand, what's decided, who's involved and what's still open.
  • Knows what's out of date. Anything that hasn't been checked against a source for a while is flagged, so you don't act on old information.
  • Everyday PM work, ready to run. Synthesis, meeting notes and research are ready-made workflows, so you get consistent results without writing prompts.
In the field

Used with a product team.

June to September 2026, at a PE-backed European marketplace, I applied OS-Intelligence to the product organisation as a team operating system.

Idea to production. A seven-week pilot took two roadmap features from a one-line idea to an evidence-backed PRD, a working prototype and a live release, with product, design and engineering setting the quality bar.

Research agent with sourced claims. An agent retrieved and synthesised company knowledge and wrote every finding as a sourced claim with a quote and a link. A PM ran it by hand and asked for the prompts.

Evals

Tested, and the results reported as they came out.

Before claiming anything worked, I measured it against simpler setups: up to 21 questions with known answers, a control page sealed before any runs, and setups compared side by side. Losses included.

TestResult
Context comparison: the knowledge layer against a plain baselineMixed
Names the right people and says what it couldn't findHeld
Facts survive when the agent writes a summaryDidn't hold: two facts lost
Knowledge prepared locally beats leaving it in company toolsHeld, and a re-test confirmed it

The knowledge layer shows promise, but it didn't win on every measure. Next: more and larger datasets, starting with a public synthetic one that anyone can rerun.

Under the hood

How it's built.

V2 · in build · coming soon

A team operating system

  • One repo for the team. Every PM completes work, saves their session and runs research in the same place.
  • Hypothesis store. One agent keeps the team's open bets in date order, each with verbatim evidence for and against.
  • Decision-maker rule. A view about how a stakeholder judges success only weakens on that person's own dated words.
  • Two tracks, never merged. The agent's read (evidence only) sits beside the PM's own view and what would change their mind.
  • Conversation partner. Raises the few issues worth discussing and ends each one with a plan in the PM's words.
  • Research agent. Desk research on the riskiest assumptions, starting from "what if this is false", with a hard cap.
  • Meeting module. Preps a meeting from a plan, then reviews the transcript and feeds the store.
  • Save sweep. One command saves the session; background agents then update the shared state.
V1 · open source · May 2026

A context layer in your repo

  • Skills loaded on demand. Each workflow is a Claude Code skill, so the agent only loads what the task needs.
  • Current-state synthesis. Meetings, PRDs, chats and notes become one current picture per project: position, decisions, people, open questions.
  • Agent memory in files. Sessions are saved as plain files in the repo, so the next session starts where the last one stopped.
  • Staleness flags. Context that hasn't been checked against a source for a while is marked, not trusted.
  • Sub-agent fan-out. Long synthesis splits across sub-agents and reconverges.
  • Eval harness. Answers scored against a known answer set.
What this shows

The skills behind it.

Context engineeringGetting the right company knowledge, current and sourced, to people and their AI tools.
Agent memory and retrievalFile-based memory, synthesis and retrieval over meetings, docs and chats.
Multi-agent orchestrationSub-agent fan-out, background agents and scheduled runs.
EvalsPass bars set before testing, known answer sets, and results reported as they came out.
Claude Code and CodexSkills, sub-agents, hooks and MCP, built hands-on every day.
Product practiceDiscovery, decision records and stakeholder work, built into the tool rather than added on.

Talks: Behind the Build (Happy Operators), AI Build Club.

V2 is in build.

The next milestone is a short video of the workflow end to end, then the V2 code. Want to hear when it's ready, or try it with your team?

Get early access

Want to try something today? The open-source V1 is on GitHub.