You have the tools. You don't have the operating layer.
An audit of how your existing tools, processes, documentation, and decision rights actually function as an operating system — and what to repair before adding anything new, including AI.
- Deliverable
- OS audit + recommendations
- Timeline
- 2 weeks
- Audience
- Both
- Cadence
- 3 working sessions
Five layers. Every organization has all of them. Most have none of them working together.
Tools & integrations
What tools are in use, what they are supposed to do, and whether they are actually doing it — or creating a second system of record alongside the first.
Process documentation
What is written down, what is assumed, and where the gap between written process and actual process is widest.
Decision rights
Who is actually authorized to decide what — versus who decisions route through by default, by habit, or because no one else has been told they can.
Handoff protocols
How work moves between people, roles, and systems — and where work disappears, gets duplicated, or stalls waiting on a handoff that was never defined.
Evidence and record systems
What the operation produces as a record of what was done and decided — and whether that record would survive an audit, a transition, or a re-compete.
The gaps between what the tools say should happen and what actually happens.
The OS audit does not evaluate whether you have the right tools. It evaluates whether the tools you have are functioning as a coherent operating system — with consistent logic, shared records, clear ownership, and reliable handoffs.
Most organizations have accumulated tools over time without designing the layer that connects them. The audit surfaces exactly where that connection is missing — and what it is costing the operation every day it stays that way.
The report is structured as a gap inventory: each finding named, located, and ranked by operational impact. Not a vendor recommendation. Not a software evaluation. An honest account of what the operation's current setup can and cannot support.
A prioritized repair list. In writing.
The specific process gaps, documentation failures, and decision-rights ambiguities that AI will expose — or accelerate — if they are not addressed first. Named, sequenced, with owners attached.
The workflows that are person-dependent rather than system-dependent — and what it takes to make them transferable before the organization adds headcount, contracts, or scope.
The knowledge, processes, and decision logic that exist in people's heads and nowhere else — prioritized by succession risk, audit exposure, and how quickly they would be missed.
Audit the operating layer before you add anything new.
Two weeks. Three working sessions. A prioritized repair list you can act on the same week you receive it.