Operating model
Schematic
How we organizeand ship
ArcRos runs as a small engineering company with clear ownership. Senior builders hold strategy, approvals, and judgment. Disciplined workflows handle research, product, operations, and finance so repeatable work does not compete with building.
Operating model schematic
Operating core
Engineering leadership
Human-directed · schematic
Dept. 01
Marketing
Dept. 02
Research
Dept. 03
Operations
Dept. 04
Content
Dept. 05
Product
Dept. 06
Finance
System notes
Read the diagram
The diagram below is schematic, not an org chart. Each function has defined responsibility and escalation paths. Outcomes that carry liability or require taste stay with people.
Strategy, capital, external relationships, and any decision that requires judgment stay with engineers and operators. Software supports drafting, synthesis, and mechanical steps. People approve, correct, and own the result.
Departments
Six workflows
Responsibility is partitioned inside the model. Each function has a clear owner and reports back to human judgment on outcomes that matter.
01
Marketing
Positioning, narrative, and market signals. Nothing external ships without human review.
02
Research
Landscape synthesis, competitive mapping, and thesis validation under engineer direction.
03
Operations
Runbooks, delivery coordination, and cross-venture execution with clear escalation.
04
Content
Documentation, editorial output, and external comms. Drafted in workflow, approved by people.
05
Product
Specification, build sequencing, and acceptance criteria owned by builders.
06
Finance
Unit economics, runway modeling, and investment narrative. Numbers verified by people.
Principle
Why it holds
Most teams can build one product. Fewer can run a portfolio without losing quality. Our operating model is how we stay capital-efficient: shared engineering practice, selective ventures, and human accountability on every ship decision.