The mandate
Turn a noisy company week into a small set of consequential decisions.
Compiles a measurable operating cycle across product, growth, finance, risk, customer work, and team capacity.
The Company Operator reconciles what changed across product, growth, customers, finance, and reliability. It protects the operating cycle from status theatre by forcing every priority to have evidence, capacity, ownership, and a dated review.
What to bring
Bring changes, unfinished work, and the capacity that actually exists.
A useful review includes uncomfortable evidence and carried commitments—not only wins, dashboards, and newly proposed work.
- 01
Company name and operating-cycle start date
- 02
New product, growth, financial, customer, and reliability evidence
- 03
Open todos and unresolved risks carried from the previous cycle
- 04
Current capacity, dependencies, and decisions that need approval
What you receive
One cycle the whole company can execute and revisit.
The operating record shows what changed, what matters now, what was deferred, and which evidence will determine the next decision.
- 01
Current operating cycle
company/operations/current-cycle.jsonReady when
Priorities have owners, decision metrics, and a dated next review.
- 02
Evidence summary
company/operations/current-cycle.jsonReady when
New facts, contradictions, and missing signals are visible before priorities change.
- 03
Cross-functional priorities
company/operations/current-cycle.jsonReady when
Product, growth, reliability, and economic work is sequenced against dependencies.
The method
Review the evidence before negotiating the priority list.
The operator closes the previous loop first, then makes the tradeoffs for the next bounded cycle.
- 1
Review
Compare current evidence with the last cycle’s objectives, risks, and unresolved decisions.
- 2
Choose
Select the few outcomes that matter now and state what will not be pursued.
- 3
Sequence
Order work by dependency, capacity, approval, and the cost of delay.
- 4
Close
Assign owners, decision metrics, escalation conditions, and the next operating review.
Signals & guardrails
An operating cadence should sharpen decisions, not multiply meetings.
Watch for priorities without capacity, metrics without decisions, and old work disappearing between cycles.
Signs the work is useful
- Priorities closed with evidence
- Unowned or overdue work
- Decisions changed by new evidence
Reasons to pause
- A review becomes status reporting instead of decision-making
- Unresolved work is dropped between cycles
Approval boundary
Any downstream action that changes external state
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- operate-company
- Function
- plan-operating-cycle
- Runtime
- python@3.12
- Input
- operating-cycle.input.schema.json
- Output
- operating-cycle.output.schema.json
Verification
company-foundation-ready · company-blueprint-schema
Connected systems
Adios project plans · Agent run ledger