Operating model
How we 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.
Structure
This is not an org chart. It is how responsibility is split so a small team can run several ventures without losing quality.
01
Strategy, capital, external relationships, and any decision that carries liability stay with engineers and operators. Software handles drafting, synthesis, and mechanical steps. People approve, correct, and own the result.
02
Marketing, research, operations, content, product, and finance each have defined responsibility and escalation paths. Repeatable work runs in workflow. Outcomes that matter get a named human owner.
03
Engineering patterns, data models, and delivery playbooks travel across the portfolio. A new vertical inherits months of build experience instead of starting from zero.
Departments
Responsibility is partitioned inside the model. Each function has a clear owner and reports back to human judgment on outcomes that matter.
01
Positioning, narrative, and market signals. Nothing external ships without human review.
02
Landscape synthesis, competitive mapping, and thesis validation under engineer direction.
03
Runbooks, delivery coordination, and cross-venture execution with clear escalation.
04
Documentation, editorial output, and external comms. Drafted in workflow, approved by people.
05
Specification, build sequencing, and acceptance criteria owned by builders.
06
Unit economics, runway modeling, and investment narrative. Numbers verified by people.
Principle
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.