Superintelligence Company Operating Model: A Weekly to Yearly Cadence

A superintelligence company operating model is a recurring cadence that separates what a company owns (memory, process, tools, permissions, tests) from the model that happens to power it. Each model upgrade then improves the work instead of forcing a rebuild. In practice it is four rhythms: a weekly review of real work, a monthly maintenance pass, a quarterly re-evaluation with a permission review, and a yearly decision about what to hand over next.

Key takeaways

• The model is the part you rent and replace. Memory, process notes, tools, tests and permissions are the part you own and compound.
• Weekly routines catch drift in real work, monthly routines keep memory and integrations clean, quarterly routines test new models and review access, and yearly routines decide scope.
• Every routine needs a named human owner and one artifact it leaves behind. Without both, it becomes a meeting with no effect.
• A model upgrade should be a scheduled experiment against your own test cases, not a switch flipped because a new version exists.
• Start with one agent role and one success criterion, then add rhythm as the role earns trust.

What does a superintelligence company operating model consist of?

Models improve on a timetable set by someone else. A company cannot control when a better one arrives, but it can control whether the improvement lands somewhere prepared. The operating model starts by separating what you rent from what you own.

The model is rented and replaceable. Everything around it is owned and compounds:

• Role definition: what the agent is for, what it never does, and who it answers to.
• Memory: facts, decisions, house style and customer context, each with a source.
• Tools: what the agent can reach, and how each tool is described to it.
• Permissions and approval boundaries: what it may do alone and what needs a person.
• An evaluation set: real tasks with known good outcomes, used to compare setups.
• Process notes: how the work is actually done, by people and by the agent.
• Logs: what happened, when, and with what result.

A stronger model reading clean memory, clear tool descriptions and a good test set produces better work almost immediately. The same model reading contradictory memory and vague tools produces more fluent mistakes. That is the whole argument for a rhythm: an upgrade is only as valuable as the assets it inherits. The structure behind these assets is covered in Build a Company Superintelligence Layer That Improves With Models. This article is about the routines that keep that structure healthy.

What should happen every week?

The weekly rhythm is about work, not technology. Its owner is the person who runs the process the agent supports, not the IT team. It should be short enough to survive a busy week and leave behind a one-page note.

• Read a sample of completed tasks, including good ones, and mark each as accepted, corrected or rejected.
• Read every escalation and every task the agent declined, and decide whether the refusal was right.
• Record each human correction in one place, with the reason in a sentence.
• Look at the approval queue for items that waited long enough to slow the work.
• Note any situation the agent met for the first time.
• Choose a few small changes and send them through your change request process.

Sampling good work matters because drift often hides there: an answer that is acceptable but slightly off in tone, or a correct result reached by an odd route. Corrections are the raw material for everything that follows. A correction that is never written down gets repeated. One that is written down with its reason can become a memory entry or a test case.

What belongs in the monthly maintenance pass?

Monthly work is housekeeping, and it is where compounding happens. The owner is a named steward of the agent, often someone in operations with technical support behind them.

• Promote repeated corrections from the weekly notes into memory or process notes, and add each one as a test case.
• Remove or date-stamp memory entries that are stale, duplicated or in conflict.
• Check every integration: credentials still valid, failed calls, and retried actions that may have run twice.
• Reread tool descriptions. If the agent keeps misusing a tool, rewrite the description before blaming the model.
• Compare cost per completed task and time saved against the success criterion you set at the start.
• Confirm that memory and configuration can be restored from backup, as described in AI Agent Backup and Restore.

Memory deserves particular care. Anything the agent retrieves is something it may act on, so an outdated refund rule left in memory is an instruction waiting to be followed. Keep each entry short, sourced and owned by a person who can say whether it is still true.

What does the quarterly review add?

The quarter is when you look up from the work and test the foundations. Three things happen: you evaluate newer models against your own tasks, you review permissions, and you remove scaffolding that is no longer needed. The owner is the executive sponsor, with the steward presenting evidence.

A plan that works for the model evaluation and review:

• Freeze the evaluation set and run the current setup to record a baseline.
• Run the candidate model on the same tasks with the same memory and tools, changing one variable at a time.
• Read the failures by hand. A score tells you where to look, not what happened.
• Check behavior at the edges: does the candidate act more boldly near an approval boundary?
• Decide one of three outcomes: adopt, adopt for some tasks only, or wait. Write down the rollback path.
• Run the access review using the steps in Quarterly AI Agent Permission Review.
• Retire instructions that were written to compensate for weaknesses of the old model.

The last step is the one most teams skip. Rigid formats, repeated warnings and long step-by-step instructions were often added to steer a weaker model. With a stronger one they can become a ceiling. Simpler instructions, tested against the same evaluation set, often do better, and the test tells you which case you are in.

What does the yearly cycle decide?

The yearly cycle is about scope and direction. The question is no longer whether the agent is working, but what it should be given next and what should be taken away. Use this as a decision guide:

• If the role is stable, accepted and measured, widen it by one adjacent task rather than adding a second role.
• If volume has grown but corrections have not fallen, narrow the role or fix the process underneath it before adding more.
• If people have stopped reading the outputs, deal with adoption first, because a larger scope will only hide more errors.
• If a provider changed its terms, data location or tooling, confirm that memory and configuration can be exported and that the setup can run on another model.
• If a new capability appeared that the role could use, run it as a separate experiment with its own success criterion.
• If a task has not been touched for months, retire it.

Use the same cycle to rehearse a restore, read the incident log from start to finish, and update your governance basics. Frameworks such as the NIST AI Risk Management Framework offer a shared vocabulary for that review. The real test is whether your own records show who decided what, and why.

How does a model upgrade move through the rhythm? An illustrative scenario

This is an illustrative scenario, not a client result. A distribution company has an agent that drafts replies to supplier delay notices and proposes order changes for a planner to approve.

Over several weeks, the weekly notes show corrections clustering around two suppliers who phrase delays ambiguously. At the monthly pass, the steward writes those patterns into memory and adds a handful of real past emails to the evaluation set. A new model then becomes available. Nobody switches to it. At the quarterly review, the team runs it against the frozen set with the same memory and tools.

The candidate reads ambiguous notices better. It also proposes order changes more assertively, and in a few cases the proposals sit closer to the approval boundary than the sponsor wants. The decision is to adopt the new model for drafting replies, keep order proposals on the previous model for another round, and delete two old instructions that forced a rigid reply format. The sponsor records the evidence and the rollback path in one page.

The upgrade helped because the company had a baseline, a test set and a record of corrections. Without them, the same change would have been a guess.

Who owns the rhythm, and how does Be Human run it?

Assign each cadence to a person by name. The process owner holds the weekly review, the agent steward holds the monthly pass, and the executive sponsor holds the quarterly and yearly decisions. The common failures are predictable: skipping the weekly review because nothing seems wrong, holding meetings that produce no artifact, upgrading by default, and treating the whole thing as an IT project instead of an operating responsibility.

Be Human designs, implements and operates this cadence as part of managed operations. That can include monitoring, recurring evaluations, integration maintenance, permission review, incident response and controlled improvements, while the agent's identity, memory, tools and approval boundaries stay under the client's control. A first engagement defines one useful role, the memory and tools it needs, its approval boundaries and an observable success criterion, and the rhythm starts small around that role.

If you want to find the first task worth handing to an agent, take the free Be Human AI diagnostic.

Frequently asked questions

How much time does this rhythm take? The weekly review is short and sits inside work the process owner already does. The monthly and quarterly passes take longer but are scheduled and bounded. The effort grows mainly when routines are skipped and problems pile up.

Do we have to adopt every new model? No. A new model is a candidate, and the quarterly evaluation decides whether to adopt it, use it for some tasks or wait. Keeping a rollback path means you can say no without losing ground.

Who should own this if we have no AI team? Give the weekly review to the person who runs the process, name a steward for the monthly pass, and ask an executive sponsor to own the quarterly and yearly decisions. Technical upkeep such as integrations and evaluations can come from an outside partner, as long as the records stay with you.

What if the agent is still a pilot? Start with the weekly review and a light monthly pass, and keep the evaluation set from the first day. The quarterly and yearly routines become useful once the pilot has a stable role and a success criterion to measure against.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.