TUR

AI-Native Venture Studio Operating System

Pillar page | Part of Insights

Most venture studios describe their stack as Notion + Slack + a CRM. That works for coordination — it does not compound learning. TUR Company OS is the operating system behind The Unnamed Roads: a decision-first control plane where portfolio state, approval policy and organizational memory stay canonical.

The problem with dashboard-first studios

Traditional studio ops optimize for visibility: boards, backlogs, status colors. AI-native studio ops optimize for decisions that compound:

  1. Signal — growth evidence, inbox, market change
  2. Decision — what we will try, and why now
  3. Expected outcome — falsifiable before work starts
  4. Work unit — bounded execution with traceability
  5. Actual outcome — measured against expectation
  6. Human correction — what we got wrong
  7. Reviewed lesson — durable memory, not chat noise

Agents belong inside steps 4–5 once the workflow is stable enough to evaluate — not as always-on employees approving their own sends.

Three planes

PlaneRole
ControlGovernance, policies, approvals, portfolio hierarchy
ExecutionHumans, agents and workflows behind adapters
KnowledgeEvents, decisions and lessons in Postgres — not duplicated in SaaS

Company OS owns state, policy, audit and memory. Providers (Linear, Vercel, Supabase, model routers) stay replaceable.

Focus · Monitor · Parked

Attention is the scarcest resource in a multi-venture studio. Full policy: Focus · Monitor · Parked.

  • Focus — at most three bets with active validation contracts and growth ranking
  • Monitor — live ventures visible to the market but outside daily growth ranking
  • Parked — archived or dormant; no false “Active” signals

Today’s Focus bets: The Hockey Analytics, Field Notes distribution here, and Föräldraledighetsplaneraren.

Comparing models? Start here: Agency vs venture studio vs incubator.

Approval levels (sketch)

LevelPolicy
0Read only — automatic
1Reversible internal write — automatic within budget
2External low-risk — standing policies
3Consequential external — explicit mobile approval
4Prohibited autonomous — human-only

Publish, cold outreach and production deploy sit at Level 3 or 4. Drafts, research and internal commits can be Level 1–2 under MethodPolicy spend gates.

What this looks like in practice

Morning: PostHog Focus funnels and inbox signals surface at most three mobile decisions.

Midday: Each Focus project keeps one active validation contract — one claim surface, one redistribution asset.

Afternoon: Marketing and development drafts run free-first models under spend gates; deterministic policy still owns approvals.

Evening: Approved drafts can commit, deploy and IndexNow after policy. Outcomes return to growth memory.

See the live pipeline on the homepage operating-system section.


The Unnamed Roads is an AI-native venture studio where TUR Company OS coordinates decisions, approvals and execution loops. Agents accelerate proven workflows; humans keep governance at critical boundaries.